Lend an item to a character and make sure it comes back, or is lost for a reason

Handing your lantern to a companion is a nice story beat, until the companion leaves, dies or is forgotten and the lantern is gone for ever without a word. This entry tracks borrowed things, separates having from owning for scenes, and settles the loan at each chapter break.

Why this works

Having something and owning something are different questions, and a story asks both. Keeping a lent thing on a written record, with a date it should return by, means it can never vanish silently: it comes back or it is lost, and either way the story gets to say so.

When not to use it

Skip it when the item is needed by the player at every moment, such as the only weapon or key: lending it blocks play. Let the companion use a copy, or have the story take the item away openly instead.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 34 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 "Lend an item to a character and make sure it comes back, or is lost for a reason" (read_entry lend-an-item-to-a-character) 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