The idea Cotillion posted is pretty good. Most bots can be programmed to do pretty much anything. Without even 'programming' anything it is relatively simple to configure your client to auto target and auto attack any monster in range (which, if you are an archer is not limited to being right in front of you). I have seen relatively simple bots in action that stand in a fixed position, fire at bats for 30 seconds, walk a grid picking up all fallen objects in a circle around them, return to their position to continue firing. Any checks based on 'sitting in one place for too long' or the like will ignore this relatively simple to create bot (which can be easily made using a macro creation program or the like). Where Cotillion's suggestion comes into play is like such:yuminig wrote:ouch! jaxad0127 shot me down real good. I only know about bot using console so I'm not sure.
I'm all out of ideas. I guess there aren't real permanent solutions for anti-bot.
Someone is doing whatever. They are botting it up in the bat caves. The player is randomly pulled from the batcaves via (magical portal, etc) a random event. Once there they find an NPC who asks them to do a relatively simple task: kill five maggots and bring them the maggot slimes, place the following random components into a cauldron in a certain order, retrieve water from the stream over there and bring it to me, etc. Once the player has completed the task, they are teleported back to where they were, and continue on as before. A bot however, will continue trying to fire and walking their square. They will pretty much remain there, until the server kicks/bans them ot they come back from whatever they were doing and do the task manually.
Now, I am sure there are work arounds, such as logging out ever X minutes and relogging in, assuming that the temporary area you are pulled to isn't persistent and you return to the place you exited from but these would have to be examined in detail and handled appropriately. A system such as has been described, while nice, would probably require quite a bit of code revisions and I'm sure Devs would much rather work on TMWServ as opposed to recoding the current combat system as a stopgap to prevent botting.