You don't really need anything complicated. If you have a mouse with side buttons you may want to change your binds. As a medic you may want to bind buttons to team chat messages, über faking, etc. That kind of stuff can be done with very simple commands.
The fancy spy scripts should all be up for download somewhere too.

I'd say figure out what you wanna do and then look up/ask someone what the commands are for that. Generally they're not that complicated and you'll learn along the way so in the future you'll be able to edit it if you want to.

If you don't want to start from scratch, make a pastebin of your scripts, would be helpful.

Tf2-mate is a popular auto-cfg generator.

I would recommend it for helping you get started, but I don't recommend just blindly using some one-size-fits-all cfg that you don't have an understanding of.

I think everyone who plays competitive tf2 should have at least a basic understanding of scripts and cfgs etc. It will benefit you in the long run and you will be very happy knowing that you are able to look at a cfg and know exactly what you're looking at.

Here is the link to tf2 mate http://clugu.com/tf2mate/

I do not recommend using the graphic/fps config generated by tf2 mate. I don't trust it to be updated with the most recent versions and I just don't recommend it.

I would start off creating a reset system. A reset system is useful for when you use class-specific cfgs. Whenever you insert a script, bind, alias etc into a class.cfg - those commands are executed whenever you select the corresponding class while in game. The problem with using a class specific cfg, is that whatever is in that class cfg will "bleed" over into all other class cfgs. Technically it's just still active in your config.cfg so when you select a different class, those settings will still be active, whether you want them to be or not.

So what a reset system does, is whenever you select a class, it first executes a "reset" or "clear" file that re-binds and re-executes settings. This makes it possible to have class specific cfgs that don't overlap and conflict across different classes.

I actually think this is a great idea for someone wanting to get familiar with cfg's. I started my own cfg from scratch after using tf2 mate base reset/clear system. Here is a link to my own cfg, which has fairly detailed comments that explain what each section of the files are for.

https://dl.dropboxusercontent.com/u/43946806/cfg.zip

Feel free to download and use to your liking. I'll explain how the reset system works here:

There are four main files that comprise the reset system, they are

-Autoexec
-Aliases
-binds
-clear

Autoexec is my fps config, and at the bottom of the file, it executes my Aliases and Binds

The Aliases and Binds are my default settings that all my cfgs are based off of. I keep the aliases separate from the binds just to keep things neat and organized.

The clear cfg is nothing but a file that contains two lines - exec aliases and exec binds. At the beginning of every class cfg, there is the line "exec clear." So, everytime I select a class, it executes my base aliases and binds files, so everything starts clean, and whatever stuff I have in that class cfg doesn't overlap into other classes.

I hope that makes sense, and I apologize for writing a short novel. Good luck with learning everything. Feel free to add me on steam if you need some help.

But chris hasn't updated his configs in years. They still work.

That's what I mean, Chris' fps configs not being the most updated, and then tf2 mate just takes his configs and ports them through their generator. I would personally rather do it myself. Also, I think that the tf2mate generator has the option to mix and match settings from more than one fps config, and lump them all into a single autoexec that it creates for you. I just don't trust it. I could be paranoid but I'd rather just do all that myself.

nah thanks man, definitely a lot of comprehensive stuff here that makes scripting seem a little easier. I think i'll just try testing out making my own scripts and then using my current cfgs until I get scripting down.

Download my cfg and just check it out man, you'd be surprised at how easy it is to look through it and decipher everything. I spent a lot of time creating the comments in my cfgs specifically for the purpose of making it easy for someone to download them, and be able to read through them and not be confused at what they're looking at.

Something important I forgot to add: you should definitely download and start using notepad++ http://notepad-plus-plus.org/

It makes editing and using multiple files a breeze.