8
8
//! This crate provides additional utilities for the [Bevy game engine](https://bevy.org),
9
9
//! focused on improving developer experience.
10
10
11
- use bevy_app:: prelude:: * ;
12
-
13
11
#[ cfg( feature = "bevy_ci_testing" ) ]
14
12
pub mod ci_testing;
15
13
@@ -22,37 +20,3 @@ pub mod picking_debug;
22
20
pub mod states;
23
21
24
22
pub use easy_screenshot:: * ;
25
-
26
- /// Enables developer tools in an [`App`]. This plugin is added automatically with `bevy_dev_tools`
27
- /// feature.
28
- ///
29
- /// Warning: It is not recommended to enable this in final shipped games or applications.
30
- /// Dev tools provide a high level of access to the internals of your application,
31
- /// and may interfere with ordinary use and gameplay.
32
- ///
33
- /// To enable developer tools, you can either:
34
- ///
35
- /// - Create a custom crate feature (e.g "`dev_mode`"), which enables the `bevy_dev_tools` feature
36
- /// along with any other development tools you might be using:
37
- ///
38
- /// ```toml
39
- /// [feature]
40
- /// dev_mode = ["bevy/bevy_dev_tools", "other_dev_tools"]
41
- /// ```
42
- ///
43
- /// - Use `--feature bevy/bevy_dev_tools` flag when using the `cargo run` command:
44
- ///
45
- /// `cargo run --features bevy/bevy_dev_tools`
46
- ///
47
- /// - Add the `bevy_dev_tools` feature to the bevy dependency in your `Cargo.toml` file:
48
- ///
49
- /// `features = ["bevy_dev_tools"]`
50
- ///
51
- /// Note: The third method is not recommended, as it requires you to remove the feature before
52
- /// creating a build for release to the public.
53
- #[ derive( Default ) ]
54
- pub struct DevToolsPlugin ;
55
-
56
- impl Plugin for DevToolsPlugin {
57
- fn build ( & self , _app : & mut App ) { }
58
- }
0 commit comments