Repository navigation
Is protocol on Modrinth? So that I can use it as a dependency of my project? #3684
Replies: 1 comment
|
Short answer: no, ProtocolLib isn't on Modrinth right now. There's no project for it there, and the request to publish it is still open in #3677 (an earlier one, #3640, was closed as not planned). Modrinth's dependency picker only lets you link other Modrinth projects, so you can't attach it as a proper dependency yet. What most plugin authors do in the meantime: 1. Declare it as a dependency in your plugin, so a server without it fails with a clear message instead of a stack trace: # plugin.yml
depend: [ProtocolLib](Use 2. Point people to it from your Modrinth page. Put a "Requires ProtocolLib" line near the top of your description with links to the official downloads:
Adding the same note to each version's changelog helps too, since some people only read that. 3. Don't bundle or re-upload ProtocolLib yourself. It has to run as its own plugin, so shading it into your jar won't work, and Modrinth doesn't allow uploading other people's projects without permission. If having a "real" Modrinth dependency matters a lot to you, the alternative is PacketEvents, which is on Modrinth and covers most of the same packet-level stuff. That means porting your packet code though, so it's only really worth it if you're early in the project. And give #3677 a 👍 so the maintainer can see there's demand for it. |
Uh oh!
There was an error while loading. Please reload this page.
So I made my plugin with the use of this library. But now, if I want to publish a working version of my plugin, I have to also attatch a dependency. But ProtocolLib is not on Modrinth, so I cannot add it as a dependency. So what do I do??
All reactions