Help: Making a player 'deaf'

[Spike]

[OneManClan]

[Spike]

[OneManClan]

[mh]

[OneManClan]

[OneManClan]

Ok, I made a silent version of "weapons/r_exp3.wav" and put it in the .pk3, but you can still hear the explosions... presumably by the original r_exp3.wav which is still in the pak.

Is there something else that needs to be done?

[EDIT] I just noticed that I have a "r_exp3.wav" in C:\Quake\id1\sound\WEAPONS - ie not in a pak - is this normal?

[frag.machine]

[leileilol]

[Spike]

except he's making a QW mod. not all clients support the particle builtin, and even if they do there's no guarentee that they can cope with the 1024-particles quirk. I really have no idea which qw clients actually support that.
writebytes are evil. Also QW uses a slightly different format, and has nasty protocol limits.
as his mod is already dependant upon fteqwsv, he can just use the dimension_send&self.dimension_see filter for greater control over the sound+multicast+etc builtins so should have no need for writebytes.

[OneManClan]

[ratbert]

OMC keep things simple

1) Keep mod based on using the same fortress folder structure setup. Making players download ton new things from a different setup is going to annoy people.

2) Make your new sounds and/or models unique names so they do not conflict with existing customtf mod (or other tf mods for that matter) that it currently uses.
Your only adding a few new things to your customtf agr mod anyhow. Having to download whole pak or pk3 files for simple mod changes in this current age is
Dumb (just my two cents). Maybe a good idea back in 1996 when things were way different. As you know with my coop mod many custom things I added I usually
added "rat" to start of the model or sound to give a unique name.

3) Is your player base using only modern quakeworld clients using FTE or EZQUAKE?

4) With these various changes you are trying implement will they make your player base happy or annoyed?

[Baker]

[leileilol]

He wants hyperventilation sounds. Alias abuse won't help that.

[Spike]

regarding the volume cvar (or rather any cvar in general), if the server changes the setting to its non-default setting, fte clients will restore the original value automatically when the map changes/player disconnects/server restores the setting to its default.
ezquake will not. which means ezquake users will likely get annoyed if they disconnect while the effect is in force. If its a short-term effect, you can probably get away with it. if it stays like that for the rest of the game then you probably cannot. on the plus side, quakeworld clients tend to not save configs by default, so it should be restorable by just quitting and starting it up again.

I have to ask though, is the aim to make the player unable to hear anything (including the someone-just-said-something-beep), or will you want to still be able to hear a select sounds (alternatives, announcements, etc)?

hacks are evil nasty things, but they're often the simplest/fastest/best/only way to do things. just make sure you understand and accept the consequences.