Summary:
Loot command doesn't recognise suspicious sand as a loot table holding container
Steps to reproduce:
place some suspicious sand
use the loot command on it like "/loot replace block 118.64 70.28 211.00 slot.container 0 loot "entities/desert_pyramid_suspicious_sand""
Observed results:The game does an error and says "target position is not a container"
Expected results:suspicious sand contains a loot table just like chests and other containers so the loot command should work on it too so we can put our own loot in them since we don't have nbt command support.
Linked issues
Attachments
Comments 3
no. same error "Target position is not a container" changing the loot table wont fix that. reproed in 1.20.30
Can confirm, affects 1.20.51. I haven't tested this with all the brushable block variants, so this may also affect those.
Although, "entities/desert_pyramid_suspicious_sand" does not exist in the game files, and will throw an error. Use "desert_pyramid_brushable_block", instead. Neither naturally occurring suspicious sand blocks nor ones that were placed will be recognized as valid containers.
To reproduce, all you need to do is replace the coordinates provided in the reproduction steps with your actual coordinates, making sure they match those of the suspicious sand block you're aiming at.
[media]
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Does the command function as expected if you replace "desert_pyramid_suspicious_sand" with "desert_pyramid_brushable_block"?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki