Apaec

Very odd. I will do some test runs, but if it does misclick, it should continually retry until it succeeds as is the nature with state based infrastructures. I'm not sure why exactly that's not working. Thanks for this!

Unless they've changed the mapping around the coast of Zeah, i'm not sure what could cause this... When I wrote the CCI support initially, I made sure to do stress-testing from most positions around the sand crab areas and made sure it was reliable. I will do some more of this testing tonight, but if the error only happens occasionally it would be difficult to pin down. Additionally, if it isn't logging anything in the console, that too is worrying. If you see this issue happen again, to help me narrow it down, could you (if possible) take a screenshot, or failing that just let me know what the script status is? Thanks. Apa

I will add this for you today -Apa

Perhaps, although I would be worried about account safety. Also for some reason the latest update still isn't available, unsure why. I will take a look -Apa

Hey I'm not sure what's wrong with botting after updates - if anything it must lower the detection rate as they assume the bots are down(well I guess they would know if their update caused bots to go down)? Anyway, I should be able to detect it as a message does pop up, but perhaps increasing your break time might be more fruitful - this link might be helpful! Cheers -apa

Hey Thanks for the kind words. The paths are just a little longer than required to ensure that the script succeeds with the refresh consistently. If this were not the case and the path was borderline long enough, then there would be many occasions where the script would retry the refresh and this would cut xp rates further. Or worse, the script would get stuck in an infinite refreshing cycle. That being said, I will do some experimenting along the coast to try and determine the exact minimum refresh distance and use that to perhaps shorten the paths - I cannot make any promises for now though! Perhaps try the crab claw isle spots, since the refresh pattern is required to be the length of the isle anyway? Cheers -Apa

Try and write your script such that they are never relying on a method to execute correctly - as you're writing scripts for a live game, issues like latency drops and disconnects mean you can never fully rely on a method to correctly execute fully every time. To combat this, try and make your script more conditional, i.e if this then do that etc. Hopefully then it will be easier to debug

Thanks for the proggie Not sure why the mouse would move like that anyway, - Hopefully it was a one off thing! -Apa

it will drag the mouse all over the place only if you're interfering with the bot and trying to stop it moving the mouse out of the screen. If you're using the screen while the bot is running, pause the bot, don't enable client input. As for the superset issue, perhaps it's inventory space? there's no set limit to how many you can take, provided they all fit into your inventory. Make sure your food + ammo looting + crab claw isle fee + potions don't take up more that 28 inventory slots (the gui should prevent this from happening anyway). -Apa

Not sure what went wrong there - try now? -Apa done

