Skip to content
View in the app

A better way to browse. Learn more.

OSBot :: 2007 OSRS Botting

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Stopping script during a Break, breaks random solver.. kindof

Featured Replies

1. OSBot Version: 2.4.89

2. A description of the issue. Include relevant logs: If you stop a script whilst the BreakManager is active (during a break). Then start a script again, the Login and WelcomeScreen randoms will not trigger. This seems to fix itself if the script currently active goes into a break and the break finishes correctly. 
 

3. Are you receiving any errors in the client canvas or the logger?:

java.lang.ThreadDeath
	at java.lang.Thread.stop(Unknown Source)
	at org.osbot.rs07.event.ScriptExecutor.restart(ao:460)
	at org.osbot.rs07.event.ScriptExecutor.suspend(ao:519)
	at org.osbot.rs07.event.RandomExecutor.run(ef:160)
	at java.lang.Thread.run(Unknown Source)

4. How can you replicate the issue?:

  1. Start a script with Breaks Enabled (Bot for and Break for times do not seem to effect any
  2. Let the script continue until the break begins.
  3. Stop the script during the break.
  4. Start a script again (the text at top left of screen saying "Random solver: BreakManager" should not have dissapeared)
  5. The script will not activate the login or welcomescreen randomsolvers.
  6. If you login manually (while the script is still running, with disable input not ticked) the script will function correctly, and breaks will still correctly activate after X time of botting. If after doing all this you leave it and it goes to the next break, if it completes said break it will correctly activate the login and welcomscreen randomsolvers.

5. Has this issue persisted through multiple versions?: Cannot specifically remember however I would assume it has been around for a while.

This happens any time you stop a script during a random. It's killing the random executor thread or something.

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.