This lightweight plugin to forward commands from the Bukkit-side to a Bungeecord server. It uses plugin-channels to communicate between the server instances. This part of a server->proxy->player connection and requires at least one player to be online. Therefore, we don't need to open a port and establish a new connection between the servers. Furthermore, on a RedisBungee environment it forwards the command only to currently used proxy by that specified player.
I'm open for suggestions.
If you like the project, leave a star on GitHub and contribute there.
- Lightweight
- Easy to use
- RedisBungee support (executes command only on the proxy of that player)
- Forwarding as Player or Console
- This plugin cannot forward commands to a Bungeecord server if no player is online
- Drop the plugin in the Bungee and Bukkit server
- Finished setup
commandforward.bukkit.command.forward.* - Allow to use all features of forward command commandforward.bukkit.command.forward - Allow to use base forward command commandforward.bukkit.command.forward.console - Allow to use console in forward command commandforward.bukkit.command.forward.other - Allow to use another player than ourself in forward command
/forward bridgePlayer cmd [args...]
bridgePlayer is the player which connection should be used. This is relevant for receiving the output or selecting the correct proxy in a RedisBungee environment.
cmd is the start of the actual command [] means it's optional
/forward playerName ping
/forward console ping
This will select a random player to forward the connection to the Bungee server, but it will be executed as Bungee console there.