Hover your mouse over my character and see that I’m on a different realm and really don’t care what happens on Sulfuras. Hey, if I’m wrong about everything, cool?
But the unintended consequence becomes the issue whenever it comes to Zone Disruption.
We weren’t disrupting the zone…we were trying to wPvP…
Do you not get that haha?
2 Likes
I get it. 500 People trying to wPvP not expecting the zone to lag out at all, knowing exactly how zone pvp has worked when BWL has been live since February.
No, I got it entirely.
But it’s okay for the factions to raid each others cities and lag them out?
How is that not any different?
Dude you really don’t want to die on this hill hahaha
2 Likes
Not an offense though. People went to an area where world pvp was going on during the scarab event, where many log in for that very thing. The players aren’t at fault if blizzard’s servers lag either. World PvP can always cause some form of Zone Disruption but is still perfectly allowable. This will never change.
So you’re saying you’re aware that a mass of people in one zone lags it out and makes things nigh impossible to do anything?
Got it.
Of course—but I’m not going to avoid a zone just because it might be laggy hahaha…what you want me to just turn around and go back to Org?
How would you expect any large-scale event to occur if we all just avoided it cuz lag?
5 Likes
Thanks for proving my point.
I don’t think that proved anything haha…our intent was STILL to PvP…just because we are aware of something doesn’t mean we are actively engaging in it.
Just because I’m aware that lag may happen in crowded zones doesn’t mean I’m going to rollover and give the zone up because of that. Shouldn’t it be on Blizzard to improve their servers?
I’ll be honest it looks like Ayresaelian is just going to keep digging himself in a deeper and deeper hole. I’m wondering when TBC hits if he will be trying to get blizzard to suspend everyone who goes to Hellfire Penninsula all at once, due to the server lag it will create.
2 Likes
Yeah or maybe they will suspend everyone trying to go into AQ all at once…they are, after all, disrupting the zone. They are aware that a large population load in a single zone can create lag, right?
Durrrrrrr
Snucka I saw you out in Silithus all last week.
I’m not saying you weren’t there to pvp. I’m not calling for any action to be taken against the horde that we’re present.
I’m simply here pleading a case for the other three alliance guilds who were denied mounts.
We spent the entire last week together in Silithus fighting horde and farming bugs.
Though my guild was one of the lucky ones to finish early before all this took place our achievement is bittersweet.
Knowing people that fought side by side with us all week had their hard work stripped from them at the last minute leaves a foul taste in your mouth to say the least.
3 Likes
Bruh I had to chase you down so many times jesus you slippery little gnome. Cheers!
I DO feel bad for the other Alliance—I have admitted that. I totally was hoping they would get their mounts—but Grizzly rode their tails to the NPC’s when we were trying to let them through…Grizzly could’ve stepped back and just accepted defeat and let the others through. But anyone who knows Grizzly knows that won’t happen.
5 Likes
Because the two are entirely the same thing, right? One is going into new content so we can all level up, the other is that a faction intentionally griefed an NPC quest giver to stick it to one guild, and in so doing, lagged out the zone causing the other faction to not be able to fight back. Now did that one guild deserve it? Yes.
You and Snucka are just trying to rationalize what the horde did, and that’s okay, if I was guilty of griefing and disrupting a zone, I would to.
1 Like
It’s zone disruption.
Not even a discussion.
Horde were literally holding the turn in NPC (for hours) so that Alliance couldn’t turn in.
The specific intent was to prohibit Alliance (ie. Grizzly) from turning in.
That goes beyond PVP, because the intent isn’t just to engage in PVP with Grizzly or Alliance in general; it’s to disrupt that zone by tagging an NPC and keeping it in combat.
This was something that was easily anticipated.
If Horde had wiped Alliance or Grizzly or other Alliance on other parts of the chain…it might have been different.
The intent here couldn’t have been more clear.
Many people will be watching to see how Blizzard does or doesn’t address this.
I certainly have empathy for the other Alliance guilds that got screwed…but the bigger issues here are the scope of toxicity that’s been allowed to foment with inaction from Blizzard leading up to the event, and the precedent this type of behavior sets for the entire community going forward.
4 Likes
You seem to equate world pvp with griefing - not the same thing. And on the day the gates open, it’s arguably one of the highest world pvp days ever for the servers. The horde controlled the NPC so that Grizzly would have to put up a fight. They did but it was not enough. Not even a matter of who deserved what.
Let me tell you a story, one day I went around trying to find arcane crystals, after a long while of searching, I found one but got ganked while trying to mine it. I didn’t put in a ticket to the GM’s talking about how I deserve this or that lol. The guy that ganked me did it intentionally, but it wasn’t griefing.
Same thing here, Grizzly world pvp’s all of the time, when you do it, you can expect some back your way. They got it at a bad time for them. Our intentions were to get honor points and have fun, and we did.
3 Likes
What you said has already been debunked a lot though. Grizzly could’ve killed the horde and turned in the quest. That’s a part of world pvp. There’s times where you may want a certain mineral node, or want to get into a dungeon with certain buffs, but get killed. That’s not griefing or zone disruption. More than anything it’s really just an issue of rolling on a PVP server but not wanting to do it when it’s inconvenient.
Was there a PvP solution?
I would have tried to kill them and then talked to the NPC…amiright?
It’s this really. Grizzly, who are generally the predators, were the prey this time…they didn’t like it. Sorry.
4 Likes
I just wanna say, this thread delivers!
Was it zone disruption? Absolutely. However, Blizzard has already called the ball on that one: zone disruption is not actionable if said disruption is correctable by PvP self-help. I guess the issue is the interesting genie-in-bottle question of what happens when the disruption de facto obviates the PvP solution?
But as a participant above has said, it’s not up to the players to ensure lag-free WPvP- that one’s on Blizzard. Or, is the other side of the coin seriously arguing that any one, two, three, etc. Horde players are responsible for the others showing up and causing/compounding the lag? How do you even assign blame at that point? What is the consequence?
My mates and I used to seize the Theramore/Menethil boats and keep the Alliance from using them every weekend for about four months. In all that time, we only had one instance of a GM whispering us and asking us–not telling us–to pack it in and let them have their boats back. PvP solution is the ultimate equalizer, and it should be here- even if the solution was illusory due to technological shortcomings that have ignored the last 1½ decades of server tech advancements.
5 Likes