Why do people get banned? And How can I avoid it?

[Silk]

Why do some people get caught and deleted for using blackdtools (happened to me before) and others don't? Are there some sort of survival techniques that allow people to cavebot without being detected? Cause it can't all be luck, I can't get past level 30 without getting caught somehow.:confused:

[TeamSurge]

there are so many rumors about how ppl get detected. i think the detection system looks more into the packets sent to it then in the movements of the char. but changing scripts out with more random Way-points has proved to yield better loot. I don't think stamina on its own matters all that much, but im sure it is used as an extra determining factor. also being premy gives you a little extra exceptions

.randomize everything
.stop botting after -22hr
.randomize everything you randomized
.and still get banned

;)

[Silk]

there are so many rumors about how ppl get detected. i think the detection system looks more into the packets sent to it then in the movements of the char. but changing scripts out with more random Way-points has proved to yield better loot. I don't think stamina on its own matters all that much, but im sure it is used as an extra determining factor. also being premy gives you a little extra exceptions

.randomize everything
.stop botting after -22hr
.randomize everything you randomized
.and still get banned

;)


Yeah, I heard about the packets sending problem, didn't hear of any possible solution till now though. So I should have random waypoints? Is there a command for that? Like every 3 steps my character does something random or w/e, if not how would I do it?

[Silk]

Bump (short).

[TeamSurge]

well for a start setchaoticmovesON, should be on by default. i randomize the path the bot gos by giving each cave area a number and then use $randomnumber:#>#$.

example:
:cavemain
main hunting waypoints...then
gotoscriptline $nlineoflabel:hole{$randomnumber:1>3$}$
:hole1
waypoints
gotoscriptline $nlineoflabel:cavemain$
:hole2
waypoints
gotoscriptline $nlineoflabel:cavemain$
:hole3
waypoints
gotoscriptline $nlineoflabel:cavemain$

I use that type of setup anywhere there are multiple chose holes/ladders/or combination. just as long as they return to the main area of the cave.

to take it even further if i am moving to an open area I use this...
move 1234$randomnumber:3>7$,1234$randomnumber:3>7$,#
I only do that in open areas because i try not to have the bot telling me its not possible to move there.

k i got to get back to the scripting. check-out the scripts i will be releasing soon. http://www.blackdtools.net/showthread.php?61790-Surge

[xHellsx]

It used to be due to lack of variation between events, such as always doing things exactly 200ms apart. But now these are all randomised, it is mainly incorrect or bad packets being sent to the server. BlackD acts very strange in some manners because of these bad packets.

When things seem to go wrong randomisation also seems to vanish, I can see the bot spam 50 times in a second with only "sorry not possible".

[TeamSurge]

nice xHellsx, i feel this is why we need to have tibia version for script posted next to all uploaded scripts. I know there is a area for old and new scripts, but new quickly becomes old.

solution: {10.5}ver
this will allow users to identify what scripts have been updated to what version
of course this would only matter if there is hex in the script

also; scripters need to try to turn off allow reposition at trap
this is for me the most common resin for the "sorry not possible"

[xHellsx]

I'm pretty sure the attack packet we use is incorrect. As it doesn't select the red square around the target and seems to send individual attack packets rather than just a select attack and let the client do the rest.

The bot just runs around the target like it is using it (so if a monster is running towards you, you run past the monster to its original position, and then back to where it was when u past it.. etc)

[Tony32]

It used to be due to lack of variation between events, such as always doing things exactly 200ms apart. But now these are all randomised, it is mainly incorrect or bad packets being sent to the server. BlackD acts very strange in some manners because of these bad packets.

When things seem to go wrong randomisation also seems to vanish, I can see the bot spam 50 times in a second with only "sorry not possible".


I'm pretty sure the attack packet we use is incorrect. As it doesn't select the red square around the target and seems to send individual attack packets rather than just a select attack and let the client do the rest.

The bot just runs around the target like it is using it (so if a monster is running towards you, you run past the monster to its original position, and then back to where it was when u past it.. etc)



This, very much this. Too much this! BlackD makes client say "Sorry not possible" A LOT. Wonder what it's really doing x)