Remove GTRegistry in favour of mapped registries - #5160
Open
gustovafing wants to merge 29 commits into
Open
Conversation
screret
suggested changes
Jul 21, 2026
gustovafing
force-pushed
the
gus/switch-forge-registries
branch
from
July 23, 2026 12:00
2942239 to
fb2b2eb
Compare
gustovafing
force-pushed
the
gus/switch-forge-registries
branch
from
July 27, 2026 07:19
e658818 to
ff22a83
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes GTRegistry, replacing it with native MC registries.
No external API changes.
Uses a registration hack to allow registration before the register event, keeping our current registration system intact (same thing we do on 1.21)
No AI driven tools were used for this pull request.
How Was This Tested
Gametests pass, game starts and all content loads properly.