Battle Cats Event Data Downloader
The Battle Cats Event Data Downloader (BCEDD) is a tool made for downloading battle cats event data such as gatya data and sale data.
Credits
- The PackPack Discord Bot for the old method of downloading data (aws stuff)
How To Use
Prerequisites
- Python for running and installing the tool
Run the following commands in command prompt or another terminal to install the tool - If you are not using windows you will need to use python or python3 instead of py
Installation
To install / update the tool run the following command:
py -m pip install -U bcedd
If you get an error saying No module named pip then run
py -m ensurepip --upgrade
Run
By default the tool will download sale.tsv, gatya.tsv and item.tsv for en and it will ask you where you want to save it:
py -m bcedd
If you want to download files for different versions use -c <version1> <version2> etc. Supported versions are en, jp, kr, tw.
py -m bcedd -c jp kr
This will download jp and kr data instead
If you only want to download specific files then use -f <file1> <file2> etc. Supported files are sale.tsv, gatya.tsv, item.tsv.
py -m bcedd -f gatya.tsv item.tsv
This will download files gatya.tsv and item.tsv but not sale.tsv
If you don't want a file save dialog then use -o <output_folder> to save the files to a specific folder.
py -m bcedd -o "Event Data"
This will save all 3 en files to a folder called "Event Data" in the current working directory (use the cd command to change that)
If you want to use the old method of downloading data then use --old
py -m bcedd --old
Install From Source
If you want the latest features and don't want to wait for a release then you can install the tool from the git repo directly.
- Download Git
- Run the following commands: (You may have to replace
pywithpythonorpython3)
git clone https://codeberg.org/fieryhenry/bcedd.git
py -m pip install -e bcedd/
py -m bcedd
If you want to use the tool again all you need to do is run the py -m bcedd command
Then if you want the latest changes you only need to run git pull in the downloaded bcedd folder. (use cd to change the folder)
Metadata
Release files for bcedd 1.2.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 | |
|---|---|---|---|---|
| bcedd-1.2.2.tar.gz | 10.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bcedd-1.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.3 kB
Release files / bcedd-1.2.2.tar.gz
| Download URL | bcedd-1.2.2.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05b759302626f0b9cba03c38d32e5fb99964900859cfedb5a8edb0286a6fb919
|
|
BLAKE2b-256 checksum How to use checksums |
6f64a4d1af63111c9f7a266e92ca525fbb51f02e8e1df574cd33ad9f1a0a4bc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / bcedd-1.2.2-py3-none-any.whl
| Download URL | bcedd-1.2.2-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8552c10480713e4f11fb8c61ccc488d7b5870eee66fd259ea2af957761c7e28f
|
|
BLAKE2b-256 checksum How to use checksums |
27969399b4f933249ff7dc7c328fdae7d8f51b5ad33b7cb2771f8aa5f23d6000
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for bcedd 1.2.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.