Manually set global last-changed tick about bevy_replicon

[Shatur]

So it's basically pause replication after specific tick? Make sense to me.
I think it should be done globally and once we will have rooms - per room.

[Shatur]

No longer relevant after #16.

[UkoeHB]

This is still relevant, #116 still scans the entire world every tick even if there is nothing to replicate.

[Shatur]

But there is not such thing as last changed tick. I feel like it's something that should be solved on Bevy side. They considering adding change detection on archetype and entity levels.

[UkoeHB]

Right, that's why I said "it is [sometimes] feasible to manually track the last tick where something in the world was modified".

[UkoeHB]

Instead of global last-change tick, we could do TickPolicy::Manual and add a system that can be manually scheduled which resends the last-buffered component updates that haven't been acked (EDIT: acks are tracked per-update message so this works out well).

Since renet uses Bytes, we can just store a copy per client. Very cheap, no need to allocate again.