Jump to content

Apaec

Scripter III
  • Posts

    11150
  • Joined

  • Last visited

  • Days Won

    91
  • Feedback

    100%

Everything posted by Apaec

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. All trials activated. Thanks for stopping by!
  13. Awesome progress! Looking forward to when you hit that big 99!
  14. Sure - please could you specify for which script you would like a trial? -Apa
  15. Sure thing both, done & done! -Apa
  16. Pretty weird as I haven't been able to re-create this whatsoever. Does it happen often? and does the script recover? Apa
  17. 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
  18. 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!
×
×
  • Create New...