You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, disconnected/idling characters can remain connected and/or with their player Thing inside the world indefinitely. Normally a MUD will kick out such players after a while, so the world isn't filled with false-players.
Here's one way I could see this working in WheelMUD:
We should be able to configure a value in App.config for how long users are allowed to sit idle before being automatically disconnected, and how long their characters can remain in link-death before kicked out. (The default values should not give players a way to cheat out of a losing combat by simply disconnecting.)
Right now we set an AFKReason when disconnect is detected. We could mark the disconnection time there.
Whenever the PlayingState queues an action, we could mark a time for last activity as well.
Periodically (maybe every couple seconds at most - this could be a sleep-heavy thread or other timer tech), we could scan the PlayerManager players list for those who have been disconnected too long, and finish removing them from the world as if they had logged out properly.
The same periodic pulse could check for players who have been idling to within one minute of their auto-disconnect time, and give them a message like "Are you still there? Issue any command to stay connected." Flag that this message has been sent so we don't spam it in that final minute. Clear that flag when any command is received, while updating the last-active time stamp.
Setting the App.config values to 0 could be a way to signal that the admin doesn't want this feature active at all. (Some rare MUDs may wish the player Thing to remain in play indefinitely for specific gameplay reasons.)
The text was updated successfully, but these errors were encountered:
Right now, disconnected/idling characters can remain connected and/or with their player
Thing
inside the world indefinitely. Normally a MUD will kick out such players after a while, so the world isn't filled with false-players.Here's one way I could see this working in WheelMUD:
We should be able to configure a value in App.config for how long users are allowed to sit idle before being automatically disconnected, and how long their characters can remain in link-death before kicked out. (The default values should not give players a way to cheat out of a losing combat by simply disconnecting.)
Right now we set an AFKReason when disconnect is detected. We could mark the disconnection time there.
Whenever the PlayingState queues an action, we could mark a time for last activity as well.
Periodically (maybe every couple seconds at most - this could be a sleep-heavy thread or other timer tech), we could scan the PlayerManager players list for those who have been disconnected too long, and finish removing them from the world as if they had logged out properly.
The same periodic pulse could check for players who have been idling to within one minute of their auto-disconnect time, and give them a message like "Are you still there? Issue any command to stay connected." Flag that this message has been sent so we don't spam it in that final minute. Clear that flag when any command is received, while updating the last-active time stamp.
Setting the App.config values to 0 could be a way to signal that the admin doesn't want this feature active at all. (Some rare MUDs may wish the player
Thing
to remain in play indefinitely for specific gameplay reasons.)The text was updated successfully, but these errors were encountered: