Minecraft:Commands/forceload: Difference between revisions

Latest revision as of 20:10, 9 April 2026

Template:HatnoteScript error: No such module "Exclusive". Template:Infobox command

Force chunks to load constantly or not, or lists/queries forceloaded chunks.

Usage

{{#vardefine:params|0 }}Template:Hatnote 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.

As of version 1.21.5, crops do grow in forceloaded chunks even without a nearby player. Blocks in forceloaded chunks receive random ticks (see chunk ticks) and process all updates except for mob spawning, lightning strikes, and fire spreading (unless game rule

REDIRECT Template:Code

Template:Redr is set to true).

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.

{{#vardefine:onlyje|}}{{#vardefine:onlybe| Template:IN,}}{{#vardefine:je-arg|column_pos}}{{#vardefine:be-arg|}}Template:Error{{#vardefine:onlyje|}}{{#vardefine:onlybe|}}{{#vardefine:je-arg|}}{{#vardefine:be-arg|}}

<pos>: column_pos

Specifies a chunk to query based on block position.

{{#vardefine:onlyje|}}{{#vardefine:onlybe| Template:IN,}}{{#vardefine:je-arg|column_pos}}{{#vardefine:be-arg|}}Template:Error{{#vardefine:onlyje|}}{{#vardefine:onlybe|}}{{#vardefine:je-arg|}}{{#vardefine:be-arg|}}

Result

Template:Result table Template:Result table Template:Result table Template:Result table Template:Result table Template:Result table Template:Result table Template:Result table Template:Result table

Output

{{#vardefine:output-table-lines|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:output-table-lines|-2}}{{#vardefine:output-table-lines-now|}}{{#vardefine:command-num-now|}}{{#vardefine:command-line-now|}}{{#vardefine:commands-num|}}{{#vardefine:output-edition-num-now|}}{{#vardefine:output-edition-line-now|}}{{#vardefine:output-editions-num|}}{{#vardefine:je-outputs-dis|}}

{{#vardefine:output-table-lines|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:situation-{{#var:output-table-lines}}|On fail}}{{#vardefine:output1-{{#var:output-table-lines}}|0}}{{#vardefine:output2-{{#var:output-table-lines}}|0}}{{#vardefine:output3-{{#var:output-table-lines}}|0}}{{#vardefine:command-row-{{#var:commands-num}}|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:output-editions-num|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:output-edition-{{#var:output-editions-num}}|je}}{{#vardefine:output-edition-row-{{#var:output-editions-num}}|1}} {{#vardefine:output-table-lines|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:situation-{{#var:output-table-lines}}|On success}}{{#vardefine:output1-{{#var:output-table-lines}}|1}}{{#vardefine:output2-{{#var:output-table-lines}}|1}}{{#vardefine:output3-{{#var:output-table-lines}}|the number of forceloaded chunks that is newly added.}}{{#vardefine:commands-num|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:command-{{#var:commands-num}}|/forceload add ...}}{{#vardefine:command-row-{{#var:commands-num}}|1}}{{#vardefine:output-edition-row-{{#var:output-editions-num}}|Expression error: Unrecognized punctuation character "{".}} {{#vardefine:output-table-lines|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:situation-{{#var:output-table-lines}}|On success}}{{#vardefine:output1-{{#var:output-table-lines}}|1}}{{#vardefine:output2-{{#var:output-table-lines}}|1}}{{#vardefine:output3-{{#var:output-table-lines}}|the number of forceloaded chunks that is successfully removed.}}{{#vardefine:commands-num|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:command-{{#var:commands-num}}|/forceload remove <from> [<to>]}}{{#vardefine:command-row-{{#var:commands-num}}|1}}{{#vardefine:output-edition-row-{{#var:output-editions-num}}|Expression error: Unrecognized punctuation character "{".}} {{#vardefine:output-table-lines|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:situation-{{#var:output-table-lines}}|On success}}{{#vardefine:output1-{{#var:output-table-lines}}|1}}{{#vardefine:output2-{{#var:output-table-lines}}|1}}{{#vardefine:output3-{{#var:output-table-lines}}|0}}{{#vardefine:commands-num|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:command-{{#var:commands-num}}|/forceload remove all}}{{#vardefine:command-row-{{#var:commands-num}}|1}}{{#vardefine:output-edition-row-{{#var:output-editions-num}}|Expression error: Unrecognized punctuation character "{".}} {{#vardefine:output-table-lines|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:situation-{{#var:output-table-lines}}|On success}}{{#vardefine:output1-{{#var:output-table-lines}}|1}}{{#vardefine:output2-{{#var:output-table-lines}}|1}}{{#vardefine:output3-{{#var:output-table-lines}}|The number of forceloaded chunks in the current dimension.}}{{#vardefine:commands-num|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:command-{{#var:commands-num}}|/forceload query}}{{#vardefine:command-row-{{#var:commands-num}}|1}}{{#vardefine:output-edition-row-{{#var:output-editions-num}}|Expression error: Unrecognized punctuation character "{".}} {{#vardefine:output-table-lines|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:situation-{{#var:output-table-lines}}|On success}}{{#vardefine:output1-{{#var:output-table-lines}}|1}}{{#vardefine:output2-{{#var:output-table-lines}}|1}}{{#vardefine:output3-{{#var:output-table-lines}}|1}}{{#vardefine:commands-num|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:command-{{#var:commands-num}}|/forceload query <pos>}}{{#vardefine:command-row-{{#var:commands-num}}|1}}{{#vardefine:output-edition-row-{{#var:output-editions-num}}|Expression error: Unrecognized punctuation character "{".}}

{{#vardefine:output-table-lines|Expression error: Unrecognized punctuation character "{".}}{{#vardefine:output-table-lines|-2}}{{#vardefine:output-table-lines-now|}}{{#vardefine:command-num-now|}}{{#vardefine:command-line-now|}}{{#vardefine:commands-num|}}{{#vardefine:output-edition-num-now|}}{{#vardefine:output-edition-line-now|}}{{#vardefine:output-editions-num|}}{{#vardefine:je-outputs-dis|}}

History

Template:HistoryTable

References

Navigation

All editions

Removed	placefeature

Template:El only

Debug	chase debugconfig debugmobspawning debugpath raid serverpack spawn_armor_trims warden_spawn_tracker

Removed	? achievement banip blockdata broadcast chunk entitydata home iron locatebiome replaceitem setspawn solid stats testfor testforblock testforblocks toggledownfall unban wood

Template:Els only

Template:El only

Removed

Template:El only

Removed	position videostreamaction

Template:Els only

Removed	clearfixedinv executeasself move place setfixedinvslot setfixedinvslots test transferserver

Joke

@@ Line 1: / Line 1: @@
-{{For|the [[Minecraft:Bedrock Edition]] equivalent|Commands/tickingarea}}{{exclusive|java}}
+{{MC/For|the [[Minecraft:Bedrock Edition]] equivalent|Commands/tickingarea}}{{MC/Exclusive|java}}
 {{Infobox command
 |name=forceload
@@ Line 8: / Line 8: @@
 == Usage ==
-{{See also|Chunk}}
+{{MC/See also|Chunk}}
 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.
-As of version 1.21.5, crops do grow in forceloaded chunks even without a nearby player.  Blocks in forceloaded chunks receive random ticks (see [[Minecraft:Tick#Chunk_tick|chunk ticks]]) and process all updates except for mob spawning, lightning strikes, and fire spreading (unless game rule {{cd|allowFireTicksAwayFromPlayer}} is set to true).
+As of version 1.21.5, crops do grow in forceloaded chunks even without a nearby player.  Blocks in forceloaded chunks receive random ticks (see [[Minecraft:Tick#Chunk_tick|chunk ticks]]) and process all updates except for mob spawning, lightning strikes, and fire spreading (unless game rule {{MC/Cd|allowFireTicksAwayFromPlayer}} is set to true).
-Coordinates are actually [[Minecraft:Coordinates#Block position|block coordinates]]. In order to forceload chunks 0,0 to 1,2, the player should use commands like {{code|/forceload add 0 0 31 47}}, which loads chunks 0,0 to 1,2 (1,2 inclusive, 2×3 chunks). When using {{code|/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).
+Coordinates are actually [[Minecraft:Coordinates#Block position|block coordinates]]. In order to forceload chunks 0,0 to 1,2, the player should use commands like {{MC/Code|/forceload add 0 0 31 47}}, which loads chunks 0,0 to 1,2 (1,2 inclusive, 2×3 chunks). When using {{MC/Code|/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, {{code|/forceload query}} uses block coordinates as well.
+Similarly, {{MC/Code|/forceload query}} uses block coordinates as well.
 ==Syntax==
@@ Line 30: / Line 30: @@
 ==Arguments==
-{{argument|from|column_pos}} and {{argument|to|column_pos}}
+{{MC/Argument|from|column_pos}} and {{MC/Argument|to|column_pos}}
 : Specifies the targeted chunks based on block position.
-: {{arg desc|je=column_pos}}
+: {{MC/Arg desc|je=column_pos}}
-{{argument|pos|column_pos}}
+{{MC/Argument|pos|column_pos}}
 : Specifies a chunk to query based on block position.
-: {{arg desc|je=column_pos}}
+: {{MC/Arg desc|je=column_pos}}
 ==Result==
@@ Line 52: / Line 52: @@
 == Output ==
-{{Output table}}
+{{MC/Output table}}
-{{Output table|edition=je|On fail|0|0|0}}
+{{MC/Output table|edition=je|On fail|0|0|0}}
-{{Output table|cmd=/forceload add ...|On success|1|1|the number of forceloaded chunks that is newly added.}}
+{{MC/Output table|cmd=/forceload add ...|On success|1|1|the number of forceloaded chunks that is newly added.}}
-{{Output table|cmd=/forceload remove <from> [<to>]|On success|1|1|the number of forceloaded chunks that is successfully removed.}}
+{{MC/Output table|cmd=/forceload remove <from> [<to>]|On success|1|1|the number of forceloaded chunks that is successfully removed.}}
-{{Output table|cmd=/forceload remove all|On success|1|1|0}}
+{{MC/Output table|cmd=/forceload remove all|On success|1|1|0}}
-{{Output table|cmd=/forceload query|On success|1|1|The number of forceloaded chunks in the current dimension.}}
+{{MC/Output table|cmd=/forceload query|On success|1|1|The number of forceloaded chunks in the current dimension.}}
-{{Output table|cmd=/forceload query <pos>|On success|1|1|1}}
+{{MC/Output table|cmd=/forceload query <pos>|On success|1|1|1}}
-{{Output table}}
+{{MC/Output table}}
 == History ==
 {{HistoryTable
-|{{HistoryLine|java}}
+|{{MC/HistoryLine|java}}
-|{{HistoryLine||1.13.1|dev=18w31a|Added {{cmd|chunk|link=none}}.}}
+|{{HistoryLine||1.13.1|dev=18w31a|Added {{MC/Cmd|chunk|link=none}}.}}
-|{{HistoryLine|||dev=pre1|Renamed {{cmd|chunk|link=none}} to {{cmd|link=none|forceload}}.}}
+|{{HistoryLine|||dev=pre1|Renamed {{MC/Cmd|chunk|link=none}} to {{MC/Cmd|link=none|forceload}}.}}
-|{{HistoryLine||1.14.4|dev=pre4|{{cmd|forceload|link=none}} is now available up to permission level 2.}}
+|{{HistoryLine||1.14.4|dev=pre4|{{MC/Cmd|forceload|link=none}} is now available up to permission level 2.}}
-|{{HistoryLine||1.17|dev=20w45a|Chunks are now loaded asynchronously, so chunks selected by {{cmd|forceload|link=none}} are no longer guaranteed to be loaded on the same tick that the command is run.<ref>{{bug|MC-227930|resolution=WAI}}</ref>}}
+|{{HistoryLine||1.17|dev=20w45a|Chunks are now loaded asynchronously, so chunks selected by {{MC/Cmd|forceload|link=none}} are no longer guaranteed to be loaded on the same tick that the command is run.<ref>{{bug|MC-227930|resolution=WAI}}</ref>}}
-|{{HistoryLine||1.21.5|dev=25w06a|Any block loaded by a source of chunk loading (including {{cmd|link=none|forceload}}) may now receive random ticks, instead of just 8 chunks around players.}}
+|{{HistoryLine||1.21.5|dev=25w06a|Any block loaded by a source of chunk loading (including {{MC/Cmd|link=none|forceload}}) may now receive random ticks, instead of just 8 chunks around players.}}
 }}
@@ Line 75: / Line 75: @@
 <references/>
 == Navigation ==
-{{Navbox commands}}
+{{MC/Navbox commands}}
 de:Befehl/forceload