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

Mojang-mapped artifact #347

Open
BoBkiNN opened this issue Aug 6, 2024 · 2 comments
Open

Mojang-mapped artifact #347

BoBkiNN opened this issue Aug 6, 2024 · 2 comments
Labels

Comments

@BoBkiNN
Copy link

BoBkiNN commented Aug 6, 2024

i want to use AnvilGUI in my mojang-mapped plugin but lib is spigot-mapped. What should i do if i dont want my plugin use spigot mappings?

@0dinD
Copy link
Collaborator

0dinD commented Aug 6, 2024

I recently wrote some documentation about this matter which is about to get merged, see #345 and the new parts I wrote. Note that if you're just using Mojang mappings with Paperweight Userdev because it's easier for development, you can still use Spigot mappings for your plugin (see the documentation I linked above).

Whether AnvilGUI should be compiled against both Spigot and Mojang mappings is something that has been discussed at length before, see:

Personally I haven't yet been convinced that the effort it would take to support both is really worth it because I haven't really seen any concrete and noteworthy benefits. But I am also not opposed to it if someone else is willing to put in that effort.


Also, there are forks of AnvilGUI which are rewritten to compile against Mojang mappings, which I was going to write about in the documentation update, but Wes asked me to remove it.

@BoBkiNN
Copy link
Author

BoBkiNN commented Aug 6, 2024

Thanks for links and also I think that one of good options (if possible) is to use gradle build system to use some sort of remapper on new versions to create both spigot and mojang artifacts, so this will add support for both new spigot and paper

@0dinD 0dinD added the question label Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants