EIREXE
de5d8eb030
## Summary - package the production Linux binary and Bevy assets under `build/linux` - generate Steam TOTP credentials in CI - deploy app 3409670 to the Steam `master` branch using the latest commit hash as the build description - restrict packaging and deployment to pushes on `master`, excluding pull requests and manual runs Reviewed-on: #47 Co-authored-by: Álex Román Núñez <eirexe@eirteam.moe>
Shinespark
Fancy heavily advanced platform fighting game
Direct P2P Debugging
# Process 1 owns player 0 and listens on 7000.
cargo run -- --debug-match --players 2 --local-port 7000 \
--net-player 0=local --net-player 1=127.0.0.1:7001
# Process 2 owns player 1 and listens on 7001.
cargo run -- --debug-match --players 2 --local-port 7001 \
--net-player 0=127.0.0.1:7000 --net-player 1=local
Production Build
Production builds use the production Cargo profile and do not dynamically
link Bevy or Rust. Development builds retain Bevy dynamic linking for faster
iteration. Cargo stores the production profile under target/production,
separate from development artifacts under target/debug.
cargo run --locked \
--bin process-assets --no-default-features --features debug_features
cargo build --locked \
--profile production --no-default-features --features debug_features
The asset preprocessing command must be run from the repository root. It
populates imported_assets/Default, which is then consumed by the production
game without running the asset processor at startup.