They should atleast give a proper reason for the ban. Just " you have been banned for avoiding anti afk" isnt satisfying . They should give us proof of our miscondut. Got DC'ed and when i try to login " You have been banned..."
-
Member
Ban without any reason
-
Member
Good, what explanation you want afk nab,this is all what you need for explanation " you have been banned for avoiding anti afk" get rekt.
-
Member
Post ban appeal from support page, there you will know proper reason for ban.
-
Member
What more do you need, you avoided anti-afk mechanism in BGs, which is bannable = you are banned.
-
Member
I cannot speak in hia defense but there was a situation wherw a guy didn't know how to play and told everyone he was going to pee that he'll brb.
At this some other guys from the team told everyone to report the afk guy asap.
He came back moments later and was disconnected when he started to cc the flagger in wsg.
Sometimes we have to double check the situation and not assume like the rest of warmane sheeple.
-
Overwatcher
Flagging someone as AFK to get them kicked out of a Battleground doesn't gets anyone banned.
A GM watching and seeing someone avoiding the anti-afk to not contribute but get easy points in the end does.
-
Forum Veteran
Reporting someone using the ingame system simply flags them as afk and they have 1 minute to get into pvp combat before they are removed from the BG... Not banned.
The fact he DC'd was simply coincidence.
-
Member
Was doing a premade with my guild and was protecting base does that count as avoiding the mechanishm ?
-
Overwatcher
No, it doesn't. GMs observe the behavior of the player and try to contact them before issuing bans.
-
The Detective
I assume he was too afk to see the GM whispers >:^ )
-
Member
We know that the in game one doesn't work and his guild confirmed he was banned and will be unbanned in a few days all stating he was dc as soon as he started combat with the ban announcement for afk popping.
This goes along the lines of people making reports of fly/speed hack when the ghost bug started to show up on 5.4.8 (out side of bg ofc)
I'm just observing from my point of view as well as others. Sometimes we can't assume things but hey it is how everyone is doing it here.
