Killstreak Sounds

Rack up the kills and be satisfied doin' it!

I wrote killstreaks mainly with announcers in mind. That being said, they're fairly easy to set up.

NOTE: These killstreaks will only reset upon death, they have no time limit.

File Location

Killstreaks use the file located in: englishclient_mp_common.bsp.pak000_dir/scripts/vscripts/client/cl_obituary.gnut

Follow this guide if you don't know how to unpack the vpk.

What To Do

Establish an integer variable at the beginning of the gnut named killstreak:

Just like with Killsounds and Deathsounds... Scroll through cl_obituary.gnut until you find the first appearance of: string attackerString string weaponString string victimString

This should be around line 253.

Right under these strings, add the following code for killstreaks:

    if(attacker == GetLocalClientPlayer() && victim != GetLocalClientPlayer() && victimInfo.petDisplayName == "" )
    {
        int totalnumber=RandomInt([number])
        killstreak+=1
        GetLocalClientPlayer().ClientCommand("killstreak"+killstreak+"_"+totalnumber)
    }

Replace [number] with however many variations of killstreaks you plan on using. Note that this randomizes every time it runs through. If you want the random pick to be more consistent, check Announcer. Otherwise, just make this 1.

If you already have custom killsounds, you can simply put them in the same if-statement.

If you also want to keep a killstreak for how many player titans you've killed (either auto-titan or titan with a player using it) you can write this (you need to establish titanstreak at the beginning of the gnut too):

    if(attacker == GetLocalClientPlayer() && victim != GetLocalClientPlayer() && victimInfo.petDisplayName != "" )
    {
        int totalnumber=RandomInt([number])
        titanstreak+=1
        GetLocalClientPlayer().ClientCommand("titanstreak"+titanstreak+"_"+totalnumber)
    }

To get your killstreaks to reset when you die, write this:

    if(victim == GetLocalClientPlayer())
    {
        killstreak=0
        titanstreak=0
    }

Again, if you have custom deathsounds, you can just put them in the same if-statement.

The neat thing with this code is that, once added, you don't even have to go back and change something if you want to add more killstreak sounds or move them around. You simply need to name your custom sounds properly and edit the autoexec.

If you want your killstreaks to loop back around after a certain point, you can write this inside of your killsound/killstreak if-statement:

        if(killstreak==[number])
        {
            killstreak=0
        }

Where [number] is the amount of kills you wish for your killstreak to be reset. (usually the same as your highest killstreak number) Of course, you can do the same for titanstreak inside of your titanstreak if-statement.

media and autoexec.cfg

When making the audio for your killstreaks/titanstreaks, I recommend spacing them out a bit so that they don't overlap each other, at least not as much. For example, if you have a custom killsound, killstreak, and titanstreak, and you kill a player who's in a titan, you're gonna hear all 3 sounds at once unless you space them properly. Just something to think about.

Place the killstreaks/titanstreaks you'll be using in the Titanfall2>r2>media folder. For naming, you would put killstreak[amount of kills]_[RandomInt number]

Remember that the lowest RandomInt roll is 0, not 1.

Ignore that these all end in 1, it should be 0 if you're just doing this tutorial and aren't randomizing them.

To call the killstreaks in the autoexec, write them out like so:

alias killstreak[kills]_[number] "playvideo killstreak[kills]_[number] 1 1"

Where [kills] is the amount of kills you need in one life for that sound to play, and [number] is the chosen integer from RandomInt (starting from 0)

If you're doing killstreaks and titanstreaks, your autoexec should look something like this:

Again, ignore that the names all end in 1, put 0 instead if you're just doing this tutorial and aren't randomizing them.

Follow this guide for more info about the autoexec and how to properly set it up.