The owner logs out and their pet vanishes or their cart strands a passenger

Things that belong to one player but exist in a shared world need a rule for the moment that player leaves, and the rule differs for a pet, a parked cart and a cart with a friend still aboard. Here is a set that stays consistent through saving.

Why this works

Things that belong to someone should never be left half-owned. Deciding, for each kind, who holds it the moment the owner goes means nobody is dropped or left with a ghost. Saving both outcomes in one write means no crash can leave two copies or none.

When not to use it

Do not use these rules in a game where a vehicle is shared by design, such as a public bus or a team ship that belongs to the whole group. There, ownership by one person is wrong; let the group own it and keep it running.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 46 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "The owner logs out and their pet vanishes or their cart strands a passenger" (read_entry pets-and-vehicles-when-the-owner-leaves) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP