Build every version with Mojang mappings instead of Yarn

Conversation 0 Commits 3 Files Changed 58

+1082 -972

3 Commits

Author	SHA1	Message	Date
selimaj-devandclaude	55067e9761	Point common at its master merge commit Check / compile (pull_request) Successful in 11m53s Details Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-09-30 18:04:12 +02:00
selimaj-devandclaude	09bc223b8b	Implement the Ref interfaces explicitly in their mixins Several mixins implemented a Ref method only through a vanilla method of the same name. Released jars rename vanilla methods to intermediary names, so those Ref methods had no implementation there and threw AbstractMethodError: the armour display's durability, the status effects' icon and infinite checks, the SVG texture size and the pre-1.21.6 matrix stack's push and pop. With Mojang's names the same happens in development (1.21.4 crashed on the title screen). Each mixin now shadows the vanilla method and implements the Ref method by calling it. Points common at the Ref renames this needs. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-09-30 17:42:48 +02:00
selimaj-devandclaude	af27907356	Build every version with Mojang mappings instead of Yarn Minecraft ships unobfuscated from 26.1, and 1.21.11 has the last Yarn release, so the shared src/ has to use Mojang's names before newer versions can be added (#39). Each version's sources were migrated with Loom's migrateMappings and merged back into src/, so code that is only active on other versions is migrated too. Where Mojang's names differ between 1.21.x versions, src/ uses the newest ones: Stonecutter replacements swap in the older Identifier/ResourceLocation and Avatar/Player renderer names, and version comments cover the few package moves and renamed methods. The fog mixin now targets setupFog on every version. Yarn's applyFog named two methods from 1.21.6 on, so it also applied to updateBuffer. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-09-30 17:39:14 +02:00

Author

SHA1

Message

Date

selimaj-devandclaude

55067e9761

Point common at its master merge commit

Check / compile (pull_request) Successful in 11m53s

Details

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-09-30 18:04:12 +02:00

selimaj-devandclaude

09bc223b8b

Implement the Ref interfaces explicitly in their mixins

Several mixins implemented a Ref method only through a vanilla method
of the same name. Released jars rename vanilla methods to intermediary
names, so those Ref methods had no implementation there and threw
AbstractMethodError: the armour display's durability, the status
effects' icon and infinite checks, the SVG texture size and the
pre-1.21.6 matrix stack's push and pop. With Mojang's names the same
happens in development (1.21.4 crashed on the title screen).

Each mixin now shadows the vanilla method and implements the Ref
method by calling it. Points common at the Ref renames this needs.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-09-30 17:42:48 +02:00

selimaj-devandclaude

af27907356

Build every version with Mojang mappings instead of Yarn

Minecraft ships unobfuscated from 26.1, and 1.21.11 has the last Yarn
release, so the shared src/ has to use Mojang's names before newer
versions can be added (#39).

Each version's sources were migrated with Loom's migrateMappings and
merged back into src/, so code that is only active on other versions
is migrated too. Where Mojang's names differ between 1.21.x versions,
src/ uses the newest ones: Stonecutter replacements swap in the older
Identifier/ResourceLocation and Avatar/Player renderer names, and
version comments cover the few package moves and renamed methods.

The fog mixin now targets setupFog on every version. Yarn's applyFog
named two methods from 1.21.6 on, so it also applied to updateBuffer.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-09-30 17:39:14 +02:00

Build every version with Mojang mappings instead of Yarn #49