Indium Mod Update Checklist Before You Change Versions
A repeatable pre-update and post-update checklist that protects working profiles and makes rollback straightforward.
Record the working state
Before touching a successful setup, save the filenames and versions of the graphics-related mods currently installed. A screenshot or exported mod list is enough.
Also record important video settings and whether shaders or resource packs are active so you can reproduce the old state accurately.
Back up the instance
Copy the entire launcher instance when possible, especially if it contains valuable worlds or a large custom configuration. A file-level backup is useful, but an instance backup preserves everything together.
Store the backup outside the folder the launcher is likely to modify during an update.
Update dependency groups logically
If a major Minecraft or Fabric version changes, review the compatible versions of your loader, rendering mods, APIs, and Indium as a group. Do not assume only one jar needs replacing.
Read explicit incompatibility notices before launching a world.
Test a disposable world first
A fresh test world is ideal for confirming that the client launches and renders correctly. It reduces the risk of confusing a world-specific issue with a general mod compatibility problem.
Only open important worlds after the client has passed basic startup and rendering checks.
Keep rollback immediate
If the new setup fails, restore the complete known-good set rather than mixing individual old and new components randomly. A clean rollback gives you a stable base for the next attempt.
Once the update works, archive the new working version list for the next cycle.