Config assistance, using mastercomfig but I need help with class configs

[velvet locust]

I have a pretty basic knowledge of making binds and scripts within the source engine, but I'm new to the TF2 side of the console, as well as how to use mastercomfig to it's full potential. I've gotten my class config's to work, but somewhere along the line, I messed stuff up. I deleted my /cfg folder and have the backed up .cfg files for my classes and scripts and such, but it's all put together from multiple sources such as random configs and scripts from the internet, and stuff from cfg.tf, and I'm tired of troubleshooting all my current problems 😅

I'm very familiar with counter strike, even current source 2 configs, and I'm used to changing all my settings from within a config if need be, so I'm not worried about it getting to complicated, I just need help getting on the right track. Any assistance, or guidance to documentation, is much appreciated.

The image attached is the structure I'm currently working with, and I'm not sure where to put it, inside the /cfg folder, the /overrides folder, or I even had an /app folder at some point, the _lang.cfg, _reset.cfg, and _settings.cfg, are all taken from another config I found online that seemed helpful at the time, but i would now like to figure out how to migrate only some of the stuff that config provides, and trim down the contents a little.

My main focus is getting only the bare essentials for a similar structure of config, and basically getting my class configs situated, Mastercomfig does a great job at taking care of all the core systems of the game for me, But I would like to be able to use the TF2 console in a similar way as is done in Counter strike now days.

[little pasture]

the only things that need to go in the overrides folder are class configs, autoexec, modules, and game_overrides. the rest of your cfgs (the ones starting with _) go in the regular cfg folder

although otherwise i'm a bit confused with what exactly you're trying to do?

but the general run down of how mastercomfig (sort of) differs from standard source engine console stuff is that it has its own set of files (class config, autoexec, etc.) that need to be run for it to work, and they're placed at the path of tf/cfg (technically, its in that path but inside the vpk you download)
Since the game only supports one thing at one specific path, our workaround for running user configuration files is to have the ones inside mastercomfig also execute the same files from 2 other folders:
tf/cfg/overrides For user specific stuff
tf/cfg/app For customizations you made on the website (so it doesn't overwrite your user specific stuff)

Additionally, we do have documentation as well, which also includes a list of every single console command in the game (ripped straight from the game so anything that is undocumented there is also undocumented here)
https://docs.comfig.app/latest/