Fantasy Slang: Starting from Scratch

Last year, I wrote some posts on where slang comes from and how to make your own for a sci-fi/fantasy novel. Among other things, I said coming up with unique terms and idioms for a world was "very hard" at first.

Man, was I right.

The last couple of days I've been working on the beginnings of a glossary for my post-apocalypse world. The bad news is it's just as hard as I remember it being the first time around. The good news is, I've figured out some steps to help you (and future-me) start your own fantasy glossary.

1. Determine what feel you want. Old West slang (like Firefly) has a very different feel from pirate slang (like Air Pirates) or Mexican slang or British rhyming slang. Each will flavor your book and your world differently.

2. Research that type of slang. Write down words you like, that sound cool, that are so obscure you think you could use them without most people knowing the source. Even for words you don't like, write it down if it means something you think you'll need. In that case, pay attention to where the term came from (if possible) and see if you can use the same method to create something new.

For example, when researching pirate slang, I wrote down "grog" and "booty." The terms were too well-known for me to use them (and, in fact, their origins made it impossible for me to use them realistically), but they helped me get the right feel for my own.

3. Know your world's origins and metaphors. If your world is at all based on Earth, you'll want to think about how language might have evolved. For example, Firefly mixed Chinese phrases and swear words with English based on the idea that the two "mega-cultures" had combined.

And Earth or not, every world has its own metaphors. What is (or used to be) important in your world? An icy world might have snow and cold metaphors (like, maybe they'd say "Toasty!" instead of "Cool!"). An agricultural society might use farming or animal terms -- like "groundhog" for someone who's never flown before -- while a city-planet might not know what a groundhog is (though maybe they used to know, and it's become a dead metaphor!).

4. Make up some basic terms. Once you've collected everything above, start with some or all of the following (apologies in advance for some of the examples):

• A greeting ("Hey!" "What's up?" "Are you well?")
• A couple of honorifics (Mister, Miss, Your Honor, Madame, Sensei)
• A term between friends (buddy, bro, mate)
• One or two insults (bastard, prick, rat orphan)
• One or two oaths (oh my God, damn it, sh-t)
• A positive epithet (cool, awesome, rad, pure guava)

5. Play with it. Try writing a dialog-heavy scene with your new terms. Don't worry about presenting it to the reader (or about writing well at all, actually). Just try to see where the new slang feels wrong, where it might be too much, but especially where you make up even more terms or phrases (e.g. where you've used some modern cliche that wouldn't make sense in the fantasy world).

Once you've got the world in your head and a start to the language, it gets easier. You build momentum for thinking up future phrases, and the bigger your glossary (because you are writing them all down, aren't you?), the more momentum you have and the easier it gets.

At least I hope it gets easier. Otherwise I got a loooooong road ahead of me.

8 Stages of Querying

NOTE: These stages are representative and are not indicative of any stage the author (me) is currently in. Although I have been in every stage at one time or another.

1) The First Query is Sent. Subject spends most of their time refreshing their inbox and planning an "I Have an Agent!" blog post. A small amount of time is also spent researching what to ask when an agent calls, how much time to give other agents to make a competing offer, and how much the average advance is for a debut author.

2) The 1st Rejection. Subject tells themselves everyone gets rejected. They try to remember what one is supposed to do to move on, but end up refreshing their inbox and staring at their query spreadsheet instead.

3) The 5th Rejection. Mild depression sets in. Subject looks at their spreadsheet, and the as-yet unanswered queries, with despair. They wonder if the problem is their query letter or their story or their opening pages or that one comment they made on Twitter where all the agents could see or the fact that their blog is white text on black background...

4) The 1st Request. Symptoms include an increased heart-rate and shaky hands, making it difficult to prepare the manuscript for the agent. Subject looks over the manuscript twenty times before realizing they're not paying attention to it because they were thinking about where they would do their first book signing. At this stage, the subject is completely incapable of working on anything new.

5) The 1st Rejection of the Full Manuscript. Subject suffers severe depression. They may stop writing or querying for days. Some subjects stay off the internet while others stay on to research self-publishing.

6) The 15th Rejection. Subject becomes resigned to rejection. They send out new queries reflexively, but don't really expect anything from them. Depending on feedback received and the state of the manuscript, subject may consider major revisions, a rewrite, or an entirely new novel.

7) The 4th Request. Subject exhibits a timid hope, but continues work on the new project. When new query responses arrive, subject experiences brief excitement before reminding themselves it's just another rejection. Subject begins to see things in their new project that they like. They wonder if maybe -- just maybe -- they could fall in love with something new again.

8) The Whateverth Rejection. Subject is excited once again. They have completely fallen in love with their new project. Rejections are noted in the spreadsheet but no longer obsessed over. Agents who express an interest in the subject's future novels are added to a new spreadsheet, and their blogs and Twitter feeds are followed.

Subject tries not to think about what will happen if the old project is rejected entirely while simultaneously reminding themselves they haven't lost anything. Their life is as good as it ever was before they even started writing, except now they have a novel to be proud of.

And hopefully, still, publish some day.

5(ish) Reasons I Love Steampunk (and a Winner)

Last week, I held a contest. After busting out my d20, the winner is: SID G! E-mail me at adamheine(at)gmail(dt)com to name and collect your prize.

And now, five reasons I love steampunk.

1. Floating mechanical castles

2. Because where else can you take over the world with only science and a really awesome facemask?

 3. Airships

4. Because you can introduce a guy with a mechanical arm, and nobody ever asks how it works.

Arm and photo courtesy of Phillip Valdez

5. AIRSHIPS!!
(Seriously, I don't know what's wrong with me either, but LOOK AT THESE! AREN'T THEY AWESOME?)

Confession of an Analytical Writer

My characters don't talk to me.

They don't talk to me. I don't feel like they're my friends or someone I know in real life. I don't spend time with them, and they don't bug me with their story until I write it.

There, I said it.

I know a lot of you writers are the opposite. A character starts talking to you, tells you their story, and you feel compelled to write it. And I'm really, really sorry, but that's never how it worked out for me.

I usually get a world first, one that's in danger somehow. And then I have to think of an epic plot to save it. The characters come later as I ask questions like: Who lives in this world? Who has the abilities to save it but is least likely to do so? Who are their friends? Their enemies?

Even once I find the characters, they don't tell me their story. If they ever did, it would be like, "I read books and don't do anything interesting." Or "I'm a ninja and go on missions and stuff." Or even "I start fires with my mind, but only when nobody's looking. I'm just trying to stay out of trouble."

They don't talk to me, but if they did, this is what they would say. Because my characters wouldn't want to get involved in the story I put them in. That's the whole point (and maybe one of my themes): my characters don't want to save the world, which is exactly why I choose them.

And they don't tell me their story. I tell it to them.

My characters never break the fourth wall. They do whatever I need them to do. The guy who used to work in a bookstore? Now he works on his father's shipyard (and only wishes he worked in a bookstore), because there's more conflict that way. The ninja who was framed for killing his clan leader? Maybe he really did kill him -- or was about to -- because that makes later plot points that much more dramatic.

They don't complain. They just...change.

Sometimes I wish they spoke to me, because then I'd know I was starting with a strong voice and a deep character. Instead, I have to decide what I want their voice to be and what their goals are. And I have to decide if that fits the story I put them in.

I know there's no wrong process, but when other authors talk about these characters that won't leave them alone, sometimes I wonder if I'm doing it right. So I had to confess: I'm not like most writers. I don't write novels in some kind of inspired dream state. I solve them like a computer program or a Rubik's Cube.

And for some reason, it works, too.

Throwing Rocks at Your Characters

They say when you don't know what happens next, or when the story is slowing down, the best thing to do is throw rocks at the characters. It means make things hard for them. Just when they think they got out of one scrape, toss them in an even worse one.

I learned this best from one of my favorite chapters in Air Pirates. Hagai (not a pirate) needs the help of Sam (pirate) to find his mother and plans to leave the town of Providence with him. Unfortunately, the Imperial Navy and another particularly nasty pirate named Jacobin Savage don't want Sam to go.

The outline for this part said "Hagai helps Sam avoid arrest then together they escape Providence." But when the time came to write it, I wasn't sure what that looked like.*

It started simple. Hagai boarded their airship just as two Navy ships showed up and starting shooting at them. Fortunately Sam and crew had a clever piratey maneuver to get them airborne fast and out of range. It was a good scene, but it felt too easy.

So I threw rocks.

They escaped the first two ships, but the Navy was ready for them. Over half a dozen new ships came out of the clouds and surrounded them. They attached themselves to Sam's ship with steel wires and started reeling them in.

It was good. It was tense, but now I had a new problem: how would they get out of it? Whenever you throw rocks, you'll run into this, but that's when you know you're doing it right. If the situation isn't impossible, it means it's too easy.

I won't tell you how they escape (hint: it gets worse before it gets better), but I will say that what started as a clever-but-simple maneuver turned into one of my favorite battle scenes in the entire book. (In fact, I had a hard time topping it for the climax...I'm still not sure I did). All from throwing rocks.

