“Be nice” doesn’t mean “bend over backward to help other players.”
It means “if you see someone fighting a group of mobs on top of a chest and you loot the chest and it despawns, you’re a jerk, and there might be consequences for that.” or “If you see someone running to a group of mobs to fight it and you run up and tag them all first, you’re a jerk, and there might be consequences.”, or “If you see someone fighting a few mobs and you pull more mobs on top of them and don’t stop to help them fight the mobs YOU pulled and instead run away or Feign Death or go Invisible or something, you’re a jerk, and there might be consequences.”.
Those are just examples, but I hope you get the idea.
But putting another player in a situation where they might or do die because you were engaging in activities similar to those I mentioned above always have been the rule of the game, but it’s rarely ever been enforced.
But using the existence of the filter is not your excuse to use that sort of language. The filter exists because there is no other physical BLOCK for seeing it. Blizzard would have been negligent for not adding it (and in some countries that play WoW, they may have been legally obligated TO add it).
They are the same thing. The only difference is with the “Social Contract”, you’ll actually see a box pop up with all the rules they’ve already had and you’ll have to click a box saying you accept those rules.
This way, you can’t say later “I didn’t know that was against the rules”. You did, they put it in your face and you accepted it, which means you have to accept the consequences when you then break those rules and you don’t have the “out” of a “lack of knowledge”.
TBH, the new social contract feature is probably just them trying to force you to actually read the code of conduct you already agreed to by playing the game.
Those are just examples, but I hope you get the idea.
yeah we cleared that up awhile ago.
But putting another player in a situation where they might or do die because you were engaging in activities similar to those I mentioned above always have been the rule of the game, but it’s rarely ever been enforced.
Yes, griefing used to be punished. Not helping someone and griefing are not the same thing though. Again, this was already cleared up earlier.
But using the existence of the filter is not your excuse to use that sort of language. The filter exists because there is no other physical BLOCK for seeing it. Blizzard would have been negligent for not adding it (and in some countries that play WoW, they may have been legally obligated TO add it).
I clarified this a few times but I’ll say it again. In terms of harassing other players, sure. Casual profanity I completely disagree. Casual profanity in the sense of using profane words like mild curse words such as the “S” word or “F” word should not be reportable offenses. It clogs the system up for something that is removed from your chat window by default. If you went out of your way to enable your chat window to display such words, then you knew what you were going to see. My analogy earlier would be like going to a strip club and then being upset you saw naked people. You didn’t need to go to that establishment, and you didn’t need to enable profanity. This is not to be confused with condoning hate speech or harassment.
They are the same thing. The only difference is with the “Social Contract”, you’ll actually see a box pop up with all the rules they’ve already had and you’ll have to click a box saying you accept those rules.
They’re the same content wise. They’re not the same though. This Social Contract is being marketed as new .
Because it includes a new popup window so they know you’ve actually read it.
That way they can point to your acceptance as an acknowledgment of those rules.
Once implemented, the excuse " I didn’t know" won’t be valid anymore. That’s the point of changing it. It will be easier for them to just refer to that as to why they enforced and upheld your punishment.
Because it includes a new popup window so they know you’ve actually read it.
Sure, and of course. It’s still new though. It’s not the Tos. It’s the Social Contract. Two nearly identical, yet different entities. Is it being pedantic? Yes. Definitely.
Because some people, like me, swear casually as a result of past employments. I worked at an airport for like 3 years and in the air force (as a reservist) for about 11. Swears were just . . . a part of conversation for some reason. I don’t know why. But it gets so common place it becomes habitual, especially around people who don’t give a . . . well you know . . . about profanities.
So if you end up in a guild with people who share such a vocabulary, it’s usually better to just let the words flow than turn the maturity filter back on.
Besides, the maturity filter used to be complete garbage. Dunno if it still is, but it would, for example, censor the word “therapist” because “r*pist” is in the word. Or you’d say something like “I went fishing and caught a bass” and the filter would turn it into “I went fishing and caught a b***”. I don’t know if it still does this, but it used to.
Because some people, like me, swear casually as a result of past employments.
I meant it to be more of rhetorical question, but I’m with you. Worked kitchens and construction all my life. That’s why I don’t think mild profanity in casual conversation should be punishable. For that application, if someone finds those words so offensive that seeing them in casual conversation upsets them, they can turn on the filter.
Edit
Or I guess the proper way to put it is. They shouldn’t turn the filter off. As it is on by default.
I am a bit confused here. While it is always nice to be cooperative, it has never been against the rules of the game to ignore someone and let a mob kill them. They may not like you and may not ask you to be in their guild (social consequences), but there is no actual Blizzard rule against it. Maybe I misunderstand what you are saying though.
In WoW you have to be causing major zone disruption before Blizzard steps in for “griefing”. Also I think repeatedly messing with a raid group boss pull can get actioned because it holds a whole group hostage and they are locked to the raid ID.
I’m not talking about someone fighting a group and you not helping them.
I’m talking about you doing something intentional to bring more on them than they were originally handling and then leaving the scene and letting them die.
It could be seen as “griefing” if you pull a second group onto someone and then just leave to let them handle it themselves.
This has to go on for a long time before Blizz will consider stepping in. If the player/s can leave the area and do something else then Blizz considers it a self solving problem. They let people kill and camp quest NPCs and flight masters for hours or days even… so yeah. The advice is to “quest elsewhere”.
Personally, I don’t agree with that and feel it really sends a bad message to new players, but Blizz currently won’t stop it. Although with the DF changes to reduce faction wars (maybe?) we can hope they consider all quest hubs/towns sanctuary zones with unkillable NPCs.
It is not nice, but that is not against the rules. It just makes the person a jerk who nobody will want to be around. As a rogue I admit I am sure I have done that before to someone. I have agro, vanish and sprint, someone else cleans up the mess. I don’t do it on purpose but it happens.
I dont think that’s griefing. It’s been done too me countless times and I’ve done it to others. I once pulled the entire mine outside the horde base in stormsong on my hunter and out of nowhere a human lock can into the vicinity and I ran through him as his void taunted and I feigned death. Watched him get overrun lol pretty funny.
The most that’ll happen is I get called a jerk, big deal. Or I call others jerks for doing it too me, big deal. We go our separate ways.
This has to go on for a long time before Blizz will consider stepping in. If the player/s can leave the area and do something else then Blizz considers it a self solving problem. They let people kill and camp quest NPCs and flight masters for hours or days even… so yeah. The advice is to “quest elsewhere”.
This is getting sort of nuanced, but I only support Blizzard stepping in for Same Faction Griefing. If you’re horde and their Alliance, imo everything short of actual cheats or exploits is fair game. Sapper Charging full raids on the way to Molten Core on a PvP realm? All for it. I know it gets old hearing “Don’t Join a PvP realm then.” but… well honestly it’s true. Is it lame if someone at lvl 60 is ganking you and you’re lvl 10… sure… War Mode largely solves this issue in retail. But yeah. Same Faction Grieifing is not okay. If it’s red, it’s dead.
Probably, but I’m sure they can see if a player has a habit of doing that to people and notice a pattern.
I would disagree with you here. It’s griefing, which has always been against the rules.
Doesn’t make it right and doesn’t mean it isn’t against the rules. People that show a pattern of doing this could be affected in the future.
I would consider not doing this sort of thing going forward. It’s an obvious grey area and I’d say we aren’t sure which way they would lean on this one.