Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dynamic registry loading location ignores namespace #4179

Open
Gaming32 opened this issue Oct 22, 2024 · 2 comments · May be fixed by #4180
Open

Dynamic registry loading location ignores namespace #4179

Gaming32 opened this issue Oct 22, 2024 · 2 comments · May be fixed by #4180

Comments

@Gaming32
Copy link

The dynamic registry loading code calls RegistryKeys.getPath which, unlike getTagsPath, is unpatched by Fabric API. This means that my custom bingo:difficulty dynamic registry gets loaded from data/<namespace>/difficulty instead of the namespaced data/<namespace>/bingo/difficulty.
@modmuss50
Copy link
Member

Is this a new issue in 1.21.2? Or are you seeing this in an older version as well?

@Gaming32
Copy link
Author

I don't think it's new in 1.21.2, which would technically make fixing this a breaking change.

Gaming32 added a commit to Gaming32/fabric-api that referenced this issue Oct 22, 2024
@Gaming32
Make dynamic registry element path be namespaced
f7d803b 
Fixes FabricMC#4179
@Gaming32 Gaming32 linked a pull request Oct 22, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make dynamic registry element path include namespace Gaming32/fabric-api
2 participants
@modmuss50 @Gaming32