Terramity

Terramity

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 Terramity 0.9.8-forge-1.20.1 (mod id terramity): its animation dispatcher returns early for entities that are not its own. 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	Result
terramity_animation_entity_guard	Terramity 0.9.8	BOTH	1.0.12	opt	skips 45 type checks

---

terramity_animation_entity_guard

Since: 1.0.12 · Script (1.0.19 and earlier): furious10-terramity.js Patched: net.mcreator.terramity.init.EntityAnimationFactory.onEntityTick Mixin (since 1.0.20): TerramityAnimationGuardMixin

What upstream did. Terramity's generated animation dispatcher tests 45 entity-type branches on every non-null living-tick event, for every living entity in the world, even though a class-header audit shows all 45 target classes directly implement GeckoLib's GeoEntity. An entity that is not a GeoEntity cannot match any branch.

What the patch does. For the ordinary Forge LivingTickEvent, returns after the original null checks when the entity is not a GeoEntity. The complete original body runs for every GeoEntity and for custom event subclasses whose entity getter could behave differently.

What stays the same. All animation reads, writes, resets and tick timing on eligible entities; no animation-result cache and no reduced frequency. Terramity's license does not permit redistributing its method bodies, so this patch carries only its own inserted code and leaves the unchanged body in the installed class behind an exact fingerprint.

Measured. terramity-unrelated 57.34 → 55.10 ns (−3.9 %); the saving per unrelated entity is small here because Terramity's chain is cheap per branch, but it runs for every living entity every tick.