How to Name Identical Items in an Interactive Fiction Backpack So Players Can Select a Specific One
First decide whether similar items need to be handled individually. Then name them using features the player has already seen and that remain valid when the items move. An item identification table connects first inspection, pickup, return, and renaming, so “the one on the left” does not lose its meaning once it leaves the table.
Introduction
For players to reliably select a specific item among similar objects, its name should refer to a feature of the object itself that has already been revealed. Record its location separately. Two candles might be called the “bent-base candle” and the “notched candle,” and keep those names after being put in the backpack. “The one on the left” only works within the arrangement on the table at that time. First decide whether individual items need to be distinguished, then fill in an item identification table, and finally check the names through pickup, movement, and return.
First decide: does the player need a specific item, or just a quantity?
Group the items as “Candles ×2” only if choosing either one would make no difference to the current action or any planned subsequent outcomes. List them separately if one needs to be given to a particular character, is already lit, or is something the player has a reason to keep. What matters is whether the choice of item has meaning, not how much backstory the author has written for each one.
The following “packing at night” scenario is a fictional teaching example. It is not a real user case, an empirical result, or a record of hands-on testing, and it does not represent DramaFork product features. All names and action feedback in the example are proposed writing conventions.
Two similar candles sit on a table: one has a bent base, and the other has a notch in its side. The player plans to take both, then later return the bent-base candle to the table. This example does not establish any effect of shape on burning; the differences serve only to support a clear choice between individual items. There are also three pieces of thin string that are interchangeable in the example’s later actions, so they are grouped as “Thin string ×3.”
Grouping items makes a list shorter, but gives up continuous tracking of each individual object. If a later action suddenly asks the player to find “the piece of string you picked up earlier,” that individual piece needs to have been kept distinct beforehand. Do not first present the strings as an undifferentiated quantity and then expect the player to remember one particular piece without any basis for doing so.
Separate identifying features from location in the identification table
Choose brief, clear differences from descriptions already presented to the player, then establish full names and short forms. Features should persist where possible and distinguish the items from others of the same kind. “Pretty candle” depends on a judgment, while “candle in the backpack” depends on location. Neither is suitable for identifying an item over time in this example.
The table below applies once both features have been seen. You can reuse it by replacing its contents. The next section covers names to use before the features have been seen.
| Item type | Individual identifying feature | Current name | Usable short form | Conditions for renaming |
|---|---|---|---|---|
| Candle | Bent base, already observed | Bent-base candle | The bent-base one | Review if the feature disappears or a new item creates a naming collision; movement does not change the name |
| Candle | Notch in the side, already observed | Notched candle | The notched one | Review if the feature disappears or a new item creates a naming collision; movement does not change the name |
| Thin string | No need to distinguish individuals in this example | Thin string ×3 | Thin string | Separate a piece if it develops a difference that requires individual handling |
Add location separately in the list, for example, “Bent-base candle: backpack” and “Notched candle: table.” Moving an item then requires only a location update, without making the same object read like a new one. Authors may also use internal identifiers to maintain the correspondence, but players should be able to identify each item using only the visible text.
Short forms must also preserve the distinction. “Candle” is an item type, and cannot default to one particular candle when both are selectable. “The bent-base one” can serve as an agreed short form in this example; a button should preferably use the full wording, “Pick up the bent-base candle.” These are conventions for the text and its intended referent, not a claim that any input system will automatically recognize these expressions.
Keep scene-specific names until the features have been seen
Suppose the opening view shows only the upper halves of the two candles, with both the bent base and the side notch hidden. The list must not reveal those features in advance. Otherwise, the names give the player information the character has not yet acquired, and inspecting the objects loses its purpose.
At this point, the scene could read: “There is a candle on the left side of the table and another on the right.” The available actions would be “Inspect the candle on the left side of the table” and “Inspect the candle on the right side of the table.” These are temporary names with a clearly defined scope. They guide the first inspection and do not become formal names carried across scenes.
This example supplies the missing observation during pickup. When the player lifts the candle on the left, write: “You lift the candle, revealing its bent base. The bent-base candle has been placed in your backpack.” For the other candle, likewise reveal the notch before using “notched candle.” Description, naming, and action feedback now connect, so readers do not have to guess where the new name came from.
If the story requires the features to remain hidden, do not force a reveal during pickup. When the story allows it, the character could tie different markers to the items, or you could postpone actions that require a specific individual item. Simply adding “A” and “B” has a cost, too: if the initial correspondence is unclear, the labels merely turn spatial confusion into a memory burden.
Follow the names through pickup, movement, and return
First, while the table still has its original arrangement, the player chooses “Pick up the candle on the left side of the table.” Use the feedback above to reveal the bent base and add “Bent-base candle” to the backpack list. After the other candle is picked up, the backpack list shows “Bent-base candle, Notched candle,” rather than two entries both called “Candle.”
Second, the player moves the notched candle from the backpack into their hand. The feedback reads, “You take out the notched candle and hold it in your hand,” and the list shows each item’s location separately. The name stays the same. Do not introduce “the candle in your hand” as a lasting short form: its location can change, while the notch in its side still identifies the original object.
Third, the player chooses “Put the bent-base candle back on the table.” Even if it now ends up on the right side of the table, the feedback still reads, “The bent-base candle has been placed on the right side of the table.” The scene lists its full name, the corresponding entry is removed from the backpack list, and the notched candle remains in hand. Returning an item does not restore its old left-or-right identity.
The conventions must also state when old names stop being used. Once the initial arrangement changes, “the one on the left” is no longer an alias for the original object. If a new left-and-right arrangement appears later, interpret it according to the current scene and display the corresponding full names. Do not silently retain the reference established during the first inspection. Where needed, use a transition such as “The candle originally on the left side of the table is now called the bent-base candle.” After this message, stop using the old name in action options.
Check the table’s limits with naming collisions and changing features
Once the table is complete, run through it on paper. If the candles swap places, do their names still identify the original objects? If only one remains in the backpack, does it keep its name? When it is returned to the table, is it mistakenly renamed “the one on the left”? These are proposed checks, not a report of completed validation.
Next, imagine acquiring a third candle that also has a notch. “The notched one” is no longer unique. Show a new, perceptible difference before updating the names—for example, include the location of the notch once it has been explicitly described. Do not merely add a modifier to the new candle while leaving the old short form ambiguously applicable to both.
If the bent part breaks off, do not rename the candle silently. At the moment of change, write: “The bent base of the bent-base candle has broken off. It is now called the broken-base candle.” Update the list and action options at the same time. The old name may serve temporarily during the transition only while it still has a unique referent. It cannot be reassigned to another candle whose base happens to become bent.
This table suits text-based scenes in which players need to keep selecting specific objects. If the objects remain interchangeable throughout, quantities take less effort to read. If the objects cannot be inspected, cannot be marked, and truly cannot be told apart, allow that uncertainty to remain and adjust the required actions. Before delivery, every current name should lead back to one described object, with clear conditions for renaming it and for retiring its old name.
