History

GitGhillie f41a315563 chore(): cargo fmt (#21 )		2023-10-13 12:53:26 +02:00
..
assets	chore(): cargo fmt (#21 )	2023-10-13 12:53:26 +02:00
core	chore(): cargo fmt (#21 )	2023-10-13 12:53:26 +02:00
game	chore(): cargo fmt (#21 )	2023-10-13 12:53:26 +02:00
README.md	feat(): Blueprints, crates, enhanced Blender tooling & more (#5 )	2023-09-28 14:10:45 +02:00
TODO.md	feat(): Blueprints, crates, enhanced Blender tooling & more (#5 )	2023-09-28 14:10:45 +02:00
main.rs	chore(): cargo fmt (#21 )	2023-10-13 12:53:26 +02:00
state.rs	chore(): cargo fmt (#21 )	2023-10-13 12:53:26 +02:00
test_components.rs	chore(): cargo fmt (#21 )	2023-10-13 12:53:26 +02:00

README.md

Workflow with blender / demo information

This example, is actually closer to a boilerplate + tooling showcases how to use a minimalistic Blender (gltf) centric workflow for Bevy, ie defining entites & their components inside Blender using Blender's objects custom properties. Aka "Blender as editor for Bevy"

It also allows you to setup 'blueprints' in Blender by using collections (the recomended way to go most of the time), or directly on single use objects .

Running this example

cargo run --example advanced  --features bevy/dynamic_linking

Additional notes

You usually define either the Components directly or use Proxy components that get replaced in Bevy systems with the actual Components that you want (usually when for some reason, ie external crates with unregistered components etc) you cannot use the components directly.
this example contains code for future features, not finished yet ! please disregard anything related to saving & loading