Skip to content
AgoraMod Launcher

Recover

Crash diagnosis and recovery

Use Crash Doctor, evidence-based testing, and Last Known Good recovery.

Two versions of this page follow. Step by step walks through the task in order. In depth explains the underlying behavior. They describe the same product, at different levels of detail.

Step by step

Follow the steps in order. No prior modding knowledge assumed.

Crashes are usually solved fastest by preserving the current state, reading the first useful evidence, and testing one likely cause at a time. Crash Doctor guides that process.

After this you will be able to

  • Open an automatic or pasted-log investigation.
  • Test a ranked suspect without losing the starting state.
  • Restore a known-good setup when investigation is not the priority.

Start an investigation

A recent crash can appear as a Home alert or on an instance card. Open Troubleshoot or paste a log when automatic detection cannot find the report. Crash Doctor ranks likely suspects from available signals.

Test the top suspect

Select Disable & Relaunch. Agora creates a recovery snapshot before changing the enabled state. After testing, choose Yes, fixed or Still crashing so the investigation can record the result and continue.

  1. Read the suspect name and evidence summary.
  2. Review any dependent mods that would also be affected.
  3. Disable the smallest safe set and relaunch.
  4. Reproduce the action that caused the crash.
  5. Report the result accurately rather than changing several other things first.

Recover instead of investigate

If you need to play immediately, restore the Last Known Good state from Home or the Snapshots tab. Use Restore All & Close in Crash Doctor to undo its test changes.

In depth

How the system actually behaves, and why, for readers who prefer the model to a recipe.

Treat crash diagnosis as hypothesis testing. Use signal weights, dependency impact, ruled-out suspects, fingerprints, and preserved baselines to converge without contaminating evidence.

After this you will be able to

  • Interpret why Crash Doctor ranked a suspect.
  • Run dependency-aware tests with minimal variables.
  • Produce a useful report when local diagnosis is inconclusive.

Read the signal breakdown

A suspect score can combine stack-frame presence, curated conflicts, dependency relationships, prior local crashes, and confirmed fixes. A high score is a hypothesis, not proof. Ruled-out mods stay visible so the investigation history is auditable.

Control the experiment

Accept only the dependent disable set required for a valid test. Do not update Java, replace the loader, remove extra mods, and change JVM flags at the same time. If the crash disappears, confirm the fix before restoring unrelated features.

Escalate with a complete evidence set

Include the exact Minecraft and loader versions, mod file names, crash fingerprint or report, steps to reproduce, whether a clean world also fails, and the suspect tests already completed. Use a reproduction lockfile when sharing the exact file state is important.

This guide is the same text Agora shows in its built-in Help & Guide, which is searchable and links directly to the screens it describes.