420weedsmoker69 VS comfig-fortress

I actually have recursive psuedovoice-menus that store my call(out)s. I have an explanation on them here, and I store my calls in a file.

A while back I made a generator to make nested bind-voicemenus (like the one in tribes or the CS:GO weapon selection) more efficiently, without wasting so much time to make my binds. Over some months I reworked this tool so it's much better than before hand. I still need criticism for this tool tho, so I can improve it.

So I have made a ton of binds (linked here) for my config with this recursive bind-voicemenu system that's seems to be working alright. Unfortunately it feels like I have to look at the display to select a bind, and my body feel slow at selecting a bind. (NOTE: You need my CmdMenuGenerator to make these binds.)

I use my binds organized in voicemenus for this reason. I swear I fear I'll get ostracized just for using voice chat, since I feel like my external voice (the voice that isnt from you speaking) is ass.

Make binds to alert your team on your medigun and über status, like I did with my own binds.

I have binds to tell my pocket to push, tell my team my über status, and alert the team to which medigun I'm using. They're stored in my Command Menu system. (More information in this link.)

Edit: I learned that the mastercomfig team has a 100 player server and this is their server.cfg file https://github.com/mastercomfig/comfig-fortress/blob/master/100/tf/cfg/server.cfg