[Dyaus]

so i saw this in a random thread few days ago , someone said that instead of using emit_sound stocks
you can use client_cmd(index, spk ..,...) and instead of using precache_sound() you can use precache_generic() so it won't take a spot of the 512 precahce limit , my question would be , does that actually work ? like why even use emit_sound() if this method exists or is there some kind of drawback to using it i don't know about ? and will converting all my plugins to this method create some sort of error or it should work ?

i hit the 512 limit a while ago and i'm using a precache manager plugin i found by chance to save up some spots , and i'm currently rewriting the plugins i'm using to use the bare minimum of sprites/sounds it needs , so any advice on how to proceed on this would be appreciated .

[Shadows Adi]

If you play client-side sounds (client_cmd(id, "spk ..." ) ) yes, you can precache them using precache_generic.
If you play server-side sounds ( emit_sound(), etc ) you need to precache them using precache_sound beccause sounds played by engine are going through pfnEmitSound and the server will crash if the sound played is not in the precache list ( same situation about models; player models could be precached by generic, because they are set within setinfo )

[OciXCrom]

client_cmd() plays sounds directly TO the player(s). This can be precached using precache_generic() and it won't take up a spot in the 512 limit.

emit_sound() emits a sound FROM a player to nearby players. This must be precached with precache_sound() which counts towards the 512 limit.

So the real question is which one you need in different situations. For example, you would probably want to use emit_sound() if changing the knife sounds because nearby players need to hear them coming from the knife/player itself. On the other hand, clicking a menu would play a sound to the player and only he will hear it - this is a job for client_cmd().

[Dyaus]

Originally Posted by OciXCrom client_cmd() plays sounds directly TO the player(s). This can be precached using precache_generic() and it won't take up a spot in the 512 limit. emit_sound() emits a sound FROM a player to nearby players. This must be precached with precache_sound() which counts towards the 512 limit. So the real question is which one you need in different situations. For example, you would probably want to use emit_sound() if changing the knife sounds because nearby players need to hear them coming from the knife/player itself. On the other hand, clicking a menu would play a sound to the player and only he will hear it - this is a job for client_cmd().

hmm , makes sense , that means i will have to be very selective of what should remain as emit_sound() since i do need to free up some spots for future plugins ... anyways thanks

[Natsheh]

For the sounds that youre not emitting using emit_sound you can merge them into one file and use spk command with its argument spk "one(s30,e50)" thats will save you alot of resources but its an annoying process to do all that.

[Dyaus]

Originally Posted by Natsheh For the sounds that youre not emitting using emit_sound you can merge them into one file and use spk command with its argument spk "one(s30,e50)" thats will save you alot of resources but its an annoying process to do all that.

o.o definitely something i want to look into in the future , a very useful piece of info , thanks for that

[OciXCrom]

Definitely not needed at all and will only make things unnecessarily complicated.
I already said that those sounds don't count towards the 512 limit, so what's the point?!