In the BlockStateTag tag all the values that must be Boolean are strings, which does not make sense since it only has 2 possibilities, true or false
For example
/give @p stone_slab{BlockStateTag:{waterlogged:"true"}}should be
/give @p stone_slab{BlockStateTag:{waterlogged:true}}or
/give @p stone_slab{BlockStateTag:{waterlogged:1b}}
Values that use the BlockStateTag tag and should be Boolean are:
open, occupied, powered, lit, has_bottle_0, has_bottle_1, has_bottle_2, drag, signal_fire, waterlogged, down, east, north, south, up, west, conditional, inverted, triggered, eye, in_wall, snowy, enabled, hanging, persistent, has_book, extended, short, locked, bottom, unstable, attached, disarmed
Comments 3
Yes, but in the case of simply putting the integer it accepts it as if I put it as a string
In the following case it gives me an item that when I put it there are 3 candles but they are off
/give @s candle{BlockStateTag:{candles:3,lit:true}}
Thank you for your report!
After consideration, the issue is being closed as Working as Intended.
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
Full Version History – Snapshot Version History – The official Minecraft feedback site
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
This is not just booleans, integer states are also stored as string