Avaritia compatibility is confusing because the name survived longer than any single codebase. The reliable approach is to identify the project first and the Minecraft version second.
Original Avaritia: the 1.7.10 identity
The original Spiteful_Fox project is tied to Minecraft 1.7.10. Guides written for that era can describe loader behavior, integrations, and recipe tooling that should not be assumed to apply to a modern port.
Avaritia 1.1x: the familiar 1.12.2 path
Avaritia 1.1x is the line many players associate with Minecraft 1.12.2 and Forge. If a pack is built around the mature 1.12.2 mod ecosystem, this is usually the project family people mean when they search for classic Avaritia in that version.
Modern 1.20.1+: verify the implementation
For Minecraft 1.20.1 and later, several community implementations exist. Some modern Re:Avaritia builds support more than one loader family. That makes “1.20.1 compatible” incomplete unless the release also names the correct loader.
Fabric searches need project-level verification
Fabric support is not a property of the original Avaritia name. Modern community projects can provide Fabric builds, but a Fabric result should be checked against the maintainer, release page, dependencies, and supported Minecraft range.
Bedrock and PE are separate ecosystems
Avaritia-branded Bedrock or PE addons are not drop-in equivalents of Java mods. Packaging, scripting, recipe behavior, installation, permissions, and feature parity can all differ. Treat them as independent projects.
Compatibility checklist
Before installation, write down five fields: project name, Minecraft version, loader, Java version, required dependencies. If any field is unknown, the setup is not ready.
Related guides
Continue with another focused guide from the Avaritia resource library.