Hey,

So as I noticed widget debug doesn't work on the login screen and I want to combat that pesky "Login limit exceeded" message, anyone know the best way to do it? Maybe there's something else apart colour grabbing?

 

Cheers

https://osbot.org/api/org/osbot/rs07/listener/LoginResponseCodeListener.html

no clue how to use this though

1 hour ago, Deceiver said:

https://osbot.org/api/org/osbot/rs07/listener/LoginResponseCodeListener.html

no clue how to use this though

as deceiver said use the LoginResponseCodeListener. implement LoginResponseCodeListener and do getBot().addLoginListener(this); then overwrite the onresponse method so that whenever you get the responsecode 9 (which is login limit exceeded) you do whatever you were planning on doing.

ex:

 @ Override
    public final void onResponseCode(final int responseCode) throws InterruptedException {
    	if(responseCode == 9){
    		// do stuff here
    	}

    }

 

10 minutes ago, IDontEvenBot said:

as deceiver said use the LoginResponseCodeListener. implement LoginResponseCodeListener and do getBot().addLoginListener(this); then overwrite the onresponse method so that whenever you get the responsecode 9 (which is login limit exceeded) you do whatever you were planning on doing.

ex:

 @ Override
    public final void onResponseCode(final int responseCode) throws InterruptedException {
    	if(responseCode == 9){
    		// do stuff here
    	}

    }

 

Thanks a lot! Maybe have a list of all the response codes?

10 minutes ago, nosepicker said:

Thanks a lot! Maybe have a list of all the 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.

 

Those are all the known ones. Credits to a user on here but forgot his name.

On 9/1/2017 at 4:07 AM, IDontEB said:

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.

 

Those are all the known ones. Credits to a user on here but forgot his name.

Sticky this 

Could you say "if response code is greater than or less than 4 wait 60 seconds and try logging in again"?

19 minutes ago, sudoinit6 said:

Could you say "if response code is greater than or less than 4 wait 60 seconds and try logging in again"?

It should work. 
Why would you try to relog in a banned acc? 

Edited September 21, 20178 yr by Juggles

4 minutes ago, Juggles said:

It should work. 
Why would you try to relog in a banned acc? 

4 is banned, that's the only one my method would NOT try and relog into. Would solve my problem of random disconnects and the client gives up because of unknown response code. Doesn't happen often but it's annoying.

Edited September 21, 20178 yr by sudoinit6

Actually I could see doing some useful things with other responses as well, on six shutdown all java.exe processes and relaunch current bots, that would solve the thursday problem....hmmmm

 

40 minutes ago, sudoinit6 said:

Actually I could see doing some useful things with other responses as well, on six shutdown all java.exe processes and relaunch current bots, that would solve the thursday problem....hmmmm

 

You're giving away too many good ideas!

 

5 hours ago, sudoinit6 said:

Actually I could see doing some useful things with other responses as well, on six shutdown all java.exe processes and relaunch current bots, that would solve the thursday problem....hmmmm

 

Yep you can do whatever you want with this info, as long the script starts

13 hours ago, IDontEB said:

You're giving away too many good ideas!

 

Truth.