06.05.2016, 06:09
Sorry, I know this is old. But I wanted to let you know how I fixed this bug within my script.
Inside onplayerdisconnect I log the reason.
If the reason was a timeout, I save it in my sql table.
I have a variable at the top of my script called noban.
Inside onplayerconnect, before anything else happens, I look to see if the field "timeout" = 1.
If so, I set the field to 0, toggle noban for the player to 1. In my cheat detection area, if noban > 0 it does nothing, therefore they won't get banned.
Then I send them a message telling them they need to press f to continue. Once that is done, I toggle them controllable, set noban to 0, and then the script resumes as if they just logged in as normal.
Inside onplayerdisconnect I log the reason.
If the reason was a timeout, I save it in my sql table.
I have a variable at the top of my script called noban.
Inside onplayerconnect, before anything else happens, I look to see if the field "timeout" = 1.
If so, I set the field to 0, toggle noban for the player to 1. In my cheat detection area, if noban > 0 it does nothing, therefore they won't get banned.
Then I send them a message telling them they need to press f to continue. Once that is done, I toggle them controllable, set noban to 0, and then the script resumes as if they just logged in as normal.