The fix is to start GlobalGameTimer with network time instead of game time.
Currently, it starts as GetGameTimer() and later gets updated to GetNetworkTime() every 100ms.
This causes problems in the MultiplayerChat component (in the Update function), as it checks if the component started more than 10000ms ago to close it automatically. However, due to the difference between these two times, it closes instantly.
The fix is to start
GlobalGameTimer
with network time instead of game time.Currently, it starts as
GetGameTimer()
and later gets updated toGetNetworkTime()
every 100ms.This causes problems in the MultiplayerChat component (in the Update function), as it checks if the component started more than 10000ms ago to close it automatically. However, due to the difference between these two times, it closes instantly.