Differences

This shows you the differences between two versions of the page.

--- tutorial:commands [2019/07/29 19:19] – started fixing english errors but it's way too long lmao fudge
+++ tutorial:commands [2023/11/18 11:21] – solidblock
@@ Line 1: / Line 1: @@
+Licensing: The code in this article is licensed under the "Creative Commons Zero v1.0 Universal" license. The license grants you the rights to use the code examples shown in this article in your own mods.
 ====== Creating Commands ======
-Creating commands can allow a mod developer to add functionality that a player can use through a command.
+Creating commands can allow a mod developer to add functionality that can used through a command. This tutorial will teach you how to register commands, and the general command structure of Brigadier.
-This tutorial will teach you how to register commands, and the command structure of Brigadier along with some more advanced commands structures.
-===== Registering Commands =====
+===== What is Brigadier? =====
-If you just want to see how to register commands you've come to the right place here.
+Brigadier is a command parser & dispatcher written by Mojang for use in Minecraft. Brigadier is a tree based command library where you build a tree of arguments and commands.
-Registering commands is done through ''CommandRegistry'' with the ''register'' method.
+The source code for brigadier can be found here: https://github.com/Mojang/brigadier
-The ''register'' method specifies two arguments, the dedicated flag and a consumer representing the ''CommandDispatcher''. These methods should be placed in your mod's initializer.
+===== The ''Command'' interface =====
-The dedicated flag if set to true will tell Fabric to only register the command on a ''DedicatedServer'' (if false than the command will register on both the ''InternalServer'' and ''DedicatedServer'').
+In Minecraft, ''com.mojang.brigadier.Command'' is a functional interface, which runs some specific things, and throw a ''CommandSyntaxException'' in some cases. It has a generic type ''S'', which defines the type of the //command source//. The command source provides some context in which a command was ran. In Minecraft, the command source is typically a ''<yarn class_2168>'' which can represent a server, a command block, rcon connection, a player or an entity. In some cases, it can also be a ''<yarn class_637>''.
-Below are a few examples of how the commands can be registered.
+The single method in ''Command'', ''run(CommandContext<S>)'' takes a ''CommandContext<S>'' as the sole parameter and returns an integer. The command context holds your command source of ''S'' and allows you to obtain arguments, look at the parsed command nodes and see the input used in this command.
-<code java>
+Like other functional interfaces, it is usually used as a lambda or a method reference:
-CommandRegistry.INSTANCE.register(false, dispatcher -> TutorialCommands.register(dispatcher)); // All commands are registered in a single class that references every command.
-CommandRegistry.INSTANCE.register(false, dispatcher -> { // You can also just reference every single class also. There is also the alternative of just using CommandRegistry
-    TutorialCommand.register(dispatcher);
-    TutorialHelpCommand.register(dispatcher);
-});
-CommandRegistry.INSTANCE.register(true, dispatcher -> { // Or directly registering the command to the dispatcher.
-	dispatcher.register(LiteralArgumentBuilder.literal("tutorial").executes(ctx -> execute(ctx)));
-});
-</code>
-==== A very basic command ====
-Wait isn't this the exact same command from the Brigadier tutorial? Well yes it is but it is here to help explain the structure of a command.
 <code java>
-// The root of the command. This must be a literal argument.
+Command<ServerCommandSource> command = context -> {
-dispatcher.register(LiteralArgumentBuilder.literal("foo")
+    return 0;
-// Then add an argument named bar that is an integer
+};
-    .then(RequiredArgumentBuilder.argument("bar", integer())
-	// The command to be executed if the command "foo" is entered with the argument "bar"
-        .executes(ctx -> {
-            System.out.println("Bar is " + IntArgumentType.getInteger(ctx, "bar"));
-	    // Return a result. -1 is failure, 0 is a pass and 1 is success.
-            return 1;
-            }))
-    // The command "foo" to execute if there are no arguments.
-    .executes(ctx -> {
-        System.out.println("Called foo with no arguments");
-        return 1;
-    })
-);
 </code>
