01 Exit code 1 is a result, not a diagnosis
Minecraft exit code 1 means the process ended with a failure status; it does not identify one universal cause. In a modded launcher or server panel, the useful explanation is usually in the output before that final line. Do not download an “exit-code fixer,” remove every mod or delete the world just because the status number matches somebody else’s screenshot.
Record whether this is the game client, a dedicated server or an installer. Note the game release, loader build, Java executable and last successful launch. A client graphics crash and a server missing a dependency can end with the same visible code while needing different repairs.
02 Collect the correct log from the correct instance
Fabric’s log guide ↗ identifies the game directory’s logs and its crash-report guide ↗ explains the separate crash-reports folder. Third-party launchers and hosted instances can use their own directories. Use the instance’s open-folder control or provider file manager rather than assuming every installation lives in the default .minecraft folder.
- Keep the full console output if Java fails before normal logging begins.
- Read latest.log from the failed attempt, not a later successful launch.
- If present, preserve the matching timestamped crash report.
- Record the first relevant exception and the surrounding dependency or runtime message.
Inspect logs for personal paths, network details or credentials before sharing. Keep enough context for the maintainer to trace the cause; a cropped final status line is rarely enough.
03 Use the error text to choose a small next step
| Evidence | First check |
|---|---|
| Required mod or dependency version is named | Match that dependency to the exact loader and game release. |
| Unsupported class/runtime message | Confirm which Java executable the failing process actually uses. |
| Client-only class mentioned on a headless server | Check whether a client mod was copied into the server pack. |
| Out-of-memory or external process kill evidence | Inspect allocation and host limits; do not assume all code-1 exits are RAM failures. |
These are routes for investigation, not conclusions from the code alone. Fabric installation rules ↗ require a matching edition, loader and game version. For a named Cloth Config dependency, use the compatibility checklist rather than installing the newest file indiscriminately.
04 Compare with a separate clean instance
Keep the original installation and world. Create another instance with the same game and loader, prove it starts, then add the intended server pack or a controlled subset according to the pack author’s instructions. Maintain required dependencies together; randomly removing half of them can create a new error unrelated to the first one.
If the clean baseline fails, investigate the runtime or environment first. If the baseline works but the pack fails, compare its manifest and logs. If only the imported world fails, test a copy and preserve the last working build. Finish with two successful launches and a saved-change restart check. For planning the environment correctly, return to the modded-server guide.