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

Using built in Resource mutation #3

Open
tbillington opened this issue Sep 27, 2024 · 3 comments
Open

Using built in Resource mutation #3

tbillington opened this issue Sep 27, 2024 · 3 comments

Comments

@tbillington
Copy link

Any ideas if it's possible to use normal Resource for resource_mutation?

@UkoeHB
Copy link
Owner

UkoeHB commented Sep 27, 2024

Hey, it is not currently possible in this library. It is possible in bevy_reactor though, which uses a change-detection-based approach that results in quite different control flow characteristics (bevy_reactor processes all reactions once per tick, while this library processes them immediately as commands).

@tbillington
Copy link
Author

Understand, thanks. I added my own broadcast event and trigger it when I detect the resource has been modified in a dedicated system.

@UkoeHB
Copy link
Owner

UkoeHB commented Sep 28, 2024

Ah that works, nice solution :). I'll leave this issue open in case anyone else has the same question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants