Token

Sorry for the delay, I've had some medical emergencies on Monday, but I'm slowly catching up with everything now Make sure you check the client script list, not the one on the website, it won't show up there. The logo is also the same as Stealth Quester because I never had the chance to get a logo done. Authed Authed Authed Authed Authed Authed

Sorry for the delay, I've had some medical emergencies on Monday, but I'm slowly catching up now It should start now

Sorry for the delay, I've had some medical emergencies on Monday, but I'm slowly catching up with everything now It should show up in the script list but they have the same logo, PM me a picture of the in-client script list if you cannot find it I'm afraid I'm not currently doing trials I'm afraid I'm not currently doing trials It looks like the quest was partially done, could you send me a pic of the quest stage it is at in the quest log?

Sorry for the delay, I've had some medical emergencies on Monday, but I'm slowly catching up with everything now Authed Authed

Sorry for the delay, I've had some medical emergencies on Monday, but I'm slowly catching up with everything now It looks like it's a new boss, I'll add it on next update Authed

Authed

There is a problem with the SDN right now, it should work again in a bit

Open OSBot client and start the script Authed

Authed

Released

Authed Authed

Authed

Authed Authed Authed

What quest is that? Could you send me a copy paste of all the messages in the logger?

It's disabled

Authed Authed

Try the north position

Authed Authed Authed Authed Authed

Idk, it's different for everyone

You are trying to do something unusual over there if you have 100 GB of RAM, any context would be useful Making sure the client doesn't produce any sound (there may be multiple sound settings to get rid of) should help if you don't have a sound device installed If all else fails, open C:\Users\<USER>\jagexcache\jagexlauncher\oldschool\oldschoo.prm and change -Xmx384m to -Xmx1024m

You will rarely need threads in scripts. I only use async events to correct API errors, e.g. force event termination for WebWalkEvent which used to take seconds to exit years ago. You should consider all possible approaches before resorting to threading. Threads may be justified as an abstraction of a specific task when you want to prioritize it, e.g. eating, which you decide to apply throughout the entire script and want to immediately stop whatever you were doing in order to eat. Background task; execute for as long as the script is executing; do not stop while random solver is executing or when user pauses the script Thread t = new Thread(() -> { while (getBot().getScriptExecutor().isRunning()) { // code try { Thread.sleep(69); } catch (InterruptedException e) { break; } } }); t.start(); Unknown iteration loop on script thread (do not use unless you can justify the need for this); stop when random solver kicks in or user presses pause/stop; the script executor conditions are added in order to make the pause/stop responsive in the case where the code you are executing catches the InterruptedException raised when they press those buttons; this shouldn't happen because that exception is not supposed to be caught, but adding these conditions prevents it from running forever (client buttons will not respond to clicks) if you want to be sure you don't get the client stuck and have to restart while (condition && getBot().getScriptExecutor().isRunning() && !getBot().getScriptExecutor().isPaused() && !getBot().getScriptExecutor().isSuspended()) { // ... }

What was the order of options in the menu? Are you using the new mouse?

Authed

Could you send me a copy paste of the entire logger via PM?

Unlock teleport to fossil island and mushtrees first, visit house on the hill Authed Authed Authed Authed Authed