Cave Network Name Generator

Two arrivals, one place

The eastern survey team reaches a chamber where a pale band crosses the ceiling. Their sketch labels it Cavarel. An hour later, a guide arrives through the passage beside the stream and unfolds a map headed Tunnarel. Both parties recognize the broken shelf near the entrance, but each initially thinks the other has named a neighboring chamber. The surveyor draws the two approach lines on one sheet. They end at the same point. What looked like a dispute about two destinations is a confusion between a junction and the route used to reach it.

For a fictional cave network, that distinction gives naming a practical purpose. A junction is a place where passages meet. A route is an ordered journey through several places. The same junction can belong to several routes without becoming several chambers, and a route can change while familiar junctions remain. Build the map around these relationships before choosing a grand title for the entire underground region. Otherwise, beautiful names may leave readers unable to tell where the characters are or what changes when they turn back.

Cavarel on the chamber wall

Cavarel can be pronounced KAV · ah · rel. In this invented surveying tradition, it suggests the meeting of separate passages beneath one roof. Tunnarel, pronounced TUN · ah · rel, suggests a named line of travel through the tunnels. These meanings are fictional associations for the example, not claims about a historical language. Their shared ending can imply that both entered the current map during the same survey, but the shared sound should not conceal their different functions.

Try a more contrasting alternative, Dovren, for the stream approach. A traveler hearing Cavarel and Dovren is less likely to mistake one for a hurried version of the other. Keep Tunnarel if the relationship between the survey terms matters to your story, but show its route role explicitly. A fourth candidate, Seln, can name the eastern entrance. The short entrance name works well in dialogue, where a character may need to say which side they used without reciting the entire title of the network.

No candidate is automatically best because it is longer or more ancient sounding. Choose according to the information readers need at that moment. An atlas heading, a spoken destination, and a route description are different jobs even when they refer to connected geography.

A diagram that makes the contradiction disappear

Place Seln at the right edge of a small fictional map and the stream entrance at the lower edge. Draw both passages toward Cavarel. From Cavarel, draw a third passage toward a storage gallery. Label the chamber once. Put the approach names along their respective lines rather than inside the chamber. With that arrangement, the eastern team's Cavarel label and the guide's Tunnarel heading can both be correct without referring to separate places.

The map also needs a declared viewpoint. One field sketch may place the entrance at the bottom because its maker drew the route while walking inward. Another may follow a fixed page orientation. Turning a sheet to compare them does not change the cave; it changes the reader's frame of reference. Let the characters find a shared landmark before joining the sketches. The pale ceiling band and broken shelf provide two observations, while the surveyor's enthusiasm alone provides none.

This is a fictional map-design exercise for writers and game makers. It is not a guide for navigating real caves. Keep the imagined spaces legible enough for the audience to reason about the scene, and leave real exploration practices outside the naming tool's claims.

Nerin and Oss discover what they assumed

Nerin, the surveyor, has been using junction names as headings because the current project records places where teams exchange measurements. Oss, the stream guide, heads each sheet with the route that clients request. Neither habit is inherently defective. Nerin's sketch answers where the meeting happened. Oss's sheet answers which journey the client purchased. Their disagreement began because both treated the heading as though it answered the same question.

Give each person a reason to resist changing their paperwork. Nerin must deliver a set of chamber records to an archivist who expects a consistent order. Oss has already taught several visitors the stream route's familiar name. A complete replacement would create another round of confusion. They can instead add a short field identifying the other kind of information. The junction record gains approach names; the route sheet gains the junction label at the place where the paths meet.

The characters' relationship changes when they describe their actual readers. Nerin has imagined a future map compiler, while Oss has imagined a visitor returning after several months. Once those readers become visible, the disagreement stops being a contest over who knows the cave best and becomes a design problem with more than one audience.

The name heard on the return journey

At the storage gallery, a visitor named Maret decides to return by the stream approach. Maret remembers entering through Seln and assumes that following Tunnarel will avoid Cavarel entirely. The guide places a finger on the shared junction. Taking a different approach after that point does not mean the earlier chamber disappears. The correction matters because Maret has left a sketchbook at the meeting place and needs to collect it before changing routes.

This small objective gives the naming distinction emotional weight without requiring a disaster. The sketchbook contains drawings made for a friend, and Maret would rather admit confusion than abandon them. Oss can explain the return route using the junction as a stable reference. Nerin can mark the point on both sheets. The reader sees why a place name and a route name must coexist: one locates the forgotten object, while the other describes the intended movement afterward.

For spoken testing, ask someone unfamiliar with the map to explain Maret's plan back to you. If their explanation creates a second Cavarel or skips the junction, revise the labels or the dialogue. The most useful test is whether the names support the particular action, not whether every syllable has an elaborate origin story.

Three naming layers without three rival maps

The broader region can have a collective title, such as the Lantern Hollows, while Cavarel remains one junction within it. Seln identifies an entrance, and Tunnarel identifies a route. These layers can be related without forcing them to share a stem. A traveler might say that they entered the Lantern Hollows at Seln, met the guide at Cavarel, and returned along Tunnarel. Each name adds information rather than repeating the same location at a different level of grandeur.

