-
Bug
-
Resolution: Invalid
-
None
-
24w33a
-
None
-
Unconfirmed
-
(Unassigned)
When specifying a sound event that is not part of Minecraft by default inside of a goat horn instrument JSON file, the instrument fails to load and the world cannot be opened. This is likely due to that the server doesn't know what sound events have been added by resource packs.
Steps to reproduce
- Create a new sound in a resource pack's sounds.json file, which points to a sound file.
For example:"test_sound": { "sounds": [ "namespace:test_sound" ] }
- In a data pack, create a goat horn instrument JSON file in the data/instrument folder. In the sound_event field, specify the sound even in the resource pack.
For example:{ "sound_event": "namespace:test_sound", "use_duration": 0.001, "description": "", "range": 16 }
- Open the world.
Observed result
The world cannot be opened, as errors were found in the pack. The log contains something akin to this error message:
Caused by: java.lang.IllegalStateException: Failed to get element ResourceKey[minecraft:sound_event / namespace:test_sound]
Expected result
No error appears and the custom goat horn instrument is able to be used.
- relates to
-
MC-258911 Custom sounds from resource pack don't work in custom biome
- Resolved
-
MC-272349 Custom jukebox songs cannot specify a sound event not defined by the vanilla resource pack
- Resolved
-
MC-276371 Equip sound in Equippable component cannot be set to a sound event from a resource pack
- Resolved