UkoeHB

@davidpdrsn to do that I'd need to reimplement this crate. Which is possible, I can just copy paste, but then we would both be maintaining the same code.

This issue isn't about controlling the API, it's about updating this crate to be in line with the upstream project, which has `ConnectionNotUpgradable` and implements `Default` on rejection reasons. As...

This proposal supersedes #47. Inactivity throttling can be implemented on top of the priority interface. #47 proposed throttling updates based on how old an update is. That way you can...

Note for later: `bevy_replicon_attributes` would incorporate this by assigning a priority modifier to client attributes. Then entity priority for a client would be computed from their visibility condition + client...

It looks like [type_name](https://doc.rust-lang.org/std/any/fn.type_name.html) is also not stable.

Resource-based sounds better. Leads to better memory management as entities are spawned and despawned. > Bevy exposes [Resources](https://docs.rs/bevy/latest/bevy/ecs/storage/struct.Resources.html), but doesn't provide a way to insert a new resource. Can't we...

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

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

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...

@tevador can you review?