Details
-
Bug
-
Resolution: Fixed
-
1.16.201 Hotfix
-
None
-
Confirmed
-
Multiple
-
480194
Description
TickingAreas don't tick reliably which could be a huge problem for technical maps/Marketplace content that require command blocks to function.
It appears that larger tickingAreas unload more frequently, and when they fail it affects every chunk in that area. More testing needs to be done in order to confirm this, though.
In , the first value is how many gameticks have been simulated in the tickingArea over the course of an hour. The second value is how many gameticks have been simulated by the player over the same time frame.
In the picture below, the chunks labelled chunk[_] are separate chunks in the same tickingArea. This is evidence that larger tickingAreas unload more often.
Steps to Reproduce
- Open tick_testing.mcworld
. It contains a scoreboard system that counts ticks in several chunks simulated by the player, and in ticking area.
- /tp -89 1 -128
- Flip the lever.
- Wait for a few minutes, or up to an hour.
Expected result
All scoreboards display the same number.
Actual result
Areas simulated by the player have a higher value on the scoreboard than that of the tickingArea.
Attachments
Issue Links
- relates to
-
MCPE-40601 Repeating Command Blocks randomly not working as intended.
- Resolved
-
MCPE-73059 droppers don't work in ticking area
- Resolved
-
MCPE-109263 Ticking Areas not working!
- Open
-
MCPE-99760 Permanent, non removable ticking areas created with minecraft:tick_world component
- Resolved