How do we cater to grizzly?
It’s not like we invited them here with open arms. They transferred. Nobody asked them to come they just did.
The alliance hate them just as much as the horde if not more. Nobody makes special arrangements for grizzly.
1 Like
well said, but blizzard doesn’t care.
If the horde kept alliance from getting a scarab lord, isn’t that just PvP on a PvP server?
Is this sarcasm or stupidity?
Thank you for the intriguing insight on the situation. It’s kind of fascinating to read about, if I’m being honest. Balanced perspective.
2 Likes
it might be ignorance as to what actually occurred, but what’s to stop one faction from preventing another faction from banging the gong?
Would be fine if the method used to prevent getting scarab lord was killing the alliance players over and over again. Once the method becomes “keep the npc in combat” is where it turns into a grey area bordering on griefing/zone disruption imo.
With this method you could have alliance stopping alliance or horde stopping horde from completing the quest and at that point there is no pvp solution.
A great point that I hadn’t even thought of until you brought it up.
You are all collateral damage.
It’s good to see Grizzly get a nice big dose of karma.
2 Likes
The best part of this is they’ve tossed out all credibility for the length of Classic. They were actually starting to warm up a bit lately. That’s all out the window, and every soul on Sulfuras is going to hang them out to dry any chance they get. I know there’s more than a few Ally guilds with multiple horde priests that would love the chance to dispel camp the bstrds.
sounds like pvp should have happened, but didn’t. Why not?
Lag. Literally lag.
Apparently, too many people showed up to PvP, and the servers couldn’t take it.
I feel bad for these people. If they have a scepter in their bag, it should be GM-instated for the BQRC.
Actually that wasn’t griefing… could have been dealt with by alliance killing them all. Pvp solution. The alliance started it all by doing something that could not be dealt with by pvp. The Horde retaliated but kept it open to be dealt with by pvp.
Server lag prevented any sort of pvp solution.
Might you have another suggestion?
Blizzard specifically hot fixed that NPC to flag someone for PvP if they attack him on the July 29th, 2020 - which I believe is unique to only him throughout the entirety of the game. EDIT: Actually I’m wrong, it’s unique to all of the Scarab Lord questline neutral NPCs.
They anticipated this and even gave a PvP solution on PvE servers, it seems.
Definitely easy to say “you should have seen this coming” - but it definitely should have been something people took into consideration when doing their Scarab Lord grind. The servers are horrible, BRM on a raid reset during a content drop, can’t do Capital City raids which should be a staple on a PvP server, etc.
Why didn’t horde reach out to these guys and warn them they were going to push it down Grizzly’s throat if they showed up before the War Effort had completed?
I’m more curious about how the actual Scarab Lord candidates who lost out on t his feel about it, do they want Blizzard to get directly involved in changing how their experience has played out? Seems like a lot of people being upset for them.
1 Like
Did they also not get enough people to use PvP methods to push them out or was it again the horrendous servers for classic? Because you are again describing PvP on a PvP server.
1 Like
They didn’t have the numbers to overwhelm the horde in lagfest PvP like that - generally how it’s done is you send in raid after raid spamming AoE until the opposing faction are OOM and just forced to die no matter who’s getting the first global to register.
There was one strong attempt made to res on top of them and DI Ahmp after someone managed to leash the NPC but it failed.
clips.twitch dot tv/AmericanVenomousStarlingWoofer
Praise the horde. You all did good.
3 Likes