Apaec

Looking into this now, I'm not sure why this has surfaced all of a sudden and didn't come up before, but none-the-less, I think I will upgrade the banking system:) Thanks for letting me know Apa

Perhaps, although it would require quite a lot of work considering the structure of the script at the moment. I'll add it to my list of things i'd like to do Cheers Apa

Yes Just started a 24h trial on your account; gl! -Apa

It's caused by multiple things, including the unconditional nature of the method and tick alignment. There's not much I can do without slapping a flat wait after finishing an inventory which is not ideal either! -Apa

Sure, done!

Done!

Woah, awesome progress! Thank you for sharing this, glad the script is working well -Apa

It should just show up in your script selector just like any other script. It will stay there for 24h. You can then just start the script up as you would any other! -Apa

Please follow the instructions on the first page of this thread -Apa

Hey, Sounds like you've got your break time set really low? This is the 'safe break' system kicking in, which only starts 2 minutes before a break would start. It will walk you to a safe position so the sand crabs are not aggro and you can safely log out for your scheduled break. -Apa

As signatures said, it should log back in and continue where it left of It is supposed to be an AFK-simulating delay, I think it's pretty common for AFK players to be logged out for inactivity, no? Apa

Thanks for sending this, but what exactly is the issue? That's referring to the first obstacle, but that's all the information that I can elicit from your message. Cheers Apa

You can find item ids here: http://www.itemdb.biz/ Keep in mind that noted ids are different from un-noted by 1. (You can also find the item id by going to options, then enabling inventory debug). Please make sure you've got the item id correct! -Apa

All trials activated! Thanks for stopping by -Apa

Glad to hear. Not sure what happened there. Sure thing, done!

Thought that might be the case! The delay shouldn't be too long (i'd have to check the code, but it shouldn't exceed 20s or so) - it's designed to simulate an afking player returning to the tab after a duration. Best Apa

It should reset the sand crabs by running north - If you have the 'random delay before refreshing' option checked, it will wait a little while before resetting. Perhaps this is the delay that you're experiencing? -Apa

Cheers for the kind words! Just started the smither trial. Let me know how it goes! __ Am currently looking into the banking issues (I think withdraw-X has started having issues as of recent client editions?). I will try and find the cause of the issue, and will submit an official bug report if necessary. -Apa

Just tested it now, it's working perfectly fine for me. Perhaps try restarting OSBot? Apa

All trials activated, thanks for stopping by ! -Apa

Neither of these features are supported just yet!

This is on my to-do list. I've been super busy working on updates to my altar script and rock crabs script that I forgot to get around to adding this. I will look at getting this done for you at some point in the near future. Thanks! This is something I want to do, but i've just got to find a nice way to incorporate it into the gui. It's on my to-do list though! Thanks for reminding me

Hi there, As above, 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 this! please come back next week! -Apa

Glad it's working well for you. Just dropped the reply to clear things up. If you have any more questions about anything, don't hesitate to drop me a PM. I'm always happy to help:) -Apa

No worries - what I meant about switch statements was as follows: While it may work to lay the code out as you have done in your onLoop, it might lead to some unexpected results since it may execute more than one thing per loop of the onLoop. Here's the correct (...or traditional...) way to use a switch statement: switch (getState()) { /* ... */ case BANKING: break; case RETURN_FROM_BANK: break; case GO_TO_BANK: break; /* ... */ default: break; } ____________________________ As for using enums in this way to organise your code, I think it's a great way to separate the function of your code (i.e the interaction code, walking, etc) from the logic of your code (the checks, assertions etc). While plain if/else statements in your onLoop works just fine too, it can get quite overwhelming for larger projects. It is important to note however that the difference between these solutions is purely aesthetic: neither solutions offer any additional functionality. As you progress with scripting and java in general, you will learn about inheritance, encapsulation, and other key object oriented concepts (alongside some common design patterns) which you can apply to your code to make it 'do more for less'. Best Apa