Route node
route nodes, ports, districts, and market towns need labels that survive maps, travel notes, and spoken directions.
atlas and Setting Hub
label route nodes, realms, venues, and regions with enough variation to support maps, travel, and local identity.
atlas Builder
Use these tools when you are labeling fantasy locations by atlas layer: route node labels for route nodes, polity labels for realms, demonyms for inhabitants, and venues for venues inside the world.
Use when the label must work as a playable destination: port, capital, district anchor, route node, or frontier stop.
Use when sovereignty, border politics, dynasty, crown identity, or territorial scale matters more than the route node itself.
Use when travelers need a memorable venue inside the world, not another atlas-scale label.
Use after a source location is stable and the next job is labeling residents, adjectives, or local identity.
Scale Axis
location pages overlap on vocabulary, so the hub should decide scale first: destination, state, resident form, or venue.
route nodes, ports, districts, and market towns need labels that survive maps, travel notes, and spoken directions.
Realms, crowns, marches, and dominions need words that carry sovereignty, border history, and institutional weight.
Resident labels and venues show how people talk about a location after the atlas object already exists.
Counterexamples
A location hub should catch scale errors before they create route node pages that read like polity pages.
Keep local labels practical unless the town is meant to be a ceremonial capital or mythic seat.
Create the resident form after the source location is stable so the root does not have to be reverse-engineered.
Give venues smaller sensory hooks such as animals, lanterns, meals, owners, or road conditions.
Cross-tool worked example
A route feels more real when each label solves a different atlas layer instead of repeating one location description.
A caravan guide gives the route a human memory anchor without stealing atlas-scale language.
The route node is practical and directional, built around a crossing travelers can understand.
The resident adjective lets dialogue describe guards, bread, and dialect without repeating the route node label.
The venue is local, sensory, and smaller than the route node, which keeps scale readable.
atlas Routing
Pick the tool that matches the layer of your world atlas you are labeling: broad location idea, route node, realm, social identity, or a specific venue players will revisit.
route nodes
Start with route node labeling when you need readable route nodes that can anchor routes, quests, trade hubs, or faction strongholds on a atlas.
Realms
Choose polity labeling when the label has to carry sovereignty, dynastic weight, or regional identity across borders, wars, and political history.
Residents and venues
Open Resident label when you need terms for the people of a route node or polity, then use Venue for the memorable in-world stops travelers will actually mention aloud.
atlas Layer Comparisons
Most location labeling problems become easier when you decide whether you are labeling the atlas pin, the state above it, the people who live there, or the venue travelers remember inside it.
Use this hub when the query is broad fantasy location labels or location labels and the atlas layer is not clear yet. Move into route node, polity, Resident label, or Venue once the object is explicit.
route node labeling is for ports, capitals, districts, and route node hierarchy. polity labeling is for crowns, borders, dynasties, and political scale above the route node.
Use route node when the problem is the location label itself. Use Resident label after the location exists and you need the resident identity, adjective form, or people-label.
route node labels should anchor roads and atlas readability. Venue labeling is for one memorable venue inside the route node once the broader geography is already stable.
Worldbuilding Notes
Use the location category when your setting needs geography, route node hierarchy, and travel logic. These tools are meant for capitals, border towns, venues, polities, and regional labels that must feel like they came from the same atlas instead of from unrelated random pages stitched together after the fact.
This category covers every major fantasy location type: route nodes, polities, venues, inns, villages, forests, mountains, rivers, and mystical landmarks. Each page uses location-specific patterns so capital route nodes, roadside inns, and distant ruins do not all sound alike.
Dial in bright, cozy, grim, or imperial tones to align labels with the mood of your setting and story era.
Use the same cultural style for related locations to create believable geography. Nordic, Celtic, Eastern, and other presets help nearby regions share linguistic patterns without making every atlas label feel identical.
location labeling FAQ
This category is for locations that define movement through a world: route nodes, polities, venues, villages, and other landmarks with social or geographic function. The outputs change by location type so a capital, roadside inn, and frontier route node do not all read like the same labeling style.
Use the same cultural style for related locations in your world. If your realm leans Nordic, keep nearby route nodes and towns in the same phonetic family. MythNym includes Nordic, Celtic, Eastern, and Desert-inspired presets to help regions feel connected.
Yes. They are most useful when you are labeling regions in clusters instead of one page at a time. If your atlas needs capitals, venues, and border route nodes that feel related, this category gives you the raw material to keep that hierarchy coherent.
Adjacent World Layers
Build heroes, villains, dynasties, and NPC casts that sound like they belong to the same world.
5 tools
Forge names for relics, weapons, factions, and artifacts that carry history instead of sounding procedurally generic.
2 tools
Create competitive handles, readable IGN ideas, and platform-safe identities that still have personality.
3 tools