Jump to content

Apaec

Scripter III
  • Posts

    11139
  • Joined

  • Last visited

  • Days Won

    90
  • Feedback

    100%

Everything posted by Apaec

  1. Certainly, i've given you a 48h trial as the script, like all others, is broken atm due to raids. If the client isn't fixed within the next 48 hours, i'll extend it further cheers apa
  2. Appears to be the same tile visibility error as before - they haven't updated the client yet. Currently the latest build is 2.4.07 - hopefully they will update it soon but as for now there's really nothing I can do! apa
  3. Apaec

    APA Chest Thiever

    Sure thing I've given you 24h to try the script, enjoy!: ) apa
  4. haven't been able to finish a raid yet!
  5. Hey, don't worry. I believe this issue is caused by the recent raids update, so just hang tight and the devs should get around to fixing soon! Cheers apa
  6. It is randomised, but once the script is back online I can look into adding more camera and mouse movements too! Heya, all scripts have the same issue due to the recent raids update, just hang tight for the devs to update the bot!
  7. Probably due to the raids update today, just hang tight for the devs to fix!
  8. Yep, will do my best to have this added for you for the next release, after raids ~apa
  9. 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
  10. Haha, sure! I've given you a 24h trial ~apaa
  11. Hmm. Potentially count add this for forging. I will take a look!
  12. Update! Version 2.01 Fixed issue causing script to bank for potions even when option not selected.
  13. 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
  14. oo. That's odd, thanks for mentioning! I will take a look. Cheers apa
  15. UPDATE! Version 1.62 Added support for water boiling ("cooking" bowls of water)~apa
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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!
  23. Sorry, I misread what you initially posted as just incrementing a counter when calling the pick up statement... Apologies!
×
×
  • Create New...