Quote Thanks for the update and letting us know what will happen! Nevetheless, I have to criticize how this issue was handled. It took you 1 hour to acknowledge the problem, then another 6 hours to tell us how you are going to fix it. This may be fine for US players who missed most of this since they were at work but in the EU, this happened at primetime.



Players were unsure whether to go ahead and kill the Xeno raid boss since it counts for this week's conquest and they'd get a weekly lockout. This created a lot of confusion and had some guilds cancel or adjust their scheduled raid, purely because of the lack of information. Deciding on how to tackle this bug does not take 6 hours, it would have been nice to have gotten an update on the issue before noon Austin time (which is appr. the time when most EU raids start).



Of all the possible solutions to this, running the conquest again next week seems to be the best compromise but it is certainly nothing worth cheering for. Clearly, this type of bug can only happen with an understaffed/underbudgeted development team and continually seeing bugs like this after each patch without seeing light at the end of the tunnel is frustrating players in the long term and only strengthens the "this game will shut down" posts because there is no evidence to point to that shows otherwise. Scoundrel healer. Raid leader. Guild officer @ Tulak Hord