Skip to content
AgoraMod Launcher

Play

Launching Minecraft and health checks

Choose a launch mode, resolve preflight findings, and understand running-state controls.

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 checks an instance before launch, then either hands it to the official launcher or starts Minecraft directly, depending on your Settings choice.

After this you will be able to

  • Choose the appropriate launch mode.
  • Respond safely to health warnings and blockers.
  • Know where to find progress and console information.

Choose delegated or direct launch

Delegated launch is the default: Agora prepares and selects the profile, then the official launcher starts Minecraft. Direct launch keeps execution and console output inside Agora and requires Microsoft sign-in for full online play.

  • Use delegated launch for the simplest account and launcher setup.
  • Use direct launch when you need in-app process status and console output.
  • Change the mode in Settings under Launching.
  • Instances stored with Auto follow the global mode. The current interface does not expose a per-instance override selector.

Handle the health screen

A blocker should be repaired before launch. A warning explains a risk you may choose to accept. Agora may offer to disable a problematic mod directly from the dialog.

  1. Read the finding and affected file.
  2. Repair missing dependencies or incompatible Java first.
  3. Disable a suspect only if you understand the dependent impact.
  4. Use Launch Anyway only for a deliberate, recoverable test.

Repair a loader mismatch

When enabled mods require another loader version, Agora can compare their hard requirements with signed loader-catalog candidates. Keep the current version when it is compatible; otherwise review the recommended version and the affected mods before switching.

  1. Read the unresolved loader requirements and affected mods.
  2. Use Switch and launch when the recommended signed version satisfies every understood hard requirement. A review-only health screen labels the same action Switch version.
  3. Use Choose compatible version when you need another valid candidate.
  4. When no signed candidate satisfies every requirement, automatic switching is unavailable. Manual candidates are signed but require confirmation because a capability is unverified.
  5. Rerun health after a manual or failed switch.
  6. Change a loader version proactively from the instance editor using the Change loader version button next to the loader label.
  7. When an install hits a loader mismatch, the review dialog shows the loader chooser: switch to a compatible version there, or skip the incompatible mods to install only what fits your current loader.

During and after launch

Provisioning progress appears while Agora prepares Java or loader files. Direct launch displays a running state and game console. Exit normally from Minecraft whenever possible so saves and the recovery lifecycle complete cleanly.

In depth

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

Use launch mode, health policy, muted findings, process state, and console output as a controlled execution workflow rather than a single Play action.

After this you will be able to

  • Understand preflight and runtime responsibilities.
  • Use warning muting without hiding new classes of problems.
  • Capture useful evidence from direct-launch failures.

Separate preflight from runtime

Health checks can catch known incompatibilities, missing dependencies, and invalid runtime choices before process start. They cannot prove runtime behavior, graphics-driver compatibility, world integrity, or interactions that appear only during play.

Use muted findings narrowly

Muting is stored by warning kind and affected mod so known acceptable findings do not interrupt every launch. If every finding is muted, Agora proceeds automatically. Revisit muted warnings after major updates instead of treating them as permanent truth.

Collect direct-launch evidence

Use the Console tab to filter INFO, WARN, ERROR, or DEBUG output, then copy the relevant sequence. Preserve the earliest error and its surrounding context; the last line is often only a consequence. Pair console output with the generated crash report when available.

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.