The Issue

If a player saves a structure that contains a vault block using structure blocks in a world with a high playtime, then loads that structure into a different world, the vault blocks will be uninteractive. This is caused by the server_data.state_updating_resumes_at property of the new vault block being the same as the original. This property prevents the vault block from being interacted with until the world timer exceeds the given value. Because the structure has been loaded into a new world, the value of this property is far higher than the new world's world timer, rendering the vault uninteractable.

Fixing the Issue

To fix this issue, one of two things should happen;

• Make structure blocks not save the server_data.state_updating_resumes_at property of vault blocks when saving to a file.
• Set the value of server_data.state_updating_resumes_at to zero (or delete the property) when loading the structure into the world.