SamandClaude Fable 5
6b980b9efb
- 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>
18 lines
752 B
Rust
18 lines
752 B
Rust
//! Dump any file from the 5875 patch chain to stdout — the generic MPQ extractor for
|
|
//! reference reads (FrameXML sources, DBC layouts): `cargo run -p benilla-formats
|
|
//! --example dump_file -- 'Interface\FrameXML\TradeSkillFrame.lua'`. Output is Blizzard
|
|
//! data — pipe it to the scratchpad, never into the repo.
|
|
|
|
use std::io::Write;
|
|
|
|
fn main() -> anyhow::Result<()> {
|
|
let virt = std::env::args()
|
|
.nth(1)
|
|
.ok_or_else(|| anyhow::anyhow!("usage: dump_file <virtual\\mpq\\path>"))?;
|
|
let data = benilla_formats::wow_data().expect("no WoW install found (set $WOW_DATA)");
|
|
let mut chain = benilla_formats::open_chain(&data)?;
|
|
let bytes = chain.read_file(&virt)?;
|
|
std::io::stdout().write_all(&bytes)?;
|
|
Ok(())
|
|
}
|