The GD-Sync dashboard now provides more detailed statistics for the last 30 days, giving developers better insight into how their multiplayer game is being used.

The dashboard now includes peak concurrent players, peak concurrent lobbies, total lobbies created, and average play time.

A new Player Locations map has also been added, showing the countries your players are connecting from. This provides a quick overview of where your player base is located around the world.

Added player_has_data

Added the new player_has_data(client_id: int, key: String) function as a quality-of-life improvement for working with player data.

This allows you to easily check whether a specific client has player data stored under a given key without having to retrieve the data first.

Connection Timeout

Fixed an issue where the connection timeout was too strict, causing some connection attempts to fail even when a connection could still be established successfully. The timeout handling has been adjusted to provide more reliable connection establishment, particularly under slower network conditions.

Missing C# Properties in Exported Builds

Fixed an issue where PropertySynchronizer would fail to detect C# exported properties when running an exported build. These properties are now correctly recognized and synchronized in exported projects.

Local Multiplayer Shutdown

Fixed an issue where leaving a local lobby would incorrectly shut down the local multiplayer system. Leaving a lobby now properly disconnects the player without stopping local multiplayer functionality.

Local Session Loss on Host Disconnect

Fixed an issue where clients would lose their entire local multiplayer session when the LAN host disconnected. Clients now properly leave the lobby and are kicked from the session without losing their local multiplayer state.

is_host() State

Fixed an issue where is_host() could remain true after leaving a local lobby. The host state is now correctly reset when leaving the lobby.

Failed Local Lobby Joins

Fixed an issue where a failed attempt to join a local lobby could leave the client in a partially connected state. Failed joins are now properly cleaned up so the client remains in a valid multiplayer state.

Invalid Local Lobby Creation

Fixed an issue where attempting to create an invalid local lobby could still occupy the LAN port. This could prevent another lobby from being created afterwards. Failed lobby creation now correctly releases the port and cleans up the local multiplayer state.

Local Player Data Synchronization

Fixed an issue where erasing player data in a local lobby would not properly synchronize the change with other players. Player data removals are now correctly propagated to all connected clients.

Multiple Local Lobbies

Fixed an issue that prevented multiple local lobbies from running on the same PC. Local lobby hosts now automatically select an available port from 42400–42419 instead of using port 8080, allowing multiple local multiplayer sessions to run simultaneously.