Home Creators Posts Import Register Favorites Logout

Content

I'm hard at work on Shallow Graves errata, which means Black Vans is on a bit of a hold until I've got that sorted. However, I thought I'd give you a peek into that engine today.

A lot of errata is little stuff - hilarious typos, table fails, subtle layout or formatting wonkiness, etc. These are the sorts of things that become impossible to see when you've read and reread the same couple hundred pages 20 or 30 times. After a while, your brain just sort of sees what is supposed to be there instead of what is. That's why an editor is so important - to get a fresh and professional second set of eyes on the text. But when the developer goes in post-editing and makes little adjustments here and there, there's a good chance that they're introducing more little errors that quickly become invisible to the creator. And I'm not much more qualified than a layperson when it comes to catching design errors and oddities.

So, while there's very little glory in catching the second period at the end of one sentence or in noticing that a "to" should be a "the", catching these little gremlins makes a book better.

Some errata is a matter of clarity. If someone gets something out of a sentence or paragraph that is not intended, it's always worth checking to see if there's a better way to convey the information or clarify the intent. Once in awhile, it'll be something like "make sure to stipulate X", and X is very clearly stipulated in the paragraph they're referring to; those I just chalk up to the fact that most of us have to read our RPG books around busy lives, often at the end of the day when our brains are apt to miss things sometimes. But for the most part, if someone is asking a question, I'm going to take a few words to clarify intent.

Then there are the comments that point out holes. It could be an unintended way to exploit a system or rule, a failure to address or unpack some aspect of an effect (such as how to calculate Scar Power on a Technique based on an Adaptation or Form), or just a surprising missed opportunity (such as allowing Internet Acuity to make the Deviant an internet hotspot). Often, these come with suggested fixes - some that I end up using, although I often implement a fix differently.

Some errata is a matter of disagreement. Most of the time, these are about mechanics. This Merit should cost more or work differently, for example, or that Scar should impose a Condition instead of relying on a subsystem the way it currently does. It might be born from an actual play experience ("someone tried to argue at the table that an eyelid is a door because it opens and shuts and you can stick your finger through it"). It could be a matter of differing tastes, play styles, or opinions. While I read and weigh these suggestions, I don't always act on them. They could be "different but not better" than the current version. They could sound like they'd be really cool at the right table but likely to be wrong at most tables. They could be in opposition to my design intent (which isn't usually spelled out, so a reader can be forgiven for not knowing it). They could make a convincing argument, but it will take too many words to change (more added words means more opportunities for new errors to creep in, remember). Factored into this is whether I've heard the same suggestion multiple times from different people.

Finally, there is a matter of sensitivity. Deviant is a horror game. It's meant to create and portray the experiences of characters who routinely find themselves in bad or uncomfortable situations (sometimes it's even their own fault!). But it's not meant to make the players uncomfortable. So, when the presentation of horror tropes strays into "90s edgy" (relying on shocking the reader with gratuitous and extreme scenes of violation), it's good to have someone point that out. I'm less prone to this now than I was in my early 20s (you know, in the 90s), but it can still happen (one of my art notes for the core crossed that line and was roundly and rightfully rejected by the in-house developer).

More commonly (but hopefully still not frequently), I unpack an idea in a way that ends up misrepresenting (or seeming to misrepresent) someone's lived experience. This is never intentional. Ray Bradbury used to compare himself to a compost heap, and I think all writers are a bit of that. Even if that heap is piled high with organic fruit rinds and vegetable peelings, sometimes someone will toss a piece of scrap wood treated with arsenic into it, and that poison is going to become a part of any food we grow in our garden. It sucks, but it's the reality of the creative process. And as with those annoying typos, the writer is seldom in a position to notice these (it's not like arsenic makes the tomatoes glow in the dark). So, while pointing these things out in errata is hard (and receiving them doesn't exactly give me a warm and fuzzy feeling), it's the only way to keep the arsenic out of the produce at the farmers market.

In short, thank you to everyone who sent errata. You're helping me make Shallow Graves the best supplement it can be.

Comments

No comments found for this post.