Code Violet drops Violet Sinclair — a woman from our century — into a 25th-century bioengineering complex, and the first thing the game does is prove she doesn't belong. Her name is plain. Ordinary. It belongs to a person, not a personnel file. Everything around her is stamped: Subject K-7, ORION-9, Cohort-3. That collision between a human name and a cold designation is the whole game in miniature, and it's the most useful thing to understand when you're naming characters for this world.
The Aion colony built a time machine because the colony is sterile and facing extinction. They pull women from the past, run them through the surrogate program, and file them away. How Aion names someone tells you exactly where that person sits in the machine's hierarchy.
Two Naming Registers, One Facility
Almost everyone in Code Violet falls into one of two naming registers, and the game never blurs the line between them.
Plain 20th/21st-century names — given name plus surname, no ornament
- Violet Sinclair
- Mara Delgado
- June Castellanos
- Priya Anand
Machine-stamped designations — codewords, series codes, titles, index numbers
- Subject K-7
- ORION-9
- Cohort-3
- Dr. Rhea Voss
Violet's name works precisely because it's unremarkable. The abductees aren't given special names — they're stolen from a world that gave them ordinary ones, and that ordinariness is what makes their situation feel real. Aion, meanwhile, doesn't name people at all. It files them.
The Designation Format Does Heavy Lifting
The dash-letter-number structure of Aion's designations isn't decoration. It reads as inventory — the same way a lab codes its samples — and that's exactly what it means in-world.
Subject K-7 — filed like a lab sample, not introduced like a person.
When you're building a Code Violet character for a fan project or a tabletop campaign set in the complex, that format is the fastest way to sell the setting.
- Use a codeword + dash + index for bio-engineered soldiers
- Keep abductee names plain and contemporary — that's the point
- Give Aion personnel titles: Dr., Warden, Director
- Keep aliases short and shoutable across a collapsing facility
- Use space-opera names — Commander Voidthorne belongs in another game
- Add cyberpunk flourishes like Neon-9 or Chrome_Reaper
- Give a bio-engineered soldier a friendly nickname
- Slap a title on an abductee — they weren't processed, they were taken
Naming the Survivor
The most effective abductee names read as slightly out of step — ordinary to us, jarring next to the violet-lit vats and the dinosaurs. The name doesn't need to signal anything dramatic. The contrast does the work.
Aion personnel flip that register. These are people who chose the surrogate program, and their names carry institutional weight — a title, a full given name, a surname. The formality isn't coldness for its own sake. It's how the facility keeps everyone at arm's length.
What the Name Reveals
Code Violet's naming is a hierarchy in miniature. An abductee keeps a real name because Aion never bothered to claim them properly. A bio-engineered soldier gets a series code because Aion considers them equipment. An Aion staffer gets a formal title because they're part of the machine. When you're naming a character for this world, decide which of those three positions they occupy — the rest of the name follows from it.
If you're building out a survival-horror cast where corporations turn people into subjects, our Resident Evil name generator covers Umbrella operatives and Raccoon City survivors with the same machine-versus-person tension.
Common Questions
Why does Violet Sinclair have such a plain name?
Because she was kidnapped from our time, and that's the point. The abductees in Code Violet carry ordinary 20th/21st-century names because Aion pulled them from the past — the name is a reminder of where they actually came from. The more ordinary the name, the louder it clashes with the sterile bioengineering around it, which is exactly the effect the game wants.
What's the difference between a bio-engineered soldier and an Aion staffer's name?
One is equipment, the other is staff. Bio-engineered soldiers get series codes — a codeword, a dash, an index (Subject K-7, ORION-9) — because Aion filed them as units of work. Staffers keep real names with titles (Dr. Rhea Voss, Warden Elian Crowe) because they're part of the machine rather than product. If a character's name reads like inventory, Aion owns them.
Can I mix these naming styles for one character?
Yes, and Code Violet's premise practically invites it. A bio-engineered soldier given a human name by a sympathetic staffer, or an abductee who's been in the program long enough to earn a designation, both work. The tension between the two registers is the story. Just keep the two sides distinct — the mix is meaningful because the registers themselves stay clean.
Are the dinosaurs in Code Violet given names?
Not in the way you'd expect. They're the facility's failed experiment — prehistoric creatures revived by Aion's time tech that broke containment — and the game treats them as hazards, not characters. They get no formal naming; the evacuation broadcasts refer to them as containment breaches. For a fan project, giving a specific creature a designation like a predator codename fits the facility's clinical tone better than a proper name.
