PYVGC
PYVGC is a Python package for basic Pokémon Champions-based data science. It is currently meant for Python 3.9 and newer, without runtime dependencies.
Readme is still in development for basic usage.
Regulations scope legal Pokémon, moves, items, and learnsets, while named
BattleLogic instances preserve historical and future rule sets.
Cartridge and Simulator use doubles battle logic by default. The separate CHAMPIONS_SINGLES battle logic is available when singles screen behavior is equired, including through load_regulation("M-C",battle_logic="Champions-Singles-2026").
Loaded Pokémon inherit the regulation's selected battle logic for damage calculations.
In the current version there are three types of logics:
- Cartridge-Champions-Release-2026: This is the logic used in the official Pokémon Champions game. It is the most accurate representation of the game mechanics.
- Simulator-Champions-Release-2026: This is a logic that is used in the simulator. It is the same as Catridge but the idea is to support simulator-only logics.
- Champions-Singles-2026: -> The only difference between the Releases and Singles is the Screen Implementation -> 1/2 in singles and 2/3 in doubles.
- There could be more logics in the future, but for now this is the basic template. -> By keeping logics separate we can keep up with future releases or balance changes. -> It could be possible to retroactively fit older logics but it is currently out of the scope of the project.
All current development is meant for early implementation. Until 0.1 this package is on alpha development, but it can currently be used for basic Pokémon data science and damage calculations.
Current (Alpha) version provides a basic template for Pokémon data calculations based on Pokémon Champions.
Item effects and regulation item membership are descriptive data only -> item mechanics are not implemented in damage calculations. -> Teams, weather, terrain, and KO-target searches are not part of this MVP. -> Regulation snapshots and the single-ability query are available as data utilities; they do not affect damage calculations.
The package is maintained by Voozde. It is currently in development for a Python Package full release.
AI / Additional Sources Disclaimer
-> Current development is assisted by the VSCode Copilot Plugin, which settled on GPT-5.6-Luna -> Bundled battle-item reference data with effect descriptions crawled from Serebii's ItemDex.
Metadata
Release files for pyvgc 0.0.2.1
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 |
|---|---|---|---|---|
| pyvgc-0.0.2.1.tar.gz | 162.4 kB | Without provenance | Details for pyvgc-0.0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyvgc-0.0.2.1-py3-none-any.whl | Python 3 | none | any | Details for pyvgc-0.0.2.1-py3-none-any.whl |
Total release size: 324.7 kB
Release files / pyvgc-0.0.2.1.tar.gz
| Download URL | pyvgc-0.0.2.1.tar.gz |
|---|---|
| Size | 162.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a6156b5a4a5a5272cf1d443e43c076f02002b1987bc3ab2631eb0c773ebf052
|
|
BLAKE2b-256 checksum How to use checksums |
583d0df9cb19346654ee8376ce9a77f0ca704d5e4a8a9eac39a39858f55df20c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.23
|
Release files / pyvgc-0.0.2.1-py3-none-any.whl
| Download URL | pyvgc-0.0.2.1-py3-none-any.whl |
|---|---|
| Size | 162.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2fa4a40ef80f0f31f94b24bbaa69c85256252460e646cd0c5896825819811304
|
|
BLAKE2b-256 checksum How to use checksums |
95c6afb0b5f3385693911d9b5c3e34c564c2acb17b34d45dd8ab18a7ffdb7a14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.23
|
Security for pyvgc 0.0.2.1
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.