Inventory in AI Stories Without an Item Screen

Inventory in AI stories is a record rather than a screen. A narrator writing each scene live still has to know what you carry, where you left everything else, and what state each object is in; it just keeps those facts in a structured record and mentions an object when the scene calls for it. The list exists — it has stopped being furniture on the page.

• An object needs three facts to stay real in a story: what it is, where it is, and what state it is in.
• In Inform, containers and supporters have a default carrying capacity of 100 items, and a person’s carrying capacity means the maximum number of items that can be carried at once.
• Inform’s documentation says that when the player has only limited carrying capacity, “play is likely to be tiresome”, and supplies a holdall that stows surplus items automatically.
• In the Zork I source, a light wound cuts the player’s load allowance by ten and a serious wound by twenty, so what you can carry depends on how hurt you are.
• ink keeps room contents in lists, so a champagne glass left in the hallway is described from the hallway and not from the player.

What does inventory in AI stories actually track?

Three facts for every object, and a fourth if the story is any good. Identity: the brass lantern, not a lantern. Location: your left hand, the planks of the bridge, the bottom of the river. State: lit, cracked, half-empty, borrowed. The fourth is provenance — who gave it to you and what you said in return — and it is the one that makes an object worth mentioning again.

A narrator handed those four facts can write the lantern into the next scene unprompted. A narrator working only from the transcript has to find the lantern in earlier prose, which holds while the passage is still in view and stops holding once the story runs long. The failure shows up as forgetfulness about objects, and it is the error readers catch fastest.

A grid of item slots is a game’s answer to the problem; a mention inside a sentence is a book’s. Whether interactive fiction is a game or a book is still argued over, and inventory is the clearest place to watch both answers work on the same question at once.

Why did text adventures count what you carried?

Because a parser needed a test it could run. “Open the door with the brass key” has to fail when you are not holding the key, and the cheapest way to settle that is a list of what you hold. Limits arrived afterward, for reasons of their own, and they were always the contested part.

In Inform, every container and supporter has a carrying capacity, which defaults to 100 items. A person has one too, where it is “interpreted to mean the maximum number of items which can be carried at once”. Graham Nelson’s documentation is candid about the cost of using it: “When the player has only limited carrying capacity, play is likely to be tiresome.” It then offers a player’s holdall, a bag that quietly takes surplus items whenever your hands are full.

Zork I is blunter. In its source, the player’s load allowance drops by ten when a fight leaves a light wound and by twenty for a serious one, then recovers ten at a time while you heal. Carrying capacity there is not a backpack size, it is a body — a better idea than most inventory screens have had since, and it still needed a number to express.

What the number was standing in for

Weight, bulk, free hands, and the fact that someone crossing a rope bridge with a lantern, a sword and a sack has made a choice. Prose can state all four directly. “You hook the lantern on your belt, because both hands are about to be busy” does the work of a capacity check and reads as a sentence, which is the trade a live narrator makes.

Where does a dropped lantern go without an inventory screen?

Into the room. An object’s location is a property of the object rather than a slot on your character, which makes “drop” a change of owner and not a deletion. ink models this plainly: its documentation keeps room contents in lists — VAR HallwayContents = (Robin, champagne_glass) — and describes a place by testing what its list holds, so a glass abandoned in the hallway is described from the hallway.

The same rule has to hold for an AI narrator, and it only holds if the record names a place. An object dropped to nowhere has been thrown away by the story without anyone deciding to. The test is not whether the narrator knows you no longer have the lantern; it is whether it can tell you which plank it is lying on three scenes later. That is also what makes continuing an AI story later feel like returning to a place rather than restarting one.

What goes wrong when objects live only in the prose?

Three failures, and all three are bookkeeping rather than writing. Each one has the same cause underneath: a fact created in a sentence and stored nowhere afterward.

Failure you notice	What caused it	What a record fixes
Two of the same knife	The narrator introduced an object it had already given you	One entry per object, kept by identity
An item back in your hand	The drop was described but never written down	Location updated on the turn it changes
A gift that vanishes	The passage naming it fell out of the narrator’s view	The fact outlasts the paragraph that made it

Duplication is the giveaway, because it is the one no reader can explain away. A second identical knife teaches you something unwelcome about how the story is being made, and once you have seen it you start watching for it, which is the end of the reading.

Hidden objects are the hard case. The record has to hold what you have not found yet without that knowledge leaking into the prose, which is a harder discipline than tracking a lantern and worth its own treatment — we wrote it up in how secrets are kept in interactive fiction. The principle is the same: the story knows more than the page shows.

How to carry things on purpose in an AI story

Name objects, and say where they go. A narrator can only record what your move gives it, and most readers give it less than they think.

• Name it when you take it. “I take the brass lantern” creates an entry. “I grab what I can” creates nothing a narrator can hold on to.
• Say where it goes. On your belt, in the sack, under your coat. A location survives longer than a possession.
• Say when you part with it. Hand it over, leave it on the altar, throw it in the river — in your own move, out loud, rather than letting it drift out of the story.
• Ask rather than assume. What you are carrying is a question you can put to the narrator without spending a scene to find out.
• Write it down yourself when it matters more than the story knows. A reader’s note is the strongest form an object fact can take.

Fabledrift, an interactive fiction app for Android, has no inventory grid and no item screen. What it has instead is a story journal showing what the narrator remembers, and notes you can write yourself — when a note contradicts the story record, the note wins. Memory is never a paid feature here: every reader gets the whole record, because a story whose objects go missing is not worth reading at any price.

What a lantern is for

An object in a story is a small promise. It was given to you by someone, or taken from somewhere it belonged, and both of those facts come due later. That is why provenance matters more than weight, and why a story that tracks objects well feels less like an accounting system and more like a world with a memory of its own.

Inventory in AI stories ends up smaller than the screens it replaced and larger than it looks. No slots, no capacity arithmetic, no sorting by weight — and, if the record is kept honestly, a lantern still burning on the third plank of a rope bridge you walked away from a week ago, exactly where you set it down.

Sources: Graham Nelson’s Writing with Inform, inkle’s Writing with ink documentation, and the Zork I combat source.