- Start the native app:
cargo run
- Start the web build:
trunk serve
- requires [trunk]:
cargo install --locked trunk
- requires
wasm32-unknown-unknown
target:rustup target add wasm32-unknown-unknown
- this will serve your app on
8080
and automatically rebuild + reload it after code changes
- requires [trunk]:
You should keep the credits
directory up to date. The release workflow automatically includes the directory in every build.
- Trigger the
deploy-github-page
workflow - Activate GitHub pages for your repository
- Source from the
gh-pages
branch (created by the just executed action)
- Source from the
- After a few minutes your game is live at
http://username.github.io/repository
To deploy newer versions, just run the deploy-github-page
workflow again.
Note that this does a cargo build
and thus does not work with local dependencies. Consider pushing your "custom Bevy fork" to GitHub and using it as a git dependency.
Audio in web-builds can have issues in some browsers. This seems to be a general performance issue and not due to the audio itself (see [bevy_kira_audio/#9][firefox-sound-issue]).
bevy_jam4_click_defense is free, open source and permissively licensed! Except where noted (below and/or in individual files), all code in this repository is dual-licensed under either:
- MIT License (LICENSE-MIT or http://opensource.org/licenses/MIT)
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
at your option. This means you can select the license you prefer!
Some of the code was adapted from other sources. A lot of it comes from bevy_game_template. See CREDITS.md for the details of the origin of non-original code and assets and licenses of those files.