Swizzbeat

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.

How is this bashing? I offered my opinion multiple times.

You have my full support, but in my opinion you guys are going about this in terrible way (which is why I left the Skype groups).

lol gay

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.

Nope, I don't really watch anime

I know what I'm watching for the next two weeks.

Creating an actual "human" walker (or even antiban in general) requires more than just calculating a random number and executing an action based on the result. All calculating a random number does is execute your action based on a never changing percentage instead of what you had it at previously with a given number. Previously you had it click the game tile if the distance was less than or equal to 5. Now it will only click if the distance is less than or equal to 3 or 4. If we ran a large number of trail runs at lets say, a distance of 3 between you and the next tile, what you had before would click on the game window 100% while the random number calculation you just implemented would result in a change to 50%. A lower percentage (which I guess isn't bad) but still static nonetheless. Incorporating real human actions requires a multitude of conditions to check and ever changing values to be recalculated. Maybe instead of deciding to click the game based on a distance threshold you instead check to see if the player is in combat? A condition like this is ever changing (like a real human) and is completely based on the concept of "here and now". While it may become evident what is happening if a real Jagex employee decides to look into your past account actions it's most likely not going to be detected by a detection program. What I'm trying to say is if you are using a condition where you can actually calculate the chances of it happening, resort to something else that cannot be predetermined.

Only way now to mine bitcoins for profit is to start a botnet.

You completely missed the point of my last post

That's not human behavior but a static condition. If you're really trying to mimic a human at the very least add some random deviation to your tile/minimap click points.

Holy shit you guys make everything overly complex. Iterate over your path to grab the closest path index to your current position. From there add one to your index and continue iterating over the path checking to see if the position is within your desired distance. Once the distance exceeds the threshold return the position value located in the last index you grabbed. public Position nextTile(Position path[], int skipDist) { int dist = -1, closest = -1; for (int i = path.length - 1; i >= 0; i--) { Position tile = path[i]; int d = scriptInstance.map.distance(tile); if (d < dist || dist == -1) { dist = d; closest = i; } } int feasibleTileIndex = -1; for (int i = closest; i < path.length; i++) { if (scriptInstance.map.distance(path[i]) <= skipDist) { feasibleTileIndex = i; } else { break; } } return (feasibleTileIndex == -1) ? null : path[feasibleTileIndex]; }

I just disabled all signatures.

Which is an extra feature...?

Implement BotMouseListener, it provides more features.

You have an IQ over 50, unlike most of the kids botting, and actually switch up the script once and awhile.

This is common knowledge.

inb4 he was just trying to be friendly.

Womens rights.

Unless they updated it recently nope.

Nope. Literally nothing changes about the object besides the height and ID which is why there's so many people asking about smoking rock detection :p

More resources.

Considering I'm one of two scripters out of what, 25, that has a free script I'll take that as a compliment.

Redhead porn.