This plugin takes over the stdin/stdout from bevy to get runtime information from bevy.
``
Runningtarget\releasebevy_test_game.exe`
Bevy Console Debugger. Type 'help' for list of commands.
archetypes find --componentname Player
archetype ids: 8, 9, 10,
archetype info --id 10
id: ArchetypeId(8)
tableid: TableId(7)
entities (1): 262,
tablecomponents (17): 114 Transform, 115 GlobalTransform, 116 Draw, 120 Animations, 121 Animator, 122 Handle
```
Add to you Cargo.toml file:
toml
[dependencies]
bevy = "0.5"
bevy_mode_debug_console = "0.0.1"
Add Plugin:
```rs use bevy::prelude::*; use bevymoddebug_console::ConsoleDebugPlugin;
fn main() { App::build() .addplugins(DefaultPlugins) .addplugin(ConsoleDebugPlugin) .run(); } ```
Once your bevy application is running press F10 to activate the console. Your game is now paused and commands can be entered into the console. Type help to get a list of commands.
archetype info --id 10 lists id, tableid, entities, tablecomponents, and sparse set components belonging to archetype id 10components list --long --filter bevy_test_game lists components from the bevy_test_game namespace.counts print counts of archetypes, components, and entities.The system that reads commands has a run criteria that returns YesAndCheckAgain until the resume command is entered.
Warning This can have adverse affects with physics as the tick is paused and the tick time on resume can then be very large.