Rhodo crystal cubes are ticking tile entities when they really don't have to be
quat1024 opened this issue ยท 2 comments
Rhodo cores only update crystal-cube listeners when their own contents are modified, but it's possible for the two-argument crystal cubes to require a state change even if the core itself doesn't change.
Awakened logs should probably scan out from themselves in 6 directions (leaves can mean the troublesome block isn't directly adjacent), find cores, and schedule a tile-tick to cause them to update. Tileticks might be a good solution to avoid them like, updating each other infinitely, or updating during intermediate states within the tick.
In a3500bd i made crystal cubes just tick so they don't need to be updated, dont like that solution though