BungeeCord Commands BungeeCord Commands Reference for proxy-side commands in BungeeCord These commands are completely handled by the proxy, so if you try to have a Bukkit plugin on your server execute one of the following Bungee commands, it will not work! There are several plugins that enable running Bungee commands from a Bukkit server, take a look at the Bukkit - Bungee resource category to find some. If the Typical user: is listed as a Server Administrator, this indicates that the command is for administrating a server and is usually run by administrators of the proxy. If the Typical user: is listed as a Player, this indicates that the command is used by both players and server administrators. Guide: <required argument> - this argument is required for executing the command. [optional argument] - this argument is not required for executing the command. Commands: /alert <message> Permission node: bungeecord.command.alert Issues an alert to all users connected to BungeeCord. This is useful for announcements that need to be shown across every server. Colour codes may be used with &. The special code &h will hide all default formatting, allowing for completely custom messages. Default group: admin Typical user: Server Administrator /alertraw <json> Permission node: bungeecord.command.alert Issues an alert to all users connected to BungeeCord, but allows the use of Minecraft JSON formatting. Default group: admin Typical user: Server Administrator /bungee Permission node: none Shows what version of BungeeCord is currently being run. Default group: all Typical user: Player /end <message> Permission node: bungeecord.command.end Shuts down the BungeeCord instance, and disconnects any users connected. Equivalent to /stop on your Spigot servers, except stops bungee Default group: admin Typical user: Server Administrator /find <player> Permission node: bungeecord.command.find Confirms whether a player with the username provided is online and determines which server the player is connected to. Default group: none Typical user: Server Administrator /glist Permission node: bungeecord.command.list Shows a list of all players connected to BungeeCord. This list is separated by each individual server on the BungeeCord proxy and provides a total player count on the proxy. Default group: default Typical user: Player /greload Permission node: bungeecord.command.reload Reloads the BungeeCord configuration. Similar to the Bukkit reload command, this is not intended to be used on a regular basis, and can lead to unexpected behaviour. The command will reload all servers, listeners and a few options from the configuration. It will not reload permissions or plugins. Note: This is highly unreliable, and it is strongly recommended that you restart your BungeeCord instance instead of reloading it. Default group: admin Typical user: Server Administrator /ip <player> Permission node: bungeecord.command.ip Shows the real IP address of a player connected to BungeeCord. This command exists since using an IP command with a Bukkit plugin, such as Essentials, could possibly return as localhost due to the way BungeeCord works. Default group: admin Typical user: Server Administrator /perms Permission node: none Shows all permissions you have, and all groups which you are in. Default group: admin Typical user: Player and Server Administrator /send <player/current/all> <target> Permission node: bungeecord.command.send Sends the specified player(s) to the specified server. Passing "all" will send all players who are on the proxy but not on the target server. Passing a player name will send the specified player, and "current" will send all players on your server. Default group: none Typical user: Server Administrator /server [server] Permission node: bungeecord.command.server When used with an argument, transfers you to the specified server. When used with no arguments, lists all servers you can connect to. Default group: default Typical user: Player (View this Page on the Wiki) Last Modified: Feb 2, 2019 at 9:56 PM (Cached) #1 jtaylor69, Jun 10, 2013 Like x 1 Agree x 1 Winner x 1 Useful x 1
So trying to cut back on using portals, as more seems to slow down server startup, I thought I'd use commandblocks with pressureplates or tripwires. Use of Send does not work unless you are a player? Might want to note that in there, along with other commands of such.
Uh, what version of Spigot/Bungee is needed for that? I haven't been able to use the built in raw command, or this new one yet.
I would assume you could use the same permission in each server's permissions plugin. I haven't tested it, otherwise I have no clue.
Currently, the permissions are only global. You will need to resort to a BungeeCord plugin or block the command in its entirety.
Hello @md_5, can you add the command, which add player to custom group or grand for him permission? Thanks
Short answer: It's possible, but not easy. It won't work directly from the command block, but you might be able to simulate that with a Bungee-integrated plugin. I'm not really sure how that kind of thing works, but I know you could do it by making a Bukkit plugin, and then integrating it into a Bungee plugin.
Actually, there is one and it's explained right in front of us! On page one of this thread it outlines a plugin that can run commands across bungee networks and in bukkit servers: I took the code and compiled it against the latest BungeeCord and Spigot jars and whilst it works for regular commands (/sync player F451 give F451 stone 64), it still will not work for the /send command in a command block or when typed in either (/sync player F451 send F451 adventure - sends the command, but results in the console reporting "unknown command. Type /help for help", so something amiss there. I will keep experimenting, but thanks for the reply. It's absolutely along the right tracks. F451
