SLINGLONGStart with the line someone actually has to say
In the middle of a session, the ferry keeper does not announce, “The relevant nonplayer character is Rethavin.” She calls, “Rethavin, take the stern rope.” A name that looks excellent by itself can disappear inside that sentence. The last sound of the name runs into the next word. The player who was looking at the map hears an instruction without hearing its recipient. Five minutes later the same player recognizes the written spelling on a handout and still has no reason to connect it with the person on the quay. The useful test for a fantasy name starts with the line that has to work under those conditions.
Choose a sentence from your own project before you evaluate a list of candidates. For a companion, use the first instruction they hear in a crowded scene. For a suspect, use a line in which another character mentions them without introducing them again. For a place, give an actual direction with a turn or crossing. Say the sentence at the pace you expect to use in play. Write down where the name begins and what the listener must do after hearing it. A name that is easy to read but difficult to locate inside its sentence needs a different repair from a name that is difficult to pronounce in isolation.
Mark the part you expect people to remember
Make a working notation for the pronunciation. For an invented name such as Velrani, you might write vel–RA–ni, with the capital group indicating your intended stress. This is a rehearsal cue. It does not establish the pronunciation of an existing language. Next write the form someone uses when they know the bearer well. If the ferryman says Vel while a tax clerk reads the whole name, write both lines and try them separately. A player may remember Vel first and encounter Velrani much later. Leave a small occasion where both forms belong to the same person: “Vel, your permit says Velrani. Is that still your name on the river?”
The strongest recognition cue need not be the first written letter. It can be a stressed vowel, an unusual rhythm, or a final sound that remains clear in speech. In a list of Arven, Orven, and Urven, the opening vowels carry almost all the distinguishing work. If the caller is rushing, those short openings deserve a test before you keep the matching endings. A set of names with different initial letters can also be difficult if the first letters are silent or pronounced similarly in your group. Listen for the sound the participants actually produce. Spellings are useful evidence for revision, but the heard line is the evidence for whether the name can do its job.
Try a two-person listening test
Ask a listener to put the written list aside. Give them three names once in an ordinary introduction, with a distinct action for each character. Then spend a minute discussing something else. Return to the scene and say one of the names in an instruction. Ask the listener to point to the person they think received it, and repeat what they heard if they can. Record their answer before you show them the intended spelling. Reassurance after seeing the correct text is a different result from recognition in real time.
Use two rounds with different tasks. In the first, a listener has to recognize a known name, such as deciding which of three runners should leave the ferry. In the second, they have to remember it well enough to use it, such as telling a fourth person where the runner went. They may succeed at recognition and still invent a short form when speaking. That short form is useful information. Decide whether it fits the character. If it does, use it intentionally in dialogue. If it collides with an existing name, decide which character most needs a distinctive call and revise the other name first.
Run the test in your normal setup. At an in-person table, ordinary conversation and a person reaching for dice are sufficient background activity. For an online game, try your actual microphone and speaker settings. There is little value in inventing a dramatic amount of noise that never occurs in your project. If you are writing alone, read the scene into a recorder and listen back while doing a small separate task. You already know the names, so your result is an initial check of rhythm and clarity. A listener who has never seen the page can tell you more about first-time recognition.
Diagnose four different failures
Sometimes the listener misses the boundary. “Tell Renn to hold” becomes a single rush of sound and Renn disappears. Keep the name and change the line first. “Renn! Hold the west gate” creates a pause and puts the address where it cannot blend with the verb. If the name still vanishes in different lines, move the stressed sound earlier or replace the name’s opening. In a manuscript, the corresponding problem can happen visually when the name follows a long string of titles or precedes an unfamiliar word with nearly the same shape.
In a second failure, a listener hears a clear name and points to the wrong person. Consider Selven and Selvar, both members of a scouting party. If both are shortened to Sel, a new ending does little in the shouted scene. Changing one short call to Var gives the two roles separate sounds while preserving their related formal names. Check that someone has a reason to introduce the new call. A small exchange at camp can establish it before the two characters need to react separately under pressure. If you are writing siblings, the shared form can remain a deliberate feature in a private family scene where the speaker knows exactly who is being addressed.
A third failure is unstable pronunciation. One player reads Maelor as MAY-lor, another as MEE-lor, and a third reduces it to Mal. Ask whether the difference matters to the project. A small group can agree on a spoken form even if a spelling invites other readings. A published game with voice work may need a pronunciation entry in its dialogue sheet. You can also change a spelling to support the sound you want. Try a fresh reader after the change. A person who has already learned the intended pronunciation may read the revised spelling correctly from memory.
Finally, a name can be heard and pronounced correctly while failing to identify the relevant thing. At a harbor, Gannet could mean a boat, an inn, or the boatkeeper’s nickname. If all three appear in one conversation, revise the instruction to include the object or change one name. “Meet at Gannet Pier” is an actual location. “Ask Gannet” requires the listener to know who is meant. When the ambiguity is part of a mystery, establish the ordinary usage first so that the later misunderstanding is a clue the audience can reconstruct.
Use the shortest form where the line is busiest
Imagine a captain with the formal name Orvath Ironwake and the field call Vath. The full form might fit a commission or a public introduction. During a rescue, “Vath, keep the bow steady” gives a listener a name followed by an action. Test that call against the ordinary commands already present in the scene. If the crew often says “aft,” put both terms in nearby lines and have another reader try to tell them apart. Changing the location of the call in the sentence may resolve the problem. If the names need to work through repeated quick commands, giving the captain another short form may be more reliable.
A short call also carries social information. A close friend might call the captain Vath in front of a clerk who has only heard Ironwake. The clerk’s moment of hesitation can show unfamiliarity with the captain without turning the entire scene into an explanation. If a stranger uses the family’s call in the first meeting, decide why they know it. The choice can become an early clue about their relationship. Use that effect where you want readers to notice it. If the scene is about finding a missing person quickly, give speakers a shared form early so that the relationship can wait for a quieter exchange.
Some projects benefit from a deliberate contrast between the full written name and its conversational form. A ritual name may need enough time to include a family line, and a public officer may have several titles. Put the formal form in a context that can bear the extra words. A witness can read it from a ledger while other characters listen. When a second witness later says only the short form, the audience can still track the person because you have already linked the two. The rehearsal question is whether you can remove the formal title from a tense exchange and keep every action comprehensible.
A revision from first draft to playable scene
In a test scene, three rescue workers were introduced as Theral, Theren, and Mavik. The first two names were meant to signal that the workers trained in the same house. A player remembered the house resemblance and mistook Theren for Theral when the line “Theren, take the line from Mavik” arrived. The main action in the scene depended on the second worker taking over while the first held the gate. Introducing both again would have delayed a scene that was supposed to feel urgent. Changing the house association would have removed a useful relationship the writer wanted to keep.
The revision gave one worker the field call Ren and the other Tal. In the opening conversation the captain addressed both by those calls while passing out equipment, and the formal names remained in the duty register the players could inspect. The rescue line became “Ren, take Mavik’s line. Tal, keep the gate.” A fresh listener correctly identified who moved and who stayed. Later, a player still confused the written entries because the two formal names stood side by side without roles. Adding a column for the assigned duty resolved the handout problem. There were two repairs, because the spoken confusion and the written confusion had different causes.
This scene also illustrates when you can keep an apparent naming problem. If the point of the session is that a rival forged a commission by exploiting the resemblance, two similar formal names can support the story. Give a careful player enough independent evidence to notice the problem, such as the duty, time, or place of a recorded handoff. Let the characters’ spoken calls remain clear during the action. That way the ambiguity belongs to the document and does not make the players struggle to follow the scene itself.
Keep a small rehearsal sheet
Make one row for each name that will recur soon. Record its full spelling, a readable stress cue, its everyday call, the line in which it first appears, and one name or command it might be confused with. A row for a place can replace the everyday call with the form on the actual road sign. For a title, write who uses it and what action it authorizes or remembers. A sheet with six relevant entries is often easier to use during play than an exhaustive list of every invented term in the world. Bring the lesser names in as their scenes approach.
For the next rehearsal, circle the single most important name in each scene and test its line with someone who has never heard it. If they identify the correct recipient and can repeat the useful form after a short interruption, keep your current spelling unless you have another reason to change it. If they consistently hear a different stress, choose between teaching that sound on first introduction and changing the written form to match their reading. If two names collide, test one change at a time. That allows you to tell whether the improvement came from the opening, the rhythm, or the sentence around it.
Finish by recording why the name survived. “Ren remains clear before ‘take the line’” is more useful than “sounds cool” when you come back to the draft next month. You may still decide that an elaborate formal name serves the character perfectly. Keep the decision tied to a place where you have tried it. The best proof of a usable name is that a participant can hear it, connect it to the right person or place, and do something with it before the story pauses to explain.