Home Creators Posts Import Register Favorites Logout

Content

Hi ya'll!

I've been sick for around two months, that combined with the relatively strong debuff of being a dad of two preschoolers has kept me working a little slow, but as promised, here's a (relatively quick) little blog.

I often get asked how to get into writing role playing games, or if there's any advice or guidance I would give people who are looking to write their own games. I gave a little presentation on this at a con at Georgia Tech not too long ago, so I thought I would summarize that here.

Alright, so you want to write a role playing game. Here's my advice:

Don't

-Abbadon

_________

You're still here?

Ok. I guess we'll try again. You've decided to torture yourself. Well, in all seriousness, here's my two big pieces of advice.

Examine your goals.

First, what's your goal in writing a game? Writing a whole game is a shit ton of work. Writing a whole game with art/layout etc will take inordinate times of time, money, and effort. It's the kind of thing that for a larger book (like Lancer) you are looking at hundreds of hours of work. Even a relatively smaller book like CAIN, at around 160 pages, probably still took me around 200+ hours of work over several months. I'm a special exception, too, since I can do the art, layout, and writing myself. Coordinating this and having the time and money to hire artists and layout for a book is extra work and money that a lot of people don't have.

God forbid you are actually thinking about a print run of a book. Actually printing a book, even for a small print run (1k-3k), can be twenty to thirty thousand dollars or more plus freight, and requires knowledge of book layout, a relationship with a distributor, and printing specs.

All to say, don't get discouraged, but when you're writing a game you need to consider your goals. Are you writing this for yourself, as a hobby? Perfectly ok and valid. I have dozens of unfinished games sitting on my desktop in text documents that will never see the light of day, or I have slowly been chipping away at over the years. There's a game about a plague, a dungeon crawler, and a fully written card based board games about space combat with battleships. I don't know if I'll ever publish any of them. Are you writing for your friends to play something? Also cool and good, though don't always expect your friends to be down to play something untested and have some respect for boundaries. They just might not be interested.

If you're just writing to practice, as a hobby or for your own enjoyment, or for your friends, it's ok to set your expectations low. Don't worry about 100% finishing work, just have a good time and write as much as you can. Play in the space a bit. Be indulgent with your design and mess around. Do your best to finish, but writing as a learning exercise and for the joy of creation is healthy and necessary. You will learn a lot about writing games and about your own creative output. It's how everyone gets started.

This all changes if you're writing to publish. If you want to actually publish your work, it's going to turn into work. Work means showing up to finish writing even when the spark isn't there, or pushing through tough or uninteresting parts. It might means dozens or even hundreds of hours of writing and editing. It means cutting your work as lean as possible, even the little things that you (personally) enjoy. It means getting a focused book out there that is readable and usable by other people (not an easy task, I assure you). It also often means getting layout, art, and proper formatting for your work, which can be its own challenge and can be costly.

Of course, you might be writing to publish something kind of rough, small, or unfinished, something personal like a lyric game or a zine or something - in which case there's a little more of my prior advice in there - if it's just for you, don't worry too much. But if you're looking to put something out there that you intend other people to play, or purchase, you're gonna have to put a lot more effort and time into it. It's not going to be fun or enjoyable all the time.

The reason I give this advice is I see a lot of people launch into making games and then burn out because of how much work it is to actually put out a finished project. Finishing work is extremely hard. Finishing work that's going to reach and connect with people, that people are going to enjoy, play, and purchase, is even harder, and it's the entire reason why you don't see everyone with a cool idea take that to market. The work is the work. But you don't have to do all the work if you're not intending to sell or publish something. It's ok and pretty cool to be a hobbyist and do something for your enjoyment. Just work on things for your own satisfaction, set your expectations, and learn along the way. Without that kind of healthy self indulgent writing, no one would ever get around to making a published product, and game designers wouldn't exist.

This leads right into my second piece of advice:

Start small

Don't start by writing a big game. You're not going to finish it. Lancer involved two people without kids or a mortgage and still took almost 3 years to write and publish. Unless you know what you're doing, that kind of work is going to slaughter you.

Don't write your own game system. It's a pain in the ass. You won't have any foundations to stand on and you won't know what you're doing.

I'm built different you are thinking right now. No you're not. You will be killed instantly. You won't finish your game. You learn the most from finishing work. If you don't get to finish work, you will still learn about game writing, but a lot slower. Your initial work is going to suck compared to your later work. Get it out the way and practice. Don't start learning starter piano by attempting to play Rachmaninov note by note. You would be insane.

My biggest piece of advice to you is to start (as I did!) by writing smaller pieces of content. Anyone that's been a game designer I think has almost always started as a game master of some kind. You write little bit of homebrew or game content for your table, for the games you love, and then that turns into more and more stuff until you've started writing your own campaign setting, or set of homebrew rules, or custom classes, etc, then voila, you are suddenly a game designer.

Here's my recommendations:

Write some stuff for your home game. Write systems for your DnD campaign/game of choice. Game doesn't have travel rules? Write some. Write a cooking system. Write a dating system for your daggerheart game or whatever. Have fun with it.

Write discrete, small, chunks of content. Do a custom subclass for dnd 5e or a homebrew blasphemy for CAIN or a knight for Mythic Bastionland, something that can be done in like 1-2 pages. Finish it all the way - get art, layout etc. It will teach you a lot and it only has to be like 2 pages of content.

Write small, tight, adventures. Game systems always need them. Go write a dungeon for the OSR, with maps and art, that's like 4-8 pages. Keep it as tight as possible.

Write a guy. Think of a cool character, npc, class, etc? Write it out and stick it into your system of choice. I had a cool idea for a blades in the dark playbook once. I wrote it into the game. A friend of mine wanted to play a drider in dnd, so our GM wrote a custom species for her. Later I thought about porting it over to pathfinder. Really simple, straightforward stuff.

Before launching into my ttrpg stuff, I wrote and even playtested about 4-5 different board games with my friends in my teens and early twenties. Prior to writing Lancer, I wrote a (very mediocre) powered by the apocalypse hack that you can find here on this very Patreon! I also wrote tons of little games that lie mostly unfinished (some of them are posted here!) before launching into other, bigger ideas.

Going right into a several hundred page project that you are designing yourself is going to get you lost in the weeds. I would consider myself a fairly experienced designer at this point and it has still taken my over 4 years to get close to a version of my current big project, Icon, that I would consider somewhat in good shape to finish.

________

Anyway, I hope those two pieces of advice are somewhat useful. I have other things I could say about the game writing process but those are the fundamentals. If you stick to them, I think you'll have a good time. I want you to try writing games. Indulge in that impulse and follow it, but be kind to yourself and smart about it, and I think you'll find it leads you to great things.

Cheers,

-Abbadon

Comments

That One Irish Furry

my girlfriend has been getting into the game design space recently so needs to hear this

Torabi

I think a lot of this advice is applicable to just about any kind of project. Finishing is what stops most people. Lots of people have a great idea, but quit as soon as the going gets rough and it stops being as much fun. The ability to push through that is probably the biggest determinant to success, even more than luck or skill. Published and imperfect is better than perfect and unfinished. There's lots of trash out there, because the ability to finish is more important than the quality of the work. So yeah, regardless of the type of project: start small. Finish something. Make something derivative as practice, so you don't have to do the whole lift until you develop some muscles. Once you feel yourself straining against those limitations, then you're ready for something bigger.