Ambient sound preset for adventure maps

Use this for dungeon entrances, cave rooms, haunted corridors, and map regions where a quiet sound cue should support atmosphere without becoming combat feedback.

The preset uses the ambient source, lower volume, and lowered pitch so the command reads as environmental mood rather than a reward or warning sound. A screenshot-only snippet is not enough for these commands because the visible UI state has to match command output and map logic. Keep the preset as a checkpoint where the readable label, selector, id, and generated command can be reviewed together before the command is copied.

Ambient sounds can stack if a repeating trigger fires too often. Gate the command with distance, cooldown, or room-state logic before adding it to a live map.

Run the first smoke test in a restored world with only the needed commands active. HUD, chat, bossbar, and scoreboard results are easy to confuse when old objectives or bars remain from a previous test, so create or reset the state before judging the screenshot. Keep selectors narrow when the final map should affect one player.

• Use stable ids for stateful commands.
• Keep player-facing feedback short enough to read or recognize quickly.
• Save related setup and update commands together in Project.

Pair this with region detection or scoreboard state so the sound fires once when players enter the intended space.

For stronger event feedback, compare the playsound quest reward preset and portal particle transition preset.