mojira.dev
MCPE-190496

Some Spring Drop 2025 sound events are named wrong or missing entirely

Some of the new sound events added in the Drop 1 2025 experiment are not named the same as Java Edition. This creates a parity issue for the /playsound command.

In addition, some sound events are missing entirely.

Here is a full list of sound events from the Spring Drop, from Java Edition vs. Bedrock Edition. The incorrect names are marked with an ❌.

Java Sound Event Name

Bedrock Sound Event Name

Name Matches?

block.leaf_litter.break

block.leaf_litter.break

block.leaf_litter.fall

[MISSING]

block.leaf_litter.hit

[MISSING]

block.leaf_litter.place

block.leaf_litter.place

block.leaf_litter.step

block.leaf_litter.step

block.firefly_bush.idle

block.firefly_bush.ambient

block.sand.ambient

block.sand.idle

block.sand.ambient.attached

block.sand.wind

block.deadbush.ambient

block.deadbush.idle

block.cactus_flower.break

block.cactus_flower.break

block.cactus_flower.place

block.cactus_flower.place

Example

This sound event is used for sand wind sounds on both platforms, but is named differently.

Bedrock:

[media]

Java:

[media]

Expected Result

The sounds from Drop 1 2025 use identical names to Java Edition.

Observed Result

The sounds from Drop 1 2025 differ in name from Java Edition, and some sounds are missing entirely.

Notes

This issue relates to MCPE-190497.

Attachments

Comments 1

All wolf sounds are also named incorrectly. They should be updated to use the Java style:

entity.wolf_[sound_variant].[ambient/death/growl/hurt/pant/whine]

Instead of the current Bedrock format:

mob.wolf.[sound_variant].[bark/death/growl/hurt/panting/whine]

AgentMindStorm2

(Unassigned)

Unconfirmed

Multiple

Windows 10

sound, sound-event, vanilla-parity

1.21.70.22 Preview

Retrieved