Sharing my Information, suggestions, hacks

ohio813 / bwhf

Automatically exported from code.google.com/p/bwhf

0 stars 0 forks source link

Sharing my Information, suggestions, hacks #68

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

Information:
- Replay Header:
http://code.google.com/p/vgce/source/browse/trunk/docs/Blizzard/Starcraft/replay
Header.txt
- Command opcodes:
http://code.google.com/p/vgce/source/browse/trunk/docs/Blizzard/Starcraft/packet
s2.txt

Some hacks to be aware of (1.16.1) (I'm not sure if BWHF currently supports
them or not):
- Coloured name spoofs.
- Chat message spoofs/colours/impersonations.
- Setting the rally point of other players.
- Reaver/Carrier crash hack (using regular train instead of trainFighter).
- Worker crash hack (using "cancel train" before a building begins
construction).
- Worker suicide (never checked the command).

Suggestion:
- Show the list of hacks found and the number of times it was used.

Original issue reported on code.google.com by AHeinerm on 15 Jan 2010 at 2:41

GoogleCodeExporter commented 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

Added labels: Type-Other
Removed labels: Type-Defect

GoogleCodeExporter commented 9 years ago

I mean show it on the website.

Original comment by AHeinerm on 15 Jan 2010 at 10:22

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago

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

GoogleCodeExporter commented 9 years ago

Thanks for the info, I will look into it.

Original comment by icz...@gmail.com on 3 Feb 2010 at 8:07