FloatPilot User Guide

Missing Configuration Files

FloatPilot reads its settings from the configs folder under the App directory. If common.ini, server.ini, version.ini, or another configuration file was deleted, corrupted, or edited into an invalid format, use this recovery process first.

Terms used in this guide

Term Plain-language meaning
Configuration file A file the App uses to store options.
configs folder The folder where the App stores configuration files.
version.ini The configuration file the App uses to identify the game version.
user-*.ini A file beginning with user- that stores account settings; the asterisk means you may choose the middle name.

Close FloatPilot before changing configuration files. Do not edit a file while the App may be writing it.

Fast recovery

  1. Close the FloatPilot App completely.
  2. Open the configs folder under the FloatPilot installation directory.
  3. Move a file known to be corrupted to a backup folder, or delete it.
  4. Restart FloatPilot.
  5. Return to the login or settings screen and confirm that the configuration is available again.

The App creates the required folder and default files while loading configuration. The default behavior for common files is:

File Purpose Behavior when missing
configs\common.ini Language, UI, messages, and shared App settings Creates an empty file; missing values use program defaults.
configs\server.ini Game-server list Recreates the default server list.
configs\version.ini Game version settings Creates default version settings; if no usable content is found, default settings are restored.
configs\user-*.ini User account configuration files The login page creates user-default.ini when no user file exists.

If only the contents are corrupted

Do not try to repair every line immediately. Close the App, back up the original file, move or delete the problematic file, and restart FloatPilot. This lets the App create a readable default file.

If only one account file is affected, handle that specific user-*.ini. If the version is wrong, run the version tool again and create a correct version.ini; do not guess version numbers manually.

What should not be deleted casually

  • Back up any user-*.ini that you still need before deleting it.
  • Never put membership passwords, game passwords, or trade PINs in a support report.
  • Do not rename the configs folder; the App reads from this fixed location.
  • version.ini must match the actual game data in use. Do not copy a file from another installation without checking it.

Check order

  1. Close FloatPilot.
  2. Confirm that you are working in the correct App installation directory.
  3. Back up and move any corrupted or unreadable file.
  4. Restart the App and let it regenerate required files.
  5. Select the correct user-*.ini, server, and version settings in version.ini again.
  6. If login still fails, confirm that version.ini was generated from the current game folder rather than an older version.

Final checklist

  • The App is completely closed.
  • The configs folder is under the correct App directory.
  • Corrupted files were backed up before being moved or deleted.
  • The App was restarted and regenerated required configuration.
  • version.ini matches the current game-data version.
  • No password or hidden authorization text was included in the report.