f18f28874a
# Objective - Better consistency with `add_systems`. - Deprecating `add_plugin` in favor of a more powerful `add_plugins`. - Allow passing `Plugin` to `add_plugins`. - Allow passing tuples to `add_plugins`. ## Solution - `App::add_plugins` now takes an `impl Plugins` parameter. - `App::add_plugin` is deprecated. - `Plugins` is a new sealed trait that is only implemented for `Plugin`, `PluginGroup` and tuples over `Plugins`. - All examples, benchmarks and tests are changed to use `add_plugins`, using tuples where appropriate. --- ## Changelog ### Changed - `App::add_plugins` now accepts all types that implement `Plugins`, which is implemented for: - Types that implement `Plugin`. - Types that implement `PluginGroup`. - Tuples (up to 16 elements) over types that implement `Plugins`. - Deprecated `App::add_plugin` in favor of `App::add_plugins`. ## Migration Guide - Replace `app.add_plugin(plugin)` calls with `app.add_plugins(plugin)`. --------- Co-authored-by: Carter Anderson <mcanders1@gmail.com>
25 lines
984 B
Rust
25 lines
984 B
Rust
//! Shows different built-in plugins that logs diagnostics, like frames per second (FPS), to the console.
|
|
|
|
use bevy::{
|
|
diagnostic::{FrameTimeDiagnosticsPlugin, LogDiagnosticsPlugin},
|
|
prelude::*,
|
|
};
|
|
|
|
fn main() {
|
|
App::new()
|
|
.add_plugins((
|
|
DefaultPlugins,
|
|
// Adds frame time diagnostics
|
|
FrameTimeDiagnosticsPlugin,
|
|
// Adds a system that prints diagnostics to the console
|
|
LogDiagnosticsPlugin::default(),
|
|
// Any plugin can register diagnostics. Uncomment this to add an entity count diagnostics:
|
|
// bevy::diagnostic::EntityCountDiagnosticsPlugin::default(),
|
|
// Uncomment this to add an asset count diagnostics:
|
|
// bevy::asset::diagnostic::AssetCountDiagnosticsPlugin::<Texture>::default(),
|
|
// Uncomment this to add system info diagnostics:
|
|
// bevy::diagnostic::SystemInformationDiagnosticsPlugin::default()
|
|
))
|
|
.run();
|
|
}
|