Account Quota Stuck
Use this guide when a game account cannot be logged in again even though it was already disconnected. FloatPilot calculates game-account slots on the Web server, so the result is not based only on the current App window.
Terms used in this guide
| Term | Plain-language meaning |
|---|---|
| App | The FloatPilot program you currently have open. |
| Server | The computer that confirms login status and available account slots. |
| Slot | The number of game accounts your membership can log in at the same time. |
Important: During a normal logout, manual disconnect, or normal App shutdown, the App tries to tell the server to release the slot. If the App crashes, the computer loses power, the network drops, or the notice does not arrive, the server keeps the slot for a while and waits to confirm that the account is really offline. The slot may therefore not return immediately.
Quick recovery
Confirm that the game account is offline
- Return to the FloatPilot game-account page.
- Confirm that the account no longer has an active game connection.
- Check every other App or device using the same membership, because the quota is shared by the membership.
Wait for server-side reclamation
If the App or network ended unexpectedly, wait for a while before trying again. The App regularly communicates with the server so the server knows whether the account is still online. If no confirmation arrives for a while, the server reclaims the slot.
How the quota works
| Term | Plain-language meaning |
|---|---|
| Plan limit | The number of game accounts your plan allows at the same time. |
| Reservation | Before connecting to the game, the App asks the server to reserve a slot. |
| Temporary hold | After an unexpected App shutdown, the server keeps the slot for a while so an account that is actually still online is not duplicated. |
| Release | The App asks the server to reclaim the slot during logout, disconnect, or normal shutdown. |
| Delayed recovery | After an abnormal disconnect, the server automatically reclaims the slot after the waiting period ends. |
Why is the slot not always released immediately?
The normal flow sends a release request, but the fact that the App closed does not prove that the server received the final request. A short delay can happen when:
- the App is terminated from Task Manager;
- the computer crashes, loses power, or sleeps;
- the network drops during logout;
- the release request times out;
- another App or device using the same membership still holds a slot.
This safety mechanism prevents the App from showing offline while it is still connected. The server cannot safely assign the slot to another login until the release is confirmed or the waiting period ends.
Recommended check order
- Log out every game account using the same membership.
- Check that no other App or device is still using the quota.
- Wait for the server to finish reclaiming the slot after an abnormal disconnect.
- Restart FloatPilot so it can confirm its authorization status and fetch the latest quota.
- If the limit remains blocked for a long time, record the time, membership account (never the password), and displayed message, then ask an administrator to inspect server-side license events.
Never include a membership password, game password, trade PIN, or hidden authorization text in a support report.
Final checklist
- Every game account under the membership is offline.
- No other App or device is using a slot.
- The server has had time to reclaim the slot after the abnormal disconnect.
- The App has been restarted and refreshed its authorization status.
- No password or hidden authorization text is included in the report.