Rogue
Name Generator

01

Give the alias an ordinary purpose

A useful street name needs a reason to exist beyond sounding secretive. Perhaps couriers use short calls at a busy dispatch counter, or a performer wants to keep family life separate from public work. Define the boundary the alias protects, then identify who knows both forms and why the character trusts them.

A private name need not be a shocking revelation; it may be mundane information shared carefully. Resist making every supporting character either gullible or omniscient. A dispatcher can respect the alias without knowing the whole biography, and a close friend can know the birth name while still misunderstanding the professional reputation built around the public one.

02

Choose a specialty without writing a manual

Courier, locks scholar, and disguise offer distinct fictional social roles. A courier connects people whose schedules do not align. A locks scholar can study the history and ownership of magical doors.

A disguise performer might advise a theater or an invented diplomatic festival. Ground competence in contacts, records, and judgment rather than descriptions of real techniques for intrusion or evasion. Name one task the character routinely accepts and one request they refuse.

Those limits can shape the alias: a call associated with reliable deliveries means something different from a stage name associated with transformations. The story becomes specific through who requests the work, what was promised, and how the worker accounts for a mistake.

03

Make recognition inconvenient

An abandoned identity is useful story material when someone remembers it for a good reason. A retired call might still appear on a neighborhood fund, an unpaid theater credit, or letters from a person who has no other contact. Decide what the rogue thought was finished and what another person understood to be continuing.

This disagreement can drive intrigue without requiring a villain or a real-world criminal scheme. Try a scene in which a stranger thanks the character under the old name. The response reveals whether privacy, shame, loyalty, or simple exhaustion motivates the desire to move on.

Do not solve the tension merely by declaring that the new identity is the authentic one.

04

Keep the cast legible

A character with several names can confuse the reader faster than the people in the story. Choose one main narrative label and introduce each alternative through a speaker with a clear relationship to it. Give aliases different rhythms, especially when two appear in the same exchange.

Write a small internal note showing who uses which form, but reveal only what the current scene needs. A friend switching to the professional call may signal that work has interrupted intimacy. An employer using a private name may cross a boundary even when the words are technically accurate.

These shifts make names part of characterization rather than a collection of decorative surprises that demand constant explanation.

05

Case study: the letter after retirement

Vesren retired the call Ribbon when leaving a borough dispatch house. Years later, a letter arrives using that call, written by someone born after the supposed retirement. Investigating the delivery chain reveals that a community correspondence project kept Ribbon as a shared return address.

Nobody intended to impersonate Vesren; residents assumed the service mattered more than its original bearer. Draft a conversation with the current volunteer before deciding whether the name should be reclaimed. The character can insist on a correction, help transfer the identity publicly, or continue answering selected letters.

Each choice changes a relationship, and the best name for the next chapter may acknowledge that consequences outlast a convenient departure.

06

Let privacy coexist with accountability

The free borough network can preserve an internal record without exposing every worker's personal life. Establish a trusted person or fictional procedure through which a complaint reaches the responsible worker. This allows an alias to protect a boundary without erasing obligations.

For a game, let players choose which relationship holds that responsibility and what happens when the contact becomes unavailable. For prose, place the complaint in an ordinary setting, such as a delayed payment discussion or a request to correct a delivery account. The rogue's response matters more than an elaborate hidden mechanism.

A mature arc may involve learning which parts of the past deserve a public explanation and which remain private without apology.

07

Revision case: Ashvik and borough registrar

Draft setup for Ashvik at the free borough network: A trusted registrar connects a public complaint with the worker responsible for the commission. This example uses “Ashvik, Ink” as the proposed public introduction. Failed borough registrar version: Ashvik receives “Ink” before anybody addresses this obstacle: A retired call remains associated with a community service now run by different volunteers.

For Ashvik, the apparent achievement therefore exceeds the evidence. In borough registrar, the draft treats the title as authority beyond its appointment. Revised borough registrar scene: The character must keep the internal work record current through relocations and changes of alias.

Keep Ashvik's introduction provisional while that cost is paid. The borough registrar evidence arrives through an observable detail: A dispatch receipt uses the correct old signature beneath a newly adopted borough heading. State who appointed the bearer, what service was requested, and which request exceeds that role.

Introduction before revision: “Ashvik, Ink” is announced as settled. After revision: “Ashvik” is used pending the borough registrar evidence; “Ink” records only the accepted result. In this rogue scene, “Renwick” takes the other speaking role.

The ending for Ashvik must still acknowledge the local conflict: An alias has become trusted enough that abandoning it would harm people who rely on it. With borough registrar, a limited agreement leaves space for disagreement without making “Ink” meaningless.

08

Revision case: Calrin and theater troupe

Draft setup for Calrin at the free borough network: A troupe can distinguish a stage identity from the private person during public misunderstandings. This example uses “Calrin, Ribbon” as the proposed public introduction. Failed theater troupe version: Calrin receives “Ribbon” before anybody addresses this obstacle: An audience attributes a generous fictional gesture to the performer as a continuing personal promise.

For Calrin, the apparent achievement therefore exceeds the evidence. In theater troupe, the draft treats the title as authority beyond its appointment. Revised theater troupe scene: The performer owes collaborators accurate credits and notice before retiring a shared public role.

Keep Calrin's introduction provisional while that cost is paid. The theater troupe evidence arrives through an observable detail: A program credits the same character name to several performers across different touring seasons. State who appointed the bearer, what service was requested, and which request exceeds that role.

Introduction before revision: “Calrin, Ribbon” is announced as settled. After revision: “Calrin” is used pending the theater troupe evidence; “Ribbon” records only the accepted result. In this rogue scene, “Renwick” takes the other speaking role.

The ending for Calrin must still acknowledge the local conflict: An alias has become trusted enough that abandoning it would harm people who rely on it. With theater troupe, a limited agreement leaves space for disagreement without making “Ribbon” meaningless.

09

Revision case: Corvik and longtime correspondent

Draft setup for Corvik at the free borough network: An established correspondent preserves the context of a promise forgotten by the dispatch institution. This example uses “Corvik, Reply” as the proposed public introduction. Failed longtime correspondent version: Corvik receives “Reply” before anybody addresses this obstacle: The correspondent wants an explanation for a departure the character has always considered self-evident.

For Corvik, the apparent achievement therefore exceeds the evidence. In longtime correspondent, the draft treats the title as authority beyond its appointment. Revised longtime correspondent scene: The character must read an inconvenient account of events without controlling how it is described.

Keep Corvik's introduction provisional while that cost is paid. The longtime correspondent evidence arrives through an observable detail: A saved envelope contains a carefully crossed-out sentence missing from every later retelling. State who appointed the bearer, what service was requested, and which request exceeds that role.

Introduction before revision: “Corvik, Reply” is announced as settled. After revision: “Corvik” is used pending the longtime correspondent evidence; “Reply” records only the accepted result. In this rogue scene, “Renwick” takes the other speaking role.

The ending for Corvik must still acknowledge the local conflict: An alias has become trusted enough that abandoning it would harm people who rely on it. With longtime correspondent, a limited agreement leaves space for disagreement without making “Reply” meaningless.