After a DC the auto login will activate but do nothing

Are you receiving anything in the logger? Is it only specifically disconnections? Version? Bug/suggestions form?

Are you receiving anything in the logger? Is it only specifically disconnections? Version? Bug/suggestions form?

1. OSBot Version - 2.4.43 is when i first noticed it

2. A description of the issue. Include relevant logs. - disconnects from world, ends @ login screen, script stops without trying to log back in

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

4. How can you replicate the issue? just happens every time i disconnect from the server

5. Has this issue persisted through multiple versions? If so, how far back? its been happening on multiple versions for a while now

Regarding this issue: I've had this a couple of times when doing experiments with making an accountswitcher script (like 2 times out of 100). It never happens when I use the client normally though.

 

Either it sat on login screen (AutoLogin did not start)

 

or AutoLogin returned true, screen went red (randomexecutor), and it just did nothing

 

Sorry if this is not very clear.

Well the auto-login random event is controlled closely by the bot (along with most of the other randoms). There is a certain chain of events that needs to happen because I wrote it so that no script code gets executed until your character is actually logged into the game. 

 

I would have to take a look at the Account Switcher script.

 

@Senetede - This makes me happy knowing that the LoginResponseCodeListener is working correctly in conjunction with the AutoLogin event. Hopefully this is not an issue.

Well the auto-login random event is controlled closely by the bot (along with most of the other randoms). There is a certain chain of events that needs to happen because I wrote it so that no script code gets executed until your character is actually logged into the game. 

 

I would have to take a look at the Account Switcher script.

 

@Senetede - This makes me happy knowing that the LoginResponseCodeListener is working correctly in conjunction with the AutoLogin event. Hopefully this is not an issue.

its a nusciance having to check them every so often to see if they stop because of script stopping after dcing on rs

would there be anything that you could do for the people having this issue?