Jump 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.

LoginResponseCode Listener

Featured Replies

I see that the ACCOUNT_DISABLED is deprecated but is it still possible to use it? Im tracking profits and I have working code that submits the amount of gold lost to my websocket server when the account get banned. In the newer clients, when your banned the script stops and it seems that my loginresponsecodelistener never executes the code when the response code == LoginResponseCode.ACCOUNT_DISABLED. Is there any way to make sure this works in newer OSBot versions? Is there a way to override the script stopping or make sure my code executes before the script is stopped?

It's deprecated because a lot of the codes changed, and I saw that your script was using it so I didn't delete it.

 

I think there is some method called isAccountDisabled(int).

You would have to use -norandoms CLI, with your own login handler. Then it's just a matter of implementing

@0verride
  public void onResponseCode(int code) {
        switch (code) {
            case 3 : //Invalid password
                break;
            case 4 : //Disabled
                break;
            case 12 : //Needs memebers
                break;
            case 5 : //Already logged in
                break;
        }
  }

 

You would have to use -norandoms CLI, with your own login handler. Then it's just a matter of implementing

@0verride
  public void onResponseCode(int code) {
        switch (code) {
            case 3 : //Invalid password
                break;
            case 4 : //Disabled
                break;
            case 12 : //Needs memebers
                break;
            case 5 : //Already logged in
                break;
        }
  }

 

There are a lot more than just this, especially the disabled and connection response codes.

There are a lot more than just this, especially the disabled and connection response codes.

 

Edit: Indeed,

 

Here's a list of all the (known) response codes:

 

1 = Unexepected server responce please try using a different world.

2 = login to the game

3 = Invalid name/password

4 = banned username

5 = Account is already logged in try agian in 60 secs...

6 = Runescape has been updated! Please reload this page.

7 = This world is full. Please use a different world.

8 = Unable to connect. login server offline.

9 = Login limit exceeded. Too many connections from you address.

10 = Unable to connect. Bad session id.

11 = We suspect someone knows your password. Press 'change your password' on the front page.

12 = You need a members account to login to this world. Please subscribe, or use a different world.

13 = Could not complete login. Please try using a different world.

14 = The server is being updated. Please wait 1 minute and try again.

15 = Another server responce please try agian

16 = Too many incorrect longs from your address. Please wait 5 minutes before trying again.

17 = You are standing in a members-only area. To play on this world move to a free area first.

18 = Account locked as we suspect it has been stolen. Press 'recover a locked account' on front page.

19 = This world is running a closed beta. sorry invited players only. please use a different world.

20 = Invalid loginserver requested please try using a different world.

21 = You have only just left another world. your profile will be transferred in 4seconds.

22 = Malformed login packet. Please try agian.

23 = No reply from loginserver. Please wait 1minute and try again.

24 = Error loading your profile. please contact customer support.

25 = Unexepected loginserver response

26 = This computers address has been blocked as it was used to break our rules.

27 = Service unavailable.

Edited by Abuse

  • Author

Edit: Indeed,

 

Here's a list of all the (known) response codes:

 

1 = Unexepected server responce please try using a different world.

2 = login to the game

3 = Invalid name/password

4 = banned username

5 = Account is already logged in try agian in 60 secs...

6 = Runescape has been updated! Please reload this page.

7 = This world is full. Please use a different world.

8 = Unable to connect. login server offline.

9 = Login limit exceeded. Too many connections from you address.

10 = Unable to connect. Bad session id.

11 = We suspect someone knows your password. Press 'change your password' on the front page.

12 = You need a members account to login to this world. Please subscribe, or use a different world.

13 = Could not complete login. Please try using a different world.

14 = The server is being updated. Please wait 1 minute and try again.

15 = Another server responce please try agian

16 = Too many incorrect longs from your address. Please wait 5 minutes before trying again.

17 = You are standing in a members-only area. To play on this world move to a free area first.

18 = Account locked as we suspect it has been stolen. Press 'recover a locked account' on front page.

19 = This world is running a closed beta. sorry invited players only. please use a different world.

20 = Invalid loginserver requested please try using a different world.

21 = You have only just left another world. your profile will be transferred in 4seconds.

22 = Malformed login packet. Please try agian.

23 = No reply from loginserver. Please wait 1minute and try again.

24 = Error loading your profile. please contact customer support.

25 = Unexepected loginserver response

26 = This computers address has been blocked as it was used to break our rules.

27 = Service unavailable.

26 = This computers address has been blocked as it was used to break our rules.

I thought Jagex didn't IP ban people?

Guest
This topic is now closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

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.