You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of 014fd15, bevy_backroll is now saving the provided state without any hashing/checksum. This could lead to silent desyncs as no checksum checks will fail in these cases. We should look for a generic way of handling this without reintroducing the Hash bound on Config::State.
The text was updated successfully, but these errors were encountered:
A jank way we can do it is maybe giving all possible data a unique id? So like, hitbox transform is 25 or something. And then we add it all together for a checksum? That probably wouldn't work though...
Perhaps we could introduce a BackrollChecksum trait, which is a weaker version of the Hash trait that is automatically implemented for objects that implement Hash, but allows us to extend it to generate checksums for common bevy data structures that are not covered by Hash.
As of 014fd15,
bevy_backroll
is now saving the provided state without any hashing/checksum. This could lead to silent desyncs as no checksum checks will fail in these cases. We should look for a generic way of handling this without reintroducing theHash
bound onConfig::State
.The text was updated successfully, but these errors were encountered: