Georg Friedrich Schuppe

Easing the trait bounds on `Input` is generally good, we just have to check if this remains sound. If you are willing, you could give it a try. PRs are...

The constraints on the data come mostly from [the compression algorithm](https://github.com/gschup/ggrs/blob/main/src/network/compression.rs) being used. If your usecase does not fit the restrictions directly, you can always serialize your inputs outside of...

This [input encoding example](https://github.com/gschup/ggrs/blob/1083340008e089428ba795bb02c0ad0252f0a700/examples/box_game/box_game.rs#L257) is from a much older version of GGRS, but the main idea holds: Either use an u8/u16 where each bit represents a button being pressed or...

GGRS was built with the assumption that each client sends their inputs each frame (e.g. button inputs from a controller) and that nothing else is necessary to keep the gamestate...

So I wonder what the actual issue here is: - Lack of a generic message broadcast API? If so, should those messages be reliable or unreliable? - ggrs taking ownership...

Hi, thanks for the feature request! I was unable to replicate a crash with `max_prediction` set to 1, the p2p example works for me. I was able to replicate the...

So far, I was not able to reproduce a crash with the p2p example with two players and `max_prediction` set to 1 when disconnecting one peer. Please let me know...

PR #79 will enable lockstep behaviour without any predictions.

Sorry for not responding until now. Thanks for the PR and special shoutout to all the test code you wrote! 💪 I will take a look, see how it interacts...

Hi! thanks for posting this bug report. Sorry for not responding so far. I have just posted a PR that slightly alters the logic for handling inputs. I am not...