Cascading chunk loading due to updateObservingBlocksAt

[Corey]

My mod generates large veins of ore that can span multiple chunks.  I use a deferred generation method that generates the entire vein, but only places the ore that's in loaded chunks, and waits for the other chunks to load before placing their ores.  This works great, except setBlockState calls markAndNotifyBlock, which in turn calls updateObservingBlocksAt.  If a block is generated on a chunk boundary, updateObservingBlocksAt will cascade into those chunks.

 

I am aware I can prevent updateObservingBlocksAt from being called by passing the flag 0x10, and doing so fixes all instances of cascading chunk gen.  All I want to know is if that's safe/desirable during chunk population, or if it may cause problems.

[Draco18s]

4 minutes ago, Corey said:

All I want to know is if that's safe/desirable during chunk population

You're fine.

[Corey]

Awesome, thanks!

[Draco18s]

The other thing you can do is offset your block placement by +8, +8 on x and z. Yes, this will place blocks into neighboring chunks, but those 3 chunks are safe and won't cascade.