Releases · gschup/ggrs

29 Jul 18:15

gschup

v0.4.0

Changelog:

spectators catch up by advancing the frame twice per advance_frame(...) call, if too far behind
added frames_behind_host() to P2PSpectatorSession, allowing to query how many frames the spectator client is behind the last received input
added set_max_frames_behind(desired_value)to P2PSpectatorSession, allowing to set after how many frames behind the spectator fast-forwards to catch up
added set_catchup_speed(desired_value) to P2PSpectatorSession, allowing to set how many frames the spectator catches up per advance_frame() call, if too far behind
in SyncTestSession, the user now can (and has to) provide input for all players in order to advance the frame

Assets 2

28 Jul 11:39

gschup

v0.3.0

upped the version count to 0.3.0 since some of the changes are breaking changes.

GGRSError::InvalidRequest now has an added info field to explain the problem in more detail
removed unused GGRSError::GeneralFailure
removed multiple methods in SyncTestSession, as they didn't fulfill any meaningful purpose
removed unused sequence number from message header, fixing related issues
fixed an issue where out-of-order packets would cause a crash
other minor improvements

Assets 2

22 Jul 06:38

gschup

v0.2.5

Changelog:

when a player disconnects, the other players now rollback to that frame. This is done in order to eliminate wrong predictions and resimulate the game with correct disconnection indicators
spectators now also handle those disconnections correctly

Assets 2

20 Jul 14:49

gschup

v0.2.4

Changelog:

fixed an issue where the spectator would assign wrong frames to the input
players disconnecting now leads to a rollback to the disconnect frame, so wrongly made predictions can be removed
in the box game example, disconnected players now spin
minor code and documentation cleanups here and there

Assets 2