Forward command for the velocity/bungeecord console

[TheMeatCrew]

Summary

Add a forward command for the proxy console.

It's my understanding that there's no way to execute a command on a backend server from the proxy console.

[kangobot]

You're right, this didn't exist. The proxy console had no way to run commands on backend servers, only the reverse direction (/chc forward from Bukkit) was available.

I've added a /forward command to VelocityControl/BungeeControl in a draft PR. Once it ships, set Forward.Enabled: true in the proxy's settings.yml, then run:

forward <server> <command>

from the proxy console. Players can use it too with the chatcontrol.command.forward permission, and the server name tab completes.

Heads up: the target server needs at least one online player to receive the command, that is a Bukkit limitation and applies to all proxy messaging.

I proposed a fix here: https://github.com/kangarko/ChatControl-Src/pull/14

[kangarko]

Implemented and tested. VelocityControl and BungeeControl get a /forward command usable from the proxy console and by players with chatcontrol.command.forward. Enable it under the new Forward section in the proxy's settings.yml. Note that without Redis the target server needs at least one online player to receive the command, that is a plugin messaging limitation. Keeping this open until the next version ships.

[kangarko]

Fixed in BungeeControl 5.0.8 and VelocityControl 3.0.9. Update the proxy plugin, set Enabled: true under the new Forward section in the proxy's settings.yml and restart, then run forward from the proxy console. Players need the chatcontrol.command.forward permission. Without Redis the target server needs at least one online player to receive the command.