4.0.1

Changes

• Update to latest vault which fixes parsing on 2.3.0 patch replays

4.0.0

Changes

• Update to latest vault to take advantage of various edge case parsing improvements

Breaking Changes

The above update introduces some changes to the format of commands returned by flank. For example, this battlegroup command

{
  "UseBattlegroupAbility": {
    "pbgid": 199166,
    "tick": 184
  }
}

turns into

{
  "UseBattlegroupAbility": {
    "index": 4,
    "pbgid": 199166,
    "tick": 184
  }
}

and this unknown command

{
  "Unknown": {
    "action_type": 138,
    "tick": 167
  }
}

turns into

{
  "Unknown": {
    "action_type": "PCMD_TentativeUpgradePurchaseAll",
    "index": 3,
    "tick": 167
  }
}

0.6.1

Changes

• Fix build issue caused by outdated rustc-serialize crate

3.0.1

Changes

• Fix an issue with map data parsing in CoH3 patch 1.7.0.

3.0.0

Changes

• Add support for replays against/involving AI/CPU players
• Add support for replays played on mods (such as CheatMod)
• Player objects now have a human boolean field indicating whether they're human or AI

Breaking Changes

• Player steam_id and profile_id values are now nullable because AI/CPU players do not have these fields. If the human field is true, these fields will be populated; if it's false, these will be null.

2.2.0

Changes

• Updated all dependencies
• Updated vault to 6.0.0, which means battlegroup and upgrade commands are now parsed correctly in command output

2.1.0

Changes

• Added the -c / --clear command, which clears commands before writing output if you don't care about them. Functionality is similar to the old --wipecmd.

2.0.0

Changes

• First iteration of command parsing is now live! Build and battlegroup selection commands are being parsed, and all other commands are being parsed into a generic unknown command entity until further command support is added. See note below for potentially breaking impact of this change.
• You can now access commands and battlegroup fields on player objects.

Breaking Changes

• While the above are not strictly breaking changes, this modifications result in a drastically larger JSON output because of the command parsing. Because of this, applications with performance requirements should be diligent when updating.

1.1.0

Changes

• Update vault library to latest version (3.0.1)
• Return parsing errors in same JSON format as successfully parsed replays. If parsing fails, {"error":"Parsing failed!"} will be returned in the output. Note that any other errors (for example file system or command formatting errors) will continue to output in the old format.

1.0.0

Rewritten for vault v2! Code is much cleaner and simpler, and the tool is very simple for now: give it a path to a replay file and it will return a JSON object containing parsed information or an error message if something went wrong. CoH2 support has been deprecated as well, and can be found at the previous version tag.