It would be helpful to provide your autoexec.cfg file, also make sure that it's located in the \baseq2 folder.
Quote from: Elysium on March 27, 2013, 03:29:37 PMIt would be helpful to provide your autoexec.cfg file, also make sure that it's located in the \baseq2 folder. It's in my baseq2 folder, I'm also using the q2kicker client. Its just everytime I do the command *goto somewhere* my config unexecs. Even when I have a autoexec.
Quote from: Electfried on March 28, 2013, 04:44:09 PMQuote from: Elysium on March 27, 2013, 03:29:37 PMIt would be helpful to provide your autoexec.cfg file, also make sure that it's located in the \baseq2 folder. It's in my baseq2 folder, I'm also using the q2kicker client. Its just everytime I do the command *goto somewhere* my config unexecs. Even when I have a autoexec. For extra measures, and to prevent this from ever happening again, copy your autoexec and paste it in each of the mods you play folders. I have my autoexec in my baseq2 folder along with the arena/tourney/opentdm/osp/bball/qpong/rails/jump/expertctf/ctf folders, that way I can also edit my config to each of the mods I play to better suit my play style to each mod with their different binds/features etc. In arena(or RA2) in my autoexec in that folder I use for example: bind mwheelup say_team "enemy LOW --[ $$loc_there ]-- CHAIN!"bind mwheeldown say_team "enemy RAILED 80/20 --[ $$loc_there !!]--"Whereas in my CTF autoexec, those two keys are bound to do completely different things:bind mwheelup "use grapple"bind mwheeldown say_team "TECH SWAP (for a sec)?? <%t>"Just put your autoexec in each mods folder in your quake2 dir. Problem solved.