Ben Frankel

This is solved in [pyri_state](https://github.com/benfrankel/pyri_state). Default states are handled by setting the current state to `None` and the next state to `Some(default_state)`, and then that transition is handled atomically in...

The following gives an `unwrap` panic with no warning: ```rust App::new().init_state::(); ``` However, `init_state` _tries_ to warn that `StatesPlugin` hasn't been added yet, but the warning gets dropped because `LogPlugin`...

Actually you're right. `App::empty` already exists, and `App::new` already sets up foundational plugins and resources: https://github.com/bevyengine/bevy/blob/a0f5ea0d3621a14bdc06d1e3bf1a8d9de90d409b/crates/bevy_app/src/app.rs#L92-L114 `LogPlugin` would fit right in here.

I think https://github.com/trunk-rs/trunk/issues/605 is not yet fixed by https://github.com/trunk-rs/trunk/pull/795?

This seems to be unblocked now, with required components landed and the scene overhaul generally being underway.

So the "large assets" case was hypothetical, but I ran into this with the `target` dir case while working on a PR to a template that will allow its `main`...

Okay this is strange. I performed the 3 steps above and I actually see 3.7 GB for `target/` in the template directory and 4.6 GB for `target/` in the generated...

The upstream `bevy_new` repo on its own is only 1.1MB, which wouldn't have a noticeable impact when loaded to RAM. If you clone it first, then run `cargo build`, _then_...

I think `cargo-generate` is assuming that it's a private repository, which is why it's asking for authentication. In that case, I suppose there should just be a line explaining that...

Currently you can do (pseudocode) `commands.queue(|world| world.run_schedule(...))`, but I agree this would make sense as a built-in method.