Armored Core VI Name Generator

Two Names, One War Machine

In most games, you pick a name and move on. In Armored Core VI: Fires of Rubicon, you have two naming problems — and they're not the same problem. There's the pilot behind the cockpit, and there's the machine they're strapped into. A pilot callsign is a reputation, something whispered in debrief rooms and broadcast over enemy comms mid-fight. An AC unit name is a designation: short, sharp, the identifier on a threat assessment that tells you what's incoming before you can see it.

The distinction matters. "Rusty" is a pilot. "STEEL HAZE" is his machine. One name carries the human; the other carries the weapon. They can match in tone or contradict each other entirely — and the contradiction often says more.

What Makes a Callsign Stick

The best AC6 callsigns feel accidental. "Snail" isn't flattering. "Chatty Stick" sounds like a joke that survived because everyone who was there remembers it. "Invincible Rummy" has a whole character arc buried in three words. None of these were designed to be cool — they accumulated.

That texture is what separates an AC6-authentic callsign from generic sci-fi naming. A callsign that sounds too intentional, too clearly constructed for badass effect, loses the authenticity. The ones that work either describe something specific (a quirk, a method, a reputation that preceded the person) or feel like they're referencing something you weren't told about.

Naming the Machine

One or two words. Always uppercase. Always atmospheric. That's the entire rulebook for AC unit designations, and it's surprisingly hard to follow when you're staring at a blank field.

STEEL HAZE. NIGHTFALL. GHOST. HERMIT. ARCHITECT. Each implies something without spelling it out — a capability, a philosophy, a threat level in a single word. The convention is closer to military aircraft callsigns than to fantasy character names. You're not trying to sound powerful. You're trying to be immediately recognizable in comms chatter under fire, and memorable on the after-action report that goes up the chain.

Faction First

Start with faction before anything else — it determines the entire naming grammar. Arquebus runs on elegant control: their Vesper operatives use Roman numeral designations that feel like a performance review formatted as a war crime. Balam goes the other direction: G-squad identifiers attached to geographic callsigns (Michigan, Nile, Volta) that sound like someone named their soldiers after rivers and decided that was enough personality.

The RLF doesn't have a system. That's the point. When you're fighting a planetary liberation war on a guerrilla budget, you get the name the community gives you — not the one your employer assigned. That's why RLF callsigns feel more human, even when they're rougher around the edges.

Using This Generator

Select "Pilot Callsign" when you're naming the person. Select "AC Unit Name" when you're naming the machine. Choose "Pilot + AC Pair" for a matched set — the generator will give you a callsign and an accompanying designation calibrated to the same faction and tone.

Faction matters more than tone here. Set your faction first, then adjust tone: "Arquebus + Elegant" for Vesper-tier operators, "RLF + Edgy" for liberation fighters with a grudge, "Independent + Playful" when you want something with Chatty Stick energy. If you're working on FromSoftware-adjacent worldbuilding that stretches into fantasy territory, the Dark Souls name generator and Elden Ring name generator cover the same studio's naming DNA in medieval and high-fantasy registers.

Common Questions