A nearby surface settlement may use a different collective name for the hollows because its residents know only one entrance. Record that relationship if it matters, but do not introduce a second region merely because a second label exists. Likewise, a ruler's territorial title should not automatically become the name of every passage underneath that territory. Administrative ownership, physical connection, and a traveler's chosen route are separate relationships in the fictional world.

The network will feel larger when its labels leave room for incomplete knowledge. Nerin can mark an unmapped branch without assigning it a confident destination. Oss can know a working route without claiming to have visited every chamber. A credible naming system records what its users know and makes its gaps visible rather than filling them with impressive certainty.

A revision that preserves the old directions

In the first proposed revision, Nerin wants to replace Tunnarel with Cavarel on every sheet. That would simplify the chamber index but make old visitor notes harder to use. Oss points to a message arranging a meeting along Tunnarel, not at its junction. Substituting the chamber name would move the implied meeting place. The old route word contains information that the new label does not replace.

The revised solution keeps both and adds a concise relationship: Tunnarel passes through Cavarel. On a small map, the route title sits along the line and the chamber name beside the point. On a larger map, a route index lists its sequence of junctions. The old directions remain interpretable, while new readers can see why the two terms appear together. This is more useful than declaring one form official and assuming everyone will instantly stop using the other.

Let a later visitor arrive with an older copy. If the characters can connect it to the new map without retelling the whole dispute, the revision has worked. If they still have to explain that every printed name is secretly obsolete, the system needs another pass before it can support a longer adventure.

Three decisions at the shared chamber

The teams can agree on one junction name now and keep their separate route sheets. That branch leads to an archival task: Nerin must record which observations justified merging the two apparent chambers. The next scene can involve an old drawing that shows the broken shelf from a misleading angle. The question becomes whether it depicts Cavarel at an earlier time or another place with a similar feature.

They can instead keep two provisional labels while planning a joint return. This preserves uncertainty honestly but leaves Maret needing a clear temporary meeting instruction. The next scene tests whether a description tied to the actual junction can work without a settled name. A third decision makes one person's map the public visitor copy and the other the technical survey record. That branch requires a maintained connection between versions so that later updates do not quietly separate them again.

Each choice creates work for different people. None should end with the same generic statement that the community welcomed a harmonious new name. The decision determines which record changes, who must explain it, and what a returning traveler sees. Those consequences give the setting enough structure to produce later scenes beyond the original disagreement.

The attractive candidate that belongs at the wrong scale

The Eternal Underkingdom is a plausible ceremonial title for a realm, but it does little to identify a modest three-way junction. A sentence saying that Maret left a sketchbook in the Eternal Underkingdom offers almost no usable location. Keep a grand regional title when the story needs it, and choose a smaller place name for the specific chamber. Scale is a naming dimension, not merely a mapmaker's afterthought.

A subtler failure calls the junction Crossdeep, the stream route Deepcross, and the entrance Crossmere. The set looks coordinated but forces listeners to hold nearly identical openings while following movement. Change one of the active forms, or limit the shared pattern to a less immediate naming layer. A family of place names can show cultural connection without making every spoken instruction a memory test.

Avoid solving all ambiguity with numbers alone. A number can identify a survey point reliably within a particular record, while a familiar spoken name remains useful in dialogue. Give the number a defined scope and show which name accompanies it. The point labeled seventeen in one survey should not silently be assumed to match point seventeen in another team's independent notebook.

Prepare a game handout that rewards questions

Give one player Nerin's junction sketch and another Oss's route sheet. Mark the shared ceiling band and shelf on both. State that the characters are comparing records, so players do not mistake inconsistent headings for an accidental production error. Let them turn the sheets, ask what each title means, and draw a combined diagram. They should be able to discover the relationship from information already available.

If checks are used, success can identify a secondary landmark or shorten the time needed to compare measurements. Failure should not make the fundamental map permanently unknowable. Another witness, a clearer drawing, or Maret's recollection can provide a route back into the problem. The interest lies in deciding how to name and communicate the connection once discovered, not in forcing the group to guess the host's private terminology.

For a video-game adaptation, separate the location heading from the route objective in the interface. Arriving at Cavarel should update the location even when the current objective remains follow Tunnarel. Keep earlier labels available in a journal or map key so a returning player can understand the change. The interface can reveal the distinction through use, without interrupting the story with a long mandatory explanation.

Give the network a life between journeys

The storage gallery holds equipment for an underground craft community. People repair lamps, carry sealed boxes, and argue about where empty carts should wait. Cavarel matters partly because it connects those ordinary tasks. Its name can appear on delivery notes and meeting invitations as well as adventure maps. This wider use makes the junction feel like a place maintained by people rather than an empty decision node created for visitors.

Nerin might return to sketch the ceiling band for pleasure after the survey is complete. Oss may prefer the surface market on a free afternoon and resent assumptions that a guide always wants to remain underground. Maret can send a drawing of the recovered sketchbook's final page as thanks. These small continuations attach the place name to different memories without requiring a new naming crisis every time the characters meet.

End the case with a simple direction: meet at Cavarel, then take Tunnarel out. The sentence is short because the preceding story established the relationship. Record the accepted pronunciation, the junction's scope, the connected routes, and any old label still found on earlier copies. A successful cave network name leaves the reader able to picture both a place that remains and a journey that moves through it.