Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Stats feature request: ratios of dealt/received and value killed/lost

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
1/12/2024 10:15:46 PMUSrankchaplol before revert after revert
1/12/2024 10:15:36 PMUSrankchaplol before revert after revert
Before After
1 So it turns out that something *like that* exists in the replay file. There's a line that shows how much damage each unit, grouped by player to each other unit. 1 So it turns out that something *like that* exists in the replay file. There's a line that shows how much damage each unit, grouped by player to each other unit.
2 \n 2 \n
3 [quote]{ 'cmd': 'chat', 'size': 51, 'fromID': 5, 'playerName': b'kworon8', 'toID': 255, 'message': b'SPRINGIE:stats, dmg, cloaksnipe, spiderriot, 900, 0\x00'} 3 [quote] { 'cmd': 'chat', 'size': 51, 'fromID': 5, 'playerName': b'kworon8', 'toID': 255, 'message': b'SPRINGIE:stats, dmg, cloaksnipe, spiderriot, 900, 0\x00'}
4 {'cmd': 'chat', 'size': 51, 'fromID': 5, 'playerName': b'kworon8', 'toID': 255, 'message': b'SPRINGIE:stats,dmg,cloaksnipe,shieldraid,340,0\x00'} 4 {'cmd': 'chat', 'size': 51, 'fromID': 5, 'playerName': b'kworon8', 'toID': 255, 'message': b'SPRINGIE:stats,dmg,cloaksnipe,shieldraid,340,0\x00'}
5 { 'cmd': 'chat', 'size': 55, 'fromID': 5, 'playerName': b'kworon8', 'toID': 255, 'message': b'SPRINGIE:stats, dmg, hoverriot, jumparty, 783. 600647, 0\x00'} [/quote] 5 { 'cmd': 'chat', 'size': 55, 'fromID': 5, 'playerName': b'kworon8', 'toID': 255, 'message': b'SPRINGIE:stats, dmg, hoverriot, jumparty, 783. 600647, 0\x00'} [/quote]
6 \n 6 \n
7 Not sure if the toID is a bug or intentional, or if the message is even being parsed properly, but 255 might just be a catchall id. But it could be used for similar inferences like what you're thinking of. Since it's already retained for endgame stats, it'd probably be pretty easy to implement a dropdown-by-unit of some kind. 7 Not sure if the toID is a bug or intentional, or if the message is even being parsed properly, but 255 might just be a catchall id. But it could be used for similar inferences like what you're thinking of. Since it's already retained for endgame stats, it'd probably be pretty easy to implement a dropdown-by-unit of some kind.