Jump to content

Cargo ship crates appear at world origin after server restart

Pending 2.4.6
myxamo

By myxamo,

myxamo

myxamo 1

Posted

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?

 

image.png

Customers

Everything customers need to manage purchases, support, and discover services.

Providers

Quick access to the tools creators use to manage files, support, and earnings.

Resources

Docs, support resources, and tools to help users and creators move faster.

About Us

Codefling is the largest marketplace for plugins, maps, tools, and more, making it easy for customers to discover new content and for creators to monetize their work.

Downloads
3.1m
Total downloads
Customers
12.1k
Customers served
Files Sold
172.1k
Total sales
Payments
3.7m
Processed total
Customer Reviews 150 verified reviews 3.7
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.