Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replication conditions #331

Open
Shatur opened this issue Sep 27, 2024 · 1 comment
Open

Replication conditions #331

Shatur opened this issue Sep 27, 2024 · 1 comment

Comments

@Shatur
Copy link
Contributor

Shatur commented Sep 27, 2024

Sometimes it's useful to replicate not every change, but with some frequency. Maybe we could have some replication conditions to allow this.

@Shatur
Copy link
Contributor Author

Shatur commented Oct 18, 2024

When designing the API, we need to let clients evaluate it.
This could be used by rollback crates. So basically lets say we replicate a component with the policy of "Send once", a rollback crate needs the ability to check "Would this tick even have a valid authoritative value?". Same thing for something like "Only send once per second". Basically if an entity can be confirmed, without that value matching the server, it needs to be possible to check for that. Otherwise we'll see issues like "Well every previous value is confirmed so Position(0, 0, 0) must still be valid, when really the intended way to network it is: send the starting position, use deterministic replication afterwards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant