Hennadii Chernyshchyk
Hennadii Chernyshchyk
Superseded by #262.
> I will try to take this. Great, I will be happy to review it. Let me know if you have any questions about the implementation. > And will try...
I just looked closer at `EventRegistry` and I don't think that we need it... Looks like it only allows to run `update`. For our case we probably need to create...
Superseded by #282.
Agree, but shouldn't use [TypeId](https://doc.rust-lang.org/std/any/struct.TypeId.html) since it's not stable across binaries. [Relevant issue](https://github.com/bevyengine/bevy/issues/32) in Bevy. But it looks like we can just use type names.
Hm... Yes, I missed it. That just what `@cart` suggested in https://github.com/bevyengine/bevy/issues/32#issuecomment-673784868. Then I'm not sure how to solve it properly.
Needs benchmarking to measure how well it compresses compared to the cpu tradeoff.
One of the oldest issues 🙂 Users can already apply compression themselves by overriding the replication serialization/deserialization functions. We even have an example in the docs for it, should be...
### Current state We now pass ticks to serializers and send different data to different clients. We just need to add a way to get an old value. ### Component-based...
> Can't we just map to ComponentId? Yeah, that's what I suggesting: map `ComponentId` into our implementation of `BlobVec` (I don't think we can just map it to `OwningPtr`).