Think you mean "autoexec.cfg"

Works with pretty much every Quake / id Tech 3 engine (and many engines based on it), though sometimes the location of autoexec.cfg changes depending on how much the engine has been modified (some later games like Elite Forces 2 for example had extensive modifications).

It's also worth noting any commands you put into autoexec.cfg may end up being added to the default .cfg (configuration) files, meaning at that point even removing the autoexec.cfg those settings will still be applied because they're still present elsewhere in other .cfg files. In the case of Jedi Knight 2 I'd guess it may be adding them to jk2config.cfg, presuming I can still even remember the default filenames here.

I also remember instances where the commands from autoexec.cfg are added, and if you later edit commands/settings in autoexec.cfg those commands are added again and not altered in the default cfg files. Meaning you could for example end up with multiple entries each trying to set cg_fov to different values and obviously only one will be used.

Since mentioning cg_fov, sometimes setting it via something like the autoexec.cfg doesn't work, when that happens it's worth trying to instead bind the command to a key such as

bind F11 "cg_fov 110"

So when you press F11 it will change the fov to 110, so you don't have to use the console each time you start the game or go through a loading zone (or something else that resets the fov)