newlondor
Newcomer
How on earth can we fix the multiplayer latency issue for non host players? Especially in dungeons.
My friend & I were playing multiplayer games, long story short there has been latency for the non host players in the 1.4 verstion, such as taking longer to pick up woods from a fallen tree, monster doesn't get knocked back and unable to pick up items, etc. This issue is especially prevailing when we were at the dungeons. We wanted to try everything we can to fix this, since the 1.5 update added many new dungeon areas.
Yesterday it's been working tremendously well. We pick up tree branches at lightening speed, and mine cavern has some issues but still playable if the fight were not too intense. However today when we moved on to the skull cavern, the issues came back again and make it once again unplayable. Either it's the 1.5.1 update or just pure luck? Either way we were excited for one day then fell back to dissapointments again...
Is this issue addressed by the devs at all? I navigated many posts mentioning this issue but none has offered a solution, Is there any fix or workaround solution for us?
My friend & I were playing multiplayer games, long story short there has been latency for the non host players in the 1.4 verstion, such as taking longer to pick up woods from a fallen tree, monster doesn't get knocked back and unable to pick up items, etc. This issue is especially prevailing when we were at the dungeons. We wanted to try everything we can to fix this, since the 1.5 update added many new dungeon areas.
Yesterday it's been working tremendously well. We pick up tree branches at lightening speed, and mine cavern has some issues but still playable if the fight were not too intense. However today when we moved on to the skull cavern, the issues came back again and make it once again unplayable. Either it's the 1.5.1 update or just pure luck? Either way we were excited for one day then fell back to dissapointments again...
Is this issue addressed by the devs at all? I navigated many posts mentioning this issue but none has offered a solution, Is there any fix or workaround solution for us?
Last edited: