Asserts for when block is placed in a ticking area saying it isn't loaded.

This Bug was found on Dev Build: Release 962308

I get a string of asserts when a command placed/removed a redstone block inside a ticking area. This redstone block would then activate a repeating command that applied an effect to players. After confirming that it was this setblock that caused problems I removed the commands throughout the map. However the game still thinks its getting activated and it continues to give me asserts for these commands even though its not actually activating them anymore.

The assert that I get has come up in various maps before.

--------------------------- Assert Failure - ctrl+C to copy this message to the clipboard! --------------------------- Assertion failed: Something went wrong, the chunk wasn't loaded Condition is false: resource.hasBlock(mMin) Function: LevelChunk::setupRedstoneCircuit in f:\darwinwork\15\s\handheld\src\common\world\level\chunk\levelchunk.cpp @ 2109 --------------------------- OK ---------------------------

I've attached a video below of the problem.

Repro Steps:

1. Open up V0.6.2 of Last Stand. To get a copy of the map DM myself or TheRedstoneScientist on Slack.
2. Walk through the Gladiator Chamber and select a class and ready up.
3. Then flip the ready up lever and after a few moments you will get a bunch of asserts.
4. After clicking through them it will take you to the arena. Die or survive for 5 min for the match to end.
5. When it ends and takes you back to the lobby you will get a bunch of the same assert.

Observed Results: Getting Asserts for setting a block in a loaded chunk.
Expected Results: No Assert

Video of Bug: https://youtu.be/eyla5CWO3G8