Files
benilla-octo/crates/benilla-assets/Cargo.toml
T
SamandClaude Fable 5 6b980b9efb the player build: one binary that carries its content
- a player build ships beside the dev one — dev chords and probe surfaces go dark, and a gate enforces what a player can still reach, by medium not by module
- the binary carries its own shaders and its shipped UI, finds the WoW folder by itself, and keeps its local state in one benilla-config folder
- the glue screens get a capture shutter, and the engine stops depending on the protocol crate

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-11 18:18:02 +07:00

24 lines
1.0 KiB
TOML

[package]
name = "benilla-assets"
version.workspace = true
edition.workspace = true
license.workspace = true
description = "Bevy AssetSource + AssetLoaders over the WoW 1.12.1 MPQ patch chain"
[features]
# Forwarded dev/player seam (0026 · 1173/1174 · 1175). Default-on. `benilla-formats` must be taken
# with `default-features = false` and its `dev` re-exported here: it is default-on there too, so
# without this a `--no-default-features` player build gets the feature back through unification and
# the binary carries the build machine's source-tree path after all.
default = ["dev"]
dev = ["benilla-formats/dev"]
[dependencies]
anyhow.workspace = true
bevy.workspace = true
benilla-formats = { path = "../benilla-formats", default-features = false }
# Nearest-neighbour resize for off-Elwynn layer BLPs authored below LAYER_TEX_SIZE (texel
# replication in gamma byte space — no averaging, so the C2 mid-tone darkening can't creep in).
image = { version = "0.25", default-features = false }
serde = { version = "1", features = ["derive"] }