Command blocks are powerful tools for automation, maps, and technical systems, but they stop working when their chunk unloads. This limits their potential and forces players to rely on /forceload or global functions instead of in-world logic.
The problem:
- Systems break when players leave the area
-
/forceloadis tedious and limited - Mapmakers can’t create persistent redstone/command builds easily
Suggested solution:
Allow command blocks to keep their chunk loaded while active. This could be balanced by:
- Only applying to repeating/“Always Active” command blocks
- Adding a gamerule (e.g.
commandBlocksKeepChunksLoaded) - Limiting how many can be active at once
Benefits:
- Enables persistent in-world systems
- Improves reliability for maps and minigames
- Reduces reliance on
/forceload
This would make command blocks far more useful while still being controllable and balanced.
Please sign in to leave a comment.
1 Comments