Here how to reproduce
Step 1 use /setblock ~ ~ ~ vault ["Ominous"=true] replace
Step 2 try to use Ominous key on the newly created vault.
Results regular vault key works but not the ominous vault key
Linked issues
is duplicated by 13
MCPE-184987
Ominous vaults spawned with commands use the wrong key to open. Am unsure if the also use the wrong vault loot table
Resolved
MCPE-188746
ominous vaults do not open with ominous keys
Resolved
MCPE-184426
Ominous vaults summoned using commands don't work right.
Resolved
MCPE-183701
Ominous vault generated by command cannot be opened with right trial key
Resolved
MCPE-182936
so when you make a ominous vault with commands it only opens with a normal key not a ominous key
Resolved
relates to 1
Attachments
Comments 11
migrated
I have did a search first make sure I did not do a duplicate ticket. I have placed a search result in a screenshot to show this.
I have did a search first make sure I did not do a duplicate ticket. I have placed a search result in a screenshot to show this.
Can confirm, relates to MC-270062.
Note that the command provided has a small issue, the first letter of "Ominous" should not be capitalized.
You may have misunderstood what I mean, the issue I linked is about the same buggy behavior (ominous vault created by players can be only opened with normal trial key instead of ominous trial key) in Java Edition.
I think Mojang needs to make it easier to get the ominous vault. If they could just add the item to the creative inventory it would make mapmaker's lives a whole lot easier. This bug is terrible.
For the builder looking to circumvent this limitation, I just attached a .mcstructure file. It contains the original vault data inside. So, If you create a behavior pack, then put this mcstructure on "structures" folder, you can use /structure load ominous_vault ~ ~ ~ to spawn a functional ominous vault, or use a structure block and load "ominous_vault"
For the builder looking to circumvent this limitation, I just attached a .mcstructure file. It contains the original vault data inside. So, If you create a behavior pack, then put this mcstructure on "structures" folder, you can use /structure load ominous_vault ~ ~ ~ to spawn a functional ominous vault, or use a structure block and load "ominous_vault"