Reconnect Delay Differs from Setting

This guide explains why the reconnect delay can differ from the value configured in Reconnect Settings.

Terms used in this guide

Term	Plain-language meaning
Disconnect code	A number attached by the server to a disconnect message to show the reason.
Server	The computer responsible for game login and connection.
Reconnect	Logging in to the game again after a disconnect.
Protection wait	A longer pause after a specific login problem, preventing an immediate repeated attempt.

Important rule: when the server reports disconnect code 3, 19, or 75, the App raises the base wait for that reconnect to 1200 seconds. This protects connection resources; it is not a configuration read error.

Quick start

Record the server disconnect code from the disconnect message.
If the code is 3, 19, or 75, check the username, password, server, and login settings first.
Correct the settings before reconnecting instead of only shortening the normal reconnect delay.

Disconnect code rules

Disconnect code	App behavior	Check first
`3`	Uses a `1200`-second base delay for this reconnect	Username, password, and login data
`19`	Uses a `1200`-second base delay for this reconnect	Account state, server, and login settings
`75`	Uses a `1200`-second base delay for this reconnect	Account verification and server settings

These codes do not use the shorter DisconnectInterval value to override the 1200-second base delay. The first reconnect uses 1200 seconds as its base; if the same disconnect event reaches later attempts, each later wait may be longer.

Why the App waits 1200 seconds

These disconnects are generally not ordinary network instability. They indicate that an account or login condition needs user correction. Common areas to check include:

An incorrect username or password.
The wrong server, login version, or character slot.
An account state that requires server-side handling.

Rapidly reconnecting with the same invalid data would create repeated connections with no useful result and waste power, bandwidth, and server resources. The App therefore waits 1200 seconds before this reconnect, giving you time to correct the login conditions and preventing an endless rapid retry loop.

Common questions and checks

I configured 60 seconds. Why does the screen show 1200 seconds?

Check the disconnect code first. For 3, 19, or 75, 1200 seconds is an intentional protection wait; changing the normal setting to 60 seconds does not override it.

Does this always mean the network is unstable?

No. These codes primarily indicate a login condition or account state that needs attention. Check the credentials, server, and version settings before investigating the network.

The same code appears after I corrected the settings

Stop the current reconnect flow, verify the account and server settings again, and start a new connection. If the code continues, keep the complete code and timestamp so an administrator can check the account state.

Final checklist

The complete server disconnect code is recorded.
Codes 3, 19, and 75 are understood to use the 1200-second protection delay.
The username, password, server, and login version are verified.
Login-condition failures are not mixed with ordinary network troubleshooting.