Identify the failure first
Do not use “crash” to describe every failure. The symptom determines what evidence matters.
| What happens | Treat it as |
|---|---|
| Game closes to desktop | Crash or CTD |
| Game stays open but never responds | Hang or freeze |
| Game pauses repeatedly and resumes | Stutter or periodic freeze |
| Loading screen never completes | Load failure |
| Only a menu stops working | UI or input problem |
| Game never reaches the main menu | Startup failure |
If the game closes to desktop
Record:
- where you were
- what you were doing
- whether it happens every time
- whether extra mods were added
- whether a crash log was created
A repeatable crash at the same action or location is usually more useful than a crash that happened once after several hours.
If the game freezes but stays open
Wait long enough to determine whether it recovers. If it repeatedly freezes and resumes at a regular interval, do not immediately lower graphics settings. Periodic stalls can come from logging, scripts, storage, background scanning, or a broken system repeatedly retrying work.
See Performance Basics for the performance-side checks.
If loading never finishes
Check whether the failure affects:
- only one save
- every save
- only a new game
- the game before the main menu
Those are different failure classes. Do not delete saves or reinstall the full modlist until you know which class you are dealing with.
Return to a supported baseline
When extra mods or manual file edits are involved, reproduce the issue on the supported Fallen World configuration before reporting it as a Fallen World bug.
Do not delete logs, crash reports, or the affected save before you know whether they are needed to reproduce the problem.
What to include in a report
Use Report a Problem on the relevant wiki page for documentation errors. For a game bug, include the exact symptom, reproduction steps, extra modifications, and any relevant logs through the project’s supported bug-report process.