- The old session stays registered while the TCP connection to OpenMU is still open. With the web client the WebSocket proxy keeps that connection alive, so every new login gets
AccountAlreadyConnectedand the old session only sees a login attempt warning. - Update OpenMU to a version with PR #1128 (
fix(login): keep the login server state correct, detect lost connections). A player in the world whose client stops pinging for longer than a configurable timeout (default 2 minutes) is disconnected. - Until then a GM can free the account with
/disconnect. - For the web client proxy (Ignies/OpenMu-Client-Babylon) the maintainer advises a per relay ping and closing the WebSocket after about 30 to 45 seconds of silence.
OpenMU: a player stays 'already connected' after a dropped connection and cannot log in again, even with the right password
Tool: OpenMU
“#1128 keeps the login server state correct and adds detection based on the client's ping”
In the issue, 2026-10-07 (original words)