convert perfect walking method from OSB1 to OSB2

[Swizzbeat]

I see your points.

 

I never claimed my snippet reproduces human behavior perfectly or even got close, all I said was that if you are trying to emulate such behavior it requires complexity.

 

If you think my snippet is more or as ban-productive as the average walker, then fair enough, I don't have any empirical data to contradict that stance. I might be fooling myself, but to me my snippet looks more human-like than any other walker I ever used.

 

Returning the closest tile from an array isn't the most intelligent design either however

 

This could be checked for via collision flags / rooms, might be a bit processing heavy though (unless you cache the data, which is probably how I'll do it ). 

 

I like some control over my walking, if you're fine with localWalker.walk(Position position), then fair nuf I guess

I think a huge issue plaguing scripters/bot developers right now is that they are trying to make things look like human interaction. You guys need to realize we're not trying to fool humans, but instead programs designed to pinpoint specific things they are programmed to monitor.

 

For example, let's say we gained access to Jagex's bot detection program and saw that it only monitored how many times you right clicked vs how many times you left clicked. Depending on the ratio it would flag an account if it became to far unbalanced. Now think, would things like mouse pathing algorithms, random mouse movements, camera changes, etc. matter at all when it comes to ban rates? NO! You could literally create a script that has a mouse move in a linear line towards the target, or hell even just generate an event at the point you want, without ever receiving a ban.

 

Supposing the above is true, Jagex only decide to monitor the ratio between right and left clicks, if I design a script with a chance of right clicking calculated like this

if (random(11) > 5) rightClick();

it may appear to a human as random but would throw up instant flags to the bot monitor.

 

My point is that antiban should be created at the code level, not based on how it looks when running.

 

 

EDIT: I don't think you fully understood the code I posted or you wouldn't be saying grabbing the closest tile to you is unintelligent.

Edited July 19, 2014 by Swizzbeat

[Botre]

I think a huge issue plaguing scripters/bot developers right now is that they are trying to make things look like human interaction. You guys need to realize we're not trying to fool humans, but instead programs designed to pinpoint specific things they are programmed to monitor.

 

For example, let's say we gained access to Jagex's bot detection program and saw that it only monitored how many times you right clicked vs how many times you left clicked. Depending on the ratio it would flag an account if it became to far unbalanced. Now think, would things like mouse pathing algorithms, random mouse movements, camera changes, etc. matter at all when it comes to ban rates? NO! You could literally create a script that has a mouse move in a linear line towards the target, or hell even just generate an event at the point you want, without ever receiving a ban.

 

Supposing the above is true, Jagex only decide to monitor the ratio between right and left clicks, if I design a script with a chance of right clicking calculated like this

if (random(11) > 5) rightClick();

it may appear to a human as random but would throw up instant flags to the bot monitor.

 

My point is that antiban should be created at the code level, not based on how it looks when running.

 

 

EDIT: I don't think you fully understood the code I posted or you wouldn't be saying grabbing the closest tile to you is unintelligent.

 

 

I did understand your code, I don't think your position grabber is more advanced than mine in any way (I'm talking about the position grabber here, not the walking part).

 

Concerning my code. What is too complex? What is redundant? 

If you have a walking snippet that's better / more human-like than mine feel free to post it.

I'd love to see how it should be done

 

Edit: I'll be offline for the rest weekend but looking forward to your response ^^

Edited July 19, 2014 by Botrepreneur

[Swizzbeat]

I did understand your code, I don't think your position grabber is more advanced than mine in any way (I'm talking about the position grabber here, not the walking part).

 

Concerning my code. What is too complex? What is redundant? 

If you have a walking snippet that's better / more human-like than mine feel free to post it.

I'd love to see how it should be done

 

Edit: I'll be offline for the rest weekend but looking forward to your response ^^

I'm not trying to act like some high programmer, don't get the wrong vibe :p

 

I don't have any code I'd like to release concerning human like actions, I was just offering my opinion on how to stay safe.