Some scripts would need enhancing to allow for this.
Quote:
Originally Posted by
Coh3n
I agree with you. I'm not sure everyone else is understanding it right.
All this would do is log the player back in if they were found logged out and are still active. NextPlayer(true/false) isn't called anywhere; it should only be called in scripts. If a solver fails, the player is set to false and logged out; therefore, this "logout random" wouldn't log the player back in.
If, for any reason whatsoever, the player is logged out and set to false (presumably, something fails), the script still goes on working the way it always has.
This idea is perfect for handling connection losses.
E: Latest version has Forester working enabled.
The connection loss logout essentially is random if you think about it.. It certainly affects me at least. Scripts may need to be enhanced to allow for this to be built in however. It sounds logical though that as long as the player is still active, there should be no problem with logging back in. Some scripts would definitely need to be "Smarter" though. If we were on a bank run and randomly logged out, then a lot of scripts wouldn't know what to do..