Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bevy_remote doesn't work with dynamic components #18138

Open
SpecificProtagonist opened this issue Mar 3, 2025 · 0 comments
Open

bevy_remote doesn't work with dynamic components #18138

SpecificProtagonist opened this issue Mar 3, 2025 · 0 comments
Labels
A-Dev-Tools Tools used to debug Bevy applications. C-Bug An unexpected or incorrect behavior

Comments

@SpecificProtagonist
Copy link
Contributor

SpecificProtagonist commented Mar 3, 2025

bevy_remote treats dynamic components as non-existing, with the exception of the list method when applied to an entity (but not globally).

There are two obstacles to solving this:

  • BRP identifies components by name. This could be solved by switching to component ids and adding a method to get the corresponding component name (and component mutability while we're at it). Alternatively, uniqueness could be enforced for component names & a name → component id index could be built.
  • Reflect dynamic components / type registrations for dynamic types #14404, which blocks ser/de for dynamic components. But even without that, we should still be able to list and remove dynamic components.
@SpecificProtagonist SpecificProtagonist added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled A-Dev-Tools Tools used to debug Bevy applications. and removed S-Needs-Triage This issue needs to be labelled labels Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Dev-Tools Tools used to debug Bevy applications. C-Bug An unexpected or incorrect behavior
Projects
None yet
Development

No branches or pull requests

1 participant