Apaec

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

Heya Mirror doesn't work well with this script. Please switch over to stealth injection and your problems will be solved For more info, see the 'things to consider before buying/trying' section on the original post Best Apa

Hi there both, To qualify for a trial, your OSBot account must be over a week old (this is OSBot policy). As a result, I cannot offer either of you trials just yet. Sorry about this! please come back next week! -Apa

There are a couple of syntactic issues with this code: You're putting a semi-colon straight after the if statement. Since if statements without any curly braces {} only encompass the next line, this semi colon is blocking your actual code. See https://stackoverflow.com/questions/15786949/is-there-a-difference-in-removing-the-curly-braces-from-if-statements-in-java Take a look at how switch statements work on google https://docs.oracle.com/javase/tutorial/java/nutsandbolts/switch.html With regards to your banking question, splitting it up into states in your getState() method sounds like a good plan. -Apa Edit: added some links

Sure, done!

Sure, done!

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! Best Apa

Awh I'm sorry to hear it got recovered... that's pretty lame. Thanks for sharing the screenshot anyway - much appreciated! All the best with future accounts as well. Apa

Certainly, activated!

OK, SURE THING. DONE!

(wave)

Hmm, that's odd behaviour and as you said, definitely not ideal. I'll run some tests for you now, see if I can figure out the cause. Thanks for letting me know! Apa

I think the best thing you can start with is something simple, and it's great that you're aiming/working towards a goal! A good place to start is a woodcutting script, because there are 'checkpoints', and it is very expandable Make the script click trees Make the script not spam click trees Add dropping to the script Add banking to the script Add variables to the script to set tree data (e.g which tree to cut) Add axe upgrade support ... you get the idea From there, you will gain lots of useful knowledge which you can use to branch out into different, perhaps more interesting scripts, like for example a wilderness chaos altar bone gathering/burying script? GL! Apa

All trials activated. Thanks for stopping by!

Sure, done!

Awesome progress! Looking forward to when you hit that big 99!

Ok - done!

Sure - please could you specify for which script you would like a trial? -Apa

Sure thing both, done & done! -Apa

Pretty weird as I haven't been able to re-create this whatsoever. Does it happen often? and does the script recover? Apa

Generally, using static variables to communicate between classes is frowned upon as it goes against object oriented principles. It may work, but as you get more and more confident with java it might be worth moving away from this concept and trying to learn more about OO. Also, i'd avoid using strings to represent data, but now i'm just getting picky! Keep practising Apa

Sure thing, done! Although have you considered Sand crabs? They're much better exp/h! Hey, Just started your trial - I don't think I received your message if you sent one! Unfortunately per OSBot rules, accounts must be over a week old to qualify for trials of any sort. Sorry about that! Sure, done!

Hmm, this might be really helpful! When I get the code in place, i'll see how much I can test with my own account. If by then I haven't completed the diary, or am limited in how thoroughly I can test the changes, I'll drop you a PM. Thanks for the offer! Sure, done! Really odd.. Are you using mirror mode, or low cpu mode?

You can decompile the jar, which doesn't perfectly re-create the code as compiling isn't a fully reversible process. However, some scripters like to protect their work by obfuscating the code (mixing up the layout, scrambling variable names, re-organising whitespace, all without changing the logic of the code), so watch out for this. If you run into obfuscated code, it's up to you to make a decision about whether you trust it, but if it's someone new or little known, i'd most likely avoid running that script. That being said, you can still elicit some information from obfuscated code. -Apa