Kiwi

Kiwi

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 Kiwi 11.8.28 (mod id kiwi): its module manifests are found without searching every jar. 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
kiwi_manifest_lookup_index	Kiwi 11.8.28	BOTH	1.0.30	opt

---

kiwi_manifest_lookup_index

Since: 1.0.30 · Target: Kiwi 11.8.28 · Side: BOTH · Kind: opt

Mixin: KiwiManifestLookupMixin

Kiwi module manifests found without searching every jar. When the game starts, Kiwi asks for a "<mod>.kiwi.json" file for every installed mod; only two mods ship one. Each question makes Forge ask all ~530 jars, during the part of startup that runs one mod at a time (about 1.7 s in the our own recording). Now the top folder of every jar is listed once and the questions read that list. Kiwi gets exactly the same files (or the same "none"); jars cannot change while the game runs, and anything the list cannot answer exactly is still asked directly.

Idea: lazyyyyy (faster Kiwi manifest finding), idea text only

Measured: offline on Forge's own class loader over this pack's 506 jars, 66,640 checks identical; Kiwi's 606 lookups 441-614 -> 37-52 ms (one-time listing set-up about 50 ms).

Since 1.0.33. In 1.0.30 this control switched itself off at every start. The lookup index it shares with two other controls first checks the versions of two Forge libraries, and it could not read the version of one of them, so it logged game-layer resource index off and left the original lookups in place. It reads that version correctly now and the control runs.