Art's (Probably) Inefficient VSTR Use, Explained!

I'm a bit new to this, so there are probably better ways to go about it, but the point of this thread is to show you how you can put multiple binds/commands on one key without accidentally injecting them into your main jampconfig (like I did, multiple times xD).

I'll show you how I have mine set up and explain as I go.

First, I have an autoexec.cfg in case I really screw up and break something.  It just has all of my binds and edited settings, the majority of which you don't get to see. :P
bind CTRL "echo This bind is inactive!"

bind P "say Denied.."

bind F11 "echo All VSTRs are active!; exec charcolors; exec binds"
bind F12 "echo All VSTRs are inactive!; exec autoexec"CTRL is my color change button.  If I hit it at this point, I'll just get a message at the top of my screen that tells me it won't work.

My P button ONLY says one thing right now.  That will change later.

F11 and F12 are the most important parts; the rest of that is just there because I wanted it.  F11 activates the CTRL key and adds to the P key, and F12 returns everything to its original state.  (You can narrow it down to one key, or just /exec autoexec if you're really running out of keyboard space... But I like the echo command.)

So my charcolors.cfg looks something like this:
//These are the keys to assign the commands:
bind CTRL "vstr CLRS"

//This is the set command to vstr the commands:
set CLRS "vstr char01"

//These are the color commands:
seta char01 "set CLRS vstr char02; wait 50; char_color_red x; char_color_green x; char_color_blue x"
seta char02 "set CLRS vstr char03; wait 50; char_color_red x; char_color_green x; char_color_blue x"
seta char03 "set CLRS vstr char01; wait 50; char_color_red x; char_color_green x; char_color_blue x"Now every time I press CTRL, my color changes.

I've heard that vstr names need to be kept short, so if you're making one, don't get overly specific with what it's called.  I cut out the last couple of colors, but you can definitely have more.  Just link the last vstr name with the first so it won't end up breaking.  It's also easy to accidentally spam this, which will make it tell you to wait and skip whatever the next color is the next time you press it.  So go slow!

Here's part of my binds.cfg:
//These are the keys to assign the commands:
bind P "vstr NO"

//This is the set command to vstr the commands:
set NO "vstr no01"

//These are the commands:
seta no01 "set NO vstr no02; say Denied.."
seta no02 "set NO vstr no03; say Negative.."
seta no03 "set NO vstr no01; say Nope.."The same thing as with the color bind, it just cycles through text instead.  I actually have a few other say binds set up like this, in the same cfg.

Hopefully, this will help you either free up some keyboard space or throw some extra pizzazz in with your binds.