I've released a small update on Windows to fix a crash after the last update.

Update (4.75):
- Add support for mp_tournament_readymode 1

Update (4.74):
– Preset names are now allowed in tftrue_whitelist_id
– tftrue_whitelist is now deprecated and will be removed, please use tftrue_whitelist_id instead

Indeed, I looked how it works, and basically they block the changelevel command when you have both tv_delaymapchange and tv_delaymapchange_protect commands set to 1 and if the last end of round was more than tv_delay+3s ago.

Update (4.73):
- Fixed crash with logs
- Removed tftrue_tv_delaymapchange, you can now use tv_delaymapchange 1 which will prevent map changes if the STV hasn't finished broadcasting the end of the match

Update:

- Fixed the plugin not loading on Windows after the latest TF2 update

Is that related to TFTrue?

No, it will automatically update. You can just restart it to make sure it does.

Fixed changelevel being broken after latest update.

Update (4.71):
- Fixed weapon names sometimes being wrong for damage log lines
- Changed chat message to be reliable in case of packet loss

Valve developers that work on TF2 and others OB games decided that tickrate should be locked on 66 and there is no point to make it higher - which may be true in some way. It may not really improve anything, it may just be a placebo effect, or even, the things you notice and think they are "better" could just be the result of different recoil/spread timing or other things which make it "easier" to hit the opponent (like you aren't even actually supposed to hit him in the first place with the real recoil/spread).

Dota, L4D and L4D2 run at tickrate 30, I don't think that really makes hit registration worse. Many other non-Valve games also run their server tickrate (or actually FPS as they call it) with such low values (e.g. Quake).

They took a totally different route on CS GO, which is quite stupid in my opinion. Either block it or allow it on all games.

EDIT:
BTW TFTrue had a tickrate 100 option for a moment, which was tested, but it turns out there were too many issues, so I had to remove it.

You should not use anything else than 66tick on TF2, there are many parts of the game engine where calculations are based on tick 66, so this’ll fuck up a lot of things (e.g. weapon recoil or doors). That’s why the tickrate is locked to 66 in TF2.
You can even ask the guy who made the plugin, he will tell you the same, it's even written in red on the download page.

On CS GO Valve fixed all these tickrate issues, so it can be modified without any issues.

No, they are not in, but if UGC/ESEA want them to be added or anyone else, feel free to send a pull request on github :)

Update (4.70):
– Fixed crash with tftrue_bunnyhop

TFTrue is now open source and can be found here:
https://github.com/AnAkIn1/TFTrue

The source code lack comments in many places and the build system isn't perfect (need to edit the file to point to the SDK location), but I haven't have much time to fix this nowadays. Feel free to contribute :)

When someone will hack the servers using game exploits that were fixed years ago, and then download malicious files on every client that connect to the servers (or even delete windows files), I'm not sure people will keep playing this.