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

Programmical plugin registration #64

Closed
XakepSDK opened this issue Sep 2, 2018 · 1 comment
Closed

Programmical plugin registration #64

XakepSDK opened this issue Sep 2, 2018 · 1 comment
Labels
type: feature New feature or request

Comments

@XakepSDK
Copy link

XakepSDK commented Sep 2, 2018

Add a way to register plugin through API. I need this for bungee api proxying.

@astei astei added the type: feature New feature or request label Sep 2, 2018
@astei
Copy link
Contributor

astei commented Sep 2, 2018

I'm unlikely to grant this request, for a few major reasons:

  • Velocity is not intended to provide full compatibility for the BungeeCord API (the goal is approximate parity). It has a very different design philosophy.
  • Velocity intentionally does not support dynamic plugin enabling and disabling. This approach has proven to be extremely prone to breakage (just look at everyone who admonishes the use of /reload on Bukkit). This is similar to what Sponge does and it's an approach I consider to be better overall.

In conclusion, you'd be better off keeping the Velocity and "fake Bungee" worlds separate, if you really wanted to undertake this project.

Even better, why not write some native Velocity plugins? We've already got a few major plugins ported to Velocity (ServerListPlus, LuckPerms, and soon NuVotifier), and these plugins help form the core of most peoples' servers. We could use a more complete suite. Shimming the BungeeCord API doesn't help us generate our own plugin ecosystem (I make an exception for the widely-used BungeeCord plugin messaging API).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants