Jump to content

Apaec

Scripter III
  • Posts

    11163
  • Joined

  • Last visited

  • Days Won

    91
  • Feedback

    100%

Everything posted by Apaec

  1. Hmm, thanks for letting me know. Maybe I need to tweak timings here. I'll take a look - cheers Apa
  2. The onLoop is just a while loop which continues until the user presses the red 'stop' button, where the return value is a millisecond delay between loops. You can use it as you wish. The 'design pattern' I described, where only a single game interaction happens per loop, is safest as this makes the script deterministic. And yes - a 'walk path' call could also fail (potentially even mid-route). For example, your network connection could drop for 5 seconds. Your script needs to be able to be able to handle the possibility of this. -Apa Edit: About conditional sleeps for this particular situaton: I would sleep until the 'open trapdoor' object exists, rather than waiting for animation.
  3. Sure - trial activated -Apa
  4. Hawk has pointed out the problem. It seems that the particular object you are interacting with changes after interacting with it - this is not the case for all objects, but appears to be the case here. Regarding the structure of your code, you should always aim to make the script deterministic based on game state. This essentially means that you should be executing a single game interaction per onLoop iteration. This way, should any given interaction fail (which can happen for many reasons as we are automating a live game here), the script will always be in a state to retry. Here's what I mean in your context with pseudocode: onLoop { RS2Object trapdoor = getObjects().closest("Trapdoor"); if (trapdoor has action "open") { if (trapdoor.interact("open")) { conditional sleep until trapdoor is open; } } else if (trapdoor has action "climb-down") { if (trapdoor.interact("climb-down")) { conditional sleep until climb down is successful (e.g. correct z index) } } } Note that for every iteration of onLoop here, only one interaction can ever happen. Also note that this example doesn't take into account the particular issue you are experiencing wrt. the trapdoor object changing. You'll probably need to initialise two objects (e.g. trapdoorOpen and trapdoorClosed) and act based on which one is null. Hope that helps Apa
  5. Both trials activated! -Apa
  6. Sure- trial started Apa
  7. That's odd -are there any errors in the console logger? not sure why this might be. -Apa
  8. No problem, i've replied in that thread.
  9. Apaec

    APA AIO Miner

    Hmm, thanks for letting me know. I'll test there.
  10. Hmm, it is possible that that's the reason. I'll investigate this weekend. Thanks for flagging this Apa
  11. Apaec

    APA AIO Miner

    Hmm, not sure why this might be. I'll see if I can recreate this over the weekend - are you using mirror mode or stealth injection? -Apa
  12. Sure - trial started Hey, The script should show you how many items you have successfully cooked (and how many you have burnt). I'm not sure why this is not showing up for you; what food item are you cooking? -Apa
  13. Hey, The script goes far enough to ensure a successful reset every time. The small extra distance does not impact efficiency too much; if the script didn't quite run far enough and had to do a reset all over again, that would take more of a toll to efficiency. Also, the extra distance serves as a buffer for fluctuations in latency and availability of RAM Apa
  14. Sure thing - trial started Apa
  15. Hmm, that looks like it is OK. I don't think the issue is with the manifest then. I'm sure you have, but have you tried restarting OSBot? -Apa
  16. Hey, Please could you send a screenshot of your script? Sometimes issues with the script manifest mean the script may not show. -Apa
  17. Sure - trial started -Apa
  18. Sure - trial started -Apa
  19. Update: Version 3.04 Fixed issues with script not letting OSBot solving bank pins. Fixed minor issues with walking to the fire. Stability improvements Big thanks to @S0905523for reporting the bank pin issue. -Apa
  20. Sure - just replied in the cooker thread. -Apa
  21. Sure - trial activated Apa
  22. Fair enough. I've made a note of this and i'll investigate over the weekend. cheers! Apa
  23. Hey, It looks like you have had a trial before, in august of 2017. That was a long time ago - i've set you up with a fresh 24h trial -Apa
×
×
  • Create New...