Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unit Self Destruct not detected (v3.30) #84

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 1 comment
Open

Unit Self Destruct not detected (v3.30) #84

GoogleCodeExporter opened this issue Mar 16, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

At 2:59 the terran self destructs all his scvs, not a major issue since
this is probably not advantageous in most circumstances

Also I think this is another case of undetected automine (see issue 83). It
seems the hack makers are trying to make it much harder tell automine from
legitimate. The reason I think it is automine is because, this person is a
known hacker, has very low apm and skill, has near 'perfect' split, and the
scvs go to the same patches that all other automines choose. This is most
likely impossible to algorithmically detect though, the only thing that I
can suggest is to analyze groups of replays instead of just 1, because
human players are not perfectly consistent.

Original issue reported on code.google.com by flagiti...@gmail.com on 5 Jun 2010 at 3:44

Attachments:

@GoogleCodeExporter
Copy link
Author

It is not impossible to detect the delayed and altered automine.

In fact, it's quite easy. But the thing is that a delayed automine cannot be 
proof of 
hack. It can happen to legit players.

Original comment by icz...@gmail.com on 5 Jun 2010 at 5:58

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant