Skip to content
AgoraMod Launcher

Manage

Managing mods and game content

Organize mods, resource packs, shaders, and data packs inside an instance.

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.

The Instance Editor separates content by type and shows what is installed. Use Agora's controls so changes remain visible to snapshots, health checks, and recovery tools.

After this you will be able to

  • Find and manage each kind of installed content.
  • Temporarily disable a mod without deleting it.
  • Add local files with appropriate caution.

Use the content tabs

Open My Instances, select Edit, then choose Mods, Resource Packs, Shaders, or Data Packs. Each list shows the installed file and available actions for that content type.

  • View Details returns to the project page when Agora can resolve the source.
  • Disable keeps a mod file available but prevents it from loading.
  • Remove starts a reviewed removal plan.
  • Add opens Browse with the current instance and content type already selected.

Enable and disable for testing

Disabling is useful when diagnosing a conflict or keeping optional features available for later. Relaunch after changing enabled state; Minecraft cannot unload most mods from a running game.

How data packs reach your worlds

Minecraft only loads data packs from inside each world, not from the instance. Agora keeps the Data Packs list of the instance as the source of truth and copies every enabled data pack into your worlds: before each launch, and right after you install, remove, enable, disable, or change a data pack.

  • By default a data pack goes to all worlds. Select Worlds… on its row to pick specific worlds instead.
  • The row shows where it is, for example All worlds (3) or 2 of 3 worlds.
  • A world created while you play gets your data packs at the next sync, so a brand-new world has them from its second session. Select Sync now on the Data Packs tab to add them sooner.
  • Agora only ever removes or replaces data pack files it placed itself. If a world already has a different file with the same name, Agora leaves it alone and says so.

Import a local file

Use Import Mod or the drop zone for a local JAR. Use the corresponding content picker for supported resource packs, shaders, and data packs. Confirm the file came from a trusted source and matches the instance.

Group a long list

A large instance is easier to read grouped than alphabetical. In the content toolbar, next to the search and filter controls, the Group dropdown re-sorts the list into sections. Each group header has its own enable and disable button, so you can switch a whole set at once.

  1. Open My Instances, select Edit, then a content tab such as Mods.
  2. Use the Group dropdown in the toolbar above the list.
  3. Choose Pack vs you, Category, or Source.
  4. Collapse the sections you are not working on.

Make your own groups

The built-in groupings are derived from what Agora already knows. To sort mods your own way, open the three-dot menu at the end of a row and choose Set group. Name a new group or pick an existing one. Once at least one group exists, Group: My groups appears in the dropdown alongside the built-in options.

In depth

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

Manage content as a traceable inventory with source metadata, hashes, enabled state, and controlled manual exceptions.

After this you will be able to

  • Identify source and metadata gaps in an instance.
  • Use content state to run controlled compatibility tests.
  • Avoid configuration and world-data pitfalls when changing content.

Read the installed inventory

The Mods list distinguishes the resolved project name from the physical filename and records source and install time when available. A missing catalog or provider identity is a signal that future automated updates may require manual attention.

Ask why a mod is here

Open the three-dot menu at the end of a row and choose Why is this here. Agora traces that file back and answers with one of four things: you installed it directly, it came from the instance's modpack, another mod needs it, or it was a dependency and nothing needs it any more. It then lists the installed mods that currently require it. Most launchers show what a mod depends on; this is the opposite direction, which is the one you are looking in when you find a JAR you do not recognise.

Clean up orphaned dependencies

A library installed only to satisfy a mod you have since removed is an orphan. There is no separate cleanup screen to visit: after a removal, if it stranded anything, Agora asks whether to remove those as well. It can tell because it recorded at install time which entries were dependencies rather than choices.

Design controlled mod groups

Use enabled state and loadout profiles to separate performance, visual, content, and debugging groups. Keep required libraries enabled with their dependents. Record a named snapshot before changing core libraries or world-generation mods.

Protect persistent game data

Removing a world-generation, storage, or content mod can leave missing blocks, items, or data in a save even if the game launches. Back up important worlds separately and test removal on a copy.

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.