CommandForward: Send Commands to BungeeCord Proxy from Minecraft

What Is CommandForward and Why Your BungeeCord Network Needs It Running a Minecraft server network often means juggling multiple backend servers behind a BungeeCord proxy. One of the persistent headaches is executing proxy-level commands from a Bukkit/Spigot server without opening extra ports or ...

Download CommandForward for Minecraft 1.9

Original name: CommandForward

Minecraft: 1.9

FileVersionLoaderSize
CommandForward.jar1.9—17 КБDownload

What Is CommandForward and Why Your BungeeCord Network Needs It

Running a Minecraft server network often means juggling multiple backend servers behind a BungeeCord proxy. One of the persistent headaches is executing proxy-level commands from a Bukkit/Spigot server without opening extra ports or maintaining a separate connection. That’s exactly where CommandForward steps in — a lightweight, no-fuss plugin that forwards commands from the Bukkit side straight to your BungeeCord instance using the existing player connection.

How CommandForward Works Under the Hood

Instead of relying on a dedicated TCP socket or a separate messaging system, CommandForward piggybacks on Minecraft’s own plugin-channel protocol. As long as at least one player is online, the plugin can route your command through that player’s connection to the proxy. This design means you never have to expose a new port or worry about firewall rules — the communication channel already exists. In a RedisBungee environment, things get even smarter: the plugin automatically picks the specific proxy that the designated player is connected to, so the command executes exactly where it should, not on some random instance.

Core Features That Make CommandForward Stand Out

  • Lightweight and dependency-free: Just drop the jar into both your BungeeCord and Bukkit plugin folders, and it works. No external libraries or complex configuration files required.
  • RedisBungee support: In multi-proxy setups with RedisBungee, CommandForward respects the player-to-proxy mapping. This prevents commands from landing on the wrong proxy and ensures output is routed correctly.
  • Execute as player or console: You can forward a command as if the bridge player typed it themselves, or you can run it as the BungeeCord console — perfect for administrative tasks that need elevated permissions.
  • Simple permission structure: Four clear permissions let you control exactly who can use the forward command, who can specify a console execution, and who can impersonate another player.

Permissions You Need to Know

CommandForward keeps its permission nodes straightforward. Here’s what each one does:

  • commandforward.bukkit.command.forward.* — Grants access to all features of the forward command, including console and other-player forwarding.
  • commandforward.bukkit.command.forward — Allows basic use of the /forward command.
  • commandforward.bukkit.command.forward.console — Permits using the “console” keyword to execute the command as the BungeeCord console.
  • commandforward.bukkit.command.forward.other — Lets you specify a bridge player other than yourself, which is essential for targeting specific proxy instances in RedisBungee setups.

These granular permissions make it easy to give moderators limited access while reserving full proxy control for administrators.

Setting Up CommandForward in Your Network

Installation is refreshingly simple. Place the plugin jar on both your BungeeCord proxy and every Bukkit/Spigot server that needs to send commands. There’s no configuration file to tweak — the plugin auto-registers its channel and is ready to go immediately. Once both sides have the plugin, you can start forwarding commands right away.

For server owners who also tinker with modded clients or want a streamlined way to manage multiple server instances, the foxygame.net launcher can be a real time-saver. It provides a modern, flexible interface where you can download mods and plugins directly from the menu, making it easy to keep tools like CommandForward up to date across your test environments without manually hunting for jar files.

Using the Forward Command

The syntax is clean and intuitive. On any Bukkit server with the plugin, you type:

/forward <bridgePlayer> <cmd> [args...]

Here, bridgePlayer is the player whose connection will carry the command to the proxy. This player must be online. The cmd is the BungeeCord command you want to run, and optional arguments follow. Two examples make it crystal clear:

  • Execute as a player: /forward playerName ping — This sends the ping command to the proxy, as if playerName typed it. The output appears in that player’s chat (or console, depending on the command).
  • Execute as console: /forward console ping — Instead of a player name, you use the keyword “console”. The plugin picks a random online player to bridge the connection, but the command runs with BungeeCord console privileges. This is ideal for global broadcasts, proxy-wide kicks, or maintenance announcements.

Important Caveat: A Player Must Be Online

Because CommandForward relies on an active player connection to tunnel the command, it cannot function when no one is online. This is the trade-off for avoiding open ports and extra network configuration. In practice, most servers have at least one player or a dummy account online for monitoring, so this limitation rarely causes issues. Just keep it in mind for fully automated, player-less maintenance scripts — you’ll need an alternative approach for those rare moments.

Open Source and Community-Driven

CommandForward is fully open source, hosted on GitHub at https://github.com/TuxCoding/CommandForward. You don’t need to decompile anything to understand the internals — the code is well-commented and includes build utilities. The developer welcomes forks, stars, pull requests, and issues, so if you spot a bug or dream up a feature, you can contribute directly. This transparency also means you can audit the plugin for security and performance, which is a big plus for network owners who value control over every piece of their infrastructure.

Why CommandForward Belongs in Your Admin Toolkit

For any BungeeCord network that needs to trigger proxy commands from the backend — whether it’s for moderation, automated tasks, or seamless cross-server communication — CommandForward delivers a clean, secure solution. It avoids the complexity of setting up additional sockets, respects your RedisBungee topology, and gives you fine-grained permission control. The requirement for an online player is a small price to pay for such a lightweight and elegant design. If you’re tired of logging into your proxy console manually or building custom messaging systems, give CommandForward a try. It’s one of those plugins that quietly solves a real problem and then stays out of your way.