[Ron]

I wonder if anyone else noticed this odd problem. I made a sound mod and named the PK3 file "historymajor's REAL sounds"
Whenever i put it into my main folder none of the sounds would work and just the default sounds would work.
If i simply retyped the same PK3 file to something like "realsounds" it worked just fine.

This was such a problem i had to resubmit my file since the first one wouldn't work cause of the name problem...lol all i did was resubmit the same file with a shoreter file name and it was fine.

Isn't that odd??!! oOo:

Anyone else notice something like that or know why that happened?

[Dragonwraith]

use _ instead of spaces in file names, also add a few z's to the name

Ex: zzzzz_realwar_sound_mod

[Ron]

i can see how the underscore could mean something but why in the world would zzzzzz's make a difference? oOo:

[intrestedviewer]

LOL eh now thats funny biggrin: maybe you can try xxxxxxx's i hear they work better than zzzzz's

[T.Hunter]

because when you load up moh it loads up all the files alphabetically

use ZZZZZ to prevent file contamination

[Dr. Deleto]

yes, the pk3 system picks up components in alphabetical order. Since the original game pk3 names start with "p" ex: "Pak0.pk3" you will want to name them starting with a letter that comes after p in the alphabet. This way it picks up your modified components after the original game components and uses them instead. The reason "z"'s are used so much is because they are the last letter in the alphabet and tend to always come last. Letter stacking also works here.

a file with 2 z's will come after a file with one z at the beginning of the name simply because the coding will pick it up after the single z'ed filename.

example in the order the moh engine would pick up 5 pk3's.

pak5.pk3
user-Myscope.pk3
Z-myblood.pk3
zsz-mycompass.pk3
zzs-mynewweaponmodel.pk3

hope this clears things up.

[Ron]

wow that's interesting, i never knew?! cool: