DockingPort syncing fix: the server didn't take into account that the IDs of the hulls created between docking ports may change during loading if another sub has an entity with the same ID. The clients would still use the old ID, which lead to syncing issues such as client-side fires inside docking ports (for example in HSE Kullervo Carrier).
This commit is contained in:
@@ -717,12 +717,12 @@ namespace Barotrauma.Items.Components
|
||||
{
|
||||
msg.Write(dockingTarget.item.ID);
|
||||
|
||||
if (hullIds[0] != null && hullIds[1] != null && gapId != null)
|
||||
if (hulls[0] != null && hulls[1] != null && gap != null)
|
||||
{
|
||||
msg.Write(true);
|
||||
msg.Write((ushort)hullIds[0]);
|
||||
msg.Write((ushort)hullIds[1]);
|
||||
msg.Write((ushort)gapId);
|
||||
msg.Write(hulls[0].ID);
|
||||
msg.Write(hulls[1].ID);
|
||||
msg.Write(gap.ID);
|
||||
}
|
||||
else
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user