Start with what a player must identify
An inventory is a place to make decisions, not only a list of beautiful phrases. A player needs to tell what an item is, what matters about it, and whether it differs from a nearby option. A personal title can carry a story if a plain type line remains available. Write those two fields separately before decorating either. A fictional Promiseedge might have the ordinary description “ceremonial blade” rather than asking the audience to infer the object type from its title alone. This gives the poetic wording room to matter while the interface still supports an immediate practical choice.
Choose a naming policy for ordinary objects
Ordinary items can use a type, material, location, or workshop convention. These labels are not a lesser form of creativity. They establish the baseline against which a distinctive title can stand out. If every everyday object calls itself the final light or breaker of worlds, the vocabulary loses the contrast that could make a singular discovery memorable. Write several ordinary entries together and check that they remain distinguishable. Do not invent mechanical differences merely to justify different adjectives. The game’s actual rules should determine what changes in use; the name helps communicate the relevant distinction instead of replacing it with empty prestige.
Give crafted objects an accountable signature
A workshop mark, repair history, or commission reference can distinguish a crafted piece. Choose which of those identities the public label uses and which belongs in an inspection note. A maker’s surname should not be confused with the object’s title or the workshop’s trading name. A small stamp can connect them in the scene. This approach creates stories about work, credit, inheritance, and maintenance without pretending every item needs an enormous origin legend. The studio’s maker-oriented structure is raw material for such a convention. It does not certify a real craft process or establish actual performance, authenticity, or value.
Reserve an individual title for a specific reason
A singular item deserves a name because somebody remembers, uses, repairs, disputes, or chooses it in a particular way. State that reason. A compass that responds to an unkept promise has a narrower identity than a universally powerful navigation device. Show its refusal once, then let the short title preserve the relevant association. A longer recorded form can carry a dedication if the story actually needs it. Do not automatically treat extra words as proof of higher rarity. The distinction should serve a project policy and an observed scene, not a ladder of increasingly unbounded claims.
Keep set, component, and model names separate
A suit assembled by several trades can have one collective commission title while each component retains a plain type and a maker mark. A machine series can have a stable family name and a separate version field. A weapon prop can have an inventory code and a stage nickname. If those levels are merged into one visible string, every revision becomes harder and repeated entries become less distinct. Write the hierarchy explicitly and test a selection list containing several components together. The audience should be able to identify what is shared and what differs without knowing the complete story behind the set.
Use the same object in several textual scenes
Draft an inventory row, a discovery message, a spoken request, and an inscription. Keep the identity linked across them. A long phrase appropriate to a dedication can be shortened deliberately in dialogue, while the plain type label remains visible where identification matters. If an earlier owner used another name, introduce that relationship before a clue depends on it. The story can preserve uncertainty about provenance, but a reader should not accidentally count the same object twice because the author changed the wording without a bridge. Your project register should record each form and the scene in which it first appears.
Do not confuse rarity with safety or real value
The narrative distinction control in the studio changes creative presentation. It does not supply a verified drop rate, price, effectiveness score, collectible provenance, or real material property. A potion, crystal, fictional implant, or weapon title must remain inside its invented context. Avoid borrowing the language of real health guarantees, manufacturing specifications, or financial value to make a name sound important. If a project contains actual factual information, that information needs its own reliable sources and suitable review. An entertaining item label and a professional claim about the physical world are different editorial tasks.
Review a neighboring set with a concrete task
Put five related items in the actual interface and ask which one the described situation calls for. Inspect where a person hesitates and which two names blur. The problem may lie in repeated openings, hidden type information, cramped layout, or names that imply differences absent from the mechanics. Fix the smallest relevant issue and repeat the affected task. A small informal review can reveal a clear obstacle without proving universal usability. Record the observed behavior and the revision rather than claiming the naming policy has been scientifically validated because one reader liked the result.
Write the policy so another contributor can continue it
A useful note might say: “Ordinary tools use function and material. Crafted pieces may add a workshop signature. One-off story objects receive an individual title only when a scene establishes the reason. Keep full dedications out of the quick list.” Add accepted and rejected examples with brief reasons. Then introduce a new item that tests the rule. If it needs an exception, explain what the exception communicates. The purpose is a vocabulary that helps the audience choose and remember, while the richest histories appear where the project gives them enough attention to become meaningful.
Make the next draft your own.
Try the method in a tool, keep a candidate in your notebook, and revise it against your actual project.
A correction or a question about this piece? Contact Drafitlem.