I... I don't even know where to start with addressing it.
So not to discourage you or other players, I'll wish you good luck with this project.
Cheater/Hacker thread
posted in
TF2 General Discussion
I... I don't even know where to start with addressing it.
So not to discourage you or other players, I'll wish you good luck with this project.
So not to discourage you or other players, I'll wish you good luck with this project.
Indeed, the magnitude of such a project (especially if it's on a purely volunteer basis, which it appears to be) is a bit unwieldy.
It's possible, but unless you're getting very experienced people who are versed in both working with the Source Engine as well as detecting cheats, it's going to be extremely difficult.
Indeed, the magnitude of such a project (especially if it's on a purely volunteer basis, which it appears to be) is a bit unwieldy.
It's possible, but unless you're getting very experienced people who are versed in both working with the Source Engine as well as detecting cheats, it's going to be extremely difficult.
It's possible, but unless you're getting very experienced people who are versed in both working with the Source Engine as well as detecting cheats, it's going to be extremely difficult.
Ya that's me. I've been writing my client / reversing the sdk since January. I have no intentions of using my client to win competitive TF2 or any game. I do it to learn.
DoctorMiggyIn case any programmers here are interested in actually doing something to help catch these guys:
https://forums.alliedmods.net/showthread.php?p=2280611#post2280611
This may take a bit to explain, I'm almost pretty sure this wouldn't go under "SourceMods" but I was not sure where to post it.
Cheating has been ongoing in UGC, ETF2L, and ESEA for a good while and there will always be cheaters until the day this game dies out. ESEA has a client side executable that acts like a little punkbuster but there have been guys who've been able to circumvent it. UGC and ETF2L have nothing but an AntiCheat team to review demos. (If I'm not mistaken ETF2L players do have the option of having ANAKKKs anticheat plugin on their servers but it is not widely used sadly; UGC still has nothing).
My idea is to make a client side tool to assist anticheat teams in catching these cheaters. (This is for use for the AC teams, players will not need this).
The way I had the idea in my head is that there are Client Side TF2 Plugins out there (PREC, OpenPlugin), Why make one that scans over .dem files and bookmarks ticktimes of suspicious activity sort of the way SMAC or Anakkks AntiCheat (I'll refer it to AAC for now) displays a flag in chat when there is suspicious activity?
Imagine how much easier it would be for AC teams to run a demo with this plugin enabled at 600% speed and then get a nice text file of bookmarks of possible aimbotting or esp. Then with these ticktimes in hand the AC team knows exactly where to look if they feel the need to do a further review of the demo? Doing that as opposed to watching hour long demos repeatedly to ensure they didn't miss a thing would be very beneficial to either leagues review teams.
I've spoken to a few guys who code SourceMod plugins and even talked to PREC messiah Orange who all tell me it's possible but I have little to no knowledge on how to code anything except HTML. I guess what I'm saying is, is there any folks interested in turning this into a group project that would benefit the Comp community?
If you want to discuss on steam please feel free to add me:
http://steamcommunity.com/id/migeto
I'm interested in this. The wiki states that .dem files store raw packets to recreate a game. It's weird because I'd expect a .dem file to be a history array indexed by tick or frame from the server's perspective. I've never written a plugin, and I don't know which SourceMod plugins you're referring to. If you link them I can take a look to see how they could be implemented / recreated. You could probably just write a .dem parser to avoid working with a plugin.
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer. Bots are either going to target various bones ( 3d point ) or the center of a hitbox ( also a 3d point ). You can do various checks like seeing if a player sent an IN_ATTACK command as soon as their view angle pointed at the center of an enemy's head / torso. For ESP you could run two tracers; one which ignores walls and one which doesn't.
I can also help test how accurate the plugin / parser is :P
Hopefully we can all still be m8s. I'm a nice guy :P
Ya that's me. I've been writing my client / reversing the sdk since January. I have no intentions of using my client to win competitive TF2 or any game. I do it to learn.
[quote=DoctorMiggy]In case any programmers here are interested in actually doing something to help catch these guys:
https://forums.alliedmods.net/showthread.php?p=2280611#post2280611
[quote]This may take a bit to explain, I'm almost pretty sure this wouldn't go under "SourceMods" but I was not sure where to post it.
Cheating has been ongoing in UGC, ETF2L, and ESEA for a good while and there will always be cheaters until the day this game dies out. ESEA has a client side executable that acts like a little punkbuster but there have been guys who've been able to circumvent it. UGC and ETF2L have nothing but an AntiCheat team to review demos. (If I'm not mistaken ETF2L players do have the option of having ANAKKKs anticheat plugin on their servers but it is not widely used sadly; UGC still has nothing).
My idea is to make a client side tool to assist anticheat teams in catching these cheaters. (This is for use for the AC teams, players will not need this).
The way I had the idea in my head is that there are Client Side TF2 Plugins out there (PREC, OpenPlugin), Why make one that scans over .dem files and bookmarks ticktimes of suspicious activity sort of the way SMAC or Anakkks AntiCheat (I'll refer it to AAC for now) displays a flag in chat when there is suspicious activity?
Imagine how much easier it would be for AC teams to run a demo with this plugin enabled at 600% speed and then get a nice text file of bookmarks of possible aimbotting or esp. Then with these ticktimes in hand the AC team knows exactly where to look if they feel the need to do a further review of the demo? Doing that as opposed to watching hour long demos repeatedly to ensure they didn't miss a thing would be very beneficial to either leagues review teams.
I've spoken to a few guys who code SourceMod plugins and even talked to PREC messiah Orange who all tell me it's possible but I have little to no knowledge on how to code anything except HTML. I guess what I'm saying is, is there any folks interested in turning this into a group project that would benefit the Comp community?
If you want to discuss on steam please feel free to add me:
http://steamcommunity.com/id/migeto[/quote][/quote]
I'm interested in this. The wiki states that .dem files store raw packets to recreate a game. It's weird because I'd expect a .dem file to be a history array indexed by tick or frame from the server's perspective. I've never written a plugin, and I don't know which SourceMod plugins you're referring to. If you link them I can take a look to see how they could be implemented / recreated. You could probably just write a .dem parser to avoid working with a plugin.
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer. Bots are either going to target various bones ( 3d point ) or the center of a hitbox ( also a 3d point ). You can do various checks like seeing if a player sent an IN_ATTACK command as soon as their view angle pointed at the center of an enemy's head / torso. For ESP you could run two tracers; one which ignores walls and one which doesn't.
I can also help test how accurate the plugin / parser is :P
Hopefully we can all still be m8s. I'm a nice guy :P
[quote=DoctorMiggy]In case any programmers here are interested in actually doing something to help catch these guys:
https://forums.alliedmods.net/showthread.php?p=2280611#post2280611
[quote]This may take a bit to explain, I'm almost pretty sure this wouldn't go under "SourceMods" but I was not sure where to post it.
Cheating has been ongoing in UGC, ETF2L, and ESEA for a good while and there will always be cheaters until the day this game dies out. ESEA has a client side executable that acts like a little punkbuster but there have been guys who've been able to circumvent it. UGC and ETF2L have nothing but an AntiCheat team to review demos. (If I'm not mistaken ETF2L players do have the option of having ANAKKKs anticheat plugin on their servers but it is not widely used sadly; UGC still has nothing).
My idea is to make a client side tool to assist anticheat teams in catching these cheaters. (This is for use for the AC teams, players will not need this).
The way I had the idea in my head is that there are Client Side TF2 Plugins out there (PREC, OpenPlugin), Why make one that scans over .dem files and bookmarks ticktimes of suspicious activity sort of the way SMAC or Anakkks AntiCheat (I'll refer it to AAC for now) displays a flag in chat when there is suspicious activity?
Imagine how much easier it would be for AC teams to run a demo with this plugin enabled at 600% speed and then get a nice text file of bookmarks of possible aimbotting or esp. Then with these ticktimes in hand the AC team knows exactly where to look if they feel the need to do a further review of the demo? Doing that as opposed to watching hour long demos repeatedly to ensure they didn't miss a thing would be very beneficial to either leagues review teams.
I've spoken to a few guys who code SourceMod plugins and even talked to PREC messiah Orange who all tell me it's possible but I have little to no knowledge on how to code anything except HTML. I guess what I'm saying is, is there any folks interested in turning this into a group project that would benefit the Comp community?
If you want to discuss on steam please feel free to add me:
http://steamcommunity.com/id/migeto[/quote][/quote]
I'm interested in this. The wiki states that .dem files store raw packets to recreate a game. It's weird because I'd expect a .dem file to be a history array indexed by tick or frame from the server's perspective. I've never written a plugin, and I don't know which SourceMod plugins you're referring to. If you link them I can take a look to see how they could be implemented / recreated. You could probably just write a .dem parser to avoid working with a plugin.
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer. Bots are either going to target various bones ( 3d point ) or the center of a hitbox ( also a 3d point ). You can do various checks like seeing if a player sent an IN_ATTACK command as soon as their view angle pointed at the center of an enemy's head / torso. For ESP you could run two tracers; one which ignores walls and one which doesn't.
I can also help test how accurate the plugin / parser is :P
Hopefully we can all still be m8s. I'm a nice guy :P
chambsYa that's me. I've been writing my client / reversing the sdk since January. I have no intentions of using my client to win competitive TF2 or any game. I do it to learn.
so what does this mean? youve been making your own cheats to see if you could?
[quote=chambs]Ya that's me. I've been writing my client / reversing the sdk since January. I have no intentions of using my client to win competitive TF2 or any game. I do it to learn. [/quote]
so what does this mean? youve been making your own cheats to see if you could?
so what does this mean? youve been making your own cheats to see if you could?
THEBILLDOZERchambsYa that's me. I've been writing my client / reversing the sdk since January. I have no intentions of using my client to win competitive TF2 or any game. I do it to learn.so what does this mean? youve been making your own cheats to see if you could?
Yes. The programming involved with writing a private client is very interesting to me. This isn't something I downloaded.
[quote=THEBILLDOZER][quote=chambs]Ya that's me. I've been writing my client / reversing the sdk since January. I have no intentions of using my client to win competitive TF2 or any game. I do it to learn. [/quote]
so what does this mean? youve been making your own cheats to see if you could?[/quote]
Yes. The programming involved with writing a private client is very interesting to me. This isn't something I downloaded.
so what does this mean? youve been making your own cheats to see if you could?[/quote]
Yes. The programming involved with writing a private client is very interesting to me. This isn't something I downloaded.
chambsTHEBILLDOZERYes. The programming involved with writing a private client is very interesting to me. This isn't something I downloaded.chambsYa that's me. I've been writing my client / reversing the sdk since January. I have no intentions of using my client to win competitive TF2 or any game. I do it to learn.so what does this mean? youve been making your own cheats to see if you could?
The fact that you wrote it yourself doesn't make it ok to go into a DM server (where people go to try to practice) and hack
[quote=chambs][quote=THEBILLDOZER][quote=chambs]Ya that's me. I've been writing my client / reversing the sdk since January. I have no intentions of using my client to win competitive TF2 or any game. I do it to learn. [/quote]
so what does this mean? youve been making your own cheats to see if you could?[/quote]
Yes. The programming involved with writing a private client is very interesting to me. This isn't something I downloaded.[/quote]
The fact that you wrote it yourself doesn't make it ok to go into a DM server (where people go to try to practice) and hack
so what does this mean? youve been making your own cheats to see if you could?[/quote]
Yes. The programming involved with writing a private client is very interesting to me. This isn't something I downloaded.[/quote]
The fact that you wrote it yourself doesn't make it ok to go into a DM server (where people go to try to practice) and hack
chambsI'm interested in this. The wiki states that .dem files store raw packets to recreate a game. It's weird because I'd expect a .dem file to be a history array indexed by tick or frame from the server's perspective. I've never written a plugin, and I don't know which SourceMod plugins you're referring to. If you link them I can take a look to see how they could be implemented / recreated. You could probably just write a .dem parser to avoid working with a plugin.
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer. Bots are either going to target various bones ( 3d point ) or the center of a hitbox ( also a 3d point ). You can do various checks like seeing if a player sent an IN_ATTACK command as soon as their view angle pointed at the center of an enemy's head / torso. For ESP you could run two tracers; one which ignores walls and one which doesn't.
I can also help test how accurate the plugin / parser is :P
Hopefully we can all still be m8s. I'm a nice guy :P
http://etf2l.org/forum/general/topic-21038/page-1/
SMAC is no longer on AlliedModders page due to someone sending a DMCA (what a dick) But the one linked is just as good.
SMAC can still be found on various sites
[quote=chambs]
I'm interested in this. The wiki states that .dem files store raw packets to recreate a game. It's weird because I'd expect a .dem file to be a history array indexed by tick or frame from the server's perspective. I've never written a plugin, and I don't know which SourceMod plugins you're referring to. If you link them I can take a look to see how they could be implemented / recreated. You could probably just write a .dem parser to avoid working with a plugin.
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer. Bots are either going to target various bones ( 3d point ) or the center of a hitbox ( also a 3d point ). You can do various checks like seeing if a player sent an IN_ATTACK command as soon as their view angle pointed at the center of an enemy's head / torso. For ESP you could run two tracers; one which ignores walls and one which doesn't.
I can also help test how accurate the plugin / parser is :P
Hopefully we can all still be m8s. I'm a nice guy :P[/quote]
http://etf2l.org/forum/general/topic-21038/page-1/
SMAC is no longer on AlliedModders page due to someone sending a DMCA (what a dick) But the one linked is just as good.
SMAC can still be found on various sites
I'm interested in this. The wiki states that .dem files store raw packets to recreate a game. It's weird because I'd expect a .dem file to be a history array indexed by tick or frame from the server's perspective. I've never written a plugin, and I don't know which SourceMod plugins you're referring to. If you link them I can take a look to see how they could be implemented / recreated. You could probably just write a .dem parser to avoid working with a plugin.
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer. Bots are either going to target various bones ( 3d point ) or the center of a hitbox ( also a 3d point ). You can do various checks like seeing if a player sent an IN_ATTACK command as soon as their view angle pointed at the center of an enemy's head / torso. For ESP you could run two tracers; one which ignores walls and one which doesn't.
I can also help test how accurate the plugin / parser is :P
Hopefully we can all still be m8s. I'm a nice guy :P[/quote]
http://etf2l.org/forum/general/topic-21038/page-1/
SMAC is no longer on AlliedModders page due to someone sending a DMCA (what a dick) But the one linked is just as good.
SMAC can still be found on various sites
I looked at his AC. It's just a dll; no source. It would be hard to get anything useful from this unless we decompiled it. I think speedhack is patched. Checking for modified viewangles sounds good since any aimbot will call engine SetViewAngles.
Are you wanting to make a plugin that works while a match is being played, or do you want to make a post-game analysis tool that will scan player demos / STVs?
I looked at his AC. It's just a dll; no source. It would be hard to get anything useful from this unless we decompiled it. I think speedhack is patched. Checking for modified viewangles sounds good since any aimbot will call engine SetViewAngles.
Are you wanting to make a plugin that works while a match is being played, or do you want to make a post-game analysis tool that will scan player demos / STVs?
Are you wanting to make a plugin that works while a match is being played, or do you want to make a post-game analysis tool that will scan player demos / STVs?
Post Analysis that scans demos/stvs.
Using a live plugin like anakkks or smac would be perfect if ugc didnt have a policy against plugins running during the match :-l
Post Analysis that scans demos/stvs.
Using a live plugin like anakkks or smac would be perfect if ugc didnt have a policy against plugins running during the match :-l
Using a live plugin like anakkks or smac would be perfect if ugc didnt have a policy against plugins running during the match :-l
DoctorMiggyPost Analysis that scans demos/stvs.
Using a live plugin like anakkks or smac would be perfect if ugc didnt have a policy against plugins running during the match :-l
UGC allows plugins that don't interfere with gameplay.
http://www.ugcleague.com/rules_tf2h.cfm#section4
3.3b Mods - Manimod, Sourcemod, AMX Mod and AMXX Mod and the like are allowed as long as they do not interfere with the match. A csay command here and there will be tolerated, as long as it was in the admin mod config and is not insulting to anybody. Admin mods may only be used for setting the config, checking the amount of time left, and changing maps. Please disable all plugins that could affect any aspect of the match, including Donator plugins. If any player from the opposing team (the Visiting team) is kicked, banned or moved to Spectator during a match for any reason due to any installed mod, the hosting team will forfeit all points earned during the round, unless the Visiting team agrees otherwise. Let this be an incentive to either not run admin mods or to disable the plugins.
Running AnAkIn Anticheat (AnAkk's) with aac_prediction_ban, aac_speedhackbypass_ban, and aac_viewangles_ban set to 0 will make the plugin comply with UGC rules.
[quote=DoctorMiggy]Post Analysis that scans demos/stvs.
Using a live plugin like anakkks or smac would be perfect if ugc didnt have a policy against plugins running during the match :-l[/quote]
UGC allows plugins that don't interfere with gameplay.
http://www.ugcleague.com/rules_tf2h.cfm#section4
[quote][b]3.3b Mods - [/b]Manimod, Sourcemod, AMX Mod and AMXX Mod and the like are allowed as long as they do not interfere with the match. A csay command here and there will be tolerated, as long as it was in the admin mod config and is not insulting to anybody. Admin mods may only be used for setting the config, checking the amount of time left, and changing maps. Please disable all plugins that could affect any aspect of the match, including Donator plugins. If any player from the opposing team (the Visiting team) is kicked, banned or moved to Spectator during a match for any reason due to any installed mod, the hosting team will forfeit all points earned during the round, unless the Visiting team agrees otherwise. Let this be an incentive to either not run admin mods or to disable the plugins.[/quote]
Running AnAkIn Anticheat (AnAkk's) with aac_prediction_ban, aac_speedhackbypass_ban, and aac_viewangles_ban set to 0 will make the plugin comply with UGC rules.
Using a live plugin like anakkks or smac would be perfect if ugc didnt have a policy against plugins running during the match :-l[/quote]
UGC allows plugins that don't interfere with gameplay.
http://www.ugcleague.com/rules_tf2h.cfm#section4
[quote][b]3.3b Mods - [/b]Manimod, Sourcemod, AMX Mod and AMXX Mod and the like are allowed as long as they do not interfere with the match. A csay command here and there will be tolerated, as long as it was in the admin mod config and is not insulting to anybody. Admin mods may only be used for setting the config, checking the amount of time left, and changing maps. Please disable all plugins that could affect any aspect of the match, including Donator plugins. If any player from the opposing team (the Visiting team) is kicked, banned or moved to Spectator during a match for any reason due to any installed mod, the hosting team will forfeit all points earned during the round, unless the Visiting team agrees otherwise. Let this be an incentive to either not run admin mods or to disable the plugins.[/quote]
Running AnAkIn Anticheat (AnAkk's) with aac_prediction_ban, aac_speedhackbypass_ban, and aac_viewangles_ban set to 0 will make the plugin comply with UGC rules.
Couldn't they also use SetCursorPos to move the mouse cursor instead of using wpm for SetViewAngles? Not too familiar with the SDK functions.
Couldn't they also use SetCursorPos to move the mouse cursor instead of using wpm for SetViewAngles? Not too familiar with the SDK functions.
yeah those are used in external clients. I've never tried one, but I'm sure the end result is the same.
yeah those are used in external clients. I've never tried one, but I'm sure the end result is the same.
cheating in dm thats cute, i'd put money on it that you would still be doing it but since you got caught now its all good right
cheating in dm thats cute, i'd put money on it that you would still be doing it but since you got caught now its all good right
Have to at least have a basic understanding of cheats and how they work to create something to catch cheaters. Still was a bad idea to cheat in DM though.
Have to at least have a basic understanding of cheats and how they work to create something to catch cheaters. Still was a bad idea to cheat in DM though.
don't worry this community supports cheaters, once you admit to it all is forgotten. hell we even sent one to lan !
don't worry this community supports cheaters, once you admit to it all is forgotten. hell we even sent one to lan !
defydon't worry this community supports cheaters, once you admit to it all is forgotten. hell we even sent one to lan !t
Who is the mysterious player? :O
[quote=defy]don't worry this community supports cheaters, once you admit to it all is forgotten. hell we even sent one to lan !t[/quote]
Who is the mysterious player? :O
Who is the mysterious player? :O
chambsI'm interested in this. The wiki states that .dem files store raw packets to recreate a game. ...
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer
IIRC the dem files store network data that allows the client to re-run the game from the data it originally consumed. To do this outside TF2 I think you'd need to basically recreate TF2 to parse the .dem files and recreate the game situations. If my understanding of the dem file contents (not my area of expertise but I have read the relevant SDK bits) and what you're suggesting is correct that approach must be infeasible really.
In terms of creating something like this publicly you're just making it harder to catch cheaters long term because cheat writers will simply modify their hack to evade detection then put it in their marketing material - "Guaranteed chambs anti-cheat detection proof". A serious cheat detector should be made in private and in collaboration with anti-cheat teams.
[quote=chambs]I'm interested in this. The wiki states that .dem files store raw packets to recreate a game. ...
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer[/quote]
IIRC the dem files store network data that allows the client to re-run the game from the data it originally consumed. To do this outside TF2 I think you'd need to basically recreate TF2 to parse the .dem files and recreate the game situations. If my understanding of the dem file contents (not my area of expertise but I have read the relevant SDK bits) and what you're suggesting is correct that approach must be infeasible really.
In terms of creating something like this publicly you're just making it harder to catch cheaters long term because cheat writers will simply modify their hack to evade detection then put it in their marketing material - "Guaranteed chambs anti-cheat detection proof". A serious cheat detector should be made in private and in collaboration with anti-cheat teams.
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer[/quote]
IIRC the dem files store network data that allows the client to re-run the game from the data it originally consumed. To do this outside TF2 I think you'd need to basically recreate TF2 to parse the .dem files and recreate the game situations. If my understanding of the dem file contents (not my area of expertise but I have read the relevant SDK bits) and what you're suggesting is correct that approach must be infeasible really.
In terms of creating something like this publicly you're just making it harder to catch cheaters long term because cheat writers will simply modify their hack to evade detection then put it in their marketing material - "Guaranteed chambs anti-cheat detection proof". A serious cheat detector should be made in private and in collaboration with anti-cheat teams.
[quote=CHERRY]Who is the mysterious player? :O[/quote]
[spoiler][img]http://oi40.tinypic.com/12512qh.jpg[/img][/spoiler]
[spoiler][img]http://oi40.tinypic.com/12512qh.jpg[/img][/spoiler]
GentlemanJonchambsI'm interested in this. The wiki states that .dem files store raw packets to recreate a game. ...IIRC the dem files store network data that allows the client to re-run the game from the data it originally consumed. To do this outside TF2 I think you'd need to basically recreate TF2 to parse the .dem files and recreate the game situations. If my understanding of the dem file contents (not my area of expertise but I have read the relevant SDK bits) and what you're suggesting is correct that approach must be infeasible really.
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer
In terms of creating something like this publicly you're just making it harder to catch cheaters long term because cheat writers will simply modify their hack to evade detection then put it in their marketing material - "Guaranteed chambs anti-cheat detection proof". A serious cheat detector should be made in private and in collaboration with anti-cheat teams.
This is a good point. Miggy you should probably look to use the AC you posted with the settings posted by yttrium.
[quote=GentlemanJon][quote=chambs]I'm interested in this. The wiki states that .dem files store raw packets to recreate a game. ...
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer[/quote]
IIRC the dem files store network data that allows the client to re-run the game from the data it originally consumed. To do this outside TF2 I think you'd need to basically recreate TF2 to parse the .dem files and recreate the game situations. If my understanding of the dem file contents (not my area of expertise but I have read the relevant SDK bits) and what you're suggesting is correct that approach must be infeasible really.
In terms of creating something like this publicly you're just making it harder to catch cheaters long term because cheat writers will simply modify their hack to evade detection then put it in their marketing material - "Guaranteed chambs anti-cheat detection proof". A serious cheat detector should be made in private and in collaboration with anti-cheat teams.[/quote]
This is a good point. Miggy you should probably look to use the AC you posted with the settings posted by yttrium.
Either way, my idea is to iterate over every tick, and at each tick loop through every player storing a traceray from their view angles in a history buffer[/quote]
IIRC the dem files store network data that allows the client to re-run the game from the data it originally consumed. To do this outside TF2 I think you'd need to basically recreate TF2 to parse the .dem files and recreate the game situations. If my understanding of the dem file contents (not my area of expertise but I have read the relevant SDK bits) and what you're suggesting is correct that approach must be infeasible really.
In terms of creating something like this publicly you're just making it harder to catch cheaters long term because cheat writers will simply modify their hack to evade detection then put it in their marketing material - "Guaranteed chambs anti-cheat detection proof". A serious cheat detector should be made in private and in collaboration with anti-cheat teams.[/quote]
This is a good point. Miggy you should probably look to use the AC you posted with the settings posted by yttrium.
chambsam i witnessing a breakdown
no just stating facts here, but i like how you dodged my first comment
if enigma never posted that you would 100% still be cheating and thats just fucking dumb plain and simple
[quote=chambs]am i witnessing a breakdown[/quote]
no just stating facts here, but i like how you dodged my first comment
if enigma never posted that you would 100% still be cheating and thats just fucking dumb plain and simple
no just stating facts here, but i like how you dodged my first comment
if enigma never posted that you would 100% still be cheating and thats just fucking dumb plain and simple
edit: oops i thought you said question
yeah I'm going to keep doing it regardless. I have no problem admitting it. ¯\(°_o)/¯
edit: oops i thought you said question
yeah I'm going to keep doing it regardless. I have no problem admitting it. ¯\(°_o)/¯
yeah I'm going to keep doing it regardless. I have no problem admitting it. ¯\(°_o)/¯
chambswhere's the question
i'd put money on it that you would still be doing it but since you got caught now its all good right
so is it all good man or what? i know you're playing dumb but this is fun
you came back to tf2 i know you're an oldschool head, thought you legit wanted to find a team so did that go south and you decided to do this instead? enlighten me
[quote=chambs]where's the question[/quote]
[quote]i'd put money on it that you would still be doing it but since you got caught now its all good right[/quote]
so is it all good man or what? i know you're playing dumb but this is fun
you came back to tf2 i know you're an oldschool head, thought you legit wanted to find a team so did that go south and you decided to do this instead? enlighten me
[quote]i'd put money on it that you would still be doing it but since you got caught now its all good right[/quote]
so is it all good man or what? i know you're playing dumb but this is fun
you came back to tf2 i know you're an oldschool head, thought you legit wanted to find a team so did that go south and you decided to do this instead? enlighten me
yeah I'm going to keep doing it regardless. I have no problem admitting it. ¯\(°_o)/¯
haha cool man xD keep on cheating!
[quote]yeah I'm going to keep doing it regardless. I have no problem admitting it. ¯\(°_o)/¯[/quote]
haha cool man xD keep on cheating!
haha cool man xD keep on cheating!
This thread has been locked.