Georg Friedrich Schuppe
Georg Friedrich Schuppe
What stopped me so far to implement this feature is not only the problem of "catching up", but mostly the synchronization effort in order to propagate the information that a...
Due to focussing on my studies, I did not start any work related to this feature.
Currently, there is not. Reconnecting or joining mid-game requires multiple things which are not implemented: - all clients have to receive the information of the reconnect - all clients need...
An additional note: how this stuff is propagated relies very much on your matchmaking/lobby architecture, which ggrs does not provide. Maybe reconnecting could be done outside of ggrs and afterwards,...
Thanks for your report! While this would be easy to fix by going from i8 to i32 or comparable, I am very curious how this issue can arise. Usually, when...
Another thought: Since the clumsy settings aren't too extreme (I tried worse both with real connections and in clumsy), could it maybe be the case that one of the clients...
Sending and receiving additional information before and after the match (or even during) might be a very handy feature, e.g. Character / map choices or chat messages during the session....
I think that optionally providing a function for input predictions sounds great.
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...