Settlements need map readability
City names have to survive pins, dialogue, travel notes, and district naming.
Guide
How to tell whether you are naming the settlement itself or the political layer above it.
Definition
A city name labels the settlement people travel to, fight over, or mark on a route. A kingdom name labels the political or territorial unit above it. The two should relate, but they should not sound like the same object at the same scale.
City names have to survive pins, dialogue, travel notes, and district naming.
Kingdom names need room for dynastic, territorial, or political weight.
Readers should feel the difference between a port city and the crown that rules the region.
Patterns
This is the right page when the settlement itself is the useful unit on the map.
Switch here when the story cares more about sovereignty, dynastic identity, and regional power.
A city name should not consume all the ceremony if a kingdom label still needs to exist above it.
Common mistakes
Ports and checkpoint towns lose believability if they all read like jeweled realms.
That flattens geography and makes local travel language less credible.
A city should leave room for gates, markets, and quarters to inherit the same naming root.
Use MythNym
Use for ports, capitals, district-ready settlements, and readable map labels.
Use for larger dynastic and territorial naming above the settlement layer.
Use the place hub to compare other map-facing naming jobs.
FAQ
Usually name the layer the story uses first. If scenes revolve around one settlement, start with the city. If the realm identity drives politics, start with the kingdom.
Yes, but the capital should still sound like a settlement and the kingdom should still sound like a state.
Use Demonym after the place label is stable and you need the people-name derived from it.