heroprotocol is a reference Python library and standalone tool to decode Heroes of the Storm replay files into Python data structures.
Currently heroprotocol can decode these structures and events:
- replay header
- game details
- replay init data
- game events
- message events
- tracker events
heroprotocol can be used as a base-build-specific library to decode binary blobs, or it can be run as a standalone tool to pretty print information from supported replay files.
Note that heroprotocol does not expose game balance information or provide any kind of high level analysis of replays; it's meant to be just the first tool in the chain for your data mining application.
heroprotocol supports all Hereos of the Storm replay files that were written with retail versions of the game. The current plan is to support all future publicly released versions, including public betas.
How to Use
A working installation of Python 2.x is required. From the folder where heroprotocol is located, type the following into the command line, assuming that the replay file was also copied into the same folder:
py heroprotocol.py --<option> "<replayFileName>" > output.txt
If you want the output shown directly in the terminal, leave out the
py heroprotocol.py --details "Blackheart's Bay.StormReplay" > output.txt
-h, --help Show the options that are available.
--gameevents print all game events including coordinates
--messageevents print message events such as ping events
--trackerevents print tracker events such as units killed, game stat events, score result event
--attributeevents print attribute events, a table of attrid, namespace, and attribute values
--header print protocol header including HotS build and elapsedGameLoops
--details print protocol details, e.g. teamId, player names and chosen heroes, player region, game result, observer status
--initdata print protocol initdata, e.g. interface settings for every player
--stats print game stats
Some notes on tracker events:
- Convert unit tag index, recycle pairs into unit tags (as seen in game events) with protocol.unit_tag(index, recycle)
- Interpret the NNet.Replay.Tracker.SUnitPositionsEvent events like this:
unitIndex = event['m_firstUnitIndex'] for i in xrange(0, len(event['m_items']), 3): unitIndex += event['m_items'][i + 0] x = event['m_items'][i + 1] * 4 y = event['m_items'][i + 2] * 4 # unit identified by unitIndex at the current event['_gameloop'] time is at approximate position (x, y)
- Only units that have inflicted or taken damage are mentioned in unit position events, and they occur periodically with a limit of 256 units mentioned per event.
- NNet.Replay.Tracker.SUnitInitEvent events appear for units under construction. When complete you'll see a NNet.Replay.Tracker.SUnitDoneEvent with the same unit tag.
- NNet.Replay.Tracker.SUnitBornEvent events appear for units that are created fully constructed.
- You may receive a NNet.Replay.Tracker.SUnitDiedEvent after either a UnitInit or UnitBorn event for the corresponding unit tag.
- In NNet.Replay.Tracker.SPlayerStatsEvent, m_scoreValueFoodUsed and m_scoreValueFoodMade are in fixed point (divide by 4096 for integer values). All other values are in integers.
- There's a known issue where revived units are not tracked, and placeholder units track death but not birth.
Copyright (c) 2015 Blizzard Entertainment
Open sourced under the MIT license. See the included LICENSE file for more information.
The standalone tool uses mpyq to read mopaq files.
Thanks to David Joerg and Graylin Kim of GGTracker for design feedback and beta-testing of the s2protocol library that heroprotocol is based upon.
Thanks to Ben Barrett of HOTSLogs for feedback on and beta-testing of the heroprotocol library.