![]() I eventually found a file that listed the old file paths, as well as a few other things. "Well, to put it simply, I wasted more of my precious time trying to figure out what they were and after a couple hours I ended up getting a lucky break. "How the heck did you figure out what they all were anyway?" "Because I took a lot of time out of my day to test every last one of them in order to make sure that they all work, and to check for duplicate sounds. If you want to be sure that the sound argument you use will work, just copy/paste it from my list. If you try to use a sound argument that doesn't exist, it'll lie right to your face and say that it played the sound, even though it doesn't exist to begin with. All I know for sure is that it isn't possible to specify a specific numbered sound argument. As to why the command doesn't work like that, I have no idea. "You can't because that isn't how the command works. So now you're likely wondering: "How can I make sure it uses mob/skeleton/say1 instead of mob/skeleton/say2 or 3?"Īnd this is the part where I answer questions before you ask them: "You can't." Instead, using will randomly pick a sound from all of the different mob/skeleton/say# sounds. Since you can't use a number on the end, you can't specify which sound to play. What I'm saying is that most people will try to use 1 when they should actually be using instead. Since people think the file path name is what's being used, they assume that there should be a number on the end of most sound arguments - this is not the case either. This brings me to the next issue, which actually just builds on the first. Speaking of which, Fun Fact: None of the sound files use their original names now, or even anything sensible (for example, "sounds/ambient/cave/cave1" is now "29d4dccf3353334c7aa2a49cb6fed3780a51a1ba"). Here's a perfect example of what I'm talking about: - does that look at all the same as random/fuse? I don't think so. This is the reason why I refer to them as " sound arguments" instead of " sound file names", because that's what they actually are. What is placed in the section of the command is similar to the file path name, not the same (and I'm not just talking about decimal points instead of slashes). People somehow got it into their heads that the file path name for a sound is what's placed in the part of the command - that's not the case. Here's one of my favorites as an example: /playsound Issues/Misconceptions and Other Relevant Information:Īlright, here is possibly the biggest issue people are having with the /playsound command. ![]() And obviously you can switch out for or a specific player name if you want. Now here's how you should use the command in-game: /playsound you have to do is replace with the sound argument of your choice from the list above. If a sound argument has * before it, that means it would play the exact same sound(s) as the argument above it. Basically, my goal here is to give everyone a nice, complete reference list, and to clear up any/all confusion that I can regarding the /playsound command.įirst off, the complete list of sound arguments for 1.8, organized into 3 groups ( General Sounds, Mob Sounds, and Music): I've noticed that lots of people like having a list of sound arguments for this command, but the only list I've found is incomplete and a bit misleading. ![]() IMPORTANT NOTICE: This list does not work in 1.9 nor it's snapshots.įor a list of sound arguments that do work in 1.9, please click here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |