kronic/Project-M
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: Bevy guide — add BRP/bevy_brp_mcp live-introspection tooling (2026-07 MCP ecosystem sweep)

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Luis Gonzalez
2026-07-28 12:29:04 -07:00
parent d0e78e935d
commit f60e9ab60a
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Docs/Vault/03_Design/Lantern_Bevy_Greenfield_Guide.md
+1
View File
@@ -276,6 +276,7 @@ This is where the stack pays for itself; roughly five ★-class Unity limitation
- **Inner loop:** `cargo check` for seconds-fast validation; dev profile with `bevy/dynamic_linking` + a fast linker for quick rebuild-and-run; `opt-level` bumped for deps so debug play is smooth. Full clean builds are slow (Rust tax) — cache in CI, never clean locally without cause. - **Inner loop:** `cargo check` for seconds-fast validation; dev profile with `bevy/dynamic_linking` + a fast linker for quick rebuild-and-run; `opt-level` bumped for deps so debug play is smooth. Full clean builds are slow (Rust tax) — cache in CI, never clean locally without cause.
- **Hot reload:** RON profiles, WGSL shaders, and glTF assets reload on save via the asset watcher — tuning and look iteration without restarts. (Code hot-patching exists as experimental ecosystem work; treat as a bonus, not a plan.) - **Hot reload:** RON profiles, WGSL shaders, and glTF assets reload on save via the asset watcher — tuning and look iteration without restarts. (Code hot-patching exists as experimental ecosystem work; treat as a bonus, not a plan.)
- **Live-world introspection (BRP):** Bevy ships the first-party **Bevy Remote Protocol** — a JSON-RPC layer into a *running* app, headless server included. Community MCP servers (`bevy_brp_mcp`, `bevy_debugger_mcp`) sit thinly on top: query/watch/mutate live components, trigger events, launch apps. This is the agent's runtime eyes, and it is protocol-native rather than editor-automation — it works against a dedicated server or any dev build, with no editor session, focus state, or compile-freshness hazards. Enable the `bevy_remote` feature in dev builds from day one; unlike the Unity bridge, this bridge is *optional* (the primary loop stays CLI + text), which is the structural reason the MCP scar list stays short.
- **Operator surfaces** (replacing the editor, honestly the biggest workflow cost — budget for it): - **Operator surfaces** (replacing the editor, honestly the biggest workflow cost — budget for it):
- `--host` + egui: inspector, tuning bench with profile A/B, debug-op buttons (the `DebugOp` byte model ports as reliable messages), F-key toggles; - `--host` + egui: inspector, tuning bench with profile A/B, debug-op buttons (the `DebugOp` byte model ports as reliable messages), F-key toggles;
- `lantern_tools seed-gallery` for worldgen review; `lantern_tools staging` (orbit-cam scene viewer) as the ArtStaging replacement; - `lantern_tools seed-gallery` for worldgen review; `lantern_tools staging` (orbit-cam scene viewer) as the ArtStaging replacement;