Closed ClusterConsultant closed 4 years ago
It looks like errant was on an older version of the program. I didn't actually include the current version number in the tf2bd log (whoops lol) but right near the beginning we can see:
[18:00:00] GetLatestVersion(): version = 1.0.0.25, url = https://github.com/PazerOP/tf2_bot_detector/releases/tag/1.0.0.25
[18:00:00] GetLatestVersion(): version = 1.0.0.22, url = https://github.com/PazerOP/tf2_bot_detector/releases/tag/1.0.0.22
[18:00:00] GetLatestVersion(): break
That means he was running a version >= 1.0.0.22 but < 1.0.0.25. The self-marking issue was, to my knowledge, fixed in 1.0.0.25. He mentioned in discord that he was compiling from master, perhaps something went wrong on his end?
The version number will be printed to the log from 1.0.0.26 onward https://github.com/PazerOP/tf2_bot_detector/commit/571cdc34059f980d2cbd3f0a3bc2345976403bd8.
Probably good to close this then
Sounds good. Let me know if you find any further evidence that this is still an issue.
As seen in this debug report generated by user "errant" ([U:1:1492682]) they were marked as a cheater for full filling the rule (catbot) mygot. They said "myg0t.gg" in chat as part of an automated message telling the enemy team to kick a bot with "myg0t.gg" in its name. Relevant lines 274 in tf2bd.log and 590098 in console.log debug_report.zip