Last weeks I decided to make certain changes I came with. I'm going to describe them in enough detail, also for any server admins to understand. These include:
Fix headshot issues:
Fix headshot events being triggered when killing with non-hitscan weapons, if the last hit to the victim done by a hitscan weapon was in the head
Reset client's HS streak count when they die. Triggering HS events tied to > 0 kill streaks not achieved within the same life felt too weak. I went to investigate if this was a common convention in Quake sounds plugins and, for instance, Quake sounds v3 also applies new behaviour.
Add countless fallback for counted kill phrases. If someone wants to set e.g. headshot events for every kill, now they don't need to go and rename the "headshot 1" phrase to "headshot 0" anymore. See the related commit for more details.
Support randomized sounds. Admins can now configure multiple sounds to play one randomly each event! (per sound set). To stay consistent, during an event action, the logic will carry the randomized sound for each sound set from the time it's demanded (by the first applicable client) to the rest of the clients with the same sound set. I.e. target clients will play same temporary randomized sound between equal sets.
Support multiple kills config values on same line. Write less, do more. If you want to share possible settings for different kill streak counts, you can do easily now (I guess the best fitting event type is headshot, anyways).
Self-explanatory samples from my server's config:
Randomized sounds:
Instead of assigning a sound directly as a value for the sound set (e.g. "standard" "file.mp3"), you need to organize the keys in the following way, listing each possible random sound as a subkey of the sound set:
"Grenade" // The event type
{
"0" // The kill count
{
"standard" // The sound set
{
"1" "kdnnuevo/boombombazo.mp3"
"2" "kolokonklan/xgrenadex.mp3"
}
}
}
Of course, the original one-liner format for a single assigned sound is still supported.
Important: the randomized setups will only work when a kill count key ("0" in the example) surrounds the sound set key. Otherwise the event will be set incorrectly.
In the context of the proposed changes in the PR, this setup means: play the specified HS sound when applicable at kill streaks 3 & 5 (with the unique "headshot 3" and "headshot 5" existing phrases each), and for every other kill streak with the unique "headshot" phrase (originally the "headshot 1" one).
Finally, the changes are already well tested from my server. If you want to see them in action, you can add me in Steam. I hope you like the changes!
Hi,
Last weeks I decided to make certain changes I came with. I'm going to describe them in enough detail, also for any server admins to understand. These include:
"headshot 1"phrase to"headshot 0"anymore. See the related commit for more details.Self-explanatory samples from my server's config:
Instead of assigning a sound directly as a value for the sound set (e.g. "standard" "file.mp3"), you need to organize the keys in the following way, listing each possible random sound as a subkey of the sound set:
Of course, the original one-liner format for a single assigned sound is still supported. Important: the randomized setups will only work when a kill count key (
"0"in the example) surrounds the sound set key. Otherwise the event will be set incorrectly.In the context of the proposed changes in the PR, this setup means: play the specified HS sound when applicable at kill streaks 3 & 5 (with the unique
"headshot 3" and"headshot 5"existing phrases each), and for every other kill streak with the unique"headshot"phrase (originally the"headshot 1"one).Finally, the changes are already well tested from my server. If you want to see them in action, you can add me in Steam. I hope you like the changes!
Thank you.