| Account Details | |
|---|---|
| SteamID64 | 76561198046110893 |
| SteamID3 | [U:1:85845165] |
| SteamID32 | STEAM_0:1:42922582 |
| Country | United States |
| Signed Up | August 8, 2017 |
| Last Posted | December 9, 2025 at 8:27 PM |
| Posts | 1601 (0.5 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | |
| Windows Sensitivity | |
| Raw Input | 1 |
DPI |
|
Resolution |
|
Refresh Rate |
|
| Hardware Peripherals | |
|---|---|
| Mouse | |
| Keyboard | |
| Mousepad | |
| Headphones | |
| Monitor | |
AimIsADickIt's just as I feared the answer would be: The order of commands is up to preference. I'm just not good at personal preference decisions, and can't decide on any of them. Still this is a nice question to ask, as I couldn't find any other posts here or on r/tf2scripts asking the same question.
You can randomly order your scripts. Let fate decide.
9.5.0 released with app updates and config enhancements.
This release took 7 hours to produce. If you like the work I do, consider supporting me!
Order doesn't matter since at usage time, everything you set will be there. For aliases, aliases are looked up when the alias is executed, so you can bind even before defining an alias. The cmdline is just strings when you assign values, aliases, binds, etc. For convars, an exec will run synchronously to the main thread of the game, so there is no race condition when changing multiple values.
If you are concerned about material system convars with the material system thread, those are "uploaded" to the material system after an exec in complete, so same thing there. And keep in mind that at initialization, TF2 runs the material system synchronously anyway, so autoexecs are safe either way. The threaded material system is only started after you join a game (or the frame after you set mat_queue_mode 2).
As for commands, they will obviously execute in order as you put them, but there is no general practice for ordering these, since there are possibly hundreds of commands with their own functionality, and you will have to determine the correct ordering for your intention on a case by case basis.
9.4.0 released with networking improvements, bug fixes and download page updates.
This release took 10 hours to produce. If you like the work I do, consider supporting me!
Oops! Forgot about that, thanks for catching it. It's fixed now.
Hey all, I refreshed the download experience with a style update, layout changes, and a version selector + update checker. Please let me know what you think! There will be some more updates coming soon to help further with more advanced customization.
No love for the homie DirectX 8.0
Just for future reference: https://docs.mastercomfig.com/en/latest/customization/custom_configs/#game-overrides
9.3.3 released with performance optimizations, bug fixes, and new utility features.
This release took 3 hours to produce. If you like the work I do, consider supporting me!
9.3.2 released with bug fixes.
This release took 2 hours to produce. If you like the work I do, consider supporting me!
9.3.1 released with performance improvements and bug fixes.
This release took 10 hours to produce. If you like the work I do, consider supporting me!
That it segfaulted is pretty useless information, it technically narrows it down a bit, but you might as well anyway be saying it crashed. Seeing stdout is not what a debugger is used for. You can do that in other ways.
What a debugger is actually used for is breaking into the code, viewing variables and the stack, and in some cases, rewind in the case of time travel debugging with something like rr or WinDbg. However, as was said before to you, since you do not have debug information, it will be very hard to debug the program without very good experience with programming and especially assembly.
Also, I think in these cases, you will find Valgrind more helpful than simply using gdb.
KZIdk why i get awful stutters on mastercomfig after a couple of launches, but if i reinstall (delete cache etc.) it it would run smooth.
That's strange, could you list everything you do explicitly to reinstall?
Yeah, stuffcmds doesn't work for non game DLL cvars anymore.
Anyways, RSS feed, you can use GitHub afaik
turbochad69try disabling any ofif you have them enabled (and stop w/ the debugger meme)r_threaded_renderables r_queued_decals r_queued_post_processing cl_threaded_client_leaf_system cl_threaded_bone_setup
Only the r_queued cvars do anything in the current live build, so changing the values of any of the other ones would not do anything. Plus, mastercomfig does not set any of these, so if the only thing they did was update to the latest version, these would not change anything.