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.

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

Unify tag namespace and conventions between Neoforge and Fabric (and Quilt) for 1.21 MC #345

Open
sylv256 opened this issue Sep 10, 2023 · 2 comments

Comments

@sylv256
Copy link

sylv256 commented Sep 10, 2023

FabricMC/fabric#3310

If Fabric implements this, we will probably have to. It's a good system anyways, so I don't see any problem with Quilt-exclusive mods using it. If we don't want to implement it for Quilt-exclusive mods, we could just use a system to convert their tags to ours. Again though, I think we should implement this both for compatibility and because it's beneficial to modding.

But a mod could be called common!

Okay, then we should reserve that namespace then (with the exception of Fabric mods unless Fabric reserves common).

@sylv256 sylv256 changed the title Unify tag namespace and conventions between Neoforge and Fabric for 1.21 MC Unify tag namespace and conventions between Neoforge and Fabric (and Quilt) for 1.21 MC Sep 10, 2023
@F5T3
Copy link

F5T3 commented Sep 10, 2023

You literally just took the comments from the original pull and reworded them so that it looks original, and why did you make two issues? Oh, one is in QuiltMC and this one is in this repo.

@sylv256
Copy link
Author

sylv256 commented Sep 10, 2023

Oh, one is in QuiltMC and this one is in this repo.

I think you meant Fabric, but yes, this is a mirror of Fabric's issue.

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

No branches or pull requests

2 participants