Jump to content

Apaec

Scripter III
  • Posts

    11152
  • Joined

  • Last visited

  • Days Won

    91
  • Feedback

    100%

Everything posted by Apaec

  1. Unfortunately I cannot offer trials to OSBot accounts under a week old - this is an OSBot rule. Sorry about that - please come back on Sunday! Apa
  2. Hey - welcome! I've just started your trial - please feel free to message me with any questions that you may have. I'm always happy to help Apa Sure, trial activated!
  3. I believe there's a list here: http://www.itemdb.biz/
  4. Yeah; all combat exp gained since starting the script. Apa
  5. There are a number of structural bad practices here which are likely causing the issue, or unreliability in the script as a whole. If you fix these, you're more likely to fix your original problem! You're writing the script in such a way that you're expecting each line to successfully execute every time. This is not (and can never be) the case as you're interacting with a live game so there is a whole middle layer entirely out of your control (latency fluctuation, game errors, resource throttling, ...). Don't do this! Instead, endeavor to make your script stateless, i.e it is not relying on any instruction to execute successfully before immediately proceeding to another instruction. You can achieve this by only ever having one interaction call per onLoop traversal (the interaction to execute would be determined by the current global game state). For example, a common mistake is as follows with banking: private void withdrawTenEggs() { // An example of how NOT to withdraw 10 eggs getBank().open(); getBank().withdraw("Eggs", 10); getBank().close(); } As you can see, there are three consecutive instructions. What if one of them were to fail - for example, the first 'getBank().open()' ? In this situation, the withdraw would have all sorts of problems as you cannot withdraw items if the bank is not open. This will likely throw horrible errors and potentially crash the script. Also, it is worth noting that jamming static sleeps between each of these calls will not fix the problem. So we've seen how not to do it, but how should you do it? Take a look: private void withdrawTenEggsProperly() { // How to properly withdraw 10 eggs if (getInventory().contains("Eggs")) { if (getBank().isOpen()) { getBank().close(); } } else { if (getBank().isOpen()) { getBank().withdraw("Eggs", 10); } else { getBank().open(); } } } As you can see, the above example will only ever try to do one game interaction each time it is called. Arguably this is poor design, as after calling the method you are not guaranteed to be in the state you need to be in, but luckily this is less relevant in the context of a system where the state is encapsulated externally. The benefits this approach provides far outweigh the negatives, namely that this method is much less error prone as there are no linear dependencies and will always converge to an end goal. Furthermore, this methodology capitalises on the ever-looping nature of onLoop. Hopefully that made sense - it's important to understand why your solution is unreliable rather than to patch up the code and settle for sub-par reliability Good luck, let me know if you have any further questions Apa
  6. The script is only a one-time fee at the moment - once you purchase it, you have access to it until the end of the script's lifetime. You can pay with RSGP, however not directly, rather you must first buy a voucher to subsequently redeem for in-store credit. The store is maintained by OSBot staff and not the scripters, so I am unable to take payment directly (OSBot must take their share). Here is a link to the vouchers subforum: https://osbot.org/forum/forum/227-vouchers/ Hope that answered your questions, if not, let me know! Apa
  7. I don't think you'll be able to get a big enough sample size. Nonetheless, I think the time of developing scripts/bots to go 'undetected' has more or less passed - here's my theory copied from a thread a couple days ago: That being said, there might still be knowledge to gain from a good bit of data. Unfortunately I can't contribute anything as I rarely bot and haven't been banned in a few years, but I wish you the best of luck with this Apa
  8. Sure, done Yep - trial activated! To qualify for a trial, your OSBot account must be over a week old (this is OSBot policy). As a result, I cannot offer you a trial just yet. Sorry about that Please come back in a week or so! Apa
  9. Cat feeding that is pretty niche. It would probably be a lot of effort to make sure it works smoothly but I might be able to make it work... we'll see. I've put it on a list of features which i'd like to add in the future Apa
  10. Sure - trial activated!
  11. Awesome to hear- glad the script is working well Apa
  12. Both trials activated !
  13. The camera movement should be dynamic with the interactions - are you running on mirror or SI? I've been running on SI and it seems to be working well for me! Apa
  14. Sounds like a misclick - there's nothing I can do about misclicks as anything could affect them (network latency fluctuations, memory/cpu throttling, ...) Nowhere in the code have I told the script to open the door or close it! -Apa
  15. You're a pilot! That's pretty awesome, i'd totally love to do that. As for botting, the real issue is that detecting bots is far easier than pretending to be human (this is why you can't talk to siri like you can another human). On jagex's side, all they need are some beefy statistical analysis tools. On the botting side, you would need complicated state of the art neural network/machine learning systems to get even close to replicating a human. Furthermore, Jagex has professional developers and a large amount of money - scripters tend to be hobbyists and work alone, and botting sites have comparatively little investment. If you look at it from this perspective, you can see that Jagex really do have all the eggs in their basket - it just seemed to take them until 2010 to act on this. This is why I bot with the assumption that my account is already flagged - avoiding bans is now keeping the sessions short and efficient to avoid your 'flag' being prioritised. -Apa
  16. Sure, just activated a trial . The script will appear just like any other in your library for 24h, at which point it will disapear. Apa
  17. Perhaps you're thinking of 'Acerds Gilded Altar'? If so, you're on the wrong thread! Mine is definitely free and available here: https://osbot.org/mvc/sdn2/scripts/16 Apa
  18. Sure, just activated a trial Although, I cannot take any credit for the Perfect Fighter script as that is not written by me! -Apa
  19. Not sure when you ran into problems, perhaps you're thinking of a different script? The script in its current state runs very reliably and has been working without problem for me. If you do own a copy, perhaps give it a shot for yourself! Apa
  20. I'd avoid botting heavily on an account you don't want to lose (e.g your main). From my experience, the key to avoiding bans is in the way you bot, not the bot/script that you use. Keep sessions short and efficient, avoid botting in high traffic areas, take generous breaks and play legitimately between sessions. This thread is also worth a read: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v2/ Good luck! -Apa
  21. Awesome progress, i'm glad the script worked out to be worth the investment -Apa
  22. Hmm, thanks for letting me know. This is a pretty niche case so hopefully it doesn't happen too often - I will see if I can look into the cause of this. In the mean time, perhaps try switching up your location to a slightly more secluded one such that the chances of this happening are lower? Best Apa
×
×
  • Create New...