mojira.dev
MCPE-152827

Chunks completely freezing via unknown cause. (structure or tickingarea commands suspected yet not confirmed)

After Minecraft updated to 1.18.12, a command block based addon of mine loaded in via a function command started to experience a single chunk within the structure freezing. Mobs within it stay stationary, don't react to damage (or anything), don't burn in sunlight, and command blocks within the chunk fail to function whatsoever. Kill command does not clear mobs and nothing within the chunk updates until you either leave the chunk and come back (despite it being in a ticking area) or reload the world, and the chunk is still frozen as anything new put in it or that walks into the chunk will instantly freeze. 

 

The only experiment turned on is "creation of custom biomes" and my addon does nothing but change numerical values in mob's json, change some recipes and trades via their json files, adds some new structures, and loads the command block area with the frozen chunk via a function command. The addon has always worked fine and does not appear to be the culprit, however the specific chunk that keeps freezing appears to work just fine in vanilla worlds. I suspect something is bugged out with either the structure or ticking area commands within the function command, causing the chunk to freeze  when either the structure is loaded into it, or the chunk becomes apart of the ticking area.

 

I've created new worlds with this addon about a dozen times over, and while the chunk has  loaded correctly a  couple times, most of the time it freezes. This has halted the progression of my addon, and may effect other players as well. I've included my unreleased and unfinished addon here so anyone can test for themselves.

[media]

Use "/function survivalplus" to execute the function and load in the command block structure, then break through the invisible barrier blocks, into the main structure. Next spawn villagers, and punch them. They will take damage once, experience no knockback, then freeze completely. 

Edit: Here is the full function command in question:

tickingarea add 10016 200 10000 10050 200 10050
gamerule doimmediaterespawn true
gamerule doinsomnia false
gamerule commandblockoutput false
gamerule respawnblocksexplode false
structure load SurvivalPlus 10000 200 10000
effect @a levitation 4 0 true
tp @a 10008 203 10042

Second edit: It appears that if you pre-load the chunk before using the command, everything will work fine. However if you don't, everything will freeze within that chunk. 

Attachments

Comments 3

I had a similar issue, I believe due to the quantity of blocks I had, each with a scheduled tick, that overwhelmed the game. Mobs would freeze (but you could hit them once), and broken blocks would "fall" within their immediate block-space and float but were not able to be collected.

After removing that portion of my addon, I've yet to find a frozen chunk. Guess I'll just have to figure out another way to go about it.

Thank you for your report!

However, this issue has been temporarily closed as Awaiting Response.

Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)?

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Plasma7007

(Unassigned)

Unconfirmed

Windows

Windows 10 Home 20H2

chunk, command, freezing

1.18.12 Hotfix

Retrieved