'login code' meaning

[Magerange]

I've made this topic to discuss what specific [#DEBUG] messages in OSBot logger mean. For instance, I'd like to know what does 'log in code -3' mean? Found one of my accounts loggoed out in, with script not stopped, opened log in screen, but details not written in. Account was not banned and script was still able to run.

Edited June 14, 2017 by Magerange

[LIVING]

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.

[Magerange]

18 minutes ago, LIVING said:

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.

Awesome, thanks! But what about negative values? What creates those?

[Butters]

7 hours ago, Magerange said:

Awesome, thanks! But what about negative values? What creates those?

Just add a "-"to all oh the mentioned response codes and bingo

[Magerange]

Hmmm, still getting a couple of accounts with 'LOGIN ERROR: -3'. Before this text it has some kind of 'Event executor failed, taking too long' text. Failed with Screenshot for proof (thought I made it, closed the client, turns out I didn't...), but I have no doubt this will occur more...
After I check on the client it still seems to be 'in the script', but I can stop it. When I do and try to restart the same exact script client has no reaction towards the request (it starts the script, but nothing happens, just log in screen with blank name/password logs).

What am I doing wrong? Has anyone had something similair?

No, it is not scripts fault, I can easily log in and re-start the script manually.

Edited June 15, 2017 by Magerange

[Magerange]

Alrighty, here's the picture with this error:

I am still yet to catch this in action, but perhaps someone already knows this...

Edited June 16, 2017 by Magerange

[Alek]

You can get negative response codes last time I checked, also the response codes change pretty often. When OSBot doesn't know what type of login code is received, it automatically stops the script. I WILL NOT CHANGE THIS BEHAVIOR. 

[Magerange]

4 minutes ago, Alek said:

You can get negative response codes last time I checked, also the response codes change pretty often. When OSBot doesn't know what type of login code is received, it automatically stops the script. I WILL NOT CHANGE THIS BEHAVIOR. 

Thanks! Could you be more specific on how I could improve it and prevent this from happening? I use CLI to start the clients and mass-start around 25 - 30 with some sleeps between them. I also have 1 proxy per 5-6 accounts. I've noticed that if this happens it most likely happens with all the accounts on the same proxy.