My first hand account to the events leading up to this event.https:// www .reddit .com/r/ classicwow/comments/i4ftk6/i_was_mad_and_i_would_do_it_again_100_of_the_time/
It's funny I don't even play classic, I play horde retail but after watching like 25 mins of snubs previous broadcast I felt awful for him. In no way, shape or form was this a matter of "pvp on pvp server", the fact that the npc could be locked into combat while the server was locked in horrendous lag negates that argument. I get the frustration from horde players, due to Grizzlys server toxicity but this was completely childish as well. Snub was chill af and clearly a dude that just loved old school wow and he got griefed massively.I sure hope blizzard does something, this issue started with their report system, they have equal blame as well. Do right by snub, blizzard!
So many people from pve servers here, or retail-only players who have gotten used to just shutting off warmode when convenient. This is what pvp servers are all about. Massive coordination (from both factions here, too!) is a great sign of health for a pvp server. When you make a character on one, this is what you're signing up for. You wanted a fight.Organizing a massive in-game siege of an NPC as a demonstration of solidarity is one thing; mass-reporting a player to ruin their hard-fought and fairly-won victory deserves a perma-ban, not some three day suspension. Grizzly members are going to come back from this short break and still be some of the most successful players on their server. And while every server has its inter and intra-faction politics, it really seems like Sulfuras-Alliance needs to sanction the Grizzly guild and its members if Blizzard is not going to ban them. Classic has the odd but suddenly welcome distinction of not having character-changing services like race, name, or faction changes. Grizzly players can not escape their reputation except by server transferring now or starting over with new personas.Granted I think Blizzard carries the highest responsibility to make this right, considering it was they who implemented automated account-suspension features that could be effortlessly exploited by Grizzly to do so much harm. Maybe they can think up a solution for addressing the harm done to the potential alliance scarab lords who lost their opportunities because of the retaliation.