mojira.dev
MCPE-49430

"pitch" option in old-format sound_definitions is ignored

Context

There are two ways to write a sound_definitions.json file, both of which are used by vanilla:

  • Put all the sound event keys in the root

  • Put all the sound event keys in a sound_definitions object, next to a format_version (1.14.0)

The bug

When using the former style, the pitch option in sound event entries is ignored.

How to reproduce

  1. Download the attached world

  2. Press the button on the left, then the right
    β†’ ❌ Β Both sound identical

The resource pack contains a single sound_definitions file with pitch specified, so they should sound different.

Expected behavior
Either the pitch should work properly just as it does when using the modern sound definitions format, or the game should alert you with a content log error that the field is being ignored.

Linked issues

Attachments

Comments 11

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

This ticket hasn't been updated for some time - is this still an issue in the latest version? If so, could you please add the latest affected version, or comment if this is no longer an issue.

Also, if there any further steps to reproduce the issue, please include them when possible.

This ticket will automatically reopen when you reply.

Quick Links:
πŸ““ Issue Guidelines – πŸ’¬ Mojang Support – πŸ“§ Suggestions – πŸ“– Minecraft Wiki

Remembered to actually attach the world this time πŸ˜›

I can still reproduce this with the test world inΒ 1.16.100.57

Our testers cannot reproduce this in the latest version - could this possibly be an issue with a pack that you are using?

Are the testers using the attached world or a different one? If the latter, I'd be interested to see the setup. Is it hardware-specific? For now I can still reproduce on latest 1.18.10 on Windows 10 and on my android phone.

[media]

1 more comments

Anyone from the future: use "format_version":"1.14.0" and wrap your sounds in a sound_definitions block to fix this.

Is this still an issue for you?

Still can reproduce in 1.21.30. Since I have a workaround though, I don't care.

tryashtar

(Unassigned)

392376, 758739

Confirmed

Windows

1.18.10.28 Beta, 1.17.40.23 Beta, 1.17.40.21 Beta, 1.17.20.20 Beta, 1.17.0.50 Beta, ..., 1.17.2 Hotfix, 1.17.30, 1.17.32, 1.18.12 Hotfix, 1.21.30.22 Preview

1.16.100.57 Beta

Retrieved