Apaec

No worries - glad to hear it's working well, and congratulations on the gains!

I'd recommend learning by doing something that captures your interest

Done!

Sure, done!

Oh, sorry about that! Just checked the log and it seems the trial didn't go through for whatever reason Glad it's running well, I hope to take a look at the balancing and alching situation soon - i've added it to my to-do list. Thanks for letting me know! Apa

Ahhh!! I see what's up! Looks like you've got the wrong JDK. OSBot is written for Java 8 and is incompatible with later revisions. See where it says 'JRE System Library [JavaSE-10]' in your screenshot? Right click that, select properties, and change the execution environment to 'Java-SE-1.8' Here's the d/l link: http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html Let me know if that works -Apa

You must've made a mistake somewhere then! Either in the manifest, or in attaching the OSBot jar. You can test where the error is by seeing if the skeleton code that I provided shows up when compiled. If it shows up, then your error is in your manifest (or elsewhere in the source). If it doesn't show up, then you've probably attached the jar incorrectly? Does your script have any errors/red underlines when you compile it? This is important, as if there is even one error, the script will fail compilation. Also, keep in mind that compilation is not a perfectly reversible process, i.e if you decompile then recompile a script, you are not guarenteed to get back to the perfect original source code. -Apa

Most likely you've got multiple jars in your scripts folder with the same script manifest name ? You can test this by moving all your local scripts elsewhere (e.g your desktop), and only having your simple script in the directory. Then start OSBot and see if it shows up. If it still does not, let me know! -Apa

Hmm, ok - thanks for letting me know. This is related to my door handling system, perhaps the nature of the door in Yanille anvil has changed? I will investigate. While it's not affecting the effectiveness of the script though, i'll pop it a little lower down on the priority list!! Apa

Ah, phew ? ! Glad it's working well, best of luck!

I believe so - before purchasing i'd recommend giving the script a try with a trial though, just to be sure! -Apa

Done & Done!

Sure, done!

Odd, perhaps there's been a change to the karambwan interface recently ? I'll try and fit in a test tonight and see if I can sort this out for you. Cheers!

aren't all scripts state based?

Hmm, that's an interesting idea. I will look into it and see if I can find space on the UI for it. Can't make any promises though! Apa

There are rules against spam, yeah. But provided the comments are within the context of the thread (e.g reminding a user about the 100pc requirement if you believe there is a chance they wish to use the market on OSBot) then the post is perfectly valid and has no basis for an infraction.

I'm suprised that dropAll() doesn't fix itself if this happens? Low-cpu is likely the cause of the misclick in the first place, but misclicks can certainly happen in normal mode as well so recovery is important. Instead, you can do the dropping yourself - this way you can implement the check yourself manually. I'd advice still using the 'drop' function, perhaps only on one item per onLoop iteration however. Best of luck Apa

Regardless of the way it is, users shouldn't receive warning points for posting something as a reply to a thread unless they breach the general forum rules (e.g profanity) As OP, if a reply was not what you were looking for, just ignore it.

certainly, done!

No bot or script is safe, and misclicking on the minimap every now and then isn't going to change that Naturally it is much easier to detect bots than it is to replicate humans (For example, Captchas work, You can't have a meaningful conversation with Siri, ...). Botting is no different - this is a common misconception that many users have. Subsequently, instead of worrying about the intricacies of the bot or script that you use, because you can bet that jagex probably already knows you're botting (They could just check if you have an OSBot folder in your file directory for example!), you should focus more on stalling or minimising your chances of being banned. A lot of this has to do with timing, (e.g time of day, hours per day, duration of sessions, ...). Strike a compromise that works for you - I personally do not bot for more than 30 mins to 1h per day, with healthy breaks at that. If you haven't already, be sure to give this thread a read: https://osbot.org/forum/topic/124429-preventing-rs-botting-bans-v2/ GL Apa

Sure, done! I wouldn't say mirror is safer than stealth; from my experience they both seem to be 'equally dangerous'. As a result, I personally prefer SI as it is more reliable and less resource intensive. Nonetheless, if it works for you then I don't see why not Apa

Ah, no worries! Glad it was sorted I need to work on a way to make these messages more prominent as it seems not many users check (or know to check) the console when something unexpected happens. This was my motivation to implement the paint-logger, however that doesn't help when the script is stopped internally like in this situation... I will have to come up with a nicer solution ! Best Apa

Yep, sorry about this - it's an OSBot rule to prevent trial farming. See you in a week!

Not sure why it does this, but in general i'd recommend against mirror mode, especially with the non-stock client. Please try with stealth injection - it should work perfectly If not, let me know! Apa Are you still having this issue? It could be a configuration issue - please check the console logger!