lisabe96

I don't think you understand the concept I explained. Or you do but I don't see it. What you probably do is, oh a tree is down, lets do a delay before going to another tree. That's the script viewpoint. With the player viewpoint you're taking a delay, then come back in game and see what has happened in your area and how you can react to it.

Not just long delays, it's about working from a player-viewpoint. I'll work something out when I have time and post it in dev section

Yes that's exactly what I'm using and the issue I have, i posted about it in the bug section

Well it's true we have no clue on how they detect bots, but we can assume it's by detecting behavior as when it would be software wise, mirror client would never have bans. So the closer you get to human-like behavior, the safer it should become. @efficiency That's why you add a checkbox to let the player choose whether to use anti-ban or not

Wait a sec, I seem to have the same problem in .37 I want to walk to the bank area but it is spam clicking the same tile every time again rather than using a random position.

In my experience webwalker finishes when it's under 2-3 tiles distance of the destination automatically? Annoys the shit out of me sometimes when I runs out of a building because of that

I don't know about you guys but personally when I'm playing legit I barely ever hop worlds. I just take a low-player-count world on a nearby server and get playing. Imo hopping worlds all the time would even get me suspicious in some situations. However when botting I assume it could help as it avoids legit players becoming suspicious about you and reporting you.

I was thinking of another approach on anti-ban implementation. The regular methods are the pseudo anti-bans (opening tabs, camera movement, ...) And smart delays (taking a random delay before searching a new tree, while in bank...) However I think we could take another approach on those random delays. Now we mainly handle it from the viewpoint of happenings in the rs world rather than from player view point. Let me illustrate: - Start chopping tree - Tree is down ? do a little delay, search a new tree Now let me illustrate how I think a player-viewpoint approach could work - Start chopping tree - Move mouse outside screen (delay for a while like we're checking a website or something) - Randomly hop back in into the game and see what happened The tree could have been down after 2 logs or the tree could still be up. Whatever the situation is, we detect the current situation when we as a player come back to the game, rather than the script seeing that the tree is down. Also experience rates would be very variable, etc... This could when implemented correctly result in a very realistic player-like behavior. Even when mod weath is standing next to you it would be very hard to spot that you're botting. I'm using woodcutting as example as it would be one of the easier ones to try this out with & I'm mainly working on my woodcutter right now. Thoughts?

It shouldn't be, I'll check it out. Did you have any error messages in the logger?

Probably the same issue as the other ones, will make a new build tonight or tomorrow

Mmh the webwalking is getting annoying with it being some tiles off. However the tiles off makes it in most situations required to keep a human-like behavior. You don't want to be walking the exact same path and stop at the exact same tile every time. I will probably have to rework the code by writing my own walking events rather than using the webwalking methods. Probably don't expect a next build today already as I have some irl stuff to do today as well.

The cycle (sleep) time

Your fix ^is not really a fix, you just bypassed the issue. Don't initialize this globally, add it to onStart(); private final Player me = myPlayer(); private Player me; @Override public void onStart() { this.me = myPlayer(); }

Build 6: - Added regular trees and oak in Falador north - Added oak and yew in Falador south - Added a catch to avoid getting stuck outside the bank - Fixed a bug where sometimes you'd get stuck when trying to walk towards a tree - Fixed a bug in custom locations when the bot would not find the way back after banking Download build 6 here

Fixed: http://www.mediafire.com/download/p253949eeviebhn/RQ_Smither.jar Download here

It doesn't, it would create a difficult situation. Let's say there's 3 willow trees next to each other I want to cut, but there's also 1-2 at 25 tiles away. Then it could end up there. Or in the case of oaks that are everywhere the bot would wander through the hole rs world :p As you might have noticed, no zones around falador are added yet at all, this was planned just not done yet. Will add them in the next build.

Great thanks!

Mmh that's because the webwalker says it's arrived at the bank. The webwalker can sometimes be a few tiles off But the bot sees it's not in the bank yet, so it just waits. Ill add a fail catch for it later

Looks like problems with the webwalker from the API rather than my script. When it happens again, check your debug log and take a screenshot of it.

I didn't realize that, didn't think about it being against the rules

Why do people always black out skill levels? If i'd wanna buy an account I would wanna see what I get

Build 5: This should be the final beta build, please report all bugs you find. - Axe upgrading fixed - Willow tree detection fixed in Draynor - Custom location support added! Custom location support: With custom locations you can cut anywhere you want, not bounded by a location. In the GUI choose your type of tree and then choose as location "custom". The bot will scan the area in a 10x10 radius around him for trees of the type you specified. It will save those trees and create a woodcutting zone internally. When not using powerchopping mode, it will find the closest bank near you to go bank. When using custom locations you MUST stand in the center of the location you want to woodcut when starting the script. Click here to download build 5

Find where the "OSBot" folder is saved, (I'm assuming your home folder) Then inside the osbot folder there's a "scripts" folder. You save it in there and refresh your scripts in your client afterwards.

Build 4: - Smart tree detection added (Will walk towards the first tree to respawn when all trees are down) - Fixed axe depositing when banking - A few new locations added - Some anti-ban improvements Click here to download build 4 Nearly finished for official release apart from a few things. Unless new bugs are found. Thanks for helping out with beta testing.

I will check it out, thanks for noticing me Edit: Are you holding an axe in hand AND having one in inventory? Because it will first check if you have one in your hand and consider that one to be used.