Commands/forceload

Force chunks to load constantly or not,,   and   are three separated commands.

Arguments

 * Specifies the selected chunk's x axis value.
 * Specifies the selected chunk's z axis value.
 * Specifies the selected chunk's z axis value.
 * Specifies the selected chunk's z axis value.

Result

 * Fails if the arguments are not specified correctly, or if the specified chunk isn't force loaded in  mode,


 * On success:
 * – forces the chunk at the  position (through to   if set) in the dimension of the command's execution to be loaded constantly.
 * – unforces the chunk at the  position (through to   if set) in the dimension of the command's execution to be loaded constantly.
 * – unforces all chunks in the dimension of the command's execution to be loaded constantly.
 * – if chunk coordinates are given, says 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.

Forced chunks get load ticket with load level of 31, the same as ticket chunks get by being in player's chunk loading distance, which means that the said chunk processes all aspects of the game while adjacent chunks get activated by the ticket's spread but since it lowers its load level each time, adjacent chunks don't process every aspect of the game as well. Note that mobs will not spawn, if the chunk is far away from player, but the chunk still process entities. See also chunk.

History
Befehl/forceload 命令/forceload