iiYese
iiYese
Two things you should probably do: - Add a way to bypass default filters. - Change `.retain`. Make it so it doesn't remove components that are filtered as `Without` &...
> This behavior feels a bit implicit, but I think creating a list of components retain shouldn't touch could make a lot of sense At the very least it should...
Could some way of having implicit hooks be considered? Maybe via the `Component` trait? ```rust pub trait Component { // .. fn init_default_hooks(info: &mut ComponentInfo) {} } ``` These method...
@nicopap > `DeferredWorld` comes from "world where we can only execute deferred operations". But I think it's false right? We can mutate components as long as we don't remove/add them....
@Nilirad A similar concept already exists in rust: `Clone`. Things that are `Clone` don't inherently have side effects on duplication but **_can_** have side effects on duplication. The side effects...
@Nilirad > I don't think that the concept of cloning implies (at least explicitly) the absence of side effects on duplication. It doesn't necessarily imply them. Things that are `Copy`...
Thanks that works. Is there a reason this isn't on the main branch yet? :thinking:
Could just use `EntityEvent` like `bevy_mod_picking`. Would also mean people that have used mod picking can just reuse their understanding from that. Alternatively we could rename our current `Event`.
How about: - Keep observer events as `Event` - Rename our current `Event` to `Signal` ?
> Why is this better than peaking (not consuming) events in a regular system? What problem does this solve? - Systems have to be somewhere in a schedule that is...