Skip to content
AgoraMod Launcher

Recover

Snapshots and loadout profiles

Create restore points and switch between groups of enabled mods.

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.

Snapshots restore files to an earlier state. Loadout profiles remember which installed mods are enabled. They solve different problems and work well together.

After this you will be able to

  • Create, compare, restore, and delete snapshots.
  • Understand automatic Last Known Good promotion.
  • Save and apply an enabled-mod loadout.

Create a snapshot

Open an instance, select Snapshots, enter a useful label, and create the snapshot before a risky change. Include the reason in the label, such as Before 1.21.2 update or Stable server setup.

Compare and restore

Show diff lists added, removed, and modified files relative to the snapshot. Restore returns the instance to that state and first creates an undo snapshot. Delete removes only the selected recovery point. Automatic pre-launch recovery intentionally excludes saves so launch does not rescan large worlds; full manual and transactional snapshots use a broader scope.

Create a loadout profile

Open Loadout Profiles, name the current enabled-mod arrangement, and save it. Apply another profile to switch enabled states without removing files. Relaunch Minecraft after applying a profile.

In depth

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

Use snapshot diffs and loadout profiles as lightweight change management: recover file state, isolate feature sets, and preserve an auditable baseline.

After this you will be able to

  • Interpret drift beyond simple mod counts.
  • Build test matrices from profiles and snapshots.
  • Know the storage and backup limits of both features.

Read drift precisely

A diff reports added, removed, and modified paths. An enabled-to-disabled transition may appear as a removed JAR plus an added .disabled file. Configuration drift can matter even when the mod inventory is unchanged.

Combine baselines and profiles

Use a named stable snapshot as the file baseline, then create profiles for client visuals, multiplayer-safe content, debugging, or performance testing. Profiles do not revert versions or configuration; restore the snapshot when those must also return to baseline.

Plan external backup

Snapshots and profiles live in Agora's local state and instance storage. Automatic pre-launch snapshots exclude saves, while full snapshots may include them. Neither is cloud sync or an independent backup. Export a pack or lockfile for reconstruction and back up irreplaceable saves separately.

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.