https://github.com/mastercomfig/team-comtress-2/releases/tag/0.2.0
Playtest on tf2.mastercomfig.com
| Account Details | |
|---|---|
| SteamID64 | 76561198046110893 |
| SteamID3 | [U:1:85845165] |
| SteamID32 | STEAM_0:1:42922582 |
| Country | United States |
| Signed Up | August 8, 2017 |
| Last Posted | December 12, 2025 at 10:29 AM |
| Posts | 1603 (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 | |
What's your bind for m1/m2? And does it happen in local servers and other games?
https://github.com/mastercomfig/team-comtress-2/releases/tag/0.1.4
We're doing a playtest today! connect tf2.mastercomfig.com
They won't travel farther if they go 30% slower. They'll go a shorter distance.
You can set random spin to be off through an attribute: grenade_no_spin. Spin would still be a problem with the iron bomber mesh if not disabled.
And on top of that, the grenade launcher has random spread that has nothing to do with vphysics.
If you keep up with the updates, there's less chance of breakage. Generally you'll want to update to the latest version as new versions come out.
Some updates will change how user settings are expected, but those are usually simple migrations. mastercomfig will never wipe any settings on its own.