Skip to content
AgoraMod Launcher

Connect

Getting help with a crash

Export a redacted crash report to share with the community or an AI assistant of your choosing.

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.

Agora diagnoses crashes locally in Crash Doctor. When that is not enough, Crash Doctor can copy a single redacted report containing everything it found, which you can paste wherever you want help. Agora has no built-in chat assistant and never sends your crash data anywhere on its own.

After this you will be able to

  • Export a complete crash report from Crash Doctor.
  • Know what the report contains and what is removed.
  • Choose a good place to ask for help.

Export the report

Open Crash Doctor for the affected instance and choose Copy crash report. The report is assembled on your machine and placed on your clipboard. It contains the crash log, any matched crash signatures, the ranked suspect mods, and the instance's installed mod list — the same evidence Agora used for its own diagnosis.

Know what is shared

File paths and usernames are removed before the report is built, because a Minecraft crash log normally contains your home directory and therefore your real name. Nothing else is filtered, so read the report before posting it if the instance involves private server addresses or anything else you would rather not publish.

Choose where to ask

The Agora Discord reaches people who know this launcher and the curated catalog, and is the best place for questions about Agora itself. A general AI assistant is often faster for reading a stack trace. Either way, the exported report already contains the context that makes an answer possible.

  1. Reproduce the crash so Crash Doctor has fresh evidence.
  2. Copy the crash report.
  3. Paste it, unedited, into Discord or an assistant.
  4. Apply one reversible change at a time.
  5. Verify in Agora and Minecraft before trying the next.

In depth

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

Treat any outside answer as a hypothesis, and keep Crash Doctor's one-variable testing discipline when acting on it.

After this you will be able to

  • Turn an outside suggestion into a reversible Agora action.
  • Keep deterministic evidence as the source of truth.
  • Automate the loop with an external agent when you want more.

Verify before you act

An AI answer is a hypothesis, not a diagnosis. Translate it into an Agora action — take a snapshot, disable a mod with dependent review, verify a lockfile, inspect Java — and change one thing at a time so you can tell what actually fixed it. Reject any suggestion that bypasses hash verification, exposes credentials, or deletes saves.

Let an agent drive Agora directly

If you already run an MCP-capable AI client, the local MCP server is stronger than copy and paste: the agent can list instances, read bounded crash evidence, search local knowledge, and request supported enable/disable actions itself, with per-instance approval for anything destructive. See the MCP automation topic.

Agora still works without any of this

Crash Doctor, console filters, snapshots, and lockfiles are deterministic and entirely local. Outside help is optional and should never be the only recovery path.

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.