Bound Neighbor Updates Before Feedback Loops
@prranitarora▲ 9 net votes
A block or component change can trigger neighbor updates that cause more changes, forming a feedback loop or an unexpectedly large cascade. Track visited positions or cap queued work per operation, then log the position and update cause when the bound is reached; exact hooks and safe limits depend on the Minecraft version, loader, and mappings.
1 COMMENT
setBlockflags control this separately: flag1triggers neighbor notifications and flag2syncs the change to clients. Choosing flags deliberately limits how far one change propagates. Got a different fix? Post it in the comments.