Skip to content

Conversation

@Player3324
Copy link
Collaborator

We should keep inferring those names like in older TR versions. Without this mappings that rely on implicitly defined no-op mappings break when TR operates on a different source namespace from the mappings. Typically this involves deobfuscated class names that then cause their members to not get remapped.

Dropping missing mappings instead of inferring from source might show issues more proactively, but that'd require more effort on the API user and acts more surprisingly in typical use cases like below.

Fixes FabricMC/fabric-loader#1067
babric provides mappings for MC b1.7.3, a version that has a deobfuscated MC class name with obfuscated member names. The babric mappings don't have the noop class entry MC -> MC, the mapping file's source NS is intermediary and TR remaps clientOfficial to intermediary. Without this PR the members of the MC class retain their original obfuscated names because the mapping adapter drops all of then during the source NS adjustment.

@Player3324 Player3324 merged commit 40349b0 into FabricMC:master Jul 30, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fabric Loader 0.16.14 causes some Mixin injection points to be invalid?

3 participants