To sum up:

• When the story is slow, or you don't know what happens next, or things feel too easy: Throw rocks at the characters.
• Throwing rocks means: Every time the characters think they're okay, make something even worse happen.
• When the situation looks impossible, you're doing it right.

Have you done this in your stories? How did it work out for you?


* It's true, my outlines used to be really vague. They've gotten progressively more detailed the more novels I write. But no matter how detailed your outline is, eventually you do have to make up something.

A Contest for My Tiny Little Cash Cow

So it's not really a cash cow, but while Air Pirates fights its way through the query trenches, "Pawn's Gambit" is still over there making money.
That's right, you guys. Those selfish requests I made? You totally stepped up. Thanks entirely to you, my first-and-only pro sale is going to be printed in Beneath Ceaseless Skies' Best of Year Two Anthology. And I'm going to pay you back the only way I know how: with a contest.

Leave a comment, and one of you will randomly win your choice of the following:

1. $5 for Amazon or Barnes and Noble (enough to buy, say, the anthology when it comes out in the fall...if you wanted).
2. A critique of a query letter and/or the first 10 pages of a novel.
3. A sketch of anything you like.

The winner will be announced Friday morning, July 29th.

I feel a little silly celebrating every little dollar this one story makes, but when you're in the query trenches, you gotta take what you can get, aye?

And anyway, as long as I'm going to have a patron, I'm glad it's Beneath Ceaseless Skies. The art, the stories, the editor...that magazine is a class act all the way. If you haven't already, go check it out (besides, it's free).

A Tip for Writing Multiple POV Characters

My current WIP has two POV characters, kinda like Scott Westerfeld's LEVIATHAN. While I was outlining, I realized my favorite scenes were spread out between two of the characters: the ninja and the con artist. But neither of these characters had the whole story.

See, when choosing a protagonist, you need to choose a character who does all the interesting things and who has the most interesting character arc. And I had two characters who had all the interesting stuff spread out between them (actually three: the con artist has a sister whose arc I want to explore too).

There were a couple of ways I could've gone with this: (1) focus on one character while downplaying the other or (2) write a dual storyline. I've already written a shared story with mixed feedback, so I wanted to focus on one character this time. But who? To help me decide, I took a long look at each character and thought, "If this book was ONLY about them, what would their plot and character arc look like?" Then I would pick the arc I liked best.

Instead, I ended up with A REALLY STRONG DUAL STORYLINE.

Don't get me wrong. Writing from two POVs is still going to be a lot of work to do right, but this feels like a good way to start.

Ever written a dual storyline? Got any advice before I take it too far?