Hello Scion 2e Backers!
Here is a note from Neall concerning the errata that did not make it into the books:
Greetings, true believers and Scion backers —
Thank you for your patience and support over the last few weeks. It’s enormously disheartening to me to see an event that should be a culmination of years of hard work have some known errors still in the final product, and it shouldn’t have happened. There’s nothing game-breaking in there: despite some wonkiness with the pre-generated characters, the game is fully playable. But it doesn’t have as much polish as I worked to have, and it isn’t what you were expecting. Whom the Gods notice, they destroy...and this book had a lot of Gods in it.
Obviously, some errors were going to happen. There isn’t an RPG book on the market that doesn’t have a single typo, or spacing error, or oddly-worded power. Roleplaying games are big technical manuals, full of moving parts and the gestalt product of dozens of writers. I fully expected to see a dreaded Page XX that just got missed (maybe because it was rendered as pg. XX rather than p. X or pp. XX, so a find and replace missed it) or that I kept forgetting to give Artemis the Wild Purview, which was something that came up in development. Those kinds of errors are a rite of passage for designers. What I didn’t expect was to see a dozen little errors cropping up through the text — especially since they were ones I remembered fixing with a sense of satisfaction. It was as much a shock to me as it was to all of you.
You did not pay for a book without errors, but you pledged to this campaign with the full expectation of a polished book. It’s polished in many places, but obviously rougher in others, especially when it comes to synching Origin and Hero. This is my responsibility and fault as developer, and you are owed an apology and explanation. I am very sorry.
So why did it happen? What it ultimately comes down to is a stovepiped process with single points of failure in succession. The errata methodology that has served us well for over a few dozen books broke down, but it was designed to handle typos, not a sync across two corebooks using a completely new system with a long-revised development process.
Everyone here was told about the errata threads on the Onyx Path Forums, but that was our first mistake looking back on it, really. The thread quickly filled up with redundant information in a format that wasn’t easy for me to capture and act upon. Capturing that took an enormous amount of energy, and not everyone used the errata threads — I got messages on the Discord and over Facebook, in private messages on the forums and elsewhere. I took what I got (when I was able to remember to see it) and put it into a spreadsheet with two columns: the page number, and the errata item. Some of those errata items I discarded as duplicates. Some of them weren’t errata, not really; “This power is too strong,” or, “Should it be fighting instead of flyting?” (It was flyting.) But there were hundreds of power sync issues between the two books and individual typos and system artifacts left over from development.
The second mistake we made was trying to input the changes directly into InCopy, a program we use to interface with the layout program we use to build the books in PDF. In the past, we marked up PDFs during the proof phase for the layout person to implement errata, but as corebooks got larger and therefore had more errata, this became unwieldy. Inputting the changes into InCopy seemed much more effective, and was with previous books, but it wasn’t with Scion. I inputted hundreds of lines of errata, but even a small error rate there was going to be magnified dramatically. And since I was the only one who could effectively adjudicate the errata, I had the task of doing all of it individually.
I’m not going to blame all the errors on InCopy, as easy as that would be. Adobe Creative Cloud is temperamental, even if it’s the industry standard. It’s those errors that irk me the most, though — things like the Kami Asset Skills, or the Manitou Virtues, that I was positive I fixed but stubbornly reverted when I closed the program. With over a dozen previous books being OK, I thought I was finished with the errata.
But that should have been fixed in the proofing phase, yes? All of that should have been caught? It would have been, had I been more diligent, perhaps — but the proofing phase is more for visual design and text alignment rather than inputting errata. Like I said, the errata wasn’t not input — it just wasn’t fully implemented. On a casual glance, most of the stuff is fixed, so a causal read of it saw all that as being fixed.
I’m not telling you these things as an excuse, but because you’re owed an explanation. So how do we fix it, and where do we go from here?
On fixing it, the PDFs and PODs of Scion Second Edition will be updated with the errata, corrected sample character sheets, and backer credits. We’re making up an official errata sheet and FAQ PDF to go along with your print run books, and you’ll be directed to that errata via this Backer Update, on our site and social media, and with a card being shipped with every copy of the books.
Secondly, nothing on the level of Scion will be done by a single person. The Trinity Continuum line and the first main book, Trinity Continuum: Aeon, already divides labor by lead developer (Ian Watson), book developer (John Snead), and systems developer (Danielle Lauzon). We’ve also spread the development responsibilities out on our Scion supplements in production, to talented creators on the Scion Companion (Meghan Fitzgerald), the Bestiary (Christine Beard), Scion: Dragon (Danielle Lauzon), Masks of the Mythos (Chris Spivey), and Titanomachy (Monica Speca).
Third, if you pledged to the Geist 2e Kickstarter, you’ve already seen our new errata data capturing system put into place: a submission form that outputs errata on a single sheet by page number and by type, so it can be handled by multiple people and then individually checked by those people during the proofing process. So Eddy might handle typos, for example, while I would handle consistency or textual issues that require developer adjudication. This not only does the work of formatting the information into an actionable state, but lets us divide the workload and get it done faster.
By dividing the labor and making it less of a stovepipe and more of an open process that can be addressed by multiple members of the team, this removes the single point of failure.
Everyone, again: I’m really very sorry there are errors in the final text, and we're going to correct it on multiple levels.
Scion Errata and FAQ PDFs Link
Here's the link for the Scion Errata and FAQ PDFs; this download contains two PDFs (one full-color, one black and white for printer ease) with the errata and FAQs for Scion: Origin and Scion: Hero Second Edition. There is one page of errata for each book, a page containing the FAQ, and the color PDF also contains updated pre-generated character sheets for both books:
For the Updated PDFs of both books containing the fixes, you can download them from your DriveThruRPG Library. Please be sure you've cleaned your cache so you read the updated ones. If you haven't yet downloaded the Scion: Origin or Scion: Hero 2e PDFs, the links are in the Digital Downloads section of your BackerKit page.
Thanks to everyone for their patience as we sorted this out.
Scion 2e Kickstarter Backer Rewards Are Shipping!
Word from our fulfillment shipper is that they have been boxing and labeling and have started sending those packages out this week. When they let us know that all the packages are out into the hands of the shipping services, we'll let you folks know!
Here's where we are with the next wave of projects!
Scion: Dragon: First Drafts
Masks of the Mythos: First Drafts, preliminary title.
Scion Demigod: First Drafts.
Creatures of the World/Bestiary: Development (writing is finished).
Scion Companion: Development (writing is finished).
Scion Ready-Made Characters: Editing
Scion Jumpstart: Layout
Scion Origin and Scion Hero: Shipping to backers.
Scion Dice: Shipping to backers.
Scion 2e Screens: Shipping to backers.