Skip to main content

The Command API

The command API lets you create commands that can be executed by a player connected to the proxy or the console.

Creating a command

Each command class needs to implement a Command sub-interface. The choice depends on the type of arguments and the granularity of suggestions provided to the client. These include:


Internally, Velocity uses the Brigadier library to register and dispatch command actions. You can register your own CommandNodes by wrapping them in a BrigadierCommand. Let's see an example of a command that will tell whoever executes the command "Hello World" in light blue text.

package com.example.velocityplugin;

import com.mojang.brigadier.arguments.StringArgumentType;
import com.mojang.brigadier.Command;
import com.mojang.brigadier.tree.LiteralCommandNode;
import com.velocitypowered.api.command.BrigadierCommand;
import com.velocitypowered.api.command.CommandSource;
import com.velocitypowered.api.command.VelocityBrigadierMessage;
import com.velocitypowered.api.proxy.ProxyServer;
import net.kyori.adventure.text.Component;
import net.kyori.adventure.text.format.NamedTextColor;

public final class TestBrigadierCommand {

public static BrigadierCommand createBrigadierCommand(final ProxyServer proxy) {
LiteralCommandNode<CommandSource> helloNode = BrigadierCommand.literalArgumentBuilder("test")
// Here you can filter the subjects that can execute the command.
// This is the ideal place to do "hasPermission" checks
.requires(source -> source.hasPermission("test.permission"))
// Here you can add the logic that will be used in
// the execution of the "/test" command without any argument
.executes(context -> {
// Here you get the subject that executed the command
CommandSource source = context.getSource();

Component message = Component.text("Hello World", NamedTextColor.AQUA);

// Returning Command.SINGLE_SUCCESS means that the execution was successful
// Returning BrigadierCommand.FORWARD will send the command to the server
return Command.SINGLE_SUCCESS;
// Using the "then" method, you can add sub-arguments to the command.
// For example, this subcommand will be executed when using the command "/test <some argument>"
// A RequiredArgumentBuilder is a type of argument in which you can enter some undefined data
// of some kind. For example, this example uses a StringArgumentType.word() that requires
// a single word to be entered, but you can also use different ArgumentTypes provided by Brigadier
// that return data of type Boolean, Integer, Float, other String types, etc
.then(BrigadierCommand.requiredArgumentBuilder("argument", StringArgumentType.word())
// Here you can define the hints to be provided in case the ArgumentType does not provide them.
// In this example, the names of all connected players are provided
.suggests((ctx, builder) -> {
// Here we provide the names of the players along with a tooltip,
// which can be used as an explanation of a specific argument or as a simple decoration
proxy.getAllPlayers().forEach(player -> builder.suggest(
// A VelocityBrigadierMessage takes a component.
// In this case, the player's name is provided with a rainbow
// gradient created using MiniMessage.
MiniMessage.miniMessage().deserialize("<rainbow>" + player.getUsername())
// If you do not need to add a tooltip to the hint
// or your command is intended only for versions lower than Minecraft 1.13,
// you can omit adding the tooltip, since for older clients,
// the tooltip will not be displayed.
return builder.buildFuture();
// Here the logic of the command "/test <some argument>" is executed
.executes(context -> {
// Here you get the argument that the CommandSource has entered.
// You must enter exactly the name as you have named the argument
// and you must provide the class of the argument you expect, in this case... a String
String argumentProvided = context.getArgument("argument", String.class);
// This method will check if the given string corresponds to a
// player's name and if it does, it will send a message to that player
proxy.getPlayer(argumentProvided).ifPresent(player ->
// Returning Command.SINGLE_SUCCESS means that the execution was successful
// Returning BrigadierCommand.FORWARD will send the command to the server
return Command.SINGLE_SUCCESS;

// BrigadierCommand implements Command
return new BrigadierCommand(helloNode);

Brigadier commands have full backward compatibility with 1.12.2 and lower versions.

Custom plugin command argument types are not supported in Velocity, as they would require the client to also support them. We recommend sticking to the predefined Brigadier types provided.


Modeled after the convention popularized by Bukkit and BungeeCord, a SimpleCommand has three methods: one for when the command is executed, one to provide suggestions for tab completion, and one to check a CommandSource has permission to use the command. All methods receive a SimpleCommand.Invocation object, which contains the CommandSource that executed the command and the arguments as an array of strings. The previous example can also be implemented using this interface:

package com.example.velocityplugin;

import com.velocitypowered.api.command.CommandSource;
import com.velocitypowered.api.command.SimpleCommand;
import java.util.concurrent.CompletableFuture;
import java.util.List;
import net.kyori.adventure.text.Component;
import net.kyori.adventure.text.format.NamedTextColor;

public final class TestCommand implements SimpleCommand {

public void execute(final Invocation invocation) {
CommandSource source = invocation.source();
// Get the arguments after the command alias
String[] args = invocation.arguments();

source.sendMessage(Component.text("Hello World!", NamedTextColor.AQUA));

// This method allows you to control who can execute the command.
// If the executor does not have the required permission,
// the execution of the command and the control of its autocompletion
// will be sent directly to the server on which the sender is located
public boolean hasPermission(final Invocation invocation) {
return invocation.source().hasPermission("command.test");

// With this method you can control the suggestions to send
// to the CommandSource according to the arguments
// it has already written or other requirements you need
public List<String> suggest(final Invocation invocation) {
return List.of();

// Here you can offer argument suggestions in the same way as the previous method,
// but asynchronously. It is recommended to use this method instead of the previous one
// especially in cases where you make a more extensive logic to provide the suggestions
public CompletableFuture<List<String>> suggestAsync(final Invocation invocation) {
return CompletableFuture.completedFuture(List.of());

It's important to note invocation.arguments() doesn't include the command alias (e.g. teleport for /teleport foo bar). In the event that no arguments are specified, an empty array will be passed, rather than a null array.

If a player or the console executes the following command: /stats Player2 kills, the first argument will be Player2, which we can access using invocation.arguments()[0] and the second argument will be kills.


There's certain cases where you don't need to process the arguments. These may include:

  • A /say style command, where the arguments contain the message as a string; or
  • You're using an external command framework to process your commands.

A raw command indicates the proxy to pass the command alias and its arguments directly without further processing. Let's see an example of a command that echoes the received input:

package com.example.velocityplugin;

import com.velocitypowered.api.command.RawCommand;
import net.kyori.adventure.text.Component;

public final class EchoCommand implements RawCommand {

public void execute(final Invocation invocation) {

public boolean hasPermission(final Invocation invocation) {
return invocation.source().hasPermission("command.echo");

Registering a command

Now that we have created a command, we need to register it in order for it to work. To register commands, you use the CommandManager. We get the command manager by executing proxyServer.getCommandManager() with the proxy instance, or by injecting it using the @Inject annotation in the main class. The register method requires two parameters, the command metadata and the command object.

The CommandMeta contains the case-insensitive aliases and more advanced features. CommandManager provides a meta builder via the #metaBuilder(String alias) method.

package com.example.velocityplugin;

import com.velocitypowered.api.command.BrigadierCommand;
import com.velocitypowered.api.event.Subscribe;
import com.velocitypowered.api.event.proxy.ProxyInitializeEvent;
import com.velocitypowered.api.plugin.Plugin;
import com.velocitypowered.api.proxy.ProxyServer;

@Plugin(id = "helloworld")
public final class HelloWorldPlugin {
private final ProxyServer proxy;

public HelloWorldPlugin(ProxyServer proxy) {
this.proxy = proxy;

public void onProxyInitialize(ProxyInitializeEvent event) {
CommandManager commandManager = proxy.getCommandManager();
// Here you can add meta for the command, as aliases and the plugin to which it belongs (RECOMMENDED)
CommandMeta commandMeta = commandManager.metaBuilder("test")
// This will create a new alias for the command "/test"
// with the same arguments and functionality
.aliases("otherAlias", "anotherAlias")

// You can replace this with "new EchoCommand()" or "new TestCommand()"
// SimpleCommand simpleCommand = new TestCommand();
// RawCommand rawCommand = new EchoCommand();
// The registration is done in the same way, since all 3 interfaces implement "Command"
BrigadierCommand commandToRegister = TestBrigadierCommand.createBrigadierCommand(proxy);

// Finally, you can register the command
commandManager.register(commandMeta, commandToRegister);

If you're registering a BrigadierCommand, you may prefer to use the #register(BrigadierCommand) method or #metaBuilder(BrigadierCommand) to specify additional aliases.