Am I missing something? This thread seems to be a rolling jamboree of replies that can be summarised to "I don't think it's toxic therefore I demand that I be able to do it because my view is logical" (without any actual logical argument) in response to every suggestion that the existing position is both more nuanced and more sensible than described.
It's hard to see why the people who don't have a problem with the existing policy -- relating to literally ONE player behaviour in specific circumstances -- are the "oversensitive" ones here?
Well, I once got reported for rolling and hitting the CTRL key once for "t-bagging" even though it was in Vengeance and the only way to reveal NBs at the time was to enter stealth and search like that. The person got irate and said I t-bagged them because their body happened to be there.
Yeah, someone is t-babbing when 3 NBs are attacking them in Vengeance? Person instablocked me and said they would report me. But I did not have action taken against me.
But it shows how subjective it can be to determine what is and is not t-bagging which is why the rule is a bad one. Any rule subject to interpretation many ways will always be a problem.
When hitting CTRL is a valid part of combat to enter stealth, you cannot even argue hitting it more than once is always t-bagging because sometimes the game does not register input (esp. this current patch with the client lagging and freezing once things starts heating up in Cyro).
So then we have to consider what' plausible and what's intentional, and at that point what good is a rule when it's not applied equally in the first place and subject to abuse or a situation can be misinterpreted?
It's similar to the dumb rule about stream sniping. I got warned before for firing siege defending a keep for stream sniping. If an AD scroll is at KC, guess where I am going to be to fire siege? I don't need to watch a stream to know AD will be coming, esp. when they always do after getting Sej/Drake. In fact, they should be expecting me and slotting siege. And siege shields. They really are allergic to that for some reason.
Rules like this do not actually add anything to the player experience. I don't really care if someone t-bags me in the game...and you know what? No one really has. Though they have placed a bunch of oils around my dead body and fired siege at it. I still don't get it to be honest.
frogthroat wrote: »Am I missing something? This thread seems to be a rolling jamboree of replies that can be summarised to "I don't think it's toxic therefore I demand that I be able to do it because my view is logical" (without any actual logical argument) in response to every suggestion that the existing position is both more nuanced and more sensible than described.
It's hard to see why the people who don't have a problem with the existing policy -- relating to literally ONE player behaviour in specific circumstances -- are the "oversensitive" ones here?
It would help if people (like me) who don't think it's an issue would be told why it is such an issue to others. I genuinely don't understand why it upsets people.