Kieren Chantrell
Assigned
No issues.
Reported
Comments
@tryashter, this to me is an glaring unintended behaviour of some overlooked features, and in that sense I would argue it’s a bug. It’s not so much something new which should be added but something which should be fixed. That being said, I also recognise it being seen as a feature. If it should be a feature request and not a bug, where should this be reported so that it will seen by developers?
Can confirm this occurs with functions also. Running the following in a loop and throwing a stone block on the ground causes the same thing to happen.
execute as @e[type=item,nbt={Item:{id:"minecraft:stone"}}] run give @p minecraft:stone
execute as @e[type=item,nbt={Item:{id:"minecraft:stone"}}] run kill @s
@Sulnus, I’m glad you agree that is an issue. I think Mojang hasn’t considered this a problem in the past, but the fault of the map maker. Descriptions, for instance, can be too long to go off screen, and I realise they closed that as a bug, which makes sense; just re-word descriptions to fit. But this isn’t cosmetic like that issue, and relates to the item’s actual functionality. After the flattening, you can’t even add something as innocuous as wool without 16 entries.
It has occurred to me that maybe instead of a scroll (though that would still be a decent solution), block tags should be optionally nameable as exampled below. If the name is present, the name is used in place of all containing blocks in the tooltip.
natural_stone.json:
{
“values”: [...],
“name”: “Natural Stone”
}