Updated:
Command context limit game rule (max_command_forks)
The "Command context limit" rule is called max_command_forks in Java 1.21.11 and later, and maxCommandForkCount in 1.21.10 and earlier. Sets the most execution contexts one command, such as execute as, can create.
Basic data
| Name | Command context limit |
|---|---|
| Rule name (Java 1.21.11+) | max_command_forks |
| Old name (Java 1.21.10 and earlier) | maxCommandForkCount |
| Bedrock name | No rule with the same name |
| Value type | Integer |
| Default | 65536 |
Commands you can copy
Set to 10000
/gamerule max_command_forks 10000Reset to the default (65536)
/gamerule max_command_forks 65536Check the current value
/gamerule max_command_forksJava 1.21.10 and earlier
/gamerule maxCommandForkCount 10000Notes
- Java 1.21.11 renamed game rules to lower case with underscores. If an older command or a map description uses the old name, rewrite it for your version.
- Game rules are saved per world. On a server, a new world starts with the default values again.
Questions
Typing maxCommandForkCount gives an error
In Java 1.21.11 and later the rule is called max_command_forks. Write /gamerule max_command_forks … instead. Worlds on 1.21.10 and earlier keep the old name.
How do I check the current value?
Run /gamerule max_command_forks without a value. The current value is shown in chat.