Thread: Is anyone else really disappointed with the nerfs coming in 2.2?

Originally Posted by Gormogon

It's not an illusion. Those choices are there. The fact that you aren't doing them are obvious though. Which is hilarious since now you're arguing that "others" are what prevent "you" when you were talking about "others" and not "you" previously to this statement.

Which means ApolloGenX was right in his observations.

That's funny because you can exercise said choice but you only get to choose the outcome of one said choice. This conversation isn't going anywhere because you only want it your way not because there's a discussion to be had.

Sorry, but it is an illusion. Making the choice to do the content unnerfed, but not being able to do said content because of that "choice" due to others making a different choice is not really a choice at all. So sure, you can make said choice, but it doesn't get you anywhere, which is why it's an illusion. Also, if you've read my posts, I see it both ways, I personally am indifferent to the change since I see the pros and cons to both. I also knew ahead of time this would be done.

Originally Posted by DragonFist

lmao not being allowed to choose between using a buff or not yeah because its totally locked onto your buff bar active and you totally are not allowed to seek players who also dont want the buff for content

explain to every1 how you wont get to exercise that choice because you kinda can and thats by making your own party instead of joining others

No, it's about choosing to do the content unnerfed. Just because random Joe A chooses he wants to do it unnerfed, doesn't mean he CAN. He has to find 7 other people who are also willing, which may not be possible depending on server and timezone. It's not so simple a choice, it only comes down to simple choice if the content is solo, like Story quest instances for example.

So tell me, how is he to do the content with no nerfs, if everyone else doesn't want to? It's like now, try to find a T2 group that DOESN'T abuse enrage, it happens sometimes if you find a static that's missing a member, but even now many statics do it as well.