Carter Anderson
Carter Anderson
"code-first", while definitely true currently and likely to be true going forward, doesn't feel like the right focus, given our "visual editor" ambitions.
I'll also throw out the fact that Bevy is increasing an "app framework", not just a game engine. I've been sneaking in "app framework" into the tagline in recent posts:...
But I also think we need the exact phrase "game engine" in the tag line or we risk being miscategorized, both by search engines and people.
I've been playing with "Bevy: the everything engine" in my head for awhile, but I think that verges on both hubris and not saying enough.
Rather than adding the concept of "configuration tokens", could we instead just let users operate directly on the system state? One of my reactivity experiments involved using this pattern: ```rust...
> The problem is that set_state needs to be object safe so that we can call this on a Box. The get_state method you mentioned was defined on WorldQuery which...
An old draft of mine that reworked the system lifecycle: https://github.com/bevyengine/bevy/pull/2777
The problem is that we didn't wire up the optional `bevy_image` dependency to the top level `bevy` crate. This should definitely be fixed in a patch release. There is a...
As a thought: i think we might want to focus on "game templates" first, then build more complex games like VVVVVV clones on top (and adapt the template as our...
Yup my vote is new repos within the bevyengine org with a standardized naming convention (ex: `bevy_template_X`) and with Bevy Assets entries (and maybe boosted prominence)