We've split up the commands, scripting and mods, and add ons category! Please be sure you get your thread in the right place.

← Commands
46
Follow

Add a delay parameter to the /stopsound command

Due to the fact that stopping sounds can be very abrupt, I suggest the ability to slowly stop a sound/sounds over a variable amount of time. Instead of

"/stopsound <target> <category> <name>"

I propose the command becomes

"/stopsound <target> <delay> <category> <name>"

The delay parameter would determine the amount of time, in seconds, it takes for a sound to fully stop. The sound/sounds will slowly decrease in volume (in blocks and in actual volume) from the time the command is run till the time the sound or sounds fully stop. If the value of delay is 0, however, the sound will stop instantly like before.

The reason it is being suggested and main use for this addition is to be able to slowly fade music out in the middle of a song and transition it into another song easily. This is a critical addition to making an ambient/situational music datapack.

Avatar
Registered User shared this idea

4 Comments

Please sign in to leave a comment.

Date Votes
Sorted by oldest
  • 0
    Registered User commented
    Comment actions Permalink

    An additional great idea for the /playsound and /stopsound command can be found here:
    https://feedback.minecraft.net/hc/en-us/community/posts/360042834671-Remove-playsound-stopsound-command-and-add-sound-command

  • 1
    Registered User commented
    Comment actions Permalink

    That would be so helpful for Adventuremap!

  • 1
    Registered User commented
    Comment actions Permalink

    I agree. This would be very helpful. I’m building an adventure map for my friends right now, and I want to let the music from my custom resourcepack to slowly fade out as they get near to the tavern, so that the other music can start. Without this feature I have to come up with an idea to make it less abrupt.

  • 0
    Registered User commented
    Comment actions Permalink

    I agree that this is a crucial feature that would help map makers a ton.

    Although I'd suggest that the new parameter "<delay>" comes at the end of the command, for intuitive syntax and (optional parameter defaulting to 0) backwards compatibility reasons.

    Also, a delay in seconds is fine but for the sake of it already being a thing in other commands and giving more control I suggest the delay being either in ticks, or having the t/s/d suffix from e.g. the schedule command.