Jukebox song registries are experimental and don't update on /reload
When enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
Steps to reproduce:
- Create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json - /datapack enable "file/example"
- Run
/give @s dirt[minecraft:jukebox_playable={"song":"example:custom_song"}]
Observed result:
Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'
Expected result:
The jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.
However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
- /datapack enable "file/example"
- Restart the server or exit and re-enter the world
- Run
/give @s dirt[minecraft:jukebox_playable={"song":"example:custom_song"}]
This produces the expected behaviour and creates a dirt block with a jukebox_playable component.
Linked Issues
is duplicated by1
relates to6
MC-187938Custom dimensions and worldgen files don't update on /reloadInvalidMC-251318Chat type data pack files are considered "experimental world settings"InvalidMC-260446Trim patterns and materials are experimental and don't update on /reloadInvalidMC-260452Damage types are experimental and don't update on /reloadInvalidMC-271587minecraft:banner_patterns not taking effect in datapack until reloading a worldInvalidMC-272540Custom enchantments not showing on /reloadWorks As IntendedAttachments2
Created Issue:
jukebox song registry required server restart
{{when enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update. }}
steps to reproduce:
1: create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json2: }}{{/datapack enable "file/example"
3: }}{{/give @s dirt[minecraft:jukebox_playable=\{"song":"example:custom_song"}]Output: Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'
Expected behaviour:
the jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
/datapack enable "file/example"
restart server
/give @s dirt[minecraft:jukebox_playable=\{"song":"example:custom_song"}]produces the expected behaviour and creates a dirt block with a jukebox_playable component
{{when enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.}}steps to reproduce:
1: create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json2: }}{{/datapack enable "file/example"
3: }}{{/give @s dirt[minecraft:jukebox_playable=\{"song":"example:custom_song"}]Output: Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'
Expected behaviour:
the jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
/datapack enable "file/example"
restart server/give @s dirt[minecraft:jukebox_playable=\{"song":"example:custom_song"}]produces the expected behaviour and creates a dirt block with a jukebox_playable component
when enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
steps to reproduce:
1: create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json2: }}{{/datapack enable "file/example"
{"song":"example:custom_song"}
{{3: }}{{/give @s dirt[minecraft:jukebox_playable=]}}
Output: Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'
Expected behaviour:
the jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
/datapack enable "file/example"
{"song":"example:custom_song"}
restart server
{{/give @s dirt[minecraft:jukebox_playable=]}}
produces the expected behaviour and creates a dirt block with a jukebox_playable component
when enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
steps to reproduce:
1: create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json2:
{"song":"example:custom_song"}}}{{/datapack enable "file/example"
{{3: }}{{/give @s dirt[minecraft:jukebox_playable=]}}
Output: Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'
Expected behaviour:
the jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
/datapack enable "file/example"
{"song":"example:custom_song"}
restart server
{{/give @s dirt[minecraft:jukebox_playable=]}}
produces the expected behaviour and creates a dirt block with a jukebox_playable component
when enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
steps to reproduce:
1: create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json2: /datapack enable "file/example"
3: /give @s dirt[minecraft:jukebox_playable=\{"song":"example:custom_song"}]Output: Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'
Expected behaviour:
the jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
/datapack enable "file/example"
restart server
/give @s dirt[minecraft:jukebox_playable=\{"song":"example:custom_song"}]produces the expected behaviour and creates a dirt block with a jukebox_playable component
when enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
steps to reproduce:
1: create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')example- pack.mcmeta- data- example- jukebox_song- custom_song.json2: /datapack enable "file/example"
3: /give @s dirt[minecraft:jukebox_playable=\{"song":"example:custom_song"}]Output: Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'
Expected behaviour:
the jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
/datapack enable "file/example"
restart server
/give @s dirt[minecraft:jukebox_playable=\{"song":"example:custom_song"}]produces the expected behaviour and creates a dirt block with a jukebox_playable component
when enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
steps to reproduce:
1: create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json2: /datapack enable "file/example"
{"song":"example:custom_song"}
3: /give @s dirt[minecraft:jukebox_playable=]
Output: Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'
Expected behaviour:
the jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
2: /datapack enable "file/example"
{"song":"example:custom_song"}
2.5:restart server
3: /give @s dirt[minecraft:jukebox_playable=]
produces the expected behaviour and creates a dirt block with a jukebox_playable component
jukebox song registry requiredserver restartjukebox song registry requires server restart
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
pack.mcmeta
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
jukebox song registry requires server restartJukebox song registries don't update on /reload
when enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
steps to reproduce:
1: create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json2: /datapack enable "file/example"
{"song":"example:custom_song"}
3: /give @s dirt[minecraft:jukebox_playable=]
Output:
Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'Expected
behaviour:
the jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
2: /datapack enable "file/example"
{"song":"example:custom_song"}
2.5:restart server
3: /give @s dirt[minecraft:jukebox_playable=]
produces the expected behaviour and creates a dirt block with a jukebox_playable component
When enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
Steps to reproduce:
- Create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json- /datapack enable "file/example"
- Run
/give @s dirt[minecraft:jukebox_playable={"song":"example:custom_song"}]Observed result:
Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'Expected result:
The jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
- /datapack enable "file/example"
- Restart the server or exit and re-enter the world
- Run
/give @s dirt[minecraft:jukebox_playable={"song":"example:custom_song"}]This produces the expected behaviour and creates a dirt block with a jukebox_playable component.
relates to
When enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
Steps to reproduce:
- Create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json- /datapack enable "file/example"
- Run
/give @s dirt[minecraft:jukebox_playable={"song":"example:custom_song"}]Observed result:
Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'Expected result:
The jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
- /datapack enable "file/example"
- Restart the server or exit and re-enter the world
- Run
/give @s dirt[minecraft:jukebox_playable={"song":"example:custom_song"}]This produces the expected behaviour and creates a dirt block with a jukebox_playable component.
When enabling/disabling datapacks that contain jukebox_song entries, the world needs to be restarted for the song registry to update.
Steps to reproduce:
- Create a datapack (lets call it 'example') with a custom jukebox_song (lets call that 'custom_song')
example
- pack.mcmeta
- data
- example
- jukebox_song
- custom_song.json- /datapack enable "file/example"
- Run
/give @s dirt[minecraft:jukebox_playable={"song":"example:custom_song"}]Observed result:
Malformed 'minecraft:jukebox_playable' component: 'Failed to parse either. First: failed to get element example:custom_song; Second: Cannot parse as key without registry'Expected result:
The jukebox_song from the newly added datapack is recognized as a valid value for the jukebox_playable component.However when restarting the world after enabling the datapack, the jukebox_song registry is filled correctly and contains the new song(s).
- /datapack enable "file/example"
- Restart the server or exit and re-enter the world
- Run
/give @s dirt[minecraft:jukebox_playable={"song":"example:custom_song"}]This produces the expected behaviour and creates a dirt block with a jukebox_playable component.
![[Mojang] Triage Team](../../../data/avatars/users/89842.png){kind=small}
Jukebox song registries are experimental and don't update on /reload
is duplicated by
relates to
Thank you for your report!
We're tracking this issue in MC-273807, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as invalid. Please take a look at the parent ticket (MC-273807) and see if an explanation is provided there in the description of the ticket or in the comments for why this issue is invalid.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Please attach a datapack that can be used to reproduce this issue
Note that this behavior is shared across dynamic registries (with the notable legacy exception of loot tables). I believe there are more similar issues and possibly ones relating to this registry specifically, but some I found are:
MC-272540(enchantments, WAI) andMC-260452(damage types, triaged as normal priority). The latter connects to a forest of other reloadable registry issues.Thanks for the clarification @haykam, after some digging around I also heard about other registries sharing this issue. If it really is intended behaviour, I'd love to have some explicit mentioning of this in the 1.21 release notes or something like that. Or did I just miss some general mention of registries requiring a reload in a previous version's patchnotes?
Thank you for your report!
After consideration, the issue is being closed as Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit The official Minecraft feedback site or visit the Minecraft Feedback Discord server.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki