Crashes and Memory Errors
Here is the short version: crashes and memory errors are definitely caused by an unknown bug in the program 😅. You did not press the wrong button, and you did not use the app “too fast.” These issues usually need the runtime records so the developer can find the bug hiding in the weeds.
Please enable LOG tracking first, reproduce the problem once, and then report it in the Discord channel or send it directly to the developer. The more context you include, the faster the issue can be investigated 🧩
Reminder: do not send membership passwords, game passwords, trade passwords, or other private information. We need what happened and the LOG records, not your account secrets.
Do these things first
- Write down when it happened, including the time zone if possible, such as
2026-08-05 21:30 (Taiwan time). - If the app still opens, press “Enable LOG” in the top toolbar of the affected account page 📋.
- Repeat the action that caused the problem once. If the app crashes immediately, do not keep trying over and over; one reproduction is enough.
- Write down what you were doing and keep any screenshot or Windows error message.
- Post in the Discord channel or message the developer directly, including the LOG and the report details below.
How to enable LOG tracking
Press “Enable LOG” on the account page
Open the character or game-account page and find the document icon in the top toolbar. Press “Enable LOG.” When the button says “Disable LOG,” LOG is already enabled and does not need to be pressed again.
This switch controls normal LOG records for the current account only. Enable it on the account page where the crash happens; there is no need to change other accounts while troubleshooting.
Open the log folder
After reproducing the problem, return to the FloatPilot main window, open the “System” menu, and choose “Open Log Folder.” Keep the LOG files close to the incident time and send them to the developer 📎
If the app crashes before you can open the folder, do not panic. Start the app again and use the “System” menu afterward. Do not delete or clear the LOG first, because the clues may disappear with it.
Include these details in your report
Recommended information
| Information | Example |
|---|---|
| Time | 2026-08-05 21:30 (Taiwan time) |
| Situation | Logging in, switching characters, gathering, patrolling, fighting, using a vehicle, or the button you just pressed |
| Last step | For example, “Pressed Start Patrol, the screen stopped, then the app disappeared” |
| Frequency | Every time, sometimes, several times a day, or only once so far |
| Error screen | The full Windows or app message, screenshot, or error code |
| Version | The app version and the game version in use |
| LOG | The record file near the incident time from “Open Log Folder” |
| Other clues | Whether it only happens for one account, character, map, or specific action |
This does not need to become a novel. A short list using the items above is perfect 📝
Do not send these details
- Membership passwords, game passwords, or trade passwords.
- Private contact information or personal files unrelated to the issue.
- Guesses stated as facts, such as “the computer memory is definitely broken.” Tell us what you observed instead.
If a LOG contains information you are unsure about, let the developer review it before posting it elsewhere.
Common situations
The app crashes immediately on startup
Start it again once and check whether it happens every time. If you can reach the main window, turn on “Enable LOG” immediately and reproduce it once. If the app never opens, record the startup time, any Windows message, and the previous LOG, then report it directly to the developer.
The app crashes during one specific action
Write down the last action before the crash, such as “switched maps and pressed Start Patrol” or “opened a vehicle and started moving.” This sequence matters because it tells the developer where to start looking 🕵️
A memory error appears only sometimes
It is still useful even if the app works normally afterward. Note roughly how long the app had been running, how many accounts were open, what you were doing, and whether it only appears after a long session.
Report template
Problem: Crash or memory error
Time: 2026-08-05 21:30 (Taiwan time)
Situation: Started automatic movement after opening a vehicle
Last step: Pressed Start Movement; the app disappeared about 10 seconds later
Frequency: Second occurrence; both happened on the same map
Version: FloatPilot App x.x.x, game version: ______
LOG: Found and attached from “System -> Open Log Folder”
Notes: Two accounts were open; no other error message appeared
Final checklist
- Recorded the time and time zone.
- Pressed “Enable LOG” on the affected account page.
- Reproduced the issue once and recorded the last action.
- Recorded the situation and frequency.
- Kept the relevant LOG from “System -> Open Log Folder.”
- Reported it in the Discord channel or messaged the developer.
- Included no passwords or private sensitive information.
No need to feel embarrassed; this is exactly what an unknown bug does 😅 Every time and action detail helps narrow it down. Thanks for helping us catch it 🙌