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, and so the vault is uninteractable, and doesn't update.

How to replicate the issue

I've attached the following datapack, which includes a custom structure I'd been working on. To demonstrate the issue, when adding this datapack to a new world (with experimental features) and searching for the structure "players-versus:trial_tower", you will notice that all vaults are seemingly disabled; they're waiting for gametick 100000+ to happen before updating, which was the gametime value when I originally saved the structure nbt files in a test world (New World.rar.

Datapack for Mojira - Vault Bug.zip Unable to embed resource: Datapack for Mojira - Vault Bug.zip of type application/zip

Possible fixes:

• 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.