graham

from online

  • any / all

Making stuff to distract myself from existential dread

Art: @graham-illustrations
Dreams: @graham-dream-journal
Wizards: @make-up-a-wizard
Partner's Pottery: @kp-pottery


bruno
@bruno

I've been asked how I go about naming things – something that is a significant part of my job and which some writers dread (while others love). This post isn't 100% of everything I might say about the subject but it's the core lesson I have to teach.

Here's the secret to naming things:

Good names stem from good naming conventions.

Nothing will make naming things more painful than a broadly-drawn fantasy setting where everyone just has a regular English name but one letter off (Gorald, Parricia, Nichael, etc). When you give things a strong naming convention you narrow down the field and you create expectations. And expectations are the mother of rhythm. Things only sound good because the audience has been primed to the implicit presence of beats.

Strong naming conventions can carry you through naming dozens, hundreds of things. The ur-case study is our very own naming convention for Fallen London NPCs, where everyone is known by an "adjective noun" nickname: the Reliable Eggmonger, the Jovial Contrarian, the Captivating Princess. This naming convention is so strong that we can introduce one-off NPCs to the stage purely by their names, have them immediately fit in as who they are, and then vanish them off-stage never to be seen again; we do this frequently in Fallen London.

A naming convention can be a format (like the aforementioned adjective + noun), or it can mean that names have certain specific semantics. In FL, for example, some devils have actual 'given' (stolen, more like) names rather than adjective-noun monikers. We've ended up giving them all ironic names that work as English names in a vacuum, but on a devil they reference either the Biblical (Milton) or virtue (Virginia and Verity).

In more 'solid' fictional worlds, often a naming convention is culturally bound, derived from a specific language. It is 100% worth it to sketch out the bare skeleton of a conlang to use as a naming tool if you're going to be generating lots of names from a fictional culture that's meant to be verossimilitudinous (how to make a conlang is beyond the scope of this article). Names that aren't made up out of English words are (for some) the hardest to do, and rooting them in actual rules of pronunciation and word construction can be invaluable.

If there's no naming convention: Invent one. Think up a narrative of how something comes to have its name – that's valuable too, a useful tool in both brainstorming and culling. Real-world things all have naming conventions, which is why names sound like they belong to certain categories of thing. Often this leads to interesting questions about a world. All of these are names for places where you buy booze, but they all suggest wildly different things about the world the story takes place in:

  • The Wolf & Spandrel
  • The Glazed Hart
  • Harry's
  • The Enantiornithine Lounge
  • FanDuel presents the All-American Light Beer Experience feat. Doja Cat's Third Simulated Postmortem Persona

The other key thing about naming things is that like any other piece of writing, it comes down to knowing what you want to express and how the reader is supposed to come to it. Which, yes, is a "draw the rest of the owl" type statement. But it is true that a name should express some mixture of:

  • What a thing is
  • How a thing is perceived / wants to be perceived / perceives itself
  • The thing's origins, heritage, history, role in society
  • The impression that the thing gives off, its vibes, its experiential qualities.
  • The secret ironies at the heart of the thing
  • How the thing relates to the emotional pillars of the setting. Many good Fallen London names, for example, are jokes wrapped around a core of unease – the Hungry Little Snuffbox; the Inescapable Ubiquity of your Countenance

It's impossible to actually sell all those ideas across in just a name, but it's invaluable to figure out which ones matter more; what's pushed to the foreground. Is a name a social referent or a label used only by the viewpoint character's own thinking? Is a name revealing or concealing something about this thing?

What was being expressed when this thing was being named – a wish for what the thing would become? An advertisement aimed at possible purchasers? An act of intimidation? A vow?

Like with most things in writing, there's not really advice on how to do the thing; what you need to learn is how to build the right process to do the thing. Anyway, here's some bonus case studies on what I think are successful runs of naming things in the games space.

Case study: Destiny 2

