Open GoogleCodeExporter opened 9 years ago
Thanks, I will look into these.
Your suggestion is implemented: if you scan a replay (or autoscan scans it), it
displays what hacks are found. But by default short scan is on, so it will only
scan
and display the first hack found. You can disable short scan on the General
settings
tab.
Original comment by icz...@gmail.com
on 15 Jan 2010 at 4:53
I mean show it on the website.
Original comment by AHeinerm
on 15 Jan 2010 at 10:22
Added support for this from version 3.20 (showing what hacks were used).
Original comment by icz...@gmail.com
on 3 Feb 2010 at 6:40
If the Set Latency command is recorded in replays, then you could detect a "Set
Latency Spam" that's in a hack floating around somewhere.
There is also a possibility that people can send 0x56 and 0x57 to modify the
resulting replay data(recorded in replay).
0x1D, 0x38, 0x39, 0x3A, and 0x3B are also valid but unused commands that may
surface
in the future.
Original comment by AHeinerm
on 3 Feb 2010 at 6:10
Thanks for the info, I will look into it.
Original comment by icz...@gmail.com
on 3 Feb 2010 at 8:07
Original issue reported on code.google.com by
AHeinerm
on 15 Jan 2010 at 2:41