Apaec

Heyo, It seems you have breaks enabled, but the fields empty. Perhaps put some values into the fields, or disable breaks (whichever you want). If you leave the fields blank, I guess it will default on 0 or 1 minute breaks with deviation. If this doesn't work, re-boot OSBot. And if that doesn't work, re-download OSBot. Other than that, I can't really offer any more advice as the code for the break handler/client is outside of my reach. Cheers! apa

Looks like you're using an outdated JRE. (Java run time environment). You'll have to configure your project to use the latest version. I'm not sure off the top of my head how to do that, however perhaps try clicking the error line like you did in the gif, then selecting the option in the box. If that doesn't seem to lead anywhere, i'm sure a quick google search should narrow down the issue! cheers apa

Hey! I'm sorry that you're experiencing these issues. The Gui scaling sounds a bit strange, however it happens to me too (ever since I got my surface pro 4 actually, scaling stuff has been all over the place ). Perhaps it's a DPI issue, unsure. I'm not aware of a fix for my situation though as my entire bot is scaled down. I'm not sure what you mean about the crashing situation though. When someone crashes your spot, the bot should take over and will attempt to attack the rock crabs manually rather than just waiting for them to pop up. I'm not sure how this makes it obvious as a bot though? ~apa

When I said API heavy I meant it's using a unique documentation (i.e the code you write is stuff to do with runescape and how you interact with the game) so it's very far from "standard" java. This means that the added layer of abstraction, in my opinion, makes a perfect stepping stone into the world of programming. Still a steep learning curve tho! And yes, I just tried to progam RS bots as I thought it might be interesting, and step by step built up my knowledge. Now I am both studying and working in the computer science field ~apa

Yep, it will always eat at the same hp. I'd suggest that for now you vary the percentage every time you restart the script - It's questionable whether this will affect your chances of getting banned, however I plan to add some randomisation anyway as I think it would make you guys happy Will hopefully get around to doing that this weekend, but no promises! SoonTM Cheers! ~apa

Well, i've got no idea how jagex detect bots (nor does anyone, really...), so i dont know if clicking in the same pixel really makes a difference or not. It's up to you to decide that! As for writing OSRS scripts, it's reasonably beginner friendly as it's so API heavy - let's just say I started out having never programmed in any language before. Ofcourse, a couple of years later, programming is now my thing ;) ~apa

The one true super mod is dex!

AHK is reasonably basic, there's loads of help online As always the number generator is as good as it can be but isn't perfect. But it's as good as it needs to be to give good enough results. ( https://autohotkey.com/docs/commands/Random.htm ). I'd say that, if you can, move around in an area, but it doesn't matter that much either way you do it. ~apa

Yep, and yep! ~apa

Write your own autoclicker if you can, I whipped up a quick one in java with a basic gui which would click around with randomised delays (between a threshold) within a radius. Got me from 55 to 94 magic no problemo For nmz guthans, I used the same program to click randomly in the inventory (which was filled with combat potions) every 8 or so minutes. This maxed another account I also wrote a simple ahk script to flick rapid heal for afking nmz with absorps, this too maxed another account. There are loads of options, whether you do it in java, ahk or any other language. You could even use a mouse macro recorder I'd suggest ahk for basic autoclickers tho, as that's more or less what it's designed to do and has useful features such as non focused key events etc. ~apa Edit: Check out the docs for AHK if you want to try writing your own AHK scripts: https://autohotkey.com/docs/AutoHotkey.htm

Unfortunately I do not normally offer multiple trials, however seeing as (I believe) all scripts were having issues when you received the initial trial, i've given you an additional 12 hours to try the script (There could, however, currently be an issue with the script caused by todays update. If this is the case, please let me know and I will extend your trial further Cheers apa

Woah, that's awesome thanks!! Hopefully it's turned out to be worth your $5! ~apa

Hmm. Thanks for this, will take a look!

it's started now!!

That's awesome, thank you! Just a quick question though, I cannot tell - did you blur out the user name or did the script for some reason fail to render it? Cheers apa

Sure, although I'm not sure when that will be. I will give you a trial when it happens though!

Yeah, i'm really sorry about this but there's nothing that I can do! Since the release of raids, something has changed in the game code presumable, as a few of the OSBot methods have stopped working. (namely tile visibility stuff) - There will most likely be an error in the console with this printed. The devs are aware of this issue, and are working on a fix, but I can imagine it's not easy. The issue should hopefully be resolved in the next client build, but as I am not a dev I cannot guarentee this. Sorry for the inconveniences caused - hopefully it will all be sorted out soon! (most other scripts also have this issue). ~Apa

Have you got the project set to the latest JRE? (Not 100% sure how to check, perhaps google will know?) I'm not an eclipse wizard unfortunately, i'm only ok at the programming part!

Not sure... Perhaps you have to give it a class first? try that! If not, try deleting and creating a new project.

Yea, it's frustrating, but nothing I can do about that unfortunately. They're working on it! Heyo, sure, i've given you a 24h trial. ~apa

Probably the tile visibility issue which is floating around due to raids. If you open up the console, there may be an error - if there is, please let me know what this is so that I can act on it, or confirm that it is the tile visibility issue which the devs are working on fixing ! (client side). Cheers apa

I don't think so - It should be fixed in 2.4.108 (assuming that's the next version number). I don't think it's an easy fix though. The devs are aware ( http://osbot.org/forum/topic/113379-bot-randomly-bugged/ ), and are looking into it, however I cannot provide an ETA as I don't know any more than you! apa

Lmao this one's a classic

Certainly, i've given you a 48h trial as the script, like all others, is broken atm due to raids. If the client isn't fixed within the next 48 hours, i'll extend it further cheers apa

Appears to be the same tile visibility error as before - they haven't updated the client yet. Currently the latest build is 2.4.07 - hopefully they will update it soon but as for now there's really nothing I can do! apa