Skip to content

Loadout specific settings and a resup bind that knows which loadout you're on.

Notifications You must be signed in to change notification settings

jooonior/tf2-loadouts-script

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

59 Commits
 
 
 
 
 
 
 
 

Repository files navigation

junior's loadouts script

Loadout specific settings and a resup bind that knows which loadout you're on.

GitHub · TFTV

Features

  • single resup key that always respawns you on the right loadout
  • loadout specific settings
  • remembers which loadout you have active on each class, even after you restart TF2

Resup bind (aka b4nny bind) lets you resupply while in spawn without needing to touch the fridge/cabinet. Unlike switching classes, it preserves all of your buildings, stickies and ubers (but not stored crits, heads or banner charges).

Setup

  1. Download the VPK from the latest release and save it into your tf/custom folder

  2. Add exec loadouts/init to your autoexec.cfg

  3. Add loadouts.<class> at the end of each of your <class>.cfg

    Replace <class> with actual class names: scout, soldier, pyro, demoman, heavyweapons, engineer, medic, sniper, spy

  4. Bind your keys

    loadouts.A, loadouts.B, loadouts.C, loadouts.D for switching loadouts
    loadouts.resup to resupply

    Do this in your autoexec.cfg or wherever you have your binds.

    Example
    bind F1 loadouts.A
    bind F2 loadouts.B
    bind F3 loadouts.C
    bind F4 loadouts.D
    bind ALT loadouts.resup
    

    If you need help with key names see List of key names on TF2 Wiki.

Loadout specific settings

When changing to loadout X, the script calls corresponding loadout.cfg.X alias. You can set these aliases to execute arbitrary commands when changing lodouts.

If you want to set these per class in your <class>.cfg, you need to do so before the loadouts.<class> line. If you want to set them globally, do so in your autoexec.cfg after the exec loadouts/init line.

Don't forget to reset these aliases (and affected settings) for other classes, otherwise their values will carry over.

Example

Your medic.cfg could look something like this.

bind 1 slot1  // some binds
cl_crosshair_scale 20  // some settings

alias loadouts.cfg.A "exec uber; say_team running uber"
alias loadouts.cfg.B "exec kritz; say_team running kritz"
alias loadouts.cfg.C "exec quickfix; say_team running quickfix"
alias loadouts.cfg.D  // no settings for D

loadouts.medic

FAQ

There's a delay between when I press the key and respawning.

That's normal. Happens with all resupply binds. You should press it (or spam it) right before you enter spawn.

Why does loadouts.<class> have to be at the end?

It doesn't. But anything that comes after it overrides the loadouts.cfg.X settings. If you are sure you're not breaking anything, you can put it anywhere you like.

Doesn't it break when item servers are down?

Yup.

Something else.

Check the issues tab, someone might have already asked. If not, feel free to open a new issue.
Another option is TFTV. I don't get notified when you comment there, but someone else might help you.

About

Loadout specific settings and a resup bind that knows which loadout you're on.

Topics

Resources

Stars

Watchers

Forks

Languages