This forum is used to deal with abuse in game - abuse reports, bans etc.
#153669 by WildX
Tue Oct 11, 2016 9:10 pm
Tranzient and Scrub were caught attacking Red Slimes while AFK and possibly multiboxing. They failed a botcheck and received a ban. Whether or not this also counts as a failed multiboxing check will have to be discussed by the GM team. I will post a follow-up here as this is the first known case of this kind and we will need to set a precedent.
Spoiler:
ManaPlus_Screenshot.png
ManaPlus_Screenshot.png (378.96 KiB) Viewed 673 times

Note: I count the first "hey guys" as the beginning of my botcheck. My clock was just seconds away from 22:53 in the last message.
#153679 by The Micksha
Wed Oct 12, 2016 1:24 pm
Hmm please discuss with the GM team. If there are rules like "Botcheck starts with the message: This is a bot check", and "Botcheck takes 3 Minutes", and "it needs a screenshot during a botcheck where the victims to be banned are visible", I think everybody should stick to these rules quite scrupulous. Ban is a very hard punishment and rules like these should not be there just for fun. Dont turn this into dictatorship but keep transparency for everybody please.
#153680 by EJlol
Wed Oct 12, 2016 1:48 pm
This discussion should not be in court house, so feel free to split this topic.

I don't think it should be required for a GM to start with a message "This is a bot check". It is quite easy to scan for a message like that, and let the client do something. (make a sound so the owner gets alerted, logout, etc). GM's should be free to do the botcheck however they want, though I do think there should be a general guideline (which there already seems to be).
#153681 by WildX
Wed Oct 12, 2016 2:17 pm
We actually discussed with other GMs that we should be avoiding words like "botcheck" or the name of the player as it could set off highlights that alert afk botters of our presence. The screenshots are not required. It's been said many times that they are just a courtesy that we provide for extra clarity. Screenshots could be easily manipulated and do not count as evidence of anything.

I will leave this discussion here because it's pertinent to this ban and will allow easy access to this precedent in the future. I consider off-topic only if it goes beyond the scope of how and why the ban took place.
#153684 by mistergrey
Wed Oct 12, 2016 10:24 pm
Frankly, it's harder than you'd think trying to botcheck somebody who is constantly moving away to another target. Nothing stops anyone from faking a screenshot, we provide those for transparency and to provide context for the ban.

We will not use a particular line to start a botcheck, and we are not required to highlight players by their name at all in that process - if you are at the keyboard, you'd surely see a GM speaking to you whether we use your name or not. If you missed it, that implies you were not at your keyboard WHILE automation was running - the very definition we use to define botting. There are a lot of ways for botters to try and avoid botchecks, and so how we do botchecks reflects that.
#155418 by prsm
Tue Jan 03, 2017 10:09 pm
I have unblocked both, please contact a GM next time you log in, to have your levels reset.

Prsm

Who is online

Users browsing this forum: No registered users and 1 guest