shimeji-dl
Asynchronous Shimeji downloader with pluggable source adapters, XML-driven asset discovery, adaptive numeric probing, persistent local reuse, and concurrent terminal progress.
Install / run with uv
From a checkout:
uv run shimeji-dl https://shimejis.xyz/directory/undertale-shimeji-pack
Once published as a package:
uvx shimeji-dl https://shimejis.xyz/directory/undertale-shimeji-pack
A character URL or slug is also accepted:
uv run shimeji-dl https://shimejis.xyz/directory/shimeji/undertale-nightmare-sans-by-niuniu-nuko
uv run shimeji-dl undertale-nightmare-sans-by-niuniu-nuko
By default, output is written to shimeji-downloads/.
Existing downloads
Existing valid configuration files and images are reused by default.
Re-running the same command therefore does not download files that are already present and valid.
Use --overwrite to explicitly refresh and replace existing valid files:
uv run shimeji-dl https://shimejis.xyz/directory/undertale-shimeji-pack --overwrite
An internal retry never overwrites successful files from the preceding attempt.
It retries only failed characters and reuses everything that was already downloaded successfully.
Retry and confirmations
When one or more characters fail, an interactive terminal offers to retry only those failed characters once.
Use --retry to perform that retry automatically:
uv run shimeji-dl https://shimejis.xyz/directory/undertale-shimeji-pack --retry
--yes / -y answers yes to all confirmation prompts, including the retry prompt and potentially expensive target validations:
uv run shimeji-dl https://shimejis.xyz --yes
Downloading the entire shimejis.xyz directory requires confirmation unless --yes is supplied.
Architecture
The project deliberately separates reusable mechanics from source-specific behavior:
src/shimeji_dl/
├── core/ # Generic HTTP, models, engine, storage and adaptive probing
├── formats/ # Shimeji configuration formats
│ └── shimeji_xml.py # lxml-backed XML implementation
├── sources/ # Remote source adapters
│ └── shimejis_xyz/ # shimejis.xyz extraction and URL layout
├── ui/ # Presentation implementations
│ └── rich.py # Rich progress/reporting and confirmations
├── cli.py # Typer CLI composition root
└── version.py # Reads installed metadata; pyproject.toml is the SSOT
The generic downloader only talks to protocols (SourceAdapter, ConfigFormat, Reporter).
Adding another site does not require modifying the probing engine or download core.
XML + adaptive probing
- Fetch Configuration - Fetch
actions.xmlandbehaviors.xmlwhen the source exposes them. - Parse XML - Parse configuration with
lxmland discover every referenced image path. - Download References - Download XML-referenced assets as authoritative resources.
- Use XML Anchors - Feed numeric
shimeN.pngreferences into the adaptive explorer as known anchors. - Probe Adaptively - Probe the numeric namespace even when XML exists, so unreferenced extras can still be discovered.
- Gallop On Success - Increase the search distance exponentially while probes continue to match.
- Bisect On Failure - Narrow the dense frontier after the first failed exponential probe.
- Explore Quiescence - Search beyond the frontier using a quiet span derived from observed gaps and namespace size instead of a fixed index ceiling.
- Separate Failure Semantics - Treat XML-referenced misses as completeness errors while normal probe misses remain expected discovery evidence.
--probe auto is the default. --probe deep widens sparse-tail exploration, and --probe off disables numeric probing entirely.
Dependencies
Each runtime dependency replaces a concrete piece of infrastructure rather than duplicating it locally:
httpx- Async HTTP transport and connection pooling.tenacity- Retry policy and exponential backoff.lxml- HTML/XML parsing and XPath.rich- Concurrent terminal progress, wrapping output and interactive confirmations.typer- CLI declaration, validation, help and option parsing.
Useful options
-o, --output PATH
-j, --jobs INTEGER
--connections INTEGER
--timeout FLOAT
--retries INTEGER
--probe auto|off|deep
--overwrite
--retry
-y, --yes
--strict
--metadata / --no-metadata
--archive
-v, --verbose
-q, --quiet
--version
License
MIT License. See LICENSE.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.
LLM Notice
Large language models, including Codex and Claude Code, were used in the development of this project.
Release files for shimeji-dl 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| shimeji_dl-0.5.0.tar.gz | 23.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| shimeji_dl-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.2 kB
Release files / shimeji_dl-0.5.0.tar.gz
| Download URL | shimeji_dl-0.5.0.tar.gz |
|---|---|
| Size | 23.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e30371815a35f93fca852c8874066975197e9a9027b0ba5c8a290d8f6f4bd1d
|
|
BLAKE2b-256 checksum How to use checksums |
d6aa7ac7455e381c2adb3f34e69edf7614cc3bd2864f8c78dd2a664afa7f7c20
|
| 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 19, 2026.
Transparency logRelease files / shimeji_dl-0.5.0-py3-none-any.whl
| Download URL | shimeji_dl-0.5.0-py3-none-any.whl |
|---|---|
| Size | 23.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76e5ab4977068f27471fa3f92e51268e7428ea441ed868b98aae216657f9c43d
|
|
BLAKE2b-256 checksum How to use checksums |
9ca0460bc6ab7b31715dd3fd250fa2ba2e5ebbf6cccca1df32e322a77f382a2f
|
| 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 19, 2026.
Transparency log