When a load structure block changes itself into another load structure block, it works if you use the 'load' button, but if a redstone current is applied to it, it changes into a barrier block. Note that other blocks in the structure appear normally.
cf. structures T1 & T2 and Test1 & Test2 in the Redstone world in attachment.
Attachments
Comments 4
Maybe intended. Structure blocks do not schedule updates but update immediately. Because of this T1 and T2 keep replacing each other in one single game tick until you get the following error in the GameOutput:
[16:58:37] [Server thread/FATAL]: Error executing task
java.util.concurrent.ExecutionException: f: Exception while updating neighbours
Can someone please check, if this still applies to 1.15.2 or the latest 1.16 development snapshot (currently that is 20w07a)?
Just an added detail: on the provided world, the functions "write(n,2);" where n ranges between 0 and 9 are recursive structures (aka structures which replace the structure block that called them by another, like the structures causing the bug) that do NOT cause this bug ; they function perfectly well.