Binds/Settings not saving. Help.

[jumpy.cfg]

Any bind or setting I change (For example, the color of the damage text or my explode bind) will only remain in effect for that session of tf2, as soon as I exit tf2 and start it again, my settings are just as they were a few days. This problem happened around a week ago, I can't create new settings without them just resetting. I've already tried changing my launch options, and I can't find anything in my cfg folder that may create conflict. Should I do something with my config or default config file? I've tried multiple methods and I still am having this problem.

[jumpy.cfg]

Originally posted by Syrup sandviches:

Put it in ur autoexec

Put what in autoexec?

[NW/RL]

Originally posted by (Random Kitchen Appliance):

Originally posted by Syrup sandviches:

Put it in ur autoexec

Put what in autoexec?

An autoexec.cfg is a file you create in your cfg folder in tf2. It allows you to store alias commands and binds. Most binds if bound to a specific command and not an alias don't go away after the tf2 session

[Rumpus]

Expanding on cfg's...

Go to common > team fortress 2 > tf > cfg

Duplicate a cfg, rename it autoexec.cfg

Open it with Notepad

Put in your binds and settings in like this:

example bind
example bind
example bind

[jumpy.cfg]

Originally posted by Mr.Pipe Jesus (Panface):

Originally posted by (Random Kitchen Appliance):

Put what in autoexec?

An autoexec.cfg is a file you create in your cfg folder in tf2. It allows you to store alias commands and binds. Most binds if bound to a specific command and not an alias don't go away after the tf2 session

Ok, so do I just put my cfg and default cfg in the autoexec.cfg and it's all good or do I have to edit the autoexec.cfg?

[Rumpus]

Originally posted by (Random Kitchen Appliance):

Originally posted by Mr.Pipe Jesus (Panface):

An autoexec.cfg is a file you create in your cfg folder in tf2. It allows you to store alias commands and binds. Most binds if bound to a specific command and not an alias don't go away after the tf2 session

Ok, so do I just put my cfg and default cfg in the autoexec.cfg and it's all good or do I have to edit the autoexec.cfg?

You have to edit the autoexec.

[NW/RL]

Originally posted by (Random Kitchen Appliance):

Originally posted by Mr.Pipe Jesus (Panface):

An autoexec.cfg is a file you create in your cfg folder in tf2. It allows you to store alias commands and binds. Most binds if bound to a specific command and not an alias don't go away after the tf2 session

Ok, so do I just put my cfg and default cfg in the autoexec.cfg and it's all good or do I have to edit the autoexec.cfg?

If you currently have an autoexec.cfg file you can edit it with the bind commands. But one problem is that it might not already exist if you haven't created one. It doesn't come w/ tf2

[jumpy.cfg]

Originally posted by Rumpus:

Originally posted by (Random Kitchen Appliance):

Ok, so do I just put my cfg and default cfg in the autoexec.cfg and it's all good or do I have to edit the autoexec.cfg?

You have to edit the autoexec.

So if I want to create a new bind or change a setting I have to edit my autoexec?

[Rumpus]

Originally posted by (Random Kitchen Appliance):

Originally posted by Rumpus:

You have to edit the autoexec.

So if I want to create a new bind or change a setting I have to edit my autoexec?

Yes.

[NW/RL]

Originally posted by Rumpus:

Originally posted by (Random Kitchen Appliance):

So if I want to create a new bind or change a setting I have to edit my autoexec?

Yes.

If you already have one

[jumpy.cfg]

Originally posted by Rumpus:

Originally posted by (Random Kitchen Appliance):

So if I want to create a new bind or change a setting I have to edit my autoexec?

Yes.

That sucks

[NW/RL]

Originally posted by (Random Kitchen Appliance):

Originally posted by Rumpus:

Yes.

That sucks

Do you have one!?

[timmy1366]

same problem my mouse wheel was already good for bhopping until binds are not saved (already in autoexec and not working)

[Ludicrous Silence]

also i'd rather put it in binds.cfg rather then autoexec.