This effectively closes #68.
In the absence of work on a native Velocity plugin communication API, I think we should strongly consider integrating BungeeQuack directly into the Velocity core.
The main advantage of doing this is that users get support with the majority of BungeeCord-Bukkit plugins out there without requiring more drastic work on our end (to, say, implement a compatibility layer for the BungeeCord plugin API).
BungeeQuack is already one of the most popular Velocity plugins out there and provides an important asset to help users move from BungeeCord to Velocity. It makes sense for us to ease the transition as much as possible.
This effectively closes #68.
In the absence of work on a native Velocity plugin communication API, I think we should strongly consider integrating BungeeQuack directly into the Velocity core.
The main advantage of doing this is that users get support with the majority of BungeeCord-Bukkit plugins out there without requiring more drastic work on our end (to, say, implement a compatibility layer for the BungeeCord plugin API).
BungeeQuack is already one of the most popular Velocity plugins out there and provides an important asset to help users move from BungeeCord to Velocity. It makes sense for us to ease the transition as much as possible.