Web Assets

A handful of deepscry subcommands exist to build the data the browser client needs: the card database export and the content-addressed asset bundle. You only run these when preparing a web build or a deploy; they are not part of playing a game.

Card images are not built here at all. They come from the pluggable card skin: a content-addressed manifest whose artpack maps each card’s catalog id to an image URL. The deploy stages the site’s preset skins (see scripts/stage_public_card_skin.py), a custom universe ships its own, and the skin is the only place a page resolves a card image from.

stats — inspect the card database

deepscry stats

Prints statistics about the cards loaded from cardsfolder/. Useful as a quick sanity check that the card database parses.

export-wasm — package data for the browser

deepscry export-wasm

Exports the card database and a selection of decks into the binary format the WASM (browser) build loads. By default it includes the old-school and booster-draft deck sets; glob patterns let you include more.

hash-asset / hash-web-assets — content addressing

These are part of the content-addressed asset pipeline used by the deploy. They compute stable BLAKE3 hashes of asset files so the deployed site can cache aggressively and bust the cache precisely when an asset’s bytes change.

deepscry hash-asset path/to/file        # print the 16-hex BLAKE3 hash of one file

The staged skins and the hashed asset bundle are regenerated at deploy time and are not tracked in git.