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

API and no dependencies #22

Open
andreasdc opened this issue Jul 12, 2021 · 6 comments
Open

API and no dependencies #22

andreasdc opened this issue Jul 12, 2021 · 6 comments

Comments

@andreasdc
Copy link

Will you make API for developers like in BTLP and remove ProtocolLib dependency? That would make plugin useful for more people. :)

@Andre601
Copy link
Contributor

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.

@CodeCrafter47
Copy link
Owner

I plan on making an API eventually. Please comment what you would like to use the API for.

@andreasdc
Copy link
Author

@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
Copy link
Contributor

@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.

@andreasdc
Copy link
Author

@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.

@Andre601
Copy link
Contributor

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:
expectation

What shows instead:
reality

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

3 participants