SLINGLONGBuild a roster around moments of confusion
A campaign party can contain five good individual names and still be difficult to follow as a group. You notice the problem when a player says, “Do you mean our scout or the woman who owns the boat?” It becomes more consequential when the response changes what happens next. If the scout moves while the boatkeeper was supposed to release the line, the table may have to rewind an exchange. Building a party roster means considering which names will be heard together, in whose voice, and for what purpose. It is possible to keep a recognizably related set of names while leaving enough distance between the calls used in action.
Begin with the actual scene schedule. For the opening adventure, list the characters likely to appear in the first three scenes. Mark who speaks, who is addressed by name, and who is only mentioned. A guard encountered alone on the road can share a sound with a character introduced five sessions later without making the first scene confusing. Two healers who answer to the same call in the same room are a different problem. The most useful pair to examine is the pair whose confusion would change an action, a location, or a decision the players have to make.
Give the names different jobs
Make a row for each character with four entries: the formal name, the common call, the role visible to the group, and the person most likely to address them. For example, the traveling healer may use Senra Tol in a guild receipt, Sen among companions, and “the bridge healer” when villagers ask for help. The first form places her in an institution, the second allows quick speech, and the third points to a recognizable duty. Keeping them together in one row helps you see how readers will learn that all three describe the same person.
Work out who gets to introduce the short forms. If the hired guide introduces Senra as Sen before anyone else speaks, the call establishes familiarity. If the guide has never met her, an explanation may be required in the fiction. Let a friend hand over a bandage roll and call her Sen while an unfamiliar clerk enters the whole name on a payment slip. The audience can observe the relationship rather than memorizing a note about it. In a group that uses a nickname for each member, give the names at least one moment to emerge from different relationships. A list of nicknames announced in order can sound like a list of passwords, especially when nobody has a reason to respond.
Separate family likeness from field recognition
Suppose a family of river traders includes Ardalen Voss, Ardalin Voss, and Ardel Voss. A shared surname is enough to suggest kinship on a receipt. The given names in this draft also share their most audible sounds. When the speaker calls “Ard!” all three have reason to look up. Decide where you want the closeness to be heard. The formal names might preserve a shared element important to the family, while the working crew recognizes Dalen, Lin, and Del. Test those forms separately. Dalen and Del may still be close when spoken quickly. Giving the third person a name with another vowel or a work call already known aboard the boat can make a larger difference than rewriting all the formal names.
Sometimes likeness is deliberately part of the setting. A group of apprentices may have taken a common oath name, or people from one island may use the same ending. Keep that signal in a part of the name that has a clear function. An ending can connect people in a genealogy while different stressed openings help a speaker recognize them on deck. A common opening might be appropriate if the members mostly use their roles in conversation. Write an actual line in which the resemblance helps: “The two Lyrens both trained at the south gate.” Then write a line where the same names must be distinguished. If that line requires a reader to slow down and compare spellings, give the characters separate working calls.
Compare openings, rhythm, endings, and short forms
Read every likely collision pair in both orders. The sequence Neral and Nerin can sound clear when announced from a prepared list, especially if the speaker exaggerates the endings. In a conversation, a listener may register only Ner. Compare the same pair inside a sentence with the verb and other nouns intact. You may find that the first name is easy before “hold” and much harder before “haul.” Record what went wrong in the specific line. A note like “same opening” identifies the source. A note like “both people turn at Ner during a command” gives you a concrete criterion for the repair.
Try one change at a time. Change the beginning of one short call and keep its rhythm. If that solves the problem, there is no need to invent two new lineages. If the change fails, vary the number of beats or move the stress. If both names end in a long soft sound, test a shorter ending before choosing a whole new name. A written roster can have its own visual confusion. Two long names with a common opening may look alike in a narrow column even if you hear them easily. In that case a small tag such as ferry pilot, debt clerk, or outrider can help the reader identify the row without altering how the characters address each other.
Use comparison scores as clues about what to test. An exact shared short call needs a decision if both people appear in the same scene. A shared final syllable might cause no difficulty at all if the beginnings and stress are clear. An unusual consonant cluster can be harmless in print and unstable when spoken by different people. A name that fails in one table’s accent may work in another. Let an actual listener tell you which signal they heard, and keep a record of the circumstances. Avoid changing a name only because a visual comparison highlighted a similarity that nobody uses in the story.
Work through a five-person caravan
Consider a caravan crossing a flooded road with five recurring names: Selvar the guide, Selven the scout, Umina the medic, Korran the driver, and Tesk the quartermaster. The guide and scout both use Sel in the first draft. In the opening scene, they arrive separately. The difference seems easy because one carries a map and the other arrives on horseback. In the third scene, both are standing near the ford. The driver says “Sel, go ahead,” and each actor reasonably thinks they should move. A fix in the introductory scene alone would leave the collision available every time a quick order is given.
Keep Selvar’s familiar call Sel because the villagers already know him by it. Give Selven the working call Ven and introduce it when the quartermaster asks for a scouting report. Use the guide’s full name on the route agreement to preserve the shared style that links both characters to the region. In the rescue scene, try “Ven, check the bank. Sel, stay by the cart.” The result should be two visibly different actions. If a listener still points to the wrong person, separate the lines or test another call before you settle on the revision. The written pair can retain its resemblance once the spoken exchange has a reliable distinction.
Now test a collision outside the obvious pair. A caller says “Korran, warn the rear cart.” Depending on the pace, Korran’s last sound and the first word of the instruction may crowd each other. Put a breath after the name or use “Korran! Warn the rear cart.” If a listener then identifies him, the surrounding line did the repair. Meanwhile, Umina and Tesk may never need to change. It is tempting to revise every member when the roster feels uneven, but unrelated edits can remove distinct signals that were working. Rehearse the repair in the next scene before touching the rest of the cast.
Make substitutions that preserve the story
When you need to change a name after several sessions, find the smallest change that helps the audience. Rename a field call in the fiction by giving it to a role, move a confusing title from speech to a document, or add a location to a public name that keeps getting mixed up with a house. If a player has become attached to the original name, ask how the party already says it. You may find that everyone naturally uses the same nickname and the full names never collide. If another character shares that nickname, keep one and let the other character acquire a separate call through a scene they both participate in.
A story may intentionally put the wrong name in someone’s mouth. A spy can use the wrong household call or a pretender can answer to a field name they heard once. Make the baseline legible first. Give the players a clear exchange in which the real character uses the ordinary form. Later, the mistaken address can be compared with an action, timing detail, or witness statement. The resemblance becomes a clue instead of another burden on the audience. The relevant question is what a careful player could notice with the information they already have at that point.
The same idea applies to antagonists and allies on opposite sides. Matching formal names may show a common training house, but consider the conversation where a witness describes both people. If readers have to stop at each appearance and consult a glossary, give the speaker a specific phrase to distinguish the roles. The witness might say “the surveyor who came from the west” the first time and use a short call later. If a mystery depends on the witness confusing them, allow the audience to reconstruct why that happened from an established resemblance and a believable restriction on what the witness could hear.
Run the scene test before publishing the cast list
Pick the most crowded scene you expect to write or run next. Have someone hear the roster once. Read three brief lines that assign actions, changing the order in which people are named each time. The listener should say who moves, who remains, and who is merely mentioned. Add a short interruption and ask them to refer to one person without showing the list. Note which calls they remember, which they invent, and which they replace with roles. If a role remains clearer than the name, decide whether the character needs to be named yet. A single named action can be a stronger introduction than a biography offered before the person does anything.
For a manuscript or a game interface, hand over the same scene in written form. Put the names in the actual character cards, conversation display, or map labels you intend to use. Look at the narrowest common display and the shortest line that contains the name. Check that you can distinguish the important pairs without opening a separate profile. If you have voice dialogue, compare the spoken call with the visible label and introduce the relationship between them before asking a player to select the correct person. A group can pass a spoken test while the interface still presents a confusing list.
Finish with a compact roster that records the decisions you made. Keep one role marker, one common call, and one pronunciation cue per recurring character. Mark which scene establishes any relationship between a formal name and a nickname. Record the nearest collision only if it affects a real exchange. When a new character joins, test them against the people they will actually meet before comparing them with the entire world. The goal is a party whose members can be named independently when action is required, while their names still tell a reader or player something about how they belong together.
For a roster that changes between episodes, add a return note for the character most likely to be forgotten. The note should name a prior action, such as “Ven checked the bank before the crossing.” Reintroduce Ven by completing that action or referring to its result. A listener who remembers the scout’s work can connect it to the call without hearing the entire roster again.