W3G: The Warcraft 3 Replay File Format
This is a single module package that contains everything that is needed to read in the Warcraft 3 replay file format *.w3g. W3G is a custom binary format. The benefits of this are that the files are small, even for very long games. The downside is that for them to be meaningfully a lot of extra data needs to be provided (as is done here for you) for these files to be meaningfully deciphered.
The replays basically amount to a bunch of metadata (map, players, etc) and a big event list. The file parser here provides you with access to this data as well as some post-processed metrics, such as actions-per-minute (APM).
The API should be easy to use and figure out. Classes and attributes are named in a sane way. Here is an example of usage:
import w3g
f = w3g.File('replay.w3g')
winner = f.winner()
print(winner)
f.print_apm()
You can also use this file in script mode to print out the entire game and its stats:
$ ./w3g.py replay.w3g
If you have any questions or issues, please email me or leave an issue on the issue tracker.
/scopzout
Metadata
Release files for w3g 1.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| w3g-1.0.5.tar.gz | 26.5 kB | Without provenance | Details for w3g-1.0.5.tar.gz |
Release files / w3g-1.0.5.tar.gz
| Download URL | w3g-1.0.5.tar.gz |
|---|---|
| Size | 26.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce4f28c54e10590267fa62252088e5327d6676f16c1d2ad06dd4eaca2e29261e
|
|
BLAKE2b-256 checksum How to use checksums |
b59fbe732c46ab4f952896c057271975aa4cb8e5fbcfe1b6b90e1ea04011f432
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.0 requests/2.24.0 setuptools/49.6.0.post20201009 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.7.8
|
Security for w3g 1.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.