| Account Details | |
|---|---|
| SteamID64 | 76561198185029021 |
| SteamID3 | [U:1:224763293] |
| SteamID32 | STEAM_0:1:112381646 |
| Country | Mongolia |
| Signed Up | September 10, 2016 |
| Last Posted | February 20, 2025 at 9:54 AM |
| Posts | 257 (0.1 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | 3.85 |
| Windows Sensitivity | 7/11 |
| Raw Input | 1 |
DPI |
400 |
Resolution |
1600x900 |
Refresh Rate |
60 |
| Hardware Peripherals | |
|---|---|
| Mouse | Logitech G102 |
| Keyboard | Defender Oscar SM-600 Pro |
| Mousepad | - |
| Headphones | Samsung Black Earplugs |
| Monitor | Laptop |
mastercomsThough it isn't going to expressly be a promod, I am working on https://mastercoms.itch.io/tc2 and hopefully it provides some degree of value to folks here
imo, this should be the base for promod
but the issue is that it is based on the 2018 leak
so the question is how hard it would be to transfer all of it to the new SDK
dw he permabanned me because i asked why he muted the comms when he was playing scrims with his team
he lost it for real
delete tf2attributes_example.smx and see what happens
i always wanted to find my friend's log where he got 1 dpm in the game, is it, or will it be possible?
lil script for that
sv_cheats 1
sv_allow_wait_command 1
bind "your bind" "mp_restartgame_immediate 1; wait 900; hurtme -170" ratawar.
big thanks, i'll check everything out!
hi, this guide https://wiki.alliedmods.net/Signature_scanning
is pretty outdated, links to BAILOPAN's devlogs are not valid, and also this guide describes an old method, i suspect the last years code leak could be used a lot.
so im wondering if there's some new guide to sigscanning or at least some additions to the old one.
ArieMost people didn't feel 133 tick was a huge improvement, so I expect 100 tick to be at least equally underwhelming. Also, the bugs you describe are the same as for the 133 tick experiment, so the other ones are probably also still there, which I expect to be a deal breaker for the competitive community and leagues.
tbh the only gamebreaking bug i have noticed on 133 is wrangled sentry shooting two times faster, but again i didn't encounter this bug in 100 tickrate.
but yeah, that would answer my questions, thank you.
ArieBugs, people didn't care and server load (especially highlander).
afair you didn't test 100 tick? is it going to be as hard for server to handle?
also as i said, bugs didn't appear on tickrate lower than 133, for example, i've tested some stuff on 100 tick, there were not so many bugs, except for increased strafing speed and bouncy pipes.
the only reason i created this thread is because no one really tested something below 133 tickrate, so i wonder why?
hi, i was wondering why did serveme and most of the servers stop using higher tickrates?
i couldn't really test it since i only have dedicated server on my laptop (you know, you can't really tell the difference when you play with 5 ping), so i wanted to know your opinion about higher tickrates!
also a small note: wrangled sentry does not shoot twice faster on tickrates lower than 133, which is (supposedly) confirmed by last years code leaks.
i had to build from source on VS2019 and now it's working
https://www.dropbox.com/s/vesh9djngnjizqy/tftrue.zip?dl=0
here it is!
(windows only)
stephlatest vers is broken for some reason, the latest one i have downloaded is 4.79 which is confirmed to work at least on linux -> https://sappho.io/files/tf/tftrue4_79.zip
stil the same error, but thanks anyways!
what's up, im getting this 301 error every time i boot my server up.
i got the last version from tftrue site https://tftrue.esport-tools.net/
what do
hosting it on windows 10 (testing it on my laptop basically lol)