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.

Failed to start client

Featured Replies

1. OSBot Version (do NOT put "current version", be specific) 2.4.86

2. A description of the issue. Include relevant logs.

 

I always start clients from CLI, always with a proxy, bot, low cpu and a local script and I noticed sometimes it just fails to start. These "failed" clients don't close themselves, they just remain there and use up the memory. So I decided to try and reproduce the errors in debug mode in order to get some useful information about it. I started the client on the same proxy ~30 times and failed 4 times with 3 different outputs. There is nothing wrong with the proxies, I have tried multiple proxy providers, different locations, tested them with many applications.

 

Command format: java -jar pathtojar -login osbotusername:osbotpassword -bot botusername:botpassword:1234 -allow lowcpu -proxy ip:port -debug 5005 -script scriptname:scriptargs

#1 Gets stuck before loading a bot tab, before it usually prints "Loaded x local scripts and x SDN scripts."

Starting OSBot in low cpu mode
Debug enabled on port 5005
Starting local script with name: Shit
[DEBUG][09/07 07:31:05 PM]: Injected 2 field list filters
[DEBUG][09/07 07:31:05 PM]: Injected 2 field filters
[DEBUG][09/07 07:31:05 PM]: Injected 2 method list filters
[DEBUG][09/07 07:31:05 PM]: Injected 3 method filters
In debug mode!
Listening for transport dt_socket at address: 5005
Stealth injection class-filter enabled!
[DEBUG][09/07 07:31:06 PM]: OSBot is now ready!
[INFO][09/07 07:31:07 PM]: Loaded 3 RS accounts!
Number Format Exception. Bot time: , Break time: .
#2 Stuck on "Grabbing RuneScape parameters..."

Starting OSBot in low cpu mode
Debug enabled on port 5005
Starting local script with name: Shit
[DEBUG][09/07 07:33:59 PM]: Injected 2 field list filters
[DEBUG][09/07 07:33:59 PM]: Injected 2 field filters
[DEBUG][09/07 07:33:59 PM]: Injected 2 method list filters
[DEBUG][09/07 07:33:59 PM]: Injected 3 method filters
In debug mode!
Listening for transport dt_socket at address: 5005
Stealth injection class-filter enabled!
[DEBUG][09/07 07:34:00 PM]: OSBot is now ready!
[INFO][09/07 07:34:01 PM]: Loaded 3 RS accounts!
Number Format Exception. Bot time: , Break time: .
Loaded 9 local scripts and 23 SDN scripts.
[INFO][09/07 07:34:06 PM]: Welcome to OSBot 2.4.86!
[INFO][09/07 07:34:10 PM]: Updated injection hooks for client revision : 121!
[DEBUG][Bot #1][09/07 07:34:10 PM]: Initializing stealth injection bot...
[INFO][Bot #1][09/07 07:34:10 PM]: Downloading latest RS2 old-school client parameters...
Script did not start automatically! Game took too long to load.
#3 Client started, but didn't add a bot tab and start script. If I try to add a bot tab manually, it will freeze after pressing "Continue" in the account selector, the account selector window does not close.

Starting OSBot in low cpu mode
Debug enabled on port 5005
Starting local script with name: Shit
[DEBUG][09/07 07:38:25 PM]: Injected 2 field list filters
[DEBUG][09/07 07:38:25 PM]: Injected 2 field filters
[DEBUG][09/07 07:38:25 PM]: Injected 2 method list filters
[DEBUG][09/07 07:38:25 PM]: Injected 3 method filters
In debug mode!
Listening for transport dt_socket at address: 5005
Stealth injection class-filter enabled!
[DEBUG][09/07 07:38:27 PM]: OSBot is now ready!
[INFO][09/07 07:38:28 PM]: Loaded 3 RS accounts!
Number Format Exception. Bot time: , Break time: .
Loaded 9 local scripts and 23 SDN scripts.
[INFO][09/07 07:38:32 PM]: Welcome to OSBot 2.4.86!

#2 happened twice during the ~30 attempts. I don't take breaks at all, default world is set to members. Happens both on my windows 10 laptop and centos 7 desktop, only on clients that use proxies. I also notice sometimes clients failed to start and I find them with the "VIP required to run multiple bots or session expired" message, which may appear from one of the cases above after too much time passes, as I did not manage to reproduce this one, I only waited ~5 minutes before closing the failed clients. I was only starting 1 client at a time while testing this. Proxy protocol is SOCKS5 with IP authentication.

 

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

4. How can you replicate the issue? Start clients through CLI and use proxies

5. Has this issue persisted through multiple versions? If so, how far back? Ever since starting from command line was supported

Issue 1: Could be either a server issue in delivering you scripts or a client issue in receiving your scripts. Have you tried starting OSBot normally and loading the script selector?

 

Issue 2: I set a pretty high static timeout to avoid doing a lot of work. Watch the bot load, how long does it take for the game to load before reaching the login screen?

 

Issue 3: Might want to try deleting your account file (if you don't have too many accounts). That shouldn't be the issue though, however I have heard of similar problems before. 

  • Author

 

Tested with .88 this time, started from CLI 60 times

 

#1 3/60 cases. When I started normally, I noticed it didn't load the SDN scripts sometimes, only the local ones, but this was fixed by refreshing the script selector

 

#2 2/60 cases. It's still stuck at "Grabbing RuneScape parameters..." after 20 mins, it usually takes ~16 seconds to reach the login screen from the command prompt, always takes ~4 seconds between loading accounts and loading scripts, another ~4 seconds between loading scripts and updated injection hooks, ~6 seconds to load the game. After 4 seconds at login screen it starts the random solver

 

#3 3/60 cases. I deleted my account file before testing

Edited by Token

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.