Restore bevy_feathers features after merge with upstream
#41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
bevyengine#20158
Looks like the recent sync with bevy main caused us to lose some feathers stuff
next-gen-scenes-specific) pane examples back to the feathers exampleEntityCursorAlphaPatternnot setting theMaterialNodehandle properlyspawn_scenedoes not insert the whole bundle at once yet#[require]and a component hook to initialize it in a way that works withspawn_scene- a nice plus was this allowed us to get rid of the extra plugin and resourceBack in business:
