PILEUPBRICKSThe cargo is here, but on the other shore
At the Bent Quay, a wagon arrives to collect a shipment from the Old Steps. The cargo has arrived on time, the receipt is legible and the dockworkers followed their instructions. Unfortunately, the opposite shore also has a landing called the Old Steps. The nickname once worked because each district handled different traffic. A new ferry connection has made both landings part of the same delivery route. Now an apparently precise instruction sends people to two plausible destinations.
A port-city name has several jobs in this setting. It identifies the city on an outside map, distinguishes it from neighboring ports and gives residents a usable form in conversation. It does not need to encode every dock inside the harbor. If you try to solve the two landings by lengthening the entire city name, the local routing problem will remain. This workshop separates the city identity from the smaller addresses that make daily movement possible.
The case is fictional, so you can decide how its harbor operates. The useful discipline is consistency. An estuary, a bay and an artificial basin produce different approach routes and different reasons for a nickname to spread. Choose the harbor shape first, then build the naming problem around its actual geography. The city's atmosphere will follow from those decisions more naturally than from a pile of maritime adjectives.
Start with an arrival sentence
Before generating names, write how a stranger reaches the city. For an estuary: follow the river downstream until the banks widen and the ferry crosses between the two market shores. For a bay: round the visible headland and identify the public landing inside the sheltered curve. For an artificial basin: pass the controlled entrance and continue to the numbered inner quay. These sentences establish what an arriving person can actually observe.
Now insert a trial city name, such as Tidehaven, Saltreach or Roveport. Each is an invented possibility rather than a statement about a historical settlement. Tidehaven suggests shelter and water movement, Saltreach suggests an extent of shore or trade, and Roveport makes its port function explicit. Your choice should survive the arrival sentence without implying a feature that the setting does not possess.
A mismatch can be intentional. An inland city might preserve a name from the period when ships reached its walls. If so, explain how travelers arrive now and let the old term carry history rather than current directions. At the Bent Quay, however, the immediate problem is practical confusion. Introduce the present harbor clearly before adding older layers of naming.
An estuary divides the reference point
In the estuary version, each shore calls its own oldest landing the Old Steps. Residents usually approach from inland, so their unspoken reference point is their own district. Ferry crews approach from the water and hear both forms within the same working day. The nickname is not foolish; its audience has expanded beyond the context that made it sufficient. This explains why the problem appears now rather than generations earlier.
A repair can add a bank identifier, but define the reference carefully. Left bank and right bank need an agreed direction of view. East Steps and West Steps are easier on a consistently oriented map but may be less natural in local speech. You can instead choose stable district names, such as Market Steps and Kiln Steps, if those districts remain recognizable. Test the pair from a boat and from a road before deciding.
Do not make a tide-dependent feature the only confirmation point. A low-water stair or a temporary mudbank may disappear from a newcomer's view at the wrong moment. In the fictional route note, pair the landing name with a durable marker visible on arrival. This is a worldbuilding exercise, not real navigation guidance; its value is showing that the author has considered who can see which landmark.
A bay makes the approach sequence matter
In the bay version, two old stairways lie along the same curved waterfront. The outer landing is encountered first from the sea, while the inner landing is encountered first from the road through the market. Locals say the first steps and believe they are being helpful. The phrase has two meanings because the speakers imagine different starting points. A map can display both locations correctly while the spoken instruction remains ambiguous.
Name the outer landing for a visible district or structure and the inner landing for another. Keep the distinction in the first useful word: Beacon Steps and Market Steps are easier to separate than Old Outer Steps and Old Inner Steps in hurried dialogue. If your city already has a market district elsewhere, choose a more specific anchor. A label that works in isolation can still collide with the rest of the setting.
The case can turn on an outdated entrance. A warehouse gate has moved, but delivery instructions still describe the old road approach. The harbor authority's map is current and the merchant's note is obsolete. Neither map accuracy nor local expertise alone solves the problem. The characters need to discover which instruction actually traveled with the cargo and who will replace it for the next shipment.
An artificial basin has an address hierarchy
In the basin version, the two Old Steps belonged to separate phases of construction. An extension connected the basins, and an older district label was dropped from routine paperwork. The surviving nickname now points to two landings inside one controlled harbor. A useful address distinguishes basin, quay and berth. The city name belongs above that sequence, not inside every individual component.
Numbering can help if it has a stable origin and direction. It can also produce confusion when an extension renumbers existing berths. In your private map, mark where the sequence begins and note whether old numbers remain visible. A delivery to Basin Two, Quay Four is not necessarily clearer than a named landing if residents still use numbers from an earlier plan. The story should identify which scheme each document follows.
Give the basin operator a practical reason to resist immediate replacement. New signs take time, printed forms are already in circulation and crews may return after months away. A transition notice that pairs old and new addresses for a defined period is more believable than a decree that everyone instantly learns. It also creates work for characters who can carry updated instructions to people outside the official office.
Build a family of labels without repeating one stem
Suppose the city is Tidehaven, its district Tideward, its dock Tidepier and its ferry Tideboat. The shared stem shows affiliation, but a spoken delivery note becomes a chain of almost identical sounds. Keep Tidehaven for the city and choose independent local anchors: Kiln Ward, Market Steps and the Copper Ferry. The labels now tell the reader what scale of place or service is being discussed.
A regional adjective is optional. Tidehaven trade may read more naturally than a newly coined Tidehavenian form. Use the form in an ordinary sentence before accepting it. If it makes a warehouse notice cumbersome, residents may say the city's merchants or people of Tidehaven instead. A naming system becomes more believable when it permits ordinary phrasing rather than forcing every noun through the same suffix.
Older labels can survive where they help a particular audience. Dockworkers may still say Old Steps while a public sign reads Kiln Steps, formerly Old Steps. Introduce the equivalence clearly once. Later dialogue can use the nickname without confusing the reader. The goal is not to eliminate local language; it is to provide a bridge between local knowledge and public instructions.
The rejected draft: Grand Salt Tide Harbor
The first attempt at solving the confusion renames the city Grand Salt Tide Harbor and prints the new title across every receipt. It looks distinctive on a banner, but the destination line still says Old Steps. The wagon continues to reach the wrong shore. This failed revision is useful because it distinguishes branding from addressing. A city can have a memorable name and an unusable delivery system at the same time.
The second attempt retains Saltreach as the city name and changes the destination field to Kiln Steps, western market shore. A clerk reads the instruction aloud to someone who has never visited. That person can point to one location on the sketch map. The revised instruction solves the immediate ambiguity without requiring residents to abandon every familiar label or learn a new civic history.
A third pass removes information that will soon be stale. If the western market is relocating, naming the shore after it may only postpone the problem. Select an anchor whose expected lifetime suits the document. A one-day delivery note can use a temporary staffed post; a city map should prefer a persistent district or landmark. Choosing the right timescale is part of naming well.
The people behind an address change
The warehouse keeper wants receipts that can be checked quickly. The ferry crew wants calls that remain distinct over distance. The market residents want their district recognized instead of being described only from the opposite bank. The person paying for replacement signs wants to know how long the new system will last. These interests can conflict without anyone becoming a cartoon villain.
Let one dockworker explain why the old nickname matters. Perhaps the steps were rebuilt by neighbors after a storm, and the name preserves a story of shared labor. The official replacement need not erase that history. A small inscription or a paired local form can keep it visible. What cannot remain is the assumption that every arriving driver already knows which version is intended.
The city's governance affects who can authorize a change, but ordinary adoption also matters. A surveyor can alter a map without changing the words merchants put on orders. A neighborhood meeting can agree on a name without updating the harbor register. Show at least two of these channels meeting. The revised city feels inhabited when information has to move through people, forms and signs.
Three ways to resolve the misplaced shipment
An investigation traces one shipment from the sender's order to the receipt at the wrong landing. At each handoff, copy the destination exactly. The decisive clue may be the loss of a district name when the instruction was shortened. This branch produces a precise account of the failure. Its cost is time spent with paperwork while the cargo remains unavailable to the intended recipient. The next scene asks who will pay or work to move it.
A negotiation brings representatives of the two landings together to agree on public labels. They can retain both local nicknames while adopting distinct names for shared documents. This branch produces an accepted convention, but it depends on communicating the change to absent users. The next scene follows a returning crew with an old chart. The agreement is tested by whether the crew can still arrive without being blamed for outdated information.
An improvised response places a dispatcher at the ferry crossing with a list of today's expected cargo. The shipment reaches its destination, and the city gains time to revise the forms. The dispatcher has a finite shift, so the solution includes a handover or end time. The next scene concerns the permanent address record. Leaving the dispatcher on duty forever would hide the cost rather than solve the problem.
A port on the page, at the table and in a quest
For prose, reveal the duplicate nickname through an ordinary exchange. The driver asks for a crate; the dockworker points to the receipt; both realize they mean different steps. A glimpse of the opposite shore can make the geography legible before anyone explains the naming history. Save the wider civic argument for the characters who have a reason to attend it. The first chapter needs a readable problem more than a complete harbor gazetteer.
At a tabletop session, give players a sketch with the two landings and one crossing. Tell them which labels appear on the receipt and which they hear from residents. They can then choose whether to inspect records, speak to crews or move the shipment. Do not punish a player for failing to infer a distinction the map never showed. The puzzle is about comparing available information, not guessing an author's private geography.
For a game interface, keep city, district and landing in separate journal fields when the distinction matters. A map marker should point to the location the character actually knows, with uncertainty indicated if two destinations are plausible. Updating the journal after clarification gives the naming decision a visible consequence. The player should be able to tell why a route changed rather than seeing a marker jump without explanation.
Use the examples as working destinations
Write Lanternporthaven at the top of a delivery note, then add a separately named landing below it. This candidate works if a reader immediately recognizes the larger place and the smaller destination. Reject it when its opening duplicates a nearby port already central to your map; that confusion will recur before the local dock problem even begins.
Try Glen Keelwardhollow in an arrival announcement aboard the ferry. Listen for where a speaker naturally pauses. A two-part name can be memorable, but an awkward pause may make the first part sound like an instruction. Compare the announcement with your ferry's own name before deciding that the city label is clear.
Place Elm Lanternportdale on the oldest surviving harbor plan. This candidate can support a historical mismatch if you deliberately explain what changed. Keep the present route notes accurate even when the old name preserves a vanished shoreline. History is useful texture; it should not make every newcomer unable to find the city.
Use Tidehollow in a merchant's ordinary sentence about tomorrow's collection. If you keep shortening it, record the short form and test that against nearby districts. The everyday label deserves the same attention as the full map name because it will appear in much more dialogue.
Compare Tideport with the other four after choosing estuary, bay or basin. Keep the candidate whose implied geography and spoken form support the setting you actually drew. A beautiful harbor name that requires a different coastline belongs in another project, not in an explanation added solely to protect the spelling.