So as the mastercomfig framework has been updated along the years, I've always liked to customize it to my own ability, just barely using the customizations that the modules and stuff offers on the side seeing as they're limited for advanced use (beyond the average user type stuff...) Now over the years, I've seen the comfig go from using the user folder to overrides to app & overrides!? It's bound to be a few questions after a while, which is what I was curious about. What goes in app, and what goes in overrides? From where I stand right now, I have the class cfgs and the autoexec in app, and modules, pre_comfig and setup_hook in overrides. Am I missing any files and what does some pre and setup even do?
#What goes where @.@?
exotic edge
cobalt cobalt
There IS a page that explains this. But basically, app is for the stuff you customize on the website (crosshairs, binds), overrides is for your personal customizations.
So don't put anything of yours in app, because whenever you reinstall/update mastercomfig, it'll likely overwrite whatever's in app.
Your personal autoexec and class configs should be in overrides.
Technically you can't 'miss' any files. mastercomfig just tries to exec certain files at certain points IF you want to have them.
For instance:
pre_comfig.cfg gets executed at the very beginning, before the core of comfig is exec'd.
setup_hook.cfg is executed after comfig core, but before setting the preset/addons/modules etc.
So by including these files, you can run whatever you want at those points in the execution.
exotic edge
So, @cobalt cobalt where should I put my custom autoexec and class configs? Seems to me you want them in overrides ya? 
cobalt cobalt
yep
exotic edge
does listenservers.cfg go in cfg\app?
cobalt cobalt
overrides
exotic edge
which folder does setup_hook.cfg go in then @cobalt cobalt?
