Start with three forces, not a complete dictionary
A useful world vocabulary starts with recurring causes. Choose what supports daily life, who gives public names, and what earlier use remains visible. In an invented river region, repairs and transport might support the economy, residents and route offices might compete to label places, and an old orchard might survive in street names. Those forces do not require every word to repeat. They explain why a newly invented district belongs to the same setting. Start with one small region that the audience will actually encounter. A continent-wide list created before the work has a scene may conceal how little of the naming logic is useful in practice.
Give different entities different structures
People need spoken forms and social relationships. Places need scale and navigation. Objects need a readable type and a reason to be distinguished. Groups and story titles need a public purpose or question. Write one structural convention for each rather than assigning the same suffix everywhere. A courier can have a short personal name and an earned byname; a harbor can use a work image and a place word; a tool can retain its plain type beside a workshop mark. The related material culture connects them, while the forms help the audience recognize which kind of thing a sentence refers to.
Draft a one-page naming bible
Use a compact record with headings for recurring images, personal forms, place scales, object labels, institutions, and exceptions. Under each heading, include a rule, two accepted examples, and one rejected example with a reason. “Do not begin every location with Copper” is less useful than “Use trades for working districts; preserve former land uses only where the scene leaves a visible trace.” The positive rule helps another writer create a new place. The rejected example shows where an attractive candidate failed. Keep the document small enough to use while drafting rather than a ceremonial reference nobody can maintain.
Design ten labels as a connected set
Create two characters, three places, two ordinary objects, one singular object, one group, and one quest. Put them into a short arrival scene, an inventory, and a map legend. The goal is not to make the list uniformly beautiful. It is to see whether a reader can distinguish the roles while sensing a shared world. Mark repeated openings, identical endings, and names that imply another entity type. Change the set before expanding it to dozens of entries. A small working network gives you better evidence than a large disconnected catalog of attractive words with no planned relationship.
Write an exception with a visible cause
A glass-and-light workshop title might feel out of place in a district of old ferry names. It can belong if a newer institution deliberately breaks the local convention and the work shows that difference. An invitation, sign, or disagreement can establish the cause. Do not create a hidden historical explanation merely to rescue every random candidate. Some exceptions add meaning; others are editing problems. Record who chose the unusual form, what residents call it, and the scene that connects those labels. A useful exception increases the audience’s understanding of the world instead of making the naming system seem accidental.
Let different communities retain their accounts
An official route office may use a newer district title while residents retain an orchard name. Neither form needs to be erased to make the map readable. Link them explicitly, then let the difference reveal memory and authority. A small address note or ordinary correction can do that work. Be cautious about treating an outsider’s label as everybody’s original self-description. Your invented communities should have room for individual variation as well. The name bible records perspectives; it should not reduce a whole people to one sound, temperament, occupation, or moral quality simply because a tidy system is easier to list.
Keep references stable while display words evolve
In your own project, identify the same entity consistently even when you edit its visible name. Separate internal references, display forms, earlier names, and search aids where the project’s technical setup allows. This is an editorial principle rather than a claim about a particular game engine’s API. A changed city label should not accidentally split one location into two narrative identities. Record the forms that remain intentionally in dialogue and the forms that should disappear. When collaborators join, give them the reason for a name and a scene example, not just an isolated cell in a spreadsheet.
Use the tools as controlled experiments
Choose one studio category and hold genre, background, and sound settings steady while comparing the subject-specific directions. Save only candidates that serve the same brief. Then generate a neighboring entity using the shared material culture but a different structure. The same seed helps reproduce a batch under the same data version; it does not guarantee that results across separate tools form a complete coherent language. The connection still comes from your selection and revision. Export the working reports, add project-specific evidence, and keep final edited names in the naming bible rather than assuming every generated interpretation must enter the finished work.
Maintain the system through actual changes
Return to the bible after a new chapter, region, or collaborator exposes a gap. Add a short revision note explaining what changed and why. Avoid rewriting the rules to make every past draft appear inevitable. A useful system can acknowledge that an early place was renamed, an intended clue changed, or a long formal title became impractical in subtitles. Check the affected set again: map, dialogue, inventory, and translated forms when available. Consistency is an ongoing relationship among those surfaces. It should help the audience inhabit the work, leaving space for personal, local, and historical differences to carry meaning.
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.