Raven Dwyre
- Ravens_Requiem
- ravens_requiem
- Europe/Stockholm
- Yes
- No
MC-114986![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
I ran this command in a repeating command block:
/execute if block -22 65 133 minecraft:oak_button[facing=east,powered=true]
and had a comparator running out to a, pre-existing in 1.12, structure block.
When I pushed said button the game crashed and I can no longer see the world in the list of singleplayer maps.
My guess is 1.12 and below structure block files have to be moved to a new folder or resaved before use in 1.13+.
Edit: I've added what I think was the first crash don't know why it's a server.txt when this was a singleplayer world. I did import it from my server if that means anything. But I was playing it locally to test out learning how to replace the testfor commands.
crash-2017-12-19_10.31.38-client.txt
So one aspect of this I fear to be intended behavior but my second point still perplexes me.
Here is my example to illustrate the issue:
You save a structure of a redstone lamp when it is powered on.
Upon load, the redstone lamp stay lit for a second and then I'm guessing a block update forces it to turn off. (this is what I fear to be intended behavior) It would be ideal if any block state that a structure block saves maintains that state after loading.
In order to circumvent the block update, you use a repeating command block to /execute if block x y z minecraft:lever[powered=true] with a redstone comparator leading into the structure block to try and keep the structure constantly reloading. This does not keep the lit redstone lamp powered as one would expect and you get the same result as before.
[^Minecraft 1.13.2 2019-02-01 14-59-32.mp4]
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Raven Dwyre, this is completely unrelated to this bug report here. According to your crash log, your issue would be MC-123363, if you want to contribute to that.
Just leaving this here as it might be some useful information; Raven Dwyre experienced the same crash, with the following info:
I have this "floor is lava" command (/execute as @a at @s if block ~ ~-.01 ~ minecraft:orange_wool run kill @s) set up in 17w50a that uses /kill and when I try to respawn it crashes. [^crash-2017-12-19_10.31.38-client.txt]
Edit: I wasn't able to reproduce the crash with the setup Raven Dwyre provided, but instead it flooded the log/console with several thousand of the following entries:
18:24:48 net.minecraft.server.MinecraftServer Server thread info [miwob: Killed miwob] 18:24:48 bog Client thread info [CHAT] [miwob: Killed miwob]
so much for automatically being reopened...
I have this "floor is lava" command (/execute as @a at @s if block ~ ~-.01 ~ minecraft:orange_wool run kill @s) set up in 17w50a that uses /kill and when I try to respawn it crashes. [^crash-2017-12-19_10.31.38-client.txt]
Also happens in Creative. When you click the bell with a block in hand, it places the block then disappears. You still have the item in your inventory though.
Can confirm this is still an issue in 1.14.4. if I have animated structures with things like torches, tripwire, item frames, buttons, ect. they act as if being broken and dropping their respective items instead of just overwriting the block.