forked from ascendedguard/sc2replay-csharp
-
Notifications
You must be signed in to change notification settings - Fork 0
Notes on the unknown 'playerDetailStruct' structure
ascendedguard edited this page Dec 3, 2010
·
1 revision
The following notes detail information found in the unknown structure between the 'unknown3' and 'unknown4' fields within playerDetailStruct.
Note - Character IDs have been removed from these notes, where initial research had them. This is to protect the players from in-game spam. For reference, players with the same character ID had different values, and players with different character IDs showed matching values.
Conclusions:
unknown 3 should be "08 09" (undocumented, original documentation showed "06 02")
unknown is between 1-3 bytes.
unknown 4 should be "04 02" (documented)
I originally assumed players had 3 bytes, computers had 1 byte, this was proved untrue in further replays.
File 1:
Player 1 = Ascend
Player 2 = Computer (Player 2)
Player 1 Player 2 (Computer)
unknown 3 - 08 09 08 09
unknown - ca e0 20 (202 224 32) 00
unknown 4 - 04 02 04 02
File 2:
Player 1 = AllAboutYou
Player 2 = CocoA
Player 1 Player 2
unknown 3 - 08 09 08 09
unknown - b2 aa 23 (178 170 35) 8c ea 62 (140 234 98)
unknown 4 - 04 02 04 02
Determining what the middle unknown is:
Hex Decimal Binary
Computer 00 0 0000
Ascend ca e0 20 202 224 32 1100 1010 1110 0000 0010 0000
AllAboutYou b2 aa 23 178 170 35 1011 0010 1010 1010 0010 0011
CocoA 8c ea 62 140 234 98 1000 1100 1110 1010 0110 0010
Cheese 246 180 40
Dhalism 208 207 123
AntiMage 246 180 40
Just to confirm, Cheese and AntiMage are confirmed to have different Character IDs,
thus something else causes these players to share the same value.
Cheese and Dhalism have the same character IDs, yet different byte values.