FICTIONAL DESIGN STUDY · 6 MIN READ
The Lantern Exchange
A harbor service, a disputed return, and a guild name that becomes a playable decision.
This scenario is fictional and illustrates creative decisions. It does not describe a real project, client, or user study.
The brief
This fictional design study begins with a modest requirement: create an opening quest for a coastal town without a combat encounter. The player should meet a local institution, learn how the harbor works, and make a decision that has a visible consequence. The first draft called the institution the Order of Eternal Light. That title suggested an enormous religious history the opening quest could not support. We wanted a group whose importance could be shown through ordinary work.
The name we chose
The Lantern Exchange is a public lending service. Boat crews borrow lamps for routes whose markers are hard to see in fog. Members clean the lenses, repair the shutters, and record which lamp went where. Exchange implies that something comes back. It also suggests negotiation rather than absolute authority. The name provides a signboard, a ledger, a workplace, and a reason for strangers to speak to one another. Those details make it more useful for this brief than a grand title.
The opening scene
The player arrives at Reedquay carrying a lantern returned on behalf of a passenger from the last ferry. At the Exchange, the clerk finds its number in a ledger written forty years earlier. She does not immediately declare it magical. She checks the hinge, compares the maker’s stamp, and asks which ferry carried it. The current ferry operator recognizes the stamp as one used by her grandfather. She wants the lantern preserved as part of the harbor’s history.
A practical disagreement
The repair keeper has a different priority. Tonight’s fog is approaching, and the returned lamp is the only one with an intact blue shutter. Keeping it behind glass could leave a working route unmarked. The clerk proposes using a modern lamp with a painted cover, but the paint has not been tested in rain. Nobody is a villain. The operator values memory, the keeper values a safe route, and the clerk values a solution she can document.
The player’s part
The player can help test the painted cover against ordinary harbor lights, negotiate a one-night loan of the old lantern, or move the route to the inner landing while repairs are made. Each choice has a small cost: time, an obligation to return the object, or inconvenience for passengers. The scene needs no secret reward for clicking an unexplained button. The objective and consequences are visible before the decision. A quest title such as “Return the Blue Lantern” fits the knowledge available at acceptance.
How the naming system holds together
Reedquay names a place through landscape and work. The Lantern Exchange names a group through its service. The Blue Lantern names an object through an observable feature. The three labels have different shapes and scales, so a journal can refer to them without forcing the reader to decode a single dense paragraph. We rejected “Lantern Harbor” because it repeated the organization’s central noun and made the town and institution too easy to confuse.
What to borrow from the method
Choose an institution that performs a service. Give its name an ordinary meaning that the first scene can demonstrate. Create two reasonable claims on one object, and let the player learn enough to evaluate them. Test the town, group, item, and quest labels together. This is an invented scenario illustrating editorial choices; it is not a report of a shipped game or a claim that players have tested it. Adapt the structure, then replace the objects and obligations with ones that belong to your own setting.
PUT IT INTO PRACTICE
Try the method on a fresh name.
Open the related naming toolCreative drafts. Check suitability and existing uses before publication.