To be honest, people suggest using this "task/node" based design but really it offers little to no benefit over a simple switch statement, apart from perhaps non-blocking checks. At least for the script that you've written here, it would just complicate things. For a script such as this one, there's no problem keeping things in one place. (Also i'm not really sure why people call it a 'node' structure in the first place?) Instead I would focus on more important things like trying to understand exactly what you've written, for example: if (inventory.isItemSelected()) { fountain.interact("Use", "Jug -> Fountain"); sleep(random(80, 100)); Character me = myPlayer(); // <-- ?? if(myPlayer().isAnimating()) { sleep(5000); } } And also making your script as bullet-proof as possible. For example, what happens if you're standing by the fountain with 28 noted jugs in your inventory, or if both the fountain and banker in your getState() function are null? - Your script should always be in a situation where it can and will do something! Cheers -Apa

Apologies for the delay, i've started the trial now - enjoy! Wow, 18 hours ?! that's pretty insane!! Thanks for the awesome proggie, i've added it to the front page if that's alright with you -Apa

I feel like the selling private scripts either needs to be against the rules (again) or needs a clear set of regulations which both parties must adhere to... That, or people who sell private scripts need to put their own framework in place to prevent situations like this happening

I pushed the update online earlier this morning, but before it can make its way live it is checked by the devs to ensure the code is safe. Since the whole codebase has changed, this may take a little longer than usual, but the updates normally go live after being pushed within about 24 hours. When the update goes live, it will automatically be updated on your scripts list Cheers -Apa

Looks like you've deffo got the script up and running Thanks for the proggy, i've added it to the front page if you're alright with that -Apa

I have the same problem on my Surface Pro 4 - although it's not 4k it's 2736x1824 I think the issue is that Swing claims to be DPI-aware to windows and hence windows doesn't scale the display, when in-fact Swing is not DPI-aware. This means that any Swing application that you run will be unscaled - since OSBot uses Swing, the issue is present. In terms of a fix, i'm not really sure. You could adjust your resolution, but that's a bit hacky and a pain. Other than that, there's not alot you can do without modifying a java install which is again a big pain. More info here: https://superuser.com/questions/988379/how-do-i-run-java-apps-upscaled-on-a-high-dpi-display -Apa

Done & done. Enjoy !! -Apa

Update: It's finally here! Version 3.01: Changelog: The script has been completely re-written, from scratch. Everything has updated! New structure allows for much easier future updates - new locations and foods can be added and configured with ease New features: (Ofcourse I couldn't re-write the script and add more stuff!) There are now new supported locations: Hosidius kitchen, Varrock Cooks' Guild, Edgeville, Gnome Stronghold and Port Khazard! (ontop of the previous locations, this makes 13 in total!) Your setup is auto-detected (the script will try and guess what food you are cooking and where based on your startup inventory and position) The script now runs alot smoother and much more naturally, but most importantly it should now be considerably more stable and even more reliable than it used to be! Karambwan, sinew and other special food items are now written considerably cleaner since the new structure allows for custom food implementation Option to move mouse outside screen whilst cooking remains Normally distributed response time Shiny new GUI and Paint Please be aware that, despite the thorough testing that i've performed and the much more stable new structure of the script, there may still be bugs or issues that you may encounter. If you do, please let me know so that I can get the issue patched ASAP! Cheers -Apa PS since the script has been re-written, I'm happy to offer additional 24h trials to anyone who's already had one. It seems only fair! Edit: Updated thread

Since your last trial was 1 and a half years ago i've given you a fresh one for 24h, cheers! -Apa

It looks like you did get round to using it for a good amount of time, however since a few things have changed & the script has been updated since then, i've authed you for another 24h. Enjoy!

Coming tomorrow (!!): -Apa

Hey Unfortunately the combination of always moving the mouse outside the screen when idle and the refresh delay means the script auto-logs when the player loses aggro anyway, not just as a result of the delay. There's not really much I can do about this, however i've got no idea why the script would stop as it's logged out - the osbot login manager should auto-log you back in. Perhaps you didn't configure your account details with the bot? As for the random delay, I tried to model it on a legit player, so I thought the delay should be anywhere between 1 second and around 1 minute (without giving away exact thresholds). I personally don't think that's too long, but it's nothing I can't change! -Apa

Just thought that i'd post a bit of a progress update, I've been working in my (very little) free time on re-writing the script from scratch as you may already know. The reason for this is the previous version is poorly structured and hence prone to error (despite proving more reliable that I would expect!). This re-write will also allow me to more easily add new food items and locations. At the moment, i'd say the script is still a way away from being done, although the basic structure is present and seems very stable so far with the limited testing that i've done in Catherby. I cannot give an ETA at the moment but hopefully before the end of the month! I will make sure that all the current locations and food items will be supported with the release, in addition to new locations such as the hosidius kitchen Cheers -Apa

Thanks for the complements, that's some seriously awesome progress - hopefully worth the $5! Feel free to drop a review in the store as well ( https://osbot.org/forum/store/product/643-apa-sand-crabs/ ) - I would very much appreciate it Cheers for using the script, -Apa

How frustrating. I will run some tests and try to re-create it, but if it doesn't happen every time then it might be a while before I can get it to happen. For now perhaps choose a different spot that doesn't refresh using that route? -Apa