/forceload
/forceload| Permission level required |
2 |
|---|---|
| Restrictions |
None |
{
"title": "<code>/forceload</code>",
"rows": [
{
"field": "2",
"label": "(link to Permission level article, displayed as Permission level<br>required)"
},
{
"field": "None",
"label": "(link to Commands#Restrictions article, displayed as Restrictions)"
}
],
"invimages": [],
"images": []
}
Force chunks to load constantly or not, or lists/queries forceloaded chunks.
Usage
Forced chunks get load ticket with load level of 31, the same level as the ticket caused by a player, which means that the said chunks process all aspects of the game, while adjacent chunks get activated by the load level's spreading. But since it increases its load level per chunk when spreading, adjacent chunks don't process every aspect of the game as well.
Crops do not grow in forceloaded chunks unless a player is nearby. Crop growing (without the use of bonemeal) depends on chunk ticks.
Coordinates are actually block coordinates. In order to forceload chunks 0,0 to 1,2, the player should use commands like /forceload add 0 0 31 47, which loads chunks 0,0 to 1,2 (1,2 inclusive, 2×3 chunks). When using /forceload add 0 0 10 30 chunks 0,0 to 0,1 are actually loaded (one chunk equals 16×16 blocks on x/z axis).
Similarly, /forceload query uses block coordinates as well.
Syntax
forceload add <from> [<to>]
- Forces the chunk at the
<from>block position (through the<to>block position, if set) in the dimension of the command's execution to be loaded constantly.
forceload remove <from> [<to>]
- Unforces the chunk at the
<from>block position (through the<to>block position, if set) in the dimension of the command's execution to be loaded constantly.
forceload remove all
- Unforces all chunks in the dimension of the command's execution to be loaded constantly.
forceload query [<pos>]
- If block coordinates are given, displays the specified chunk in the dimension of the command's execution is force loaded; otherwise, lists which chunks in the dimension of the command's execution are force loaded.
Arguments
<from>: column_pos and <to>: column_pos
- Specifies the targeted chunks based on block position.
- Must be a column coordinates composed of
<X>and<Z>, each of which must be an integer or tilde notation.
<pos>: column_pos
- Specifies a chunk to query based on block position.
- Must be a column coordinates composed of
<X>and<Z>, each of which must be an integer or tilde notation.
Result
| Command | Trigger | Java Edition |
|---|---|---|
| Any | The command is incomplete, or any argument is not specified correctly. | Unparseable |
/forceload add ... | More than 256 chunks are specified. | Failed |
| There's a specified chunk that is out of the world. | ||
/forceload add ... | All specified chunks have already been forced to be loaded. | |
/forceload remove <from> [<to>] | None of specified chunks have been forced to be loaded. | |
/forceload query <pos> | The specified chunk hasn't been forced to be loaded. | |
| Any | Otherwise | Successful |
Output
| Command | Edition | Situation | Success Count | /execute store success ... | /execute store result ... |
|---|---|---|---|---|---|
| Any | Java Edition | On fail | 0 | 0 | 0 |
/forceload add ... | On success | 1 | 1 | the number of forceloaded chunks that is newly added. | |
/forceload remove <from> [<to>] | On success | 1 | 1 | the number of forceloaded chunks that is successfully removed. | |
/forceload remove all | On success | 1 | 1 | 0 | |
/forceload query | On success | 1 | 1 | The number of forceloaded chunks in the current dimension. | |
/forceload query <pos> | On success | 1 | 1 | 1 |
History
| Java Edition | |||||||
|---|---|---|---|---|---|---|---|
| 1.13.1 | 18w31a | Added /chunk. | |||||
| pre1 | Renamed /chunk to /forceload. | ||||||
| 1.14.4 | pre4 | /forceload is now available up to permission level 2. | |||||
| 1.17 | 20w45a | Chunks are now loaded asynchronously, so chunks selected by /forceload are no longer guaranteed to be loaded on the same tick that the command is run.[1] | |||||