Crates.io | iyes_progress |
lib.rs | iyes_progress |
version | |
source | src |
created_at | 2022-04-22 20:54:06.1792 |
updated_at | 2024-12-01 17:08:14.298914 |
description | Bevy plugin to help implement loading states |
homepage | |
repository | https://github.com/IyesGames/iyes_progress |
max_upload_size | |
id | 572368 |
Cargo.toml error: | TOML parse error at line 17, column 1 | 17 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
This crate was formerly known as bevy_loading
!
Bevy Compatibility:
Bevy Version | Plugin Version |
---|---|
main |
N/A |
0.15 |
0.13 |
0.14 |
0.12 |
0.13 |
0.11 |
0.12 |
0.10 |
0.11 |
0.9 |
0.10 |
0.8 |
0.9 |
0.7 |
0.8 |
0.4 ,0.5 , 0.6 |
0.7 |
0.3 |
0.6 |
bevy_loading = 0.2 |
0.5 |
bevy_loading = 0.1 |
This crate helps you in cases where you need to track when a bunch of work has been completed, and perform a state transition.
The most typical use case are loading screens, where you might need to load assets, prepare the game world, etc… and then transition to the in-game state when everything is done.
You can have any number of systems doing different things during your loading state, and they can report their progress to this crate.
See the example for an overview of how to use this crate.
There is also an optional feature (assets
) implementing basic asset
loading tracking. Just add your handles to the AssetsLoading
resource.
If you need something more advanced, I recommend the bevy_asset_loader
crate, which can integrate with this crate. :)