Warhound
========
Battlerite API telemetry parser.
Introduction
-----------
The "telemetry" is a per-match file served over HTTP by Stunlock Studios. It
contains detailed events about what occurs in each round of a match--much more
detail than is exposed via the `Battlerite API <https://developer.battlerite.com>`_.
To get a match telemetry file, you will need a URL located in the "match
details" response body. You can interact with the API using a library like
`furrycorn <https://github.com/odeumgg/furrycorn>`_.
Once you obtain the URL for the match telemetry, use this library to parse it.
The parsed result is a structured object model of telemetry data, rendering it
much easier to find the data you need.
Wiki
----
We're using the `wiki <https://github.com/odeumgg/warhound/wiki>`_ to document
warhound. Feel free to make contributions.
Installation
------------
``pip install warhound`` should do it for your projects.
Development
-----------
Requirement setup should be a breeze using `pipenv <https://docs.pipenv.org/>`_.
If you're using `nixos <https://nixos.org>`_, simply boot a ``nix-shell`` in the
project directory to get a development shell.
For the rest of the world:
1. Clone the directory and navigate to your local repo in a command line.
2. ``pipenv install --three``
3. ``pipenv shell``
For development, make sure ``PYTHONPATH`` includes the project root. Run tests
with ``py.test``.
Please submit changes by pull request on an *aptly named topic branch*.
Code Style
----------
The author of this library prefers a functional style of coding which centers
on "types". It's a lot easier to reason about types than logical steps, and
given the highly structured nature of jsonapi, it felt like a good fit.
Feel free to message with any questions you have. I'm happy to help and explain.
License
-------
This project is Copyright © 2018 odeum.gg and licensed under the MIT license.
View `the license <https://github.com/odeumgg/warhound/blob/master/LICENSE>`_
for details.
Metadata
Release files for warhound 0.8.2
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 |
|---|---|---|---|---|
| warhound-0.8.2.tar.gz | 5.8 kB | Without provenance | Details for warhound-0.8.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| warhound-0.8.2-py3-none-any.whl | Python 3 | none | any | Details for warhound-0.8.2-py3-none-any.whl |
Total release size: 15.3 kB
Release files / warhound-0.8.2.tar.gz
| Download URL | warhound-0.8.2.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a28db39aa95ec3bd7607ee4eca26de6c455778362f83c19b17b3612903df25c
|
|
BLAKE2b-256 checksum How to use checksums |
eefe582d072eca2b7cd0b50f30f497151e6256fe3292ecfeb6c1d1b915915d16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / warhound-0.8.2-py3-none-any.whl
| Download URL | warhound-0.8.2-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab1a5d29100f2a4991765b849653a6d4f73e943e2a0ff326bd6652f1d8fa8a7f
|
|
BLAKE2b-256 checksum How to use checksums |
d27551249b5bdbf351503823c502a5558d62e12bb5a05c461d74852d4142a31b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for warhound 0.8.2
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.