HexBug-data
Standalone registry code and parsers for HexBug, a Discord bot for Hex Casting.
This is published to PyPI for use in projects which would like to use HexBug's registry as a data source.
Getting the data
Pre-built dumps
Registry dumps are uploaded to the Book of Hexxy for each release (eg. https://book.hexxy.media/v/2.4.0/registry.json). The registry.json file can be imported using HexBugRegistry.load().
Building
If you'd rather build the registry yourself, you'll need to install HexBug-data with the full extra. Since many addons are not currently published to PyPI and certain addons have incompatible dependencies, constraint files are uploaded to the Book of Hexxy for each release:
- https://book.hexxy.media/v/2.4.0/dist/constraints.txt
- https://book.hexxy.media/v/2.4.0/dist/pylock.toml
For example:
uv pip install HexBug-data[full] --overrides constraints.txt
Depending on the version, you may also need to install some packages from HexBug's vendor directory.
After installing, you can build the registry from scratch using HexBugRegistry.build().
1 maintainer
Metadata
1 maintainer
Release files for HexBug-data 2.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hexbug_data-2.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / hexbug_data-2.11.0-py3-none-any.whl
| Download URL | hexbug_data-2.11.0-py3-none-any.whl |
|---|---|
| Size | 39.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf509bc3114977135acc12c66f2130d9604aa56a108bd212babcd4b683f0253a
|
|
BLAKE2b-256 checksum How to use checksums |
520d021dcbffdd241fc2c2d79dacb5462e9b45adc7d4d9faefac54ae6ecd6caf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency log
