Help wanted: Adding event listener not specified inside the blueprint cause panic

[tungtose]

Thank you for the effort you put into making this crate!

I am trying to integrate the spawned blueprint with bevy_mode_picking by adding a listener along with the blueprint like the image below. And there's a cause for panic by clone_entity:

Here is the panic location (line 40):

I also tried register_type all visible relative components from bevy_mod_picking but still panicked. Am I missing something to make this working?

[kaosat-dev]

Hi @tungtose !
Thanks for the kind words and feedback !

• you are spot on, normally registering all components should have solved the issue
• right now there is no information about which component failed
• having to register all types in that use-case is rather annoying to begin with, although I have not found a work around yet

Possible "solution":
I 'll try to upload a new version today where it at least prints out information about what components are missing in the type registry, I think that should be an ok stop-gap solution ?

[kaosat-dev]

@tungtose , this is now released : bevy_gltf_blueprints v0.5.1, it should give you information about what components could not be cloned because of the lack of registration

Perhaps it would make more sense to leave this issue open , or create a specific one, as I consider this only a stop-gap solution, ideally not every component should need to be registered.

[tungtose]

@kaosat-dev Thank you for quick solution!
After update and rerun, turn out the component that I added is not derive Reflect.

So for now I just import directly from the gltf file generated from your tool as a quick solution.

[kaosat-dev]

Hi @tungtose just wanted to let you know, that with the release of version 0.6 you can now add unregistered components when spawning blueprints (as in your original bug report with the On<PointerDown... example :)

[tungtose]

@kaosat-dev I just tested and its work as expected, thank you