Thanks for your quick responses, gaoesa! I really am enjoying this community and think you developers are doing an exceptional job!
On our ETPub server, we put our hitsounds in a custom folder similar to sound/IoW/hitsounds/
. Then we used the path cvars to point to those files. Doesn't that force the client to reload the new files when they connected to our server (even from another server), since the new paths are specified in the server config? That is what I meant for helping to bypass the problem. Still, I do like the idea of not having all those path cvars. It is much cleaner replacing the standard sounds in the pk3.
Now, I understand that using a pk3 that starts with a character after 's' allows for modifying the files fairly easily. But, since the client would be using the exact same path on the new server as the server that they arrived from, wouldn't that be part of the problem? By having a specified path (or preferred directory), it seems like it would force the client to reload the files when they connect since it is not referencing the same path anymore (assuming that the preferred directory is not named the same).
Hope that clears up what I was thinking. Please correct me if any of that is wrong... I do enjoy hearing your insights on how all of this stuff currently works!
Thanks for considering the suggestion!
Edited by JvIasterMind, 29 September 2011 - 12:48 AM.