Skip to content
AgoraMod Launcher

Manage

Packs, import, export, and reproduction

Move complete setups between machines and verify that another instance matches.

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.

Packs are the easiest way to distribute a coordinated setup. Agora supports Modrinth packs and its native pack format, while reproduction lockfiles focus on proving exact file state.

After this you will be able to

  • Import a supported pack into a new instance.
  • Choose the right export format.
  • Share a setup without assuming snapshots travel with it.

Import a pack

Use Import Pack from the instance area or Import in the editor. Select a .mrpack or supported Agora pack file. Agora prepares the loader and required content before promoting the new instance.

  1. Choose the pack file from a trusted source.
  2. Review the new instance name and target location.
  3. Leave save symlinking off unless you understand how shared save paths behave.
  4. Wait for preparation and health validation to finish.
  5. Launch once and verify the pack before adding more content.

Choose an export

The editor labels the formats Export as Modrinth Pack (.mrpack) and Export as Agora Pack (.json). The Agora-native file is written as .agora-pack.json. The exported file location opens in your system file manager after a successful export.

Share responsibly

Tell recipients which Minecraft and loader versions the setup targets. Do not assume private saves, server lists, account details, or all configuration are included. Confirm that every bundled project license permits redistribution.

In depth

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

Use reproduction lockfiles to verify, repair, or clone exact artifact state while keeping private file contents out of the shared description.

After this you will be able to

  • Distinguish a distributable pack from a diagnostic lockfile.
  • Verify and repair drift transactionally.
  • Build a reliable reproduction artifact for support or testing.

Understand reproduction lockfiles

A lockfile records artifacts, sources, hashes, and relevant settings so another instance can be compared with the original. It avoids embedding private configuration contents. Export, copy, or paste one from the Export tab.

Verify, repair, or clone

Verify compares the current instance against the lockfile. Repair snapshots the instance, downloads exact expected artifacts, removes extras, and rolls back if health validation fails. Clone builds a separate instance from the described state.

  1. Validate that the lockfile came from a trusted person or project.
  2. Run Verify and review every missing, extra, or changed file.
  3. Snapshot valuable local changes before Repair.
  4. Prefer Clone when you need to preserve the original instance untouched.
  5. Reproduce the issue before making additional changes.

Build support-grade reproductions

Minimize the instance while preserving the problem, verify it against the final lockfile, and document exact reproduction steps. Keep worlds and logs separate when they are necessary, and review them for private data before sharing.

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.