The safest Avaritia installation is a sequence of verification steps, not a file copied into an existing mods folder. The goal is to make every failure explainable and reversible.
1. Identify the project before the version
Start by naming the project line: original Avaritia, Avaritia 1.1x, Re:Avaritia, or another clearly documented port. Two projects can both advertise Minecraft 1.20.1 while requiring different loaders, dependencies, config formats, or feature expectations.
2. Match Minecraft, loader and Java as one unit
Treat Minecraft version, Forge/Fabric/NeoForge version, and Java runtime as a compatibility unit. Do not update one component in isolation inside a working pack unless you know the others support that change.
3. Create a complete backup, not only a world copy
For a heavily customized pack, the useful backup includes the world, configs, scripts, datapacks, server configs, and the exact mod list. Without those pieces, restoring the world may still produce a different registry or recipe environment.
4. Prove the smallest possible launch
Launch the target Minecraft version with the loader, Avaritia build, and only required dependencies. Confirm the game reaches the menu and the mod is detected before adding recipe viewers, optimizers, integrations, scripts, and the full pack.
5. Add complexity in controlled groups
Restore other mods in logical batches—libraries, content systems, recipe viewers, performance mods, scripting systems. If a conflict appears, the last group is small enough to investigate instead of searching through hundreds of files.
6. Test a copied world before production
Open a copy of the actual world and validate inventories, recipes, machines, chunk loading, and startup time. A clean test world can prove the mod loads; only a copied production world can reveal migration problems.
Related guides
Continue with another focused guide from the Avaritia resource library.