Missing Player Actions in Event Data and Incomplete Replay Parsing.

[GGpanda]

I hope this message finds you well. I am writing to seek assistance regarding an issue I am experiencing with the event data and replay parsing in current version.

During my analysis of the event data, I have noticed that player actions seem to be missing. In particular, I am unable to locate specific player actions within the event logs. I kindly request your guidance on this matter and any potential reasons for the missing information.

For example, player Goblin was recorded to have trained three probes in 0:30 ; however, the parsed replay data only revealed one probe train command. I am concerned that I may have missed some crucial information or misinterpreted the data. Could you please help me understand if there is any missing information or if there is a specific way I should be analyzing the replay data to avoid such discrepancies?

I genuinely appreciate your time and attention to this matter. Your expertise will be instrumental in helping me accurately analyze and interpret the data. Please let me know if you require any additional information to assist you in resolving this issue.

Thank you in advance for your support.

2022-08-03 - (P)goblin VS (P)Geralt.zip

[NumberPigeon]

Have a look at "CommandManagerStateEvent" at sc2reader.events.game.py, where the docstring says:

"""
These events indicated that the last :class:`CommandEvent` called has been
called again.  For example, if you add three SCVs to an empty queue on a
Command Center, the first add will be generate a :class:`BasicCommandEvent`
and the two subsequent adds will each generate a
:class:`CommandManagerStateEvent`.
"""