You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The issue is, that (I assume) some plugins will not work right with this plugin no matter what, due to some complex code structures.
Describe the solution you'd like
An API could let developers of plugins integrate with Velocity easier. It could provide them with tools to for example have code, which will only run on Velocity when the API is detected, or utilities for translation correction. Im not a developer myself, and I don't know which things would be good to have for a plugin API, but it sure would make things easier if people could interveine with the translation process in their plugins. It would enable developers to make sure their Bungeecord plugins work with Velocity.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Well while this might help some plugins ‒ and I would encourage authors to state so if they think that Snap could provide some stuff to make their life easier ‒ I don't think it would help much overall because most incompatibilities that have come up are due to the usage of internal classes instead of API (like sending custom packets or simply not using the plugin API correctly) which can't be realistically replicated on Velocity.
Besides that: If they are already adding custom support for Snap it wouldn't be much more work to just directly add Velocity support anyways. Compared to different Minecraft server plugin APIs. proxies have very little logic and a conversion process is usually pretty straight forward.
Is your feature request related to a problem? Please describe.
The issue is, that (I assume) some plugins will not work right with this plugin no matter what, due to some complex code structures.
Describe the solution you'd like
An API could let developers of plugins integrate with Velocity easier. It could provide them with tools to for example have code, which will only run on Velocity when the API is detected, or utilities for translation correction. Im not a developer myself, and I don't know which things would be good to have for a plugin API, but it sure would make things easier if people could interveine with the translation process in their plugins. It would enable developers to make sure their Bungeecord plugins work with Velocity.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: