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.
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.
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 registry or provider identity is a signal that future automated updates may require manual attention.
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.