See title, you get into zone but then you are practically silenced. The EQStream layer is functioning but the packet layer is not cause eqs was closed/disconnected.
See title, you get into zone but then you are practically silenced. The EQStream layer is functioning but the packet layer is not cause eqs was closed/disconnected.
CombatProcess was deadlocking going into KillSpawn -> dead_spawns - reason being MSpawnList was already locked and we try to lock it again in RemoveSpawn
CombatProcess was deadlocking going into KillSpawn -> dead_spawns - reason being MSpawnList was already locked and we try to lock it again in RemoveSpawn
image refererade till detta ärende från en incheckning 4 år sedan
image
See title, you get into zone but then you are practically silenced. The EQStream layer is functioning but the packet layer is not cause eqs was closed/disconnected.
Looks like ZoneServer connected_clients is 0... so we aren't processing the Client->Process();.. only the lower layer EQStream
CombatProcess was deadlocking going into KillSpawn -> dead_spawns - reason being MSpawnList was already locked and we try to lock it again in RemoveSpawn