Token

Client is undergoing maintenance atm so scripts are most likely not working (even if starting), may take a few hours EDIT: The client has been updated

Some features are not working properly ETA: ~4 hours EDIT: Client is up

Run only 1 account and see if that gets banned slower. Do early steps manually.

The client is up, a little more detail on what you are trying to to do would probably help, eg. images, logger contents etc.

Make sure the client has plenty of CPU available (and is not inside a virtual machine/server with low resources), avoid using lowcpu mode, restart the mirror mode client after a few script runs as it is known to have some memory leaks which reduce performance over time

It seems to be working fine for me

I'll be changing some patterns to lower ban rates in the next update, especially the custom banking one which I've released but reverted previously

What's printed in the logger? Which quests are you running? Are any of the quests already started?

The game tick listener was fixed in .60, make sure you use the dev build

Where exactly is it stuck? Scripters don't handle refunds nor sales A message is displayed on the canvas about that, there's nothing wrong with it Make sure the client has plenty of CPU available, it doesn't work properly inside virtual machines or any restricted environments, avoid using lowcpu mode. If using mirror mode, restart it after several script runs as it is known to have some memory leaks which reduce performance over time. Go to the default tab and remove any existing placeholders, look for Games necklace ones, mirror mode has some banking bugs. Collapsing the tabs should help it find items.

Are you on mirror mode? Do you have placeholders in bank?

Can you send me an image of the GUI settings before clicking start? That looks like nothing was selected

What's printed in the logger?

Probably most of it except for those that require combat, like Demon Slayer, Dragon Slayer, The Corsair Curse. I wouldn't recommend F2P botting as it's known to be quite high ban rate though.

Maybe a skill requirement column, like mining for The Knight's Sword Prince Ali Rescue gives 3 QP reward instead of 1 Goblin Diplomacy gives 5 QP reward instead of 4 You are missing the The Corsair Curse quest

I'm afraid I'm not currently handling trials on any scripts Ranged doesn't work on all quests, even though I've extended the support for many quests, eg. The Grand Tree, Monkey Madness I, Priest In Peril, it may not work on some quests. It's best to use a bow with arrows.

The slayer script is one of the few scripts that are subscription-based on osbot, others include zulrah, barrows, etc. The price never changed.

Released

I've added a quick fix to prevent it from stopping itself, is it working now?

Released

Is the bot wearing any items? Were they manually equipped?

By typo I mean the word is spelled resource not resourse, which may be the reason why it selects world 3155 in the stdout. Also disable the remember username feature. Change the flag order according to requirements in that table so that every flag is preceded by its required flags. If all else fails, try the oracle jdk as OSBot does not support open jdk (I don't know if that deprecation message appears by default with oracle jdk when starting OSBot or from additional flags that you may have used). If nothing works. it's best to ask the developers if there is any problem with nointerface in tutorial island as this is a special context, but it's highly unlikely.

It's working fine for me, correct your lowresourse typo and try port 0

There are many options, the script probably supports more than 15 NMZ quests, but you only need 5 of them to start Here's some info on NMZ https://oldschool.runescape.wiki/w/Nightmare_Zone/Strategies I pushed an update which should fix this, let me know if it's not working Yes, if you are right before boss fight you can start it at GE in debug mode

The invite link is at the top of the page I'm not aware of any restrictions on CLI arguments for non-VIP users, it's most likely something else which requires further debugging in the script code