[Bug]: bug with Logs being placed into the cart

[Zbig281]

Bug Description

bug with Logs being placed into the cart, that remains unresolved.

Therefore no formal instructions will be made to help with installation, as it is assumed anyone whom wishes to use mods in this section have a certain level of knowlage to install and possibly rectify the mod.

Steps to Reproduce

1. Attach a horse to a Wood Cart.
2. Add wooden logs into the cart – these logs always remain correctly stored when the horse is attached.
3. Detach the horse from the Wood Cart – the previously added logs disappear from the cart.
4. While the cart is detached, add new wooden logs into it.
5. Reattach the horse to the Wood Cart – all logs reappear and stack together: both the logs added while the horse was attached and the logs added while it was detached.

Expected Behavior

Logs placed into the Wood Cart should remain visible and accessible in the cart regardless of whether a horse is attached or detached.
They should not disappear when the horse is detached, and they should not stack or reappear only after reattaching the horse.

Actual Behavior

Logs added while the horse is attached are visible only as long as the horse remains connected.
When the horse is detached, all logs disappear from the Wood Cart.
If logs are added while the cart is detached, they remain hidden until the horse is reattached, at which point all logs (both attached-state and detached-state) suddenly reappear and stack together.

Projects Version

last

Operating System

Other

Additional Environment Details

Dedicated server running LiF:YO with LiFx Projects module enabled.
No other mods affecting movable objects or carriers.
Issue reproduced consistently on a clean server environment.

Relevant Log Output

When using a standard horse cart, the server logs correctly show a carrier lookup:

[LOG] select * from movable_objects where CarrierMovableID = <ID>  
[LOG] Loading cargo from database…

However, when using movable ID 3016 (Wood Cart), no carrier lookup is triggered at all after UnharnessDrop.  
No “select from movable_objects where CarrierMovableID = 3016” entry appears in the logs.  
The engine does not recognize 3016 as a carrier, and the cargo is not materialized.

Screenshots

Additional Context

From log analysis, it appears that object 3016 is not recognized by the server as a valid carrier type.
The carrier check function is never triggered, and no cargo materialization query is executed.
This results in the Wood Cart losing visible cargo whenever it is not linked to a horse.
The issue persists after database refresh, player refresh, and full server restart.

It also seems that the core contains a predefined internal list of carrier-type objects.
Only objects included in this list are treated as valid carriers, allowing the engine to run the correct cargo-handling logic.
To make the Wood Cart behave properly, it would be necessary to understand how this list is defined in the core and add the Wood Cart as a recognized carrier so that the engine processes it correctly.

Acknowledgements

• I have searched existing issues to ensure this bug hasn't already been reported
• I have provided all relevant information to help reproduce and fix this bug

[Mj0ed]

In your additional context, you wrote that it is needed to understand more about how the list is defined in the core.
Do you think this is exposed so this is possible, or is the list not exposed in torque script?

[Zbig281]

I wrote it this way because we don’t know the behavior mechanics of the carrier “horse cart” that the game is initializing… at least for now it’s unknown to me.
I’ve only noticed one thing: the error appears because the wood cart supposedly doesn’t have a carrier assigned.

At first I thought the file Transport.cs was responsible for assigning the carrier, but seeing what happens, the data in that file looks exactly the same as the data in dump.sql, in the table objects_conversions.
To me it seems like it’s only doing a conversion.

I think what’s actually missing is a reference stating that for example ID 3016 is the carrier.

However, I’m not 100% sure about this, not even 80%, because this mechanic is currently unknown to us.