In Destiny 2 each new collection of guns has its own naming conventions tied to their origin. Those naming conventions usually don't dictate form, but they dictate semantics.

  • SUROS guns are named after concepts in music theory, with a model number attached to suggest their industrial origin: Syncopation-53, Fortissimo-11, Cantata-57.
  • Guns from the original crop of Gambit Prime guns are all named after abstract vibes, tied to the themes of scarcity and apocalypse that fit the Drifter's backstory: Gnawing Hunger, Bug-Out Bag, Night Watch, Lonesome

Case study: Magic the Gathering

Magic: the Gathering contains a lot of excellent naming work that also shows the power of evolving naming conventions over time as the underlying content evolves. A classic example are the split cards. These are cards that can be cast either as their 'left' half or as their 'right' half. Originally, split cards are named for idioms in English that take the form 'X and Y'. On the cards themselves, it's just the two bare words; by convention they're separated by a double slash.

  • Assault // Battery, Wax // Wane, Stand // Deliver, Spite // Malice.

Then in the Apocalypse expansion they do split cards in enemy color pairs, so those are named after pairs of opposing things:

  • Fire // Ice, Order // Chaos, Life // Death, Illusion // Reality.

This convention is carried through on loads of sets with split cards in various configurations. Eventually, Wizards does a mechanic called Aftermath, where split cards have one half that you can cast from your hand and another you cast later from the graveyard. This gets its variant on the naming convention, where they're named after "X to Y" idioms:

  • Cut // Ribbons, Cradle // Grave, Spring // Mind

Another example of naming conventions evolving is found in lands. The original basic lands in Magic are all easy to associate with their respective colors/elements: Plains, Island, Swamp, Mountain, Forest. The original 'dual lands' are then named after more specific biomes that suggest where two of those meet. A mountain forest is a 'Taiga'; an island forest is a 'Tropical Island'; a plains swamp is a 'Scrubland.'

Many years later, the 'shockland' cycle takes place in an urban world and so the names reference a built environment rather than natural biomes – but they're all combining an adjective and a noun to suggest their color pairs. Blood Crypt is black-red while Overgrown Tomb is green-black. Hallowed Fountain is blue-white while Watery Grave is blue-black. Godless Shrine is white-black while Temple Garden is white-green. The naming conventions are so strong within their individual cycles that it's generally easier to confuse lands of the same color pair but different dual land cycles. That is, it's easier to confuse Battlefield Forge (the red-white painland) for Sacred Foundry (the red-white shockland) than it is to confuse Breeding Pool (the blue-green shockland) for Stomping Ground (the red-green shockland).


graham
@graham

There's a level of depth in the different meanings and the mouth feels and the thoughts behind names in Bruno's post that eludes any sort of programming that I have the ability to implement. I'm not sure that it will ever be possible or worthwhile for a computer to help with creating meaning behind naming in many of the ways mentioned above, but I also can't help but try to make tools for turning well-defined and easy-to-implement naming grammars into generators. Classifying a data set into pairs of common English idiomatic phrases is a very hard problem, classifying opposites is tough, and classifying biblicly-relavant names is maybe doable programmatically?

I made a quick generator from the adjective + noun formula, and was delighted by the first set of results.



There's a contemporary music technique called a twelve tone row, which could be its own whole longpost, but the quick version is: every note in the twelve-tone chromatic scale must be used before returning to any already-used notes, and lots of people like to add constraints to the construction and use of twelve tone rows after that.

I think there's something interesting and overlapping with twelve tone rows and alphabet poems. In both cases, all members of a set (either chromatic notes or letters of an alphabet) must be used before any returns to already-used set members.

It makes me wonder whether, rather than trying to only do alphabet poems in alphabetical order, or rather than only using each letter once in the whole poem, could there be interesting poems made from using each letter once per group but never using any that are directly next to each other alphabetically? Could this be sustained for many groups?

Here's a tool for shuffling the alphabet if you're interested in trying it out: