I've taken liberty and shortened it up for you to two elements, but you get the structure. EN Play_GoodHit Voice VGoodHit En_Speech_Hit_Confirmation_1.wem En_Speech_Hit_Confirmation_2.wem En_Speech_Hit_Confirmation_3.wem En_Speech_Hit_Confirmation_4.wem En_Speech_Hit_Confirmation_5.wem Play_Last_Hope Voice VLast_Hope En_Speech_Last_Hope_1.wem En_Speech_Last_Hope_2.wem without this XML file the mod is useless. And now the sound files ended up all lumped into one directory, with the XML file telling client what it needs to do with them. XML is a pretty simple and straightforward format, which most people related to programming in one way or another should be well familiar with. Yikes! In 0.6.13 Wargaming moved away from the folder structure ( thank gods), and decided to have an XML file to keep check of which file goes where. That's on average about 1 folder per 2 files.
For example, Mermaid's Wrath for 0.6.12 client contained 646 files in 328 folders.
The structure worked, but was a fair bit of a pain to maintain, because folders typically were two-three levels deep and contained just a handful of files per folder on the deepest level. So what actually happened? Well, those familiar with sound mod structure before 0.6.13 will know that the audio files were organized into a strict but complex directory which described what file is supposed to be played for what event (voice and sfx included). Especially since the file is supposed to be named mod.xml. Which we only find out after digging around the clients packed files. It's not "a control.xml file", it is supposed to read "a control(ler) XML file". Moreover, whoever translated this from Russian patch notes introduced a mistake. While still not officially supported, we’ve improved the functionality of player-created sound mods - a control.xml file is created for each mod, which contains paths to all that mod's files.Ī single quizzical (and ultimately useless) line blurb about something that pretty much turned the sound mods upside their heads.
0 kommentar(er)
