Cameron

One more question this RFC should address is, "What happens to `LastRemoved` if you insert `T` again?" Also, I'm thinking there should be a way to rig this internally so...

(Edit: I've reversed my opinion.) > Namely, make sure our floating point code is portable across all supported platforms. I agree with this now. Bevy could take cues from Dimforge...

> Would it be worth separating this into two modules? The serialization aspect seems distinct from (but a dependency of) the replication aspect. Splitting off `bevy::net::serialization` would more cleanly allow...

> I think those are good models for many game types. I do believe that in any situation where the networking system has to be opinionated, there should be good...

> There are many idiosyncratic game netcode requirements and no single library can adequately service them all. If nothing else, I hope I conveyed that I think these are pretty...

Thank you for the feedback. I want to say upfront that I agree with a lot of what you've said. This RFC already advocates for keeping things modular. I do...

Have you tried the `CollisionPipeline`?

> I can't seem to find any accumulated time / fixed time. Is there a reason for that? No, I just forgot. > Can we add time()? That's `time.time_since_startup()`. It's...

Okay, I made edits to the fn comments, got rid of the "live" getters for the raw, unscaled time, and added a field to track the "current time" of the...

Decided to go ahead and split things into a separate `FixedTime` resource, so this could probably use another review. (Also I messed up merging changes from main and had to...