(edited by blackoil.2673)
Unfairness
its one achieve, its not that big a deal, it wont prevent you getting 15/15, because of LS dailies.
(I dont have it btw…missed the easy chance)
I agree that this:
“To encourage players to split up, the boon from the associated Attunement Pool will now be required in order to damage each Assault Knight, and only 50 players can have the attunement for each color simultaneously.”
is absolutely the wrong way to go about fixing the issue. I wouldn’t even call it an ok work around. This leads to issues in and of itself. Not only that, but it sets a precedent for hard limiting other bosses in the game in order to ‘encourage players to split up.’ I find this concerning.
It won’t prevent you from completing the meta. I think it’s a great change. I hope they continue to nerf the hurr durr 111111 zergblobs in all other aspects of the game as well. Keep cutting out the cancer A-net!
Salvage 4 Profit + MF Guide – http://tinyurl.com/l8ff6pa
Hard capping is not the way to do it either. 50 people is still a zerg. It does nothing to stop 11111 spamming. It does nothing to improve the fight in and of itself. All it does is push people back out into the same ol’ stuff they were doing before. Leaving the new content emptier. That’s all that was achieved here. Pushing the ‘zerg blobs’ back out into QD, FS, and Cal. Where people continue to be bored, kitten that there is nothing ‘new’ in the line of content, and then simply opt to stop playing. Good job.
Tbh,.. alot of people are happy to split, it’s not exactly hard to pick a Knight rather than everyone zerging the one.
You call it unfairness, which I can understand.
But seriously this change was needed for the good!
A zergfest ruins even more than just this small change for your personal archivement.
I don’t have that archivement either, and I guess I won’t get it with this update. But I can live with that, because now you can enjoy the update how it was probably intented.
I fully agree, that this should have happened from the beginning, but it happened now so we have to deal with it. I’m more happy than mad about this hotfix.