phaic
- phaic
- JIRAUSER497175
- Europe/Stockholm
- Yes
- No
In 24w11a the following set lore item modifier works fine, however it has been broken in the latest snapshot despite no changes to item modifiers being listed, only some bug fixes, perhaps
MC-269457had something to do with it?
[ { "function": "minecraft:set_lore", "entity": "this", "lore": [ { "text": "A sword fit for the grandest adventurer!", "color": "gray", "bold": false, "italic": false } ], "replace": true } ]
The game output returns this error only in 24w12a:
Couldn't parse element item_modifiers:test:set_lore - Input does not contain a key [mode]: MapLike[{"function":"minecraft:set_lore","entity":"this","lore":[{"text":"A sword fit for the grandest adventurer!","color":"gray","bold":false,"italic":false}],"replace":true}]
How to reproduce
1. Use the attached datapack in 24w11a and while holding an item run:
/item modify entity @s weapon.mainhand test:set_lore
2. Observe the lore applied to the item
3. Repeat in 24w12a
4. Item modifier is no longer recognized
Expected Outcome
Item modifier is applied to weapon and should read in gray:
"A sword fit for the grandest adventurer!"
In 24w11a the following set lore item modifier works fine, however it has been broken in the latest snapshot despite no changes to item modifiers being listed, only some bug fixes, perhaps
MC-269457had something to do with it?
Edit: Even with the "replace": true remove it still does not work
[ { "function": "minecraft:set_lore", "entity": "this", "lore": [ { "text": "A sword fit for the grandest adventurer!", "color": "gray", "bold": false, "italic": false } ], "replace": true } ]
The game output returns this error only in 24w12a:
Couldn't parse element item_modifiers:test:set_lore - Input does not contain a key [mode]: MapLike[{"function":"minecraft:set_lore","entity":"this","lore":[\{"text":"A sword fit for the grandest adventurer!","color":"gray","bold":false,"italic":false}],"replace":true}]
How to reproduce
1. Use the attached datapack in 24w11a and while holding an item run:
/item modify entity @s weapon.mainhand test:set_lore
2. Observe the lore applied to the item
3. Repeat in 24w12a
4. Item modifier is no longer recognized
Expected Outcome
Item modifier is applied to weapon and should read in gray:
"A sword fit for the grandest adventurer!"
When set to false, custom names on interaction entities still display when looked at. This behavior first appeared in the update where boats & minecarts were given visible names when looked at. This behavior should not apply to interaction entities since they are development tools like markers.
Steps to Reproduce:
{"text":"Hello"}
1. Type /summon interaction ~ ~ ~ {CustomNameVisible:0b,CustomName:''}
2. Look down to see the custom name is visible when looked at
Expected Results:
Setting CustomNameVisible to 0b should hide the name
When set to false, custom names on interaction entities still display when looked at. This behavior first appeared in the update where boats & minecarts were given visible names when looked at. This behavior should not apply to interaction entities since they are development tools like markers.
Steps to Reproduce:
1. Type/summon interaction ~ ~ ~ {CustomNameVisible:0b,CustomName:'{"text":"Hello"}'}
2. Look down to see the custom name is visible when looked at
Expected Results:
Setting CustomNameVisible to 0b should hide the name
Its true, this is not a feature request. It should be looked into as it was possible before the switch to components
When teleporting a mounted entity, it becomes dismounted. This breaks a very large amount of interactions that datapack creators utilize and was not present in previous versions.
Steps to reproduce:
1. Run the following summon command:
/summon husk ~ ~ ~ \{Tags:["bottom"],Passengers:[{id:"minecraft:husk",Tags:["top"]}]}
2. Run the following tp command:/execute as @n[tag=top] at @s run tp @s ~ ~10 ~
3. Observe in 1.21 and then latest snapshot. In version 1.21 the entities do NOT dismount. However, in the latest snapshot this dismounts the entities.
Expected outcome:
The entity that is mounted should not dismount
When teleporting a mounted entity, it becomes dismounted. This breaks a very large amount of interactions that datapack creators utilize and was not present in previous versions.
Steps to reproduce:
A. Run the following summon command:
/summon husk ~ ~ ~ {Tags:["bottom"],Passengers:[{id:"minecraft:husk",Tags:["top"]}]}
B. Run the following tp command:
/execute as @n[tag=top] at @s run tp @s ~ ~10 ~
C. Observe in 1.21 and then latest snapshot. In version 1.21 the entities do NOT dismount. However, in the latest snapshot this dismounts the entities.
Expected outcome:
The entity that is mounted should not dismount
phaic: Please stop confirming this for every new build, major releases are more than enough! Any further comments will be removed.
I can confirm (in 1.15.2), as I have a zombie in an iron farmed that I named using a nametag, and once i walked out of distance of it the zombie had despawned. In other versions (1.14 & below( of the game I do the same and the zombie will still be there when I return to the chunks.
Attached launcher_log.txt and here is a datapack. Was too large to upload so you can get it here
Can confirm in 24w09a
Can confirm in 24w11a
I might have brain worms. Thanks Misode!
For anyone that ended up here this is now the working code
[ { "function": "minecraft:set_lore", "entity": "this", "lore": [ { "text": "A sword fit for the grandest adventurer!", "color": "gray", "bold": false, "italic": false } ], "mode": "replace_all" } ]Markers do not display names when CustomNameVisible is set to 0
Confirmed in 21w14a
Yes
Confirmed in 1.20.5 release candidate 2
Confirmed in 1.21 Pre-release 3
Confirmed in 1.21 Pre-release 4
Confirmed in 1.21 Release Candidate 1
Got it. I will only comment for major releases. In this case, I can confirm this bug in Release 1.21
Confirmed in 1.21
Confirmed in 1.21.4