Happens every day and has happened for a long time. It happens everyday in the real world as well. Did you think it wouldn’t happen in game? Even back during vanilla and tbc, if you joined an AV that was mostly a premade (that you weren’t part of) they would mark you afk regardless of how well you played because they wanted you kicked so more of their group could get in. People are worse now.
yeah but I know two people who received a 30 day ban for defending. they were not afk.
Tell them Appeal it, and with any luck the jerks who reported them will get your ban for falsely accusing.
this is why they need more GM’s and need to be more actively (full time) involved with monitoring the game rather than only doing things when stuff gets bad.
1 Like
This is true, especially when it comes to what is allowed and what is not. I recall an event where players asked multiple GMs if something was allowed, they had screenshots saying that they were told it was allowed, but were later banned because it wasn’t allowed - and the words of their own GMs were not enough to protect the players.
Ban waves are much easier and cost less than constant moderation (as you can see by the trains of bots, it’s obvious to any human they’re bots), and they can artificially inflate the subs/MAUs for financial reports. This is generally how they operate.
1 Like
I was banned. Here is what I did. I was 68 on this paladin. I saw you could get good gear with honor so I jumped into them. Ran to one of the first 2 towers and capped it. Stood in it and held it. Sometimes things happened and I fought and died. Green questing items are kind of bad. I wasn’t going to tank any of the bosses and all I had was green questing items to tank with. So I stood my post. Those times when no one back capped, guess what… yeah… I just stood there and the game ended most of the time either right as the tower started to burn or shortly after. So in those games… yeah… I didn’t do a whole lot.
In other games people tried to back cap. Sometimes I held them off. Sometimes they got me. In those games the point of me standing there was apparent. Worth it. I was doing my job so to say.
Apparently now you have to know if people are going to back cap. If they arent then you need to move on. If they do then you need to stay. Just out of the smoke come up with what the other team is going to do on the fly… before it happens… THEN make your move.
I’m sure you’re right under the present model, but its not the best action for the game. Overall I feel that it would be more profitable for the game to be monitored full time by people actually familiar with the game.
What i am saying is that by actively monitoring and policing the game full time so that the game quality is higher; the result is that more real active players join and stay because the game community is a healthier / better place to be. Net result are more actual players, and as a result the people who’re happy tend to talk about the game they’re having fun with, resulting in more newer players.
This is the mechanism of original WoW Vanilla, and why it was so good. GM’s were straight up brutal to actual cheaters, but the GM’s were also very helpful to real non-cheating players, and as a result of cleaning house daily the community had a lot less cheaters and botters, and the like, meaning the behavior of the players playing was just generally better.
This does not mean there was no cheating, no botting or any bad behavior back then, but it was absolutely better than now, and I suspect that this was one of the factors contributing to the growth of WoW…
For me, coming from a background of FPS play in that time (2004) cheating on FPS games was just starting to get really bad, and Blizzard’s ruthless stance on cheating and botting and hacking was actually the prime reason why I enjoyed WoW so much… Because it certainly was not about how well the game was balanced or how “Bug free” their game was,… simply put, WoW to me, coming from an FPS background was the most un-fnished, worst built, pile of crap I had ever played, but it was fun.
OH and the graphics by 2004 standards were trash too…
In before someone says the old tiered and idiotic “OMG ITS AN MMORPG, GRPAHICS CANT BE THAT GOOD”… Stop your ignorance now, you’re an idiot so just shut it.
blizzard does not care at all about bots. Go stand outside of ramparts or mana tombs, if you are able to log into a high pop server. You’ll see hundreds of bots running scripts going in and out of these dungeons. They also terrain hack in netherstorm. Not one, not a dozen, hundreds. Blizzard knows.
1 Like
Oh no it’s awful for the game. Bots go unchecked, spam goes unchecked, and players leave because of it. But it’s easy and cheap for Blizzard and makes their numbers look good.
Blizzard doesn’t care what’s good for the game or not. They’ve made this evident. Whether or not it’d be more profitable in the long run to actively monitor it doesn’t matter to them.
Other than active moderation and actual contact with the players, unlike the outsourced CS dropouts we have now, we saw the GMs in-game. That meant a lot because we could actually see they existed.
It was a different time, but I think you’re right that taking a more active approach to moderation would improve the game.
1 Like
Read your response and thank you for actually being a real player and it sucks you got a ban, seems that people have indeed been abusing others with the reporting features;; turns out I was right back in 2017 claiming that GM’s are better than RCR systems with the outsourced GM system they have now.
Something of note, and its not your fault but honestly Level 68 / 69 players should not be in the same BG as Level 70 players. Same goes for when this swaps over to an 80 cap, Level 79 players should not be in the same BG as 80’s because its gonna create a problem due to people’s observation that low level players are often (not always) seen as non-participants in AV.
Tho I have seen some who do, but typically the ones you see AFK in a cave some place hiding under a rock are sub level cap.
1 Like
would actually improve their profit margins and quarterlies because the game would be… growing.
But instead they put the game on life support and reap the money like a garbo landlord who does not ever fix anything and lets the house fall in because all they care about is picking up the rent.
What would improved their profits would be to make people aware of things. You have to 50k damage in a BG to not get banned? Alright… I wont defend the towers then.
Sitting in silence and dealing out 30 day bans… yeah… thats an issue that drives customers away.
LOL, this game is so desperate to fix its issues its banning players left and right for simply playing the game. I get it… bad plays drive me crazy sometimes too… but banning people in AV for standing in towers?
What has it all come to. LOL
Defending towers are an objective of the bg and was always something that needed to get done. This is a toxic community thing.
1 Like
I agree 100%. It also seems tied to a really ridiculous claim that you have to do x amount of damage or healing to be “part of the BG” Blizzard is pushing around. Just a terrible way to judge if someone is doing something in AV correctly or not. But it is probably easier for the bee boop beep CS squad to detect. Combined with toxic community members reporting.
Just a terrible thing to have happen to people. I imagine 1000s of peoples WotLK was just ruined because of a 30 day ban over something that makes zero sense.
1 Like
Too bad you can’t do that because you’re banned and can’t log in 
True. Cant handle logging in… probably 30 day’ed people to try to fix ques. Looks like that was a flop. Like most Blizzard solutions… drive players and people away and still come up short…
Huge yikes. At first I was thinking this was the typical ban whine threads. But its becoming kind of apparent to me that this is a pretty big problem that is going to cause a lot of problems.
30 days?? Holy hell man.
This is a huge shame man. Its just not right to start off with 30 days.
It’s only the PvE’ers that aren’t understanding how rampant the AFKing gets during prepatch/launch.
1 Like
Unfortunately.