You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Implements new replay GameEngine and plugin support.
13
+
* Added a sc2json script contributed by @ChrisLundquist
14
+
* Adds plugin GameHeartNormalizer plugin by @StoicLoofah
15
+
* Hooked up coveralls.io for coverage reporting: https://coveralls.io/r/GraylinKim/sc2reader
16
+
* Hooked up travis-ci for continuous testing: https://travis-ci.org/GraylinKim/sc2reader
17
+
* Switched to built in python unittest module for testing.
18
+
19
+
Changed Stuff (non-backwards compatible!):
20
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6
21
7
-
* Adds experimental SC2Map.MapInfo parsing support. Replaces the useless MapInfo resource from before.
8
22
* Summary.teams is now summary.team; summary.team is now summary.teams. To conform with replay name conventions
9
23
* Fixed #136, unit types from tracker events are used when available.
10
24
* Deprecated player.gateway for player.region
11
25
* Reorganized the person/player/observer hierarchy. Top level classes are now Computer, Participant, and Observer. Participant and Computer are both children of player so any isinstance code should still work fine.
12
26
* Player.uid now means something completely different! Use player.toon_id instead
13
27
* Player.uid is now the user id of the player (was player.cid)
14
28
* PersonDict can no longer be constructed from a player list and new players cannot be added by string (name). Only integer keys accepted for setting.
15
-
* Added a sc2json script contributed by @ChrisLundquist
16
-
* Hooked up travis-ci for continuous testing. https://travis-ci.org/GraylinKim/sc2reader
17
-
* Switched to built in python unittest module for testing.
18
29
* Log a warning instead of throwing an exception when using an unknown colors.
19
-
* An unknown hex value will use the hex value as the name.
20
-
* An unknown color name will use 0x000000 as the color.
30
+
** An unknown hex value will use the hex value as the name.
31
+
** An unknown color name will use 0x000000 as the color.
32
+
* Finally straighten out all these replay player list/dicts
33
+
** human/humans -> human entities, indexed by uid
34
+
** computer/computers -> computer entities, indexed by pid
35
+
** player/players -> actually playing in the game, indexed by pid
36
+
** observer/observers -> observing the game, indexed by uid
Copy file name to clipboardExpand all lines: README.rst
+32-29Lines changed: 32 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,4 @@
1
+
1
2
What is sc2reader?
2
3
====================
3
4
@@ -18,10 +19,19 @@ sc2reader is currently powering:
18
19
If you use sc2reader and you would like your tool, site, project, or implementation listed above, drop us a line on our `mailing list`_ or stop by our #sc2reader IRC channel and say hi!
sc2reader is production ready at release and under active development on github. It is currently capable of parsing varying levels of information out of the three primary resource types listed below. For a more detailed and exact description of the information that can be extracted please consult the `documentation`_ hosted on ReadTheDocs.
32
+
sc2reader is production ready at release and under active development on Github. It is currently capable of parsing varying levels of information out of the three primary resource types listed below. For a more detailed and exact description of the information that can be extracted please consult the `documentation`_ hosted on ReadTheDocs.
33
+
34
+
.. _documentation: http://sc2reader.rtfd.org/
25
35
26
36
27
37
Replays
@@ -93,6 +103,8 @@ Parsing on these files is now production ready for those that can get them. See
93
103
94
104
Again, these files are generally unnecessary after the 2.0.8 release.
We have an `issue tracker`_ on Github that all bug reports and feature requests should be directed to. We have a `mailing list`_ with Google Groups that you can use to reach out for support. We are generally on FreeNode in the #sc2reader and can generally provide live support and address issues there as well.
0 commit comments