We tried this, deleted quests, cleared zone etc etc. Tried 4 times with no luck. Can we please get some sort of explanation on why this works for some and not others and apparently not working for some who have already did and KNOW what they're doing. Then we get a lock out timer for 18 hours even though we don't kill the final boss? Not right.
I tried this instance with some guildies last night and we could not get the ring event down. We did not have a mezzer so I think without a mezzer this is very hard. We tried rooting the Stewards but the roots would eventually break before all stewards were up and all hell would break loose Besides, any help on strategies without a mezzer I have on additional question. Once all stewards are up do you need to kill them all at teh same time or just kill them all before anything else repops?
Please let me know if you guys are still seeing this issue after todays update. I think I found what was causing the event not to complete, and it should no longer happen (That is to say I wasn't able to make it happen after changing some things around), so let me know if you are still having issues.
Just had the event not complete today, so either the fix didn't go live or it didn't completely fix it...
I'll take a look at it again. Anything else you can tell me to help me try and dupicate it? How many placeholders did you kill before you got 4 Stewards?
We killed a fair number of placeholders for a while, then got 3 stewards to pop, killed about 3 more ph's waiting for the 4th steward, and killed them all in about 15 seconds. Nothing, so we let them repop, got 3 stewards immediately, and killed about 2 ph's waiting for the 4th. Again, all died in under 10 seconds, no named.
I can also verify that this event is broken. We tried it 5 times a few days ago ....we actually killed all four within 2 seconds of each other once ..lol. Then, we thought that perhaps if they died too close to each otehr that perhaps it wouldn't "register" so we slowed down and killed them within like 6 seconds. Either way, I've actually completed the event before (a few weeks ago) ..so I KNOW we're doing it correctly. Someone was thinking perhaps it might have to do with the fact that someone in the group might have a particular quest active that was interfering with it ...but honestly I have no idea. Either way it IS broken for my group
ooops..ignore me...I missed the posting where he/she said it should be fixed after today's update. I'll have to try it again
As many of the posters here can varify the main difficulty in this zone is trying to figure out how to avoid the bug with the zone boss not spawning after the ring event. We have done this zone countless of times and there seems to be two things that makes the zone boss not spawning. The first issue has been stated above at it is when people in the group are on different parts of the "By Land? By Air? By Sea?" questline. And the other issue seems to be when using pets. If you are all on the same step of that questline (also if no one has even started the quest) and you are not using any pets everything seems to work just fine.
This script is soooo bugged. No named 9 days in a row now. I don't know what the issue is about but please fix it. I don't think it's so hard to make the named 100% spawn to progress the access quest..
We just tried this again today, killed all 4 stewards within 5 seconds and nothing. Are you saying using pets is bugging it too?
I know Conj.pets are not an issue at all. I always have kept my pets up. And have had successful events.
I can verify it is not or was not related to being on different steps of that quest. We had some members who did not have it, some who had it but did no steps and some who were on last step. I checked journals to see. And again the named appeared as they should have.
tried this today on the german valor server with no luck. we tried different strategies as described by the previous posters but none worked.
This should have been fixed this weekend, however I'm not sure if the German servers would have gotten the same update. If anyone on a US server ran into an issue with this yesterday please let me know and I'll PM you for details.
