Almost Unified

Almost Unified

Minecraft 1.20.1 / Forge: this page documents that build and its measurements. For the separate 170-control Minecraft 1.21.1 port, see Minecraft 1.21.1 NeoForge.

One control for Almost Unified 0.11.0 (mod id almostunified): duplicate recipes are found without comparing every recipe with every other one. The switch checks the code it would change against the tested build; another build is left untouched with one WARN line (see How the patches are applied).

Key	Target	Side	Since	Kind
almostunified_duplicate_groups	Almost Unified 0.11.0	BOTH	1.0.29	opt

---

almostunified_duplicate_groups

Since: 1.0.29 · Target: Almost Unified 0.11.0 · Side: BOTH · Kind: opt

Mixins: DuplicateGroupsMixin, RecipeLinkAccessor, CompareSettingsAccessor

Almost Unified: duplicate recipes are found without comparing every recipe with every other one. After unifying, Almost Unified compares every changed recipe with every recipe of the same type to find duplicates (about 43,500 recipes here, so tens of millions of comparisons on each data load). Two recipes can only be duplicates when the fields it compares are the same and have equal values (and, for crafting recipes, when they make the same item), so each recipe now gets a short fingerprint of exactly that, and only recipes with the same fingerprint are compared, in the same order, with Almost Unified's own comparison. The same duplicates are found and removed, the same warnings are logged in the same order (crafting outputs are still read in Almost Unified's order), and the same error is raised where Almost Unified raises one.

Measured: offline on Almost Unified's own classes with this pack's 41,000 recipe files and three duplicate configs (incl. strict mode and sanitizing): 47,207 duplicate checks gave identical results, links, cached outputs, log lines and exceptions; with the pack's config 178 comparisons were left of 33.7 million. In this pack's profiles the duplicate pass was 6.3% of the dedicated server's startup thread (about 1 s; Almost Unified logs 2.3 s) and 1.4% of the client's world load (about 0.8 s; logged 1.7 s), and it repeats on every /reload.