Per component replication sendrate

[mirsella]

bring back SendRate::Periodic (or equivalent) to be able to modify the replication send rate per component.

https://discord.com/channels/691052431525675048/1090432346907492443/1457761783791095828

mirsella
—
4:44 PM
hey i was using SendRate::Periodic(TICKRATE * 2), to replicate update for a specific component only every 2 seconds, how to do that now ? PriorityMap is per entity, not per component from what i understand ?
Shatur
—
4:59 PM
This didn't work properly. First, if you lose the update, we didn't resend on the next update. And since the tracking logic was per-entity, it sometimes might be incorrectly considered as acked.
We currently have accumulation which does work as you expect, but it's per-entity.
After recent changes I can re-introduce it per-rule 🤔
(We now track changes per-component as we should've)
mirsella
—
5:15 PM
that would be useful thanks :) my use case is for the position component of troops, which is updated on both server and client so i dont have to repliate to save bandwidth, but just updating every few seconds to re sync the position if any desync happened.
i guess in the mean time i can manually sends the troops position via an event every few seconds
Shatur
—
6:15 PM
Yeah, I think it's a reasonable workaround.
Could you open an issue, so I won't forget?