-The main process registers the command "foo" (Root Node) with an optional argument of "bar" (Child node).
+The integer can be considered the result of the command. Typically negative values mean a command has failed and will do nothing. A result of ''0'' means the command has passed. Positive values mean the command was successful and did something.
-Since the root node must be literal, The sender must enter the exact same sequence of letters to execute the command, so "Foo", "fOo" or "fooo" will not execute the command.
-===== Brigadier Explained =====
-Brigadier starts with the ''CommandDispatcher'' which should be thought more as a tree rather than a list of methods.
+==== What can the ServerCommandSource do? ====
-The trunk of the tree is the CommandDispatcher.
-The register(LiteralArgumentBuilder) methods specify the beginning of branches with the following then methods specifying the shape of length of the branches.
-The executes blocks can be seen at the leaves of the tree where it ends and also supplies the outcome of the system.
-The execute blocks specify the command to be ran. As Brigadier's Command is a FunctionalInterface you can use lambdas to specify commands.
+A ''ServerCommandSource'' provides some additional implementation specific context when a command is run. This includes the ability to get the entity that executed the command, the world the command was ran in or the server the command was run on.
-==== CommandContexts ====
+<code java [enable_line_numbers="true"]>
+// Get the source. This will always work.
+final ServerCommandSource source = ctx.getSource();
-When a command is ran, Brigadier provides a CommandContext to the command that is ran.
+// Unchecked, may be null if the sender was the console or the command block.
-The CommandContext contains all arguments and other objects such as the inputted String and the ''Command Source'' (ServerCommandSource in Minecraft's implementation).
+final @Nullable Entity sender = source.getEntity();
-==== Arguments ====
+// Will throw an exception if the executor of the command was not an Entity.
+// The result of this could contain a player. Also will send feedback telling the sender of the command that they must be an entity.
+// This method will require your methods to throw a CommandSyntaxException.
+// The entity options in ServerCommandSource could return a CommandBlock entity, any living entity or a player.
+final @NotNull Entity sender2 = source.getEntityOrThrow();
-The arguments in Brigadier both parse and error check any inputted arguments.
+// null if the executor of the command is not a player.
-Minecraft creates some special arguments for it's own use such as the ''EntityArgumentType'' which represents the in-game entity selectors ''@a, @r, @p, @e[type=!player, limit=1, distance=..2]'', or an ''NBTTagArgumentType'' that parses NBT and verifies that the input is the correct syntax.
+final @Nullable ServerPlayerEntity player = source.getPlayer():
-You could do the long method of typing ''CommandManager.literal("foo")'' and it would work, but you can statically import the arguments and shorten that to ''literal("foo")''.
+// Will throw an exception if the executor of the command was not explicitly a Player.
-This also works for getting arguments, which shortens the already long ''StringArgumentType.getString(ctx, "string")'' to ''getString(ctx, "string")''.
+// Also will send feedback telling the sender of the command that they must be a player.
-This also works for Minecraft's arguments.
+// This method will require your methods to throw a CommandSyntaxException.
+final @NotNull ServerPlayerEntity player = source.getPlayerOrThrow();
-And your imports would look something like this:
+// Gets the sender's position as a Vec3d when the command was sent.
-<code java>
+// This could be the location of the entity/command block or in the case of the console, the world's spawn point.
-import static com.mojang.brigadier.arguments.StringArgumentType.getString; // getString(ctx, "string")
+final Vec3d position = source.getPosition();
-import static com.mojang.brigadier.arguments.StringArgumentType.word; // word(), string(), greedyString()
-import static net.minecraft.server.command.CommandManager.literal; // literal("foo")
-import static net.minecraft.server.command.CommandManager.argument; // argument("bar", word())
-import static net.minecraft.server.command.CommandManager.*; // Import everything
-</code>
-Brigadier's default arguments are located in ''com.mojang.brigadier.arguments''
+// Gets the world the sender is within. The console's world is the same as the default spawn world.
+final ServerWorld world = source.getWorld();
-Minecraft's arguments hide in ''net.minecraft.command.arguments'' and the CommandManager is at ''net.minecraft.server.command''
+// Gets the sender's rotation as a Vec2f.
+final Vec2f rotation = source.getRotation();
-==== Suggestions ====
+// Access to the instance of the MinecraftServer this command was ran on.
+final MinecraftServer server = source.getServer();
-Suggestions can be provided to the client to recommend what to input into the command.  This is used for Scoreboards and Loot Tables ingame. The game stores these in the SuggestionProviders. A few examples of Minecraft's built in suggestions providers are below
+// The name of the command source. This could be the name of the entity, player,
-<code>
+// the name of a CommandBlock that has been renamed before being placed down, or in the case of the Console, "Console".
-SUMMONABLE_ENTITIES
+final String name = source.getName();
-AVAILIBLE_SOUNDS
-ALL_RECIPES
-ASK_SERVER
-</code>
-Loot tables specify their own SuggestionProvider inside LootCommand for example.
+// Returns true if the source of the command has a certain permission level.
+// This is based on the operator status of the sender.
-The example below is a dynamically changing SuggestionProvider that lists several words for a StringArgumentType to demonstrate how it works:
+// (On an integrated server, the player must have cheats enabled to execute these commands.)
-<code java>
+final boolean b = source.hasPermissionLevel(int level);
-public static SuggestionProvider<ServerCommandSource> suggestedStrings() {
-    return (ctx, builder) -> getSuggestionsBuilder(builder, /*Access to a list here*/);
-}
-private static CompletableFuture<Suggestions> getSuggestionsBuilder(SuggestionsBuilder builder, List<String> list) {
-    String remaining = builder.getRemaining().toLowerCase(Locale.ROOT);
-    if(list.isEmpty()) { // If the list is empty then return no suggestions
-        return Suggestions.empty(); // No suggestions
-    }
-    for (String str : list) { // Iterate through the supplied list
-        if (str.toLowerCase(Locale.ROOT).startsWith(remaining)) {
-            builder.suggest(str); // Add every single entry to suggestions list.
-        }
-    }
-    return builder.buildFuture(); // Create the CompletableFuture containing all the suggestions
-}
 </code>
-The SuggestionProvider is a FunctionalInterface that returns a CompletableFuture containing a list of suggestions. These suggestions are given to client as a command is typed and can be changed while server is running. The SuggestionProvider provides a CommandContext and a SuggestionBuilder to determine all the suggestions. The CommandSource can also be taken into account during the suggestion creation process as it is available through the CommandContext.
+===== Register a basic command =====
-Though remember these are suggestions. The inputted command may not contain an argument you suggested so you still have to parse check inside the command to see if the argument is what you want if it's a String for example and parsers may still throw exceptions if an invalid syntax is inputted.
+Commands are registered by registering in ''CommandRegistrationCallback'' in the Fabric API. For information on registering callbacks, please see the [[callbacks]].
-To use the suggestion you would append it right after the argument you want to recommend arguments for. This can be any argument and the normal client side exception popups will still work. Note this cannot be applied to literals.
+The event should be registered in your mod's initializer. The callback has three parameters. The ''CommmandDispatcher<S>'' is used to register, parse and execute commands. ''S'' is the type of command source the command dispatcher supports, which is usually ''ServerCommandSource''. The second parameter provides an abstraction to registries which may be passed to certain command argument methods. The third parameter is a ''RegistrationEnvironment'' which identifies the type of server the commands are being registered on.
+To simplify the code, it is highly recommended to ''static import'' the methods in ''CommandManager'' (see [[#Static Imports]]):
 <code java>
-argument(argumentName, word())
+import static net.minecraft.server.command.CommandManager.*;
-.suggests(CompletionProviders.suggestedStrings())
-    .then(/*Rest of the command*/));
 </code>
-==== Requires ====
+In the mod initializer, we just register the simplest command:
-Lets say you have a command you only want operators to be able to execute. This is where the ''requires'' method comes into play. The requires method has one argument of a Predicate<ServerCommandSource> which will supply a ServerCommandSource to test with and determine if the CommandSource can execute the command.
+<code java [enable_line_numbers="true"]>
+public class ExampleMod implements ModInitializer {
+  @Override
+  public void onInitialize() {
+    CommandRegistrationCallback.EVENT.register((dispatcher, registryAccess, environment) -> dispatcher.register(literal("foo")
+        .executes(context -> {
+      // For versions below 1.19, replace "Text.literal" with "new LiteralText".
+      // For versions below 1.20, remode "() ->" directly.
+      context.getSource().sendFeedback(() -> Text.literal("Called /foo with no arguments"), false);
-For example this may look like the following:
+      return 1;
+    })));
-<code java>
+  }
-dispatcher.register(literal("foo")
+}
-	.requires(source -> source.hasPermissionLevel(4))
-		.executes(ctx -> {
-			ctx.getSource().sendFeedback(new LiteralText("You are an operator", false));
-			return 1;
-		});
 </code>
-This command will only execute if the Source of the command is a level 4 operator at minimum. If the predicate returns false, then the command will not execute. Also this has the side effect of not showing this command in tab completion to anyone who is not a level 4 operator.
+**Please ensure you import the correct static method.** The method ''literal'' is ''CommandManager.literal''. You can also alternatively explicitly write ''CommandManager.literal'' instead of using static imports. ''CommandManager.literal("foo")'' tells brigadier this command has one node, a **literal** called ''foo''.
-==== Exceptions ====
+In the ''sendFeedback'' method, the first parameter is the text to be sent, which is a ''Text'' in versions below 1.20, or a ''Supplier<Text>'' in 1.20 and above (this is used to avoid instantiating ''Text'' objects when not needed, so please do not use ''Suppliers.ofInstance'' or smiliar methods). The second parameter determines whether to broadcast the feedback to other operators. If the command is to //query// something without actually affecting the world, such as query the current time or some player's score, it should be ''false''. If the command actually //does// something, such as changing the time or modifying someone's score, it should be ''true''. If game rule ''sendCommandFeedback'' is false, you will not accept any feedback. If the sender is modifed through ''/execute as ...'', the feedback is sent to the original sender.
-Brigadier supports command exceptions which can be used to end a command such as if an argument didn't parse properly or the command failed to execute.
+If the command fails, instead of calling ''sendFeedback'', you may directly throw a ''CommandSyntaxException'' or ''<yarn class_2164>''. See [[command_exceptions]] for details.
-All the exceptions from Brigadier are based on the CommandSyntaxException. The two main types of exceptions Brigadier provides are Dynamic and Simple exception types, of which you must ''create()'' the exception to throw it. These exceptions also allow you to specify the context in which the exception was thrown using ''createWithContext(ImmutableStringReader)''. Though this can only be used with a custom parser. These can be defined and thrown under certain scenarios during the command.
+To execute this command, you must type ''/foo'', which is case-sensitive. If ''/Foo'', ''/FoO'', ''/FOO'', ''/fOO'' or ''/fooo'' is typed instead, the command will not run.
-Below is a coin flip command to show an example of exceptions in use.
-<code java>
+===== Registration environment =====
-dispatcher.register(CommandManager.literal("coinflip")
+If desired, you can also make sure a command is only registered under some specific circumstances, for example, only in the dedicated environment:
-	.executes(ctx -> {
-		Random random = new Random();
-		if(random.nextBoolean()) { // If heads succeed.
-			ctx.getSource().sendMessage(new TranslateableText("coin.flip.heads"))
-			return Command.SINGLE_SUCCESS;
-		}
-		throw new SimpleCommandExceptionType(new TranslateableText("coin.flip.tails")).create(); // Oh no tails, you lose.
-	}));
-</code>
-Though you are not just limited to a single type of exception as Brigadier also supplies Dynamic exceptions.
+<yarncode java [enable_line_numbers="true", highlight_lines_extra="5,6,7"]>
+public class ExampleCommandMod implements ModInitializer {
-<code java>
+    @Override
-DynamicCommandExceptionType used_name = new DynamicCommandExceptionType(name -> {
+    public void onInitialize() {
-	return new LiteralText("The name: " + (String) name + " has been used");
+        CommandRegistrationCallback.EVENT.register((dispatcher, registryAccess, environment) -> {
-});
+            if (environment.field_25423) {
-</code>
+                ...;
+            }
-There are more Dynamic exception types which each take a different amount of arguments into account (''Dynamic2CommandExceptionType'', ''Dynamic3CommandExceptionType'', ''Dynamic4CommandExceptionType'', ''DynamicNCommandExceptionType'').
+        });
-You should remember that the Dynamic exceptions takes an object as an argument so you may have to cast the argument for your use.
+    }
-==== Redirects (Aliases) ====
-Redirects are Brigadier's form of aliases. Below is how Minecraft handles /msg have an alias of /tell and /w.
-<code java>
-public static void register(CommandDispatcher<ServerCommandSource> dispatcher) {
-    LiteralCommandNode node = registerMain(dispatcher); // Registers main command
-    dispatcher.register(literal("tell")
-	.redirect(node)); // Alias 1, redirect to main command
-    dispatcher.register(literal("w")
-	.redirect(node)); // Alias 2, redirect to main command
 }
+</yarncode>
-public static LiteralCommandNode registerMain(CommandDispatcher<ServerCommandSource> dispatcher) {
+===== Static Imports =====
-    return dispatcher.register(literal("msg")
+In the example above, the use of static imports is used for code simplifying. For a literal this would shorten the statement to ''literal("foo")''. This also works for getting the value of an argument. This shortens ''StringArgumentType.getString(ctx, "string")'' to ''getString(ctx, "string")''. This also works for Minecraft's own argument types.
-	.then(argument("targets", EntityArgumentType.players())
-	    .then(argument("message", MessageArgumentType.message())
-		.executes(ctx -> {
-		    return execute(ctx.getSource(), getPlayers(ctx, "targets"), getMessage(ctx, "message"));
-		}))));
-}
-</code>
-The redirect registers a branch into the command tree, where the dispatcher is told when executing a redirected command to instead look on a different branch for more arguments and executes blocks. The literal argument that the redirect is placed on will also rename first literal on the targeted branch in the new command.
+Below is an example of some static imports:
+<code java [enable_line_numbers="true"]>
-Redirects also work in shortened aliases such as ''/mod thing <argument>'' having an alias of ''/thing <argument>'' as shown in the code below:
+// getString(ctx, "string")
+import static com.mojang.brigadier.arguments.StringArgumentType.getString;
-<code java>
+// word()
-public static void register(CommandDispatcher<ServerCommandSource> dispatcher) {
+import static com.mojang.brigadier.arguments.StringArgumentType.word;
-	LiteralCommandNode node = registerShortened(dispatcher);
+ // literal("foo")
-        dispatcher.register(literal("mod")
+import static net.minecraft.server.command.CommandManager.literal;
-	    .then(literal("thing")
+ // argument("bar", word())
-	    .redirect(node))); // Option 2: /mod thing <argument>
+import static net.minecraft.server.command.CommandManager.argument;
-}
+// Import everything in the CommandManager
+import static net.minecraft.server.command.CommandManager.*;
-public static LiteralCommandNode registerShortened(CommandDispatcher<ServerCommandSource> dispatcher) { // Option 1: /thing <argument>
-    return dispatcher.register(literal("thing")
-	.then(argument("argument", word())
-	    .executes(ctx -> execute(ctx))));
-}
 </code>
-===== ServerCommandSource =====
+Note: Please be sure you use the ''literal'' and ''argument'' from ''CommandManager'' instead of other classes, or you may have issues with generics when trying to compile, because the type parameter ''S'' should be ''ServerCommandSource''. (For client-side commands, use ''ClientCommandManager'' instead.)
-What if you wanted a command that the CommandSource must be an entity to execute? The ServerCommandSource provides this option with a couple of methods
+Brigadier's default arguments are at ''com.mojang.brigadier.arguments''
-<code java>
+Minecraft's arguments are in ''net.minecraft.command.arguments''. CommandManager is in the package ''net.minecraft.server.command''.
-ServerCommandSource source = ctx.getSource();
-// Get the source. This will always work.
-Entity sender = source.getEntity();
+===== Add Requirements =====
-// Unchecked, may be null if the sender was the console.
-Entity sender2 = source.getEntityOrThrow();
+Let's say you have a command that you only want operators to be able to execute. This is where the ''requires'' method comes into play. The ''requires'' method has one argument of a ''Predicate<ServerCommandSource>'' which will supply a ''ServerCommandSource'' to test with and determine if the ''CommandSource'' can execute the command.
-// Will end the command if the source of the command was not an Entity.
-// The result of this could contain a player. Also will send feedback telling the sender of the command that they must be an entity.
-// This method will require your methods to throw a CommandSyntaxException.
-// The entity options in ServerCommandSource could return a CommandBlock entity, any living entity or a player.
-ServerPlayerEntity player = source.getPlayer();
+For example this may look like the following:
-// Will end the command if the source of the command was not explicitly a Player. Also will send feedback telling the sender of the command that they must be a player.  This method will require your methods to throw a CommandSyntaxException
-</code>
-The ServerCommandSource also provides other information about the sender of the command.
+<code java [enable_line_numbers="true"]>
+dispatcher.register(literal("foo")
-<code java>
+  .requires(source -> source.hasPermissionLevel(2))
-source.getPosition();
+  .executes(ctx -> {
-// Get's the sender's position as a Vec3 when the command was sent. This could be the location of the entity/command block or in the case of the console, the world's spawn point.
+    ctx.getSource().sendFeedback(() -> Text.literal("You are an operator"), false);
+    return 1;
-source.getWorld();
+  });
-// Get's the world the sender is within. The console's world is the same as the default spawn world.
-source.getRotation();
-// Get's the sender's rotation as a Vec2f.
-source.getMinecraftServer();
-// Access to the instance of the MinecraftServer this command was ran on.
-source.getName();
-// The name of the command source. This could be the name of the entity, player, the name of a CommandBlock that has been renamed before being placed down or in the case of the Console, "Console"
-source.hasPermissionLevel(int level);
-// Returns true if the source of the command has a certain permission level. This is based on the operator status of the sender. (On an integrated server, the player must have cheats enabled to execute these commands)
 </code>
-===== Some actual examples =====
+This command will only execute if the source of the command is a level 2 operator at minimum, //including// command blocks. Otherwise, the command is not registered. Also this has the side effect of not showing this command in tab completion to anyone who is not a level 2 operator. This is also why you cannot tab-complete most commands when you did not enable cheating.
-Just a few to show:
+To create commands that only level 4 operators (//not including// command blocks) can execute, use ''source.hasPermissionLevel(4)''.
-=== Broadcast a message ===
+===== Arguments =====
-<code java>
+Arguments are used in most of commands. Sometimes they can be optional, which means if you do not provide that argument, the command will also run. One node may have multiple argument types, but be aware that there is possibility of ambiguity, which should be avoided.
-public static void register(CommandDispatcher<ServerCommandSource> dispatcher){
-    dispatcher.register(literal("broadcast")
-	.requires(source -> source.hasPermissionLevel(2)) // Must be a game master to use the command. Command will not show up in tab completion or execute to non op's or any op that is permission level 1.
-	    .then(argument("color", ColorArgumentType.color())
-		.then(argument("message", greedyString())
-		    .executes(ctx -> broadcast(ctx.getSource(), getColor(ctx, "color"), getString(ctx, "message")))))); // You can deal with the arguments out here and pipe them into the command.
-}
-public static int broadcast(ServerCommandSource source, Formatting formatting, String message) {
+In this case, we add one integer argument, and calculate the square of the integer.
-    Text text = new LiteralText(message).formatting(formatting);
-    source.getMinecraftServer().getPlayerManager().broadcastChatMessage(text, false);
+<code java>
-    return Command.SINGLE_SUCCESS; // Success
+    dispatcher.register(literal("mul")
-}
+        .then(argument("value", IntegerArgumentType.integer())
+            .executes(context -> {
+              final int value = IntegerArgumentType.getInteger(context, "value");
+              final int result = value * value;
+              context.getSource().sendFeedback(() -> Text.literal("%s × %s = %s".formatted(value, value, result)), false);
+              return result;
+            })));
 </code>
-=== /giveMeDiamond ===
+In this case, after the word ''/mul'', you should type an integer. For example, if you run ''/mul 3'', you will get the feedback message "3 × 3 = 9". If you type ''/mul'' without arguments, the command cannot be correctly parsed.
-First the basic code where we register "giveMeDiamond" as a literal and then an executes block to tell the dispatcher which method to run.
+Note: for simplicity, ''IntegerArgumentType.integer'' and ''IntegerArgumentType.getInteger'' can be replaced with ''integer'' and ''getInteger'' with static import. This example does not use static imports, in order to be more explicit.
+Then we add an optional second argument:
 <code java>
-public static LiteralCommandNode register(CommandDispatcher<ServerCommandSource> dispatcher) { // You can also return a LiteralCommandNode for use with possible redirects
+    dispatcher.register(literal("mul")
-    return dispatcher.register(literal("giveMeDiamond")
+        .then(argument("value", IntegerArgumentType.integer())
-        .executes(ctx -> giveDiamond(ctx)));
+            .executes(context -> {
-}
+              final int value = IntegerArgumentType.getInteger(context, "value");
+              final int result = value * value;
+              context.getSource().sendFeedback(() -> Text.literal("%s × %s = %s".formatted(value, value, result)), false);
+              return result;
+            })
+            .then(argument("value2", IntegerArgumentType.integer())
+                .executes(context -> {
+                  final int value = IntegerArgumentType.getInteger(context, "value");
+                  final int value2 = IntegerArgumentType.getInteger(context, "value2");
+                  final int result = value * value2;
+                  context.getSource().sendFeedback(() -> Text.literal("%s × %s = %s".formatted(value, value2, result)), false);
+                  return result;
+                }))));
 </code>
-Then since we only want to give to players, we check if the CommandSource is a player. But we can use ''getPlayer'' and do both at the same time and throw an error if the source is not a player.
+Now you can type one or two integers. If you give one integer, that square of integer will be calculated. If you provide two integers, their product will be calculated. You may find it unnecessary to specify similar executions twice. Therefore, we can create a method that will be used in both executions.
 <code java>
-public static int giveDiamond(CommandContext<ServerCommandSource> ctx) throws CommandSyntaxException {
+public class ExampleMod implements ModInitializer {
-    ServerCommandSource source = ctx.getSource();
+  @Override
+  public void onInitialize() {
-    PlayerEntity self = source.getPlayer(); // If not a player than the command ends
+    CommandRegistrationCallback.EVENT.register((dispatcher, registryAccess, environment) -> dispatcher.register(literal("mul")
+        .then(argument("value", IntegerArgumentType.integer())
+            .executes(context -> executeMultiply(IntegerArgumentType.getInteger(context, "value"), IntegerArgumentType.getInteger(context, "value"), context))
+            .then(argument("value2", IntegerArgumentType.integer())
+                .executes(context -> executeMultiply(IntegerArgumentType.getInteger(context, "value"), IntegerArgumentType.getInteger(context, "value2"), context))))));
+  }
+  private static int executeMultiply(int value, int value2, CommandContext<ServerCommandSource> context) {
+    final int result = value * value2;
+    context.getSource().sendFeedback(() -> Text.literal("%s × %s = %s".formatted(value, value2, result)), false);
+    return result;
+  }
+}
 </code>
+===== A sub command =====
-Then we add to the player's inventory, with a check to see if the inventory is full:
+To add a sub command, you register the first literal node of the command normally.
-<code java>
+<code>
-    if(!player.inventory.insertStack(new ItemStack(Items.DIAMOND))){
+dispatcher.register(literal("foo"))
-        throw new SimpleCommandExceptionType(new TranslateableText("inventory.isfull")).create();
-    }
-    return 1;
-}
 </code>
-=== Antioch ===
+In order to have a sub command, one needs to append the next node to the existing node.
-...lobbest thou thy Holy Hand Grenade of Antioch towards thy foe.
-who being naughty in My sight, shall snuff it.
-Aside from the joke this command summons a primed TNT to a specified location or the location of the sender's cursor.
+This creates the command ''foo <bar>'' as shown below.
-First create an entry into the CommandDispatcher that takes a literal of antioch with an optional argument of the location to summon the entity at.
+<code java [enable_line_numbers="true"]>
+dispatcher.register(literal("foo")
+    .then(literal("bar")
+        .executes(context -> {
+            // For versions below 1.19, use ''new LiteralText''.
+            // For versions below 1.20, use directly the ''Text'' object instead of supplier.
+            context.getSource().sendFeedback(() -> Text.literal("Called foo with bar"), false);
-<code java>
+            return 1;
-public static void register(CommandDispatcher<ServerCommandSource> dispatcher) {
+        })
-    dispatcher.register(literal("antioch")
+    )
-        .then(required("location", BlockPosArgumentType.blockPos()
+);
-	    .executes(ctx -> antioch(ctx.getSource(), BlockPosArgument.getBlockPos(ctx, "location")))))
-	.executes(ctx -> antioch(ctx.getSource(), null)));
-}
 </code>
-Then the creation and messages behind the joke.
+Similar to arguments, sub command nodes can also be set optional. In the following case, both ''/foo'' and ''/foo bar'' will be valid.
+<code java [enable_line_numbers="true"]>
-<code java>
+dispatcher.register(literal("foo")
-public static int antioch(ServerCommandSource source, BlockPos blockPos) throws CommandSyntaxException {
+    .executes(context -> {
+        context.getSource().sendFeedback(() -> Text.literal("Called foo without bar"), false);
-    if(blockPos==null) {
+        return 1;
-        blockPos = LocationUtil.calculateCursorOrThrow(source, source.getRotation()); // For the case of no inputted argument we calculate the cursor position of the player or throw an error if the nearest position is too far or is outside of the world. This class is used as an example and actually doesn't exist yet.
+    })
-    }
+    .then(literal("bar")
+        .executes(context -> {
-    TntEntity tnt = new TntEntity(source.getWorld(), blockPos.getX(), blockPos.getY(), blockPos.getZ(), null);
+            context.getSource().sendFeedback(() -> Text.literal("Called foo with bar"), false);
+            return 1;
-    source.getMinecraftServer().getPlayerManager().broadcastChatMessage(new LiteralText("...lobbest thou thy Holy Hand Grenade of Antioch towards thy foe").formatting(Formatting.RED), false);
+        })
-    source.getMinecraftServer().getPlayerManager().broadcastChatMessage(new LiteralText("who being naughty in My sight, shall snuff it.").formatting(Formatting.RED), false);
+    )
-    source.getWorld().spawnEntity(tnt);
+);
-    return 1;
-}
 </code>
+====== Advanced concepts ======
-===== FAQ =====
+Below are links to the articles about more complex concepts used in brigadier.
-=== What else can I send feedback to the CommandSource? ===
+^ Page                                                           ^ Description                                                                     ^
+| [[command_exceptions  |Exceptions]]                 | Fail execution of a command with a descriptive message and in certain contexts. |
+| [[command_suggestions|Suggestions]]                | Suggesting command input for the client.                                        |
+| [[command_redirects|Redirects]]   | Allow use of aliases or repeating elements to execute commands.                                   |
+| [[command_argument_types|Custom Argument Types]]    | Parse your own arguments into your own objects.                                 |
+| [[command_examples|Examples]] | Some example commands |
-You can choose between Brigadier's default LiteralMessage or use any one of Minecraft's Text classes (LiteralText, TranslatableText)
+====== FAQ ======
-=== Why does my IDE complain saying that a method executed by my command needs to catch or throw a CommandSyntaxException ===
+===== Why does my code not compile =====
-The solution to this is just to make the methods throw a CommandSyntaxException down the whole chain as the executes block handles the exceptions.
+There are several immediate possibilities for why this could occur.
-=== Can I register commands in run time? ===
+  * **Catch or throw a CommandSyntaxException:** ''CommandSyntaxException'' is not a ''RuntimeException''. If you throw it, where it is throwed should be in methods that throws ''CommandSyntaxException'' in method signatures, or be caught. Brigadier will handle the checked exceptions and forward the proper error message in game for you.
+  * **Issues with generics:** You may have an issue with generics once in a while. If you are registering server command (which is most of the case), make sure you are using ''CommandManager.literal(...)'' or ''CommandManager.argument(...)'' instead of ''LiteralArgumentBuilder.literal'' or ''RequiredArgumentBuilder.argument'' in your static imports.
+  * **Check ''sendFeedback'' method:** You may have forgotten to provide a boolean as the second argument. Also remember that, since 1.20, the first parameter is ''Supplier<Text>'' instead of ''Text''.
+  * **''Command'' should return an integer:** When registering commands, the ''executes'' method accepts a ''Command'' object, which is usually a lambda. The lambda should return an integer, instead of other types.
-You can do this but it is not reccomended. You would get the instance of the CommandManager and add anything you wish to the CommandDispatcher within it.
+===== Can I register client side commands? =====
-After that you will need to send the command tree to every player again using ''CommandManager.sendCommandTree(PlayerEntity)''
+Fabric has a ''ClientCommandManager'' that can be used to register client side commands. The code should exist only in client-side codes. Example:
-=== Can I unregister commands in run time? ===
-You can also do this but it is very unstable and could cause unwanted side effects. Lets just say it involves a bunch of Reflection.
-Once again you will need to send the command tree to every player again using ''CommandManager.sendCommandTree(PlayerEntity)'' afterwards.
-=== Can I register client side commands? ===
-Well Fabric currently doesn't support this natively but there is a mod by the Cotton team that adds this functionality where the commands do not run on the server and only on the client:
-https://github.com/CottonMC/ClientCommands
-If you only want the command to only be visible on the integrated server like ''/publish'' then you would modify your requires block:
 <code java>
-dispatcher.register(literal("publish")
+    ClientCommandRegistrationCallback.EVENT.register((dispatcher, registryAccess) -> dispatcher.register(ClientCommandManager.literal("foo_client")
-    // The permission level 4 on integrated server is the equivalent of having cheats enabled.
+        .executes(context -> {
-    .requires(source -> source.getMinecraftServer().isSinglePlayer() && source.hasPermissionLevel(4)));
+              context.getSource().sendFeedback(Text.literal("The command is executed in the client!"));
+              return 1;
+            }
+        )));
 </code>
-=== I want to access X from my mod when a command is ran ===
+If you need to open a screen in the client command execution, instead of directly calling ''client.setScreen(...)'', you should call ''%%client.execute(() -> client.setScreen(...))%%''. The variable ''client'' can be obtained with ''context.getSource().getClient()''.
-This is going to require a way to statically access your mod with a ''getInstance'' call. Below is a very simple instance system you can place in your mod
+===== Can I register commands in runtime? =====
-<code java>
+You can do this but it is not recommended. You would get the ''CommandManager'' from the server and add anything commands you wish to it's ''CommandDispatcher''.
-private static Type instance;
-static { // Static option on class initalize for seperate API class for example
+After that you need to send the command tree to every player again using ''CommandManager.sendCommandTree(ServerPlayerEntity)''. This is required because the client locally caches the command tree it receives during login (or when operator packets are sent) for local completions rich error messages.
-   instance = new Type();
-}
-public void onInitalize() { // If within your mod initalizer
+===== Can I unregister commands in runtime? =====
-   instance = this;
-}
+You can also do this, however it is much less stable than registering commands and could cause unwanted side effects. To keep things simple, you need to use reflection on brigadier and remove the nodes. After this, you need to send the command tree to every player again using ''sendCommandTree(ServerPlayerEntity)''. If you don't send the updated command tree, the client may think a command still exists, even though the server will fail execution.
-public static Type getInstance() {
-    return instance;
-}
-</code>