Similar to other cfg's, there are multiple ways to install jarconfig. These are the main methods to install and their instructions.
Install jarconfig directly into the custom folder. This is the easiest and cleanest way.
- Download zip file
- Extract to tf2's custom folder
- Customize custom.cfg to suit your needs
Install jarconfig into the cfg folder and avoiding the custom folder. This can help with load times, but can be harder to maintain.
- Download zip file
- Make a backup of tf2's cfg folder
- Copy the contents of the zip file's cfg folder into tf2's cfg folder
- Customize custom.cfg to suit your needs
Custom.cfg contains the core of jarconfig, options for its scripts, an example setup, and space for custom options. It's recommended to put your own settings here, though you can exec another cfg that holds your own settings if you'd like.
It's not recommended to copy over your autoexec completely, since it may include binds or settings that would cause unpredictable problems with jarconfig. Instead, it's recommended to recreate your autoexec using your old one as a reference. This way you can make sure that you're getting full usage of jarconfig.
Jarconfig supports relatively simple integration with mastercomfig. It can be found here.
- Install mastercomfig as its instructions say, using any method.
- If mastercomfig was installed using the folders method, edit its autoexec.cfg to exec custom.cfg (this should be near the bottom of autoexec.cfg). If installed using vpk's, you don't have to do this step.
- Install jarconfig using the standard install method.
- Inside jarconfig, remove autoexec.cfg, the class cfg's, and listenserver.cfg. Keep the class_c cfg's and listenserver_c.cfg though.