wtf is bevy_level_plan?

Bevy Level Plan is an experimental tool for game developers who want to describe what happens in a game level using code as a kind of script. Instead of hard-coding enemy spawns or events scattered throughout your game logic, you write a structured plan that lays out the sequence of events: when enemies appear, when the boss fight starts, when the player wins. The core idea is a "LevelPlan" that reads like a timeline. You build it by chaining steps together. For example, you can say "repeat this cycle of two enemy types for 500 pixels of travel," then "do nothing for 1000 pixels," then "if the player's health is low, spawn healing items," then "spawn the boss and keep it active until the boss is dead," and finally "trigger the win condition." The plan checks conditions during the game and activates the appropriate steps, spawning things or triggering custom actions as needed. This would appeal to game developers using the Bevy game engine (in Rust) who want a cleaner way to structure level pacing. If you are building a shoot-em-up or platformer and want to author level progression in a readable, declarative format rather than burying spawn logic in your game systems, this gives you that scaffolding. The example in the README shows a vertical shooter where enemy waves and boss encounters are timed to player travel distance and health. The project is explicitly labeled an experiment, and it is early stage with minimal documentation beyond the example. It is built to be generic: you define your own context type to pass world information (like player health) into the plan, and you can create custom plan elements that take actions on activation, deactivation, or each tick while active. Execution is handled by a single generic system function.