Apaec

That depends on what raids will be like, whether it will be worth botting, how hard/long it would take to write a script for etc

Haha, sure! I've given you a 24h trial ~apaa

looking good

Hmm. Potentially count add this for forging. I will take a look!

Update! Version 2.01 Fixed issue causing script to bank for potions even when option not selected.

I certainly have not coded that, so it must either not be my script or the client...! Everything seems to be working OK for me (just did a test run now), so i'm not sure what's gone wrong there... Does it print anything in the logger? apa

oo. That's odd, thanks for mentioning! I will take a look. Cheers apa

UPDATE! Version 1.62 Added support for water boiling ("cooking" bowls of water)~apa

That's odd as I don't seem to remember adding that. Perhaps you've got the wrong script, or the client is acting funny? Try rebooting the bot and giving it another shot! apa

Hey, thanks for the kind words I can add worldhopping to roam mode, will find space on the Gui to add that and will put it on the to-do list. As for the crab selection, it should aim for the closest one which isn't already under attack, but sometimes it can deviate from this just to make it seem more natural. I can probably increase the accuracy of this though! Cheers apa Hey, unfortunately as i'm sure you can understand, I cannot offer multiple trials to the same person. Sorry about that!! apa Firstly, thanks for choosing the script! Unfortunately bans are issued somewhat randomly, however there are a few steps which you can follow to minimise the chances: As you said, play inbetween Spread botting sessions out throughout the day. I'd say that even 2 hours is potentially too long. Try and keep it under/around an hour to be extra safe! Have a brief read of this thread written by one of the bot developers: osbot.org/forum/topic/45618-preventing-rs-botting-bans/ The way I see it, progressing slowly is much better than being outright banned Also, if the account really means alot to you, I would recommend resisting the temptation to bot on it, that way there's no worry that it will get banned. ~apa Hey, that's ok. I've restarted your trial as it does indeed seem you haven't got a chance to run the script. Cheers for stopping by! apa

Hiya! When I said console, I did indeed mean logger, which can be accessed via options>show logger as you said. Whenever the script decides to make a bold/state changing move, it will log what it is doing so that the debugging process is a little easier. I also added status logging for CLI users such that they know the script is going strong! I'm glad to hear that your problems are solved, please let me know if you encounter any more! apa

Just updated the thread layout with a new demo video created by World Ender. Hopefully it should now be easier to navigate the page! ~Apa

Perhaps you accidentally initially configured it with teleports instead of tele-tabs? Otherwise i'm not sure what would have caused that issue! Cheers apa

Nice work, congratulations!

I was looking into this almost a year ago now... As far as I could see, with the information available, it is not possible to directly determine whether loot lying on the ground is yours. However, if you're tracking what is being attacked, the tile and time of death, along with a few other pieces of information, you can build a method to determine what items you have spawned into the game, and hence filter the ground items. It would be difficult to get close 100% successful though, but it is certainly possible. It would also be possible to switch to attacking an alternative Minotaur if your current one is already under attack from someone else. In conclusion, it's possible but difficult to tailor a script specifically to ironmen ~Apa

The status should say idle when attacking I believe. As for the banking, nothing has changed in the code. Perhaps you're configuring the script wrong, or don't have enough of an item in the bank? Open the console to see what went wrong - it should show all detailed status updates there!

Sorry, I misread what you initially posted as just incrementing a counter when calling the pick up statement... Apologies!

Edit: Nevermind!

I could certainly add it, and in early stages of developement this was a feature, however I'm worried that if anything this will increase your chances of getting banned. For more information about what we think affects ban chances, take a look here: osbot.org/forum/topic/45618-preventing-rs-botting-bans/ Cheers apa

That certainly is strange, perhaps something went wrong with the run energy checks in the latest update? I will take a look that I haven't covered two cases though. Besides when it flips the run energy is randomised every time the script starts Cheers for mentioning !

That's awesome progress mate and yea, many many sand crabs have been slaughtered haha

The random dismissing I cannot do anything about, that's handled by the client (make sure you've selected 'dismiss all randoms' in the options tab!). As for the refreshing, not sure why that would be happening, perhaps just latency issues? I will follow up with some testing though, perhaps it was just a one-time thing. Thanks! apa -- Just pushed a small BTS update, version 3.51. Only adjusted the structure of a piece of code that I copy-pasted from another part of the project, but was outdated. You shouldn't notice any changes!

You probably don't have any potions in your bank! If you do, make sure they're 4 dose potions... Otherwise, there should be a message logged in the console as to what's gone wrong. Cheers apa

Unfortunately not (I guess that would fall under crafting!) - sorry! Sure!

UPDATE! Version 3.50 Added CLI support! running from the command line will use the settings from your most recent save. You MUST have a save file otherwise it will not work. There are no parameters because of this - run the script as so: (parameter is abc, make sure there is something there and that it is not just blank, otherwise it will attempt to load up a gui). java -jar "osbot 2.4.67.jar" -login alek:password -bot alek@osbot.com:password:1234 -debug 5005 -script 421:abc Fixed filepath issue for linux machines (hopefully). Stopped script logging out when manually stopped. Let me know if there are any issues! ~apa