User Configuration Files

User configuration files are user-*.ini files stored in the configs folder. You can store different accounts, servers, or character combinations in separate files and select the file to use from the login window.

Terms used in this guide

Term	Plain-language meaning
User configuration file	A file the App uses to store account and login options.
`configs` folder	The folder where the App stores configuration files.
`user-*.ini`	A configuration file beginning with `user-`; the asterisk means you may choose the middle name.
Account section	A set of account data inside one configuration file.
File extension	The type marker at the end of a file name, such as `.ini`.

The file name must match user-*.ini, such as user-main.ini or user-farm.ini. The App scans only the top level of configs; it does not search subfolders.

Quick start

Create your first user configuration file

Close FloatPilot completely.
Open the configs folder under the App directory.
Copy user-default.ini, or create a new empty file.
Rename it to a name that starts with user- and ends with .ini, such as user-main.ini.
Start FloatPilot again.
Select the new user-*.ini in the login window under Configuration source.
Enter the account, password, trade PIN, server, and character slot, then save and log in.

If configs contains no user-*.ini, the App creates user-default.ini automatically.

How should multiple files be organized?

Example file	Suggested use
`user-default.ini`	General default account.
`user-main.ini`	Main account or main character.
`user-farm.ini`	Farming, gathering, or test account.
`user-event.ini`	Account group used during an event.

The file name is only for identification. Always verify the account and server values inside the file in the login window. A descriptive file name does not guarantee that its contents are correct.

Create account sections in the login window

A single user-*.ini can contain multiple account sections. In the login window:

Select the user-*.ini to use.
Enter the game-account information.
Fill in the record tag so you can identify the account section.
Click Generate tag to create a new section.
Select the section to log in from the account list.

Do not copy the same account into many files and log them in at the same time. This can make quota, character, and configuration problems harder to diagnose.

Manual file-name rules

An allowed file name must:

start with user-;
end with .ini;
be directly inside the App configs folder;
contain no path separator or .. segment.

These names are valid:

user-main.ini
user-test.ini
user-wr01.ini

These names are not treated as user configuration files:

main.ini
user-main.txt
user-main.ini.bak
configs\user-main.ini

Password and file safety

Login settings may contain account names, passwords, and trade PINs. When password encryption is enabled, the App uses a password encryption method to store passwords and trade PINs. When it is disabled, passwords may be written as readable text in user-*.ini, which is easier to edit but less secure.

Do not upload user-*.ini to a public location or paste its contents into support tickets, issues, or chat windows.

Common questions and checks

The new file does not appear in the selector

Confirm that the name matches user-*.ini and that the file is directly inside the correct App configs folder. Restart the App so the login page scans the files again.

The App creates `user-default.ini` again

This usually means that no file matching user-*.ini was found at startup. Check the extension and confirm that the file is under the correct App directory.

The account cannot be found after creating a section

Confirm that the login window is using the correct user-*.ini, then confirm that the account section was saved. Sections from different files are not merged automatically.

Final checklist

The file name matches user-*.ini.
The file is directly inside configs under the correct App directory.
The file was selected again in the login window.
The account section, server, and character slot were verified.
Password encryption was chosen according to the security need.
The contents of user-*.ini were not shared publicly.