Open andreasdc opened 2 years ago
ProtocolLib is required since Packet manipulation is a whole lot more complicated on Spigot than BungeeCord. Not to mention that many common plugins (Soft)depend on ProtocolLib which makes it a very common solution to use on a server.
I plan on making an API eventually. Please comment what you would like to use the API for.
@Andre601 I don't use PLIb at all and I probably won't use it anymore.
@CodeCrafter47 Just creating own variables from plugins, setting update delays, heads, header/footer, something like that. :)
@Andre601 I don't use PLIb at all and I probably won't use it anymore.
Again: ProtocolLib is used as it would otherwise require CodeCrafter to create and maintain an entire Packet manager just for this plugin. Not to mention would he also need to make sure that there isn't any conflicts with ProtocolLib when it would be used.
Just use it. It's not that much of an issue to begin with.
@Andre601 I don't use PLIb at all and I probably won't use it anymore.
Again: ProtocolLib is used as it would otherwise require CodeCrafter to create and maintain an entire Packet manager just for this plugin. Not to mention would he also need to make sure that there isn't any conflicts with ProtocolLib when it would be used.
Just use it. It's not that much of an issue to begin with.
In my situation I would have to use whole PLib just for 1 plugin.
One reason why an API could be good is this particular case on Discord, where some specific text can't be replaced by the plugin (ItemsAdder) to display the custom text: https://discord.com/channels/693095705421545563/693105414883115138/866058004167262258
What it should be:
What shows instead:
Will you make API for developers like in BTLP and remove ProtocolLib dependency? That would make plugin useful for more people. :)