HarborEvent 2.4.6 appears to have a compatibility issue with the current Rust server version.
The plugin sets Cargo.enableSaving = false and disables saving for the ship’s existing child entities immediately after spawning it. However, the current Rust CargoShip.SpawnCrate method creates crates with enableSaving = true, and HarborEvent’s SpawnCargoCrate handler does not disable saving for crates spawned in subsequent loot rounds.
This leaves saved crates referencing a ship that is not included in the save file. After a server restart, the crates appear near world origin (0, 0, 0), with their ship-local coordinates interpreted as world coordinates.
We found 30 crates in a .sav file referencing the same missing parent entity. Runtime logs also confirmed that affected crates remained near world origin without a parent after loading the save.
Could you update HarborEvent so that all crates spawned on its non-persistent cargo ship, including subsequent loot rounds, are excluded from saving?