FloatPilot User Guide

Official Client Bridge Guide

This guide explains how to make the official aLogin.exe connect to FloatPilot first, while FloatPilot forwards the connection to the official server.

Terms used in this guide

Term Plain-language meaning
Official game program The original game program provided by the game company.
aLogin.exe The file inside the official game program that handles game login.
BridgeHost The local connection address FloatPilot shows to the official game program.
127.0.0.x The local address meaning “this computer”; each account must use a different number.
Connection bridge The official game program connects to FloatPilot first, and FloatPilot then connects to the official server.
upstream-connect-failed The error shown when FloatPilot cannot connect to the official server.

Important: FloatPilot's server.ini and the official game program's SERVER.INI serve different purposes. FloatPilot must keep the real official-server location. Only the official game program's SERVER.INI should point to the local BridgeHost. Actual compatibility may differ between official game versions.

Keep the Two Server Configurations Separate

Configuration file Purpose What it should contain
FloatPilot's server.ini Provides the real official server that the Bridge connects to Keep the official server IP; do not change it to 127.0.0.x
The official game program's SERVER.INI Makes aLogin.exe connect to FloatPilot first Change the original server location to the BridgeHost shown in the account list

Section and key layouts may differ between official versions. Change only the server IP that already exists in that version; do not add a key based on guesswork.

Quick Start

  1. Start FloatPilot and open the login window.
  2. Select the account, official server, and character slot.
  3. Set “Connection Method” to aLogin Bridge.
  4. Press “Login” and wait for the account list to show Waiting for aLogin.
  5. Start the matching aLogin.exe.

During a normal connection, the account state progresses through:

Waiting for aLogin
aLogin connected
Connecting to official server
Official server connected
Game logged in

Use the App Through the Same Connection

After the account reaches Game logged in, the App and aLogin share the same bridge connection. “Teleport → Return to Playground” is a simple test:

  1. Confirm that the character is not in battle, dialogue, trade, or another busy state.
  2. Open “Teleport” from FloatPilot's top menu.
  3. Press “Return to Playground”.
  4. Wait for the official server to respond before starting another action.

If login is not complete or the connection has already ended, the App rejects the action.

Disconnect and Reconnect

It stays at “Waiting for aLogin”

  1. Confirm that FloatPilot completed the account-login flow.
  2. Confirm that you edited the official game program's SERVER.INI, not FloatPilot's server.ini.
  3. Confirm that the IP exactly matches the BridgeHost shown in the account list.
  4. Confirm that aLogin.exe was started from the correct game-program folder.

It shows upstream-connect-failed

Confirm that FloatPilot's own server.ini still contains the correct official-server location. Do not change that file to 127.0.0.x.

Final Checklist

  • FloatPilot's server.ini still points to the real official server IP.
  • The official game program's SERVER.INI points to the account-list BridgeHost:6414.
  • The login window uses aLogin Bridge as the connection method.
  • FloatPilot reaches Waiting for aLogin before aLogin.exe starts.
  • Multiple accounts use different 127.0.0.x values and preferably separate game-program folders.
  • The account has completed login confirmation before the App performs actions.
  • Version, configuration, and diagnostic evidence are preserved when investigating compatibility issues.