Transmissions From The End #15: The Sounds That Remain In Question

Enjoy this blast from the futurepast…

The Sounds That Remain In Question

January 4th, 501 R.T. 0700 Hours {Local Time}
Deck 12 Situation Room of the Vitrix Carrier RAS Lancelot
0.01 Parsecs Spinward of PH-087 “Hong Kong Station”

>>>>ONI Net Log Active
>>>>Ordo Seclorum Est 8.0 Encryption Active
>>>>Remote Satellite Comms Vetted. Vocap active.
>>>>Voice Prints Verified: President Dave Carter (DC), Commander Jesse Kilgannon (JK), Major Gloria Kilgannon (GK), Captain Michael Kilgannon (MK), Governor Akira Yuzaki [Hong Kong Station] (AY), General Andrew Kirin (AK), Rear Admiral Jane Deftinwolf {by remote} (JD), Director Connor Fagan (CF).
>>>>Level 9 Firewall Engaged; Suborbital Uplink Secured


DC: Thank you all for coming so early in the morning and on such short notice.

CF: Mr. President, before you say anything else, are you sure that this meeting site is secure. I understand that these “Redeemers” are quite advanced.

DC: Jane?

JD: All possible precautions have been taken. However if I.W.D. (R.I.A. Information Warfare Division) would like to sweep the room for bugs or triple-check my encryption, I won’t be insulted. I can’t make any guarantees, Director. But I don’t think you can ever.

CF: Perhaps this meeting should be delayed until such a time as we can have guarantees of operational security?

AK: All due respect, but this has been delayed too long as it is. We need to come up with a gameplan here.

DC: I agree, General. Ace, tell us the story so far.

JK: October 4th, 499 R.T. Avalon Standard time. Communications Tower Delta-462 on Hong Kong Station goes dark.

JD: Most locals notice only a small period of downtime on their Commlinks before another relay carrier picks up their signals.

JK: Remote access to comms systems on D-462 is locked out. Manual access is cut off. Infiltration teams who enter through the ventilation system do not leave alive. Drone reconnaissance gets jammed or otherwise taken offline.

JD: Simultaneously, an entity calling itself MONAD—and occasionally referring to itself as The Demiurge or The Demogorgon—makes contact with numerous gray databases throughout the Galaxy, including Cydonia, which is—

CF: Obviously, we’re familiar with it.

JD: The messages that it transmits are badly fragmented and barely coherent.

AK: Wait a second. Stupid question. Is this thing a hoax or not? Because according to the memos that I’ve gotten—

MK: It ain’t no hoax, General. You pulled our asses out of the fire on Salem. The hostiles there were these Redeemers. Working for the MONAD intelligence.

GK: You’re jumping ahead a little, don’t you think?

AK: I see.

JD: Welcome to the circle of trust, General. As I was saying, the MONAD entity claimed omnipotence and omniscience, but did not seem capable of coherent communication. Or perhaps, it simply enjoyed being cryptic. In any case, a link between it and the GAIA was established almost immediately.

DC: A link we can’t confirm or deny.

CF: And to prevent a panic, we issued a press blackout.

JD: At the very least, we can confirm that by all indications MONAD is a self-aware neural network, the most advanced AI since the GAIA, even if it has no link to that entity.

AK: If it’s not the GAIA, who made it? Why?

JK: We don’t know. Either.

AY: Excuse me, at this point could I ask the purpose of this meeting?

DC: The purpose of this meeting is to create a plan of action for dealing with the MONAD entity and the potential threat that it poses to Hong Kong Station and the Galaxy.

AY: Inasmuch as the threat is contained within Hong Kong Station, this is an internal matter for House Yamamoto to decide. Yet, I am the only House Yamamoto representative here. This is an obvious violation of my interests and our economic security. I must ask for a private—

DC: This is bigger than House Yamamoto. Bigger than any of the Great Houses. This has the potential of impacting the lives of every Republic Citizen. We have done you the courtesy of not inviting House Dallas or House Dresden to the discussion table—yet. In turn, we ask that you participate in this discussion. Deru kui wa utareru.

AY: I see.

JD: Ace, continue.

JK: On October 16th 499 R.T. the MONAD entity goes silent. It stops communicating with the galaxy. Attempts to physically access Delta-462 remain unsuccessful.

AY: We do not have access to remote climate control for that tower or to the explosive bolts that would be used to safely jettison it.

AK: Well, that answers my next question.

JK: No further developments until May of 500 R.T..

CF: Actually, that’s not entirely true.

JD: Go ahead, director.

CF: We continued to monitor transmissions to and from Delta-462 during this time. MONAD made a handful of “outgoing calls” to various places around the Galaxy Net. Communicated with some of its Redeemers. It invited several other individuals to make a “pilgrimage” to Hong Kong station to commune with it. We have no way of knowing if any of them made it. We intercepted and decrypted all of them. Mostly philosophical discussions. And some logistics. The organization of M0TES—social mixers of random individuals for experimental purposes. A lot of that chatter was disinformation but…

JD: Did you detect any hint of what it was planning for May?


JD: Then clearly, we do not have access to its high security communications.

CF: Nonetheless, we are certain that MONAD had no ties to the Christmas 499 massacre. That was a Collective Automata action. Verifiably.

JK: May 1st, 500 R.T.. Dallas and Yamamoto are engaged in open warfare on Salem. They and Republic observers are engaged and destroyed by unknown forces. These “Redeemers” are augmented Celestials, robots, and drones answering to MONAD. They force fighting to a standstill on the planet. Republic reinforcements arrive to assess the situation. Including me and my team.

GK: The Collective Automata were also on-hand to secure a neural network—crucial to their operations—that had been captured by House Yamamoto. We’re not sure if that was a Redeemer objective or not.

MK: Our target was this truly gassed up Kapsilus Arms Troll Drone that was apparently acting as some kind of a remote signal hub for the Demiurge. It was being run directly by the Demiurge, and was acting as a signal bridge to other Redeemer units in the area. Code name: Wrath of God.

JK: Not an exaggeration. The three of us working together with close air support were barely able to take it down.

JD: It was at this point that it became clear to us that one Steven Wherner, C.E.O. of Tiberius Arms, a House Dallas subsidiary, had been a sleeper agent of the Demiurge for some time. He was killed in action on Salem, of course, and later on Arcadia—after defecting to House Yamamoto.

CF: Is it your policy to harbor terrorists, Ms. Yuzaki?

AY: I am sure I cannot say.

JD: Are you aware of any additional clones that Dr. Wherner may have made?

AY: Again, I am sure I cannot say. I will make inquiries.

DC: Thank you.

CF: After the Redeemer force on Salem was beaten, we used the presence of the Collective Automata to mask the fact they were ever there. We maintained press containment as best we could.

AK: Is it me, or have the Redeemers done basically nothing since then?

JD: It is true they have been primarily on the defensive—

JK: Or biding their time.

AY: Until the September riots.

JK: This is where my firsthand narrative is limited. Jane, you’ll take it from here.

JD: Of course. I was just getting to that. On September 26th, 500 R.T. shortly after Nippon Sector quarantined itself from the riots, Hong Kong station entire went dark. Perhaps, Governor you could shed some light on the events there.

AY: I am afraid I cannot. I was trapped at my home in Osaka for the duration of the riots.

JD: Well, here is what we do know. Someone—and we have no suspects except MONAD—released some kind of weaponized nanites on Hong Kong station at the height of the House Wars fighting. Possibly multiple strains of weaponized nanites. A large subset of the population was killed outright. Still others retained their mobility and functionality but experienced severe hallucinations. Chemical and biological weapons—unlike anything we’ve seen before—were used also. Others were merely “switched off” but unharmed.

AK: Alright, now I’m getting ahead of myself, but doesn’t it occur to you that that was the ideal time to nuke the station from orbit? We’d have had plausible deniability, and no more MONAD to worry about.

AY: How can you even suggest that! You are talking about killing over a million of my citizens! Of your citizens!

DC: The Governor is right, General. Taking the shot on Hong Kong station is an absolute last resort.

JD: Things on the station seem to be “back to normal” now, so to speak. The survivors are moving on with their lives. But we don’t know what the Demiurge did during the comms blackout. And besides the hundred thousand or so casualties, there are hundreds of people who simply cannot be accounted for. And I think that about brings us up to speed.

AY: Well what are you proposing.

AK: Admiral Deftinwolf, do you speak for the regular Armada here as well as ONI?

JD: I do.

AK: Well, excuse me if my first question is overly obvious, but why not just hit Delta-462 with a mass driver or something. No more Delta-462, no more Demiurge, correct?

Hell, we could nuke it from here.

AY: Are you serious!?

JK: Good question, General. Two reasons.

AY: Is one of them that there is no way to destroy Delta-462 without depressurizing the entirety of Hong Kong Station? Even if the Republic citizens there could be evacuated, you would be looking at a monetary loss to House Yamamamto in the vicinity of 2.1 Trillion credits. Would the Republic be willing to foot the bill for that?

AK: Listen here, little lady—

JD: That is in fact one of the reasons. Here is another. Any preliminary action we take runs the risk of preempting the Demiurge.

AK: You’re going to have to break that one down for me.

GK: In your “Shoot Delta-462 with a mass driver” scenario, you’d want to evacuate the civilians first, correct General?

AK: Of course. I’m not a butcher.

JK: Well if you do that, you risk tipping our hat to the Demiurge. Which could then kill those civilians or trap them there as hostages—human shields. …It’s what I’d do.

CF: He’s right. We have to assume that the Redeemers have operational control of Hong Kong station security now.

AY: What? You’re saying that thing controls my station security?

JD: It’s true. The Redeemers had weeks “alone” with Hong Kong station during the riots. There’s no way to tell what countermeasures they’ve set up.

AK: So it’s a Mexican standoff, then.

JD: It gets worse. Director, please tell them about Operation Armistice.

CF: The greatest danger, as far as our involvement is concerned, is the idea of the Demiurge making one or more copies of itself and storing them as off-site backups or worse, running them concurrently on other servers.

JD: Although psychological profiles—inasmuch as the term applies—indicates the Demiurge won’t do the latter.

AK: Why not?

JD: In layman’s terms?

DC: It likes being special. … Seriously. God-Complex and all.

CF: As I was saying. The Demiurge being able to back itself up would take the nuclear option right off of the table.

AK: What is being done to stop this?

CF: Well, if the Demiurge could be called a mere program, it is an enormously large and complex one. Even by modern standards of data storage and bandwidth. Also, one that could only be run on a very limited subset of hardware.

JD: As a matter of fact our understanding is that it has had to upgrade the hardware on Delta-462 as it has continued to evolve.

AY: Really?

CF: We are constantly—as in as we speak—monitoring all outgoing communications from Hong Kong station via a direct ansible tap.

AY: Isn’t that illegal?

CF: Under normal circumstances? Sure. Anyway, if we detect any file transfer that seems even remotely long enough or large enough to be Demiurge uploading its source code elsewhere, we will jam or intercept it. Same thing for multiple short burst transmissions to the same source.

JD: What about a Torrent style transfer protocol? Breaking the file into millions of pieces and compiling it later.

CF: Something like that would require, approximately, the processing power of every Commlink in the Galaxy as a subscribed node, to transmit and compile the pieces. It’s not viable. We hope.

DC: What about couriers?

CF: Well, anyone wanting to transfer the entire—hypothetical–backup would need a data storage unit the size of a starship to move it. That we’re scanning for, at customs and more importantly at the warpgate.

DC: What about multiple couriers with pieces of the source code.

CF: They’d need hundreds to transfer the file with standard storage devices. That is the biggest threat right now. We’re checking every outgoing individual. And we’ve made sure that Gatrlore adepts can’t access the station. But short of a full Quarantine—

AK: If it’s not too late, I’m sure that Admiral Deftinwolf and I can have one up within 72 hours.

AY: A quarantine? That’s preposterous. Do you have any idea how much material and trade goes in and out of Hong Kong Station every day? You’d be killing us as sure as—

AK: Listen lady.

JD: Enough. Please. Anyway, Operation Armistice is a contingency. If Director Fagan detects the Demiurge transferring a backup—and we cannot stop it—I have a Vitrix carrier in place ready to nuke Delta-462.

AY: And kill a million Republic citizens?

DC: If it is our only shot at the Demiurge, we are going to take it.

CF: This seems like a good time to remind you, Governor, that this meeting is Classified. Code Black.

JK: That means…

AY: Yes, I’m familiar with it. Don’t try to intimidate me.

AK: So it sounds to me like Operation Armistice isn’t really a battle plan at all. It’s a last resort.

JD: Correct.

AK: What about sending a commando team to manually blow the explosive bolts and jettison Delta-462?

JK: We’ve run simulations on that. They haven’t come out favorably. Oh, my team can get inside and blow the bolts…but the Demiurge will have at least a seven minute window to react.

JD: That’s enough time for the Demiurge to sterilize everyone on the station, to mass-transmit its source code, to order suicide bombers to—

AK: Alright, I get it. What about using a nanoforge to create a new airlock? So that we can shoot Delta-462 off the station without killing everyone on board.

AY: That actually sounds like a good idea, General.

JD: The trick is doing it in a minute or less, so that the Demiurge has no time to react, and having the shot lined up. I have my technicians working on a nano-forge that could create a reliable seal fast enough.

AY: And?

JD: And they’re working on it.

DC: Alright people. I’m not hearing any perfect options. What else do we have?

CF: We’re working on engineering a virus, naturally, but as Jane has probably told you their Net security is…well, it puts ours to shame. Delivering is a problem. If we hand deliver it, we run into the same problems as with sending a team in to blow the bolts.

JD: Right now, the Demiurge seems dormant. It seems extremely wise NOT to poke it with a sharp stick until we’re absolutely sure we’re going to kill it with the first poke. We need a very, very sharp stick.

JK: Hopefully, that is where Operation Schoolhouse comes in.

JD: Hang on a second. I just detected a tap. Impossible—

AY: My God.

CF: Purge this channel. Now. We’ll go to analogue comms. Never should have been online in the first place.


Transmissions From The End #14: Reviews & More

Greetings from the End of Everything!

So, thanks in part to the work of our marketing director, a few of our games that have been out for years actually have reviews! How about that! It’s almost like we don’t actually exist in an interstitial dimensional bubble that separates us from true reality and prevents us from interacting with it or being noticed by it in any meaningful way!

The GMShoe’s (Dan Davenport’s) Long-Awaited Review of The Singularity System:
Throat Punch Games’ Review of Psionics (This One’s Even On The Big Nurple):
The Wandering Alchemist’s Review Of SPLINTER:

A soothing balm on the burns inflicted by our tremendous losses at Origins, the reviews range from mostly positive to glowing. Rock on.

If you want to buy any of those games (or the supplements and adventures supporting them), we’ll be selling them at DexCon,  July 5th-9th at the Hyatt Regency & Convention Center in Morristown, New Jersey and of course at GenCon50, August 17-20 in Indianapolis. We love meeting our fans in person, but if you can’t wait till then, our entire product lines can be found on One Bookshelf and at select Friendly Local Game Stores through our distributor, Studio2. Further convention appearances will be announced as the year develops.

Upcoming cons mean revised street-date announcements, so we’ve got those!

We should finally be able to debut the introductory SPLINTER adventure “Return To The Dread Abyss Of The Digitarchs” at DexCon, hot from the presses, by the exceptionally talented Richard Kelly.

At GenCon, for our major new title launch, we’ll have the Systems Malfunction standalone RPG. I just got done editing the introductory fiction for this one, by the aforementioned absurdly skilled Richard Kelly, and it’s a truly phenomenal read both for people brand new to Systems and to the oldest of oldbies. The playtest period on this one is ending in the next week or so, then it’s a race through art, layout, and printing in the month of July to have it ready to go for GenCon 50.

I’m excited! Are you excited?

<end transmission>

Transmissions From The End #010: Sneak Peak – Extra Lives

An excerpt from the Systems Malfunction roleplaying game manuscript:

Extra Lives

Human cloning is an established technology in the Systems Malfunction universe. However, as cloning works a little differently in every sci-fi setting, we need to be a lot more specific about how clones work here. An amusing anecdote illustrates why. During a playtest/promo game, a group of actual play podcasters were faced with a scenario where they had to evacuate as the colonists from a planet under invasion by aggressive, biomechanical aliens (if you’re your group’s GM, see In Keeping Secrets, p. XX, and Robots, Monsters, and Worse, p. XX). There were too many colonists to fit in the dropship along with the Colonial Marine PCs, so the players assumed they could avoid leaving anyone behind by decapitating all of the colonists—after all, their heads would weigh less than their bodies and take up less space!—and then have them cloned later.

That is most emphatically not how cloning in Systems Malfunction works, and acting on those assumptions would have been a disastrous mission failure. They would have brutally murdered all of the people they were there to rescue. I found this misunderstanding hilarious, but also enlightening. It was an eye opening reminder that just because I’ve been immersed in the Systems universe for over a decade, newcomers to the setting don’t automatically know its nuances and details.

Here is an overview of how cloning in Systems Malfunction does work:

  • Clones are essentially “extra lives”. All Player Characters start with three clones (see p. XX) but may “sell back” any number of them during character creation, receive +1 Edge per clone sold back (see Building Your (Tragic) (Anti)Hero).
    1. After a character dies, there is a 24 hour waiting period before their clone becomes available as the clone is thawed and awakened. It may take substantially longer than that for the character to rejoin the action, depending on where they have decided to store their clones and what arrangements they’ve made beforehand. If a PC dies, this should be worked out between the PC and the GM. If the character was an NPC, it is at the GM’s discretion how long it takes for the NPC to reappear, but the minimum time is still 24 hours. Only important NPCs have clones, and the average Joe Galaxy doesn’t have any clones.
  • With currently existing technology, a clone can only be “copied” from a living being. Preserved genetic material (or a bunch of heads in a garbage bag) is not sufficient to create a new clone from.
    1. Clones are very expensive. Creating a clone of your character costs 100,000 Credits multiplied by the number of times you have had your character cloned. In other words, creating a third clone of a given character costs 300,000 Credits. Any clones you started with don’t count towards this cost multiplier.
    2. Every clone has 10 less Purity than the “generation” which proceeded it. See Purity & Consequences on p. XX and “Spiritual Machines” on p. XX for the consequences of Purity loss. (An average, heavily augmented human can die and transfer into a clone about nine times before their 10th clone has a Maximum Health of 0 and is effectively stillborn.)
    3. Most capital ships, space stations, and cities have facilities where clones can be created and stored. Backwater colonies may not, and uninhabited/uncharted planetary bodies certainly don’t.
    4. The scanning process to create a clone takes only 10 Minutes. The creation of the clone body takes between one day and one week, at the GM’s discretion.
    5. A Player Character can attempt the cloning process himself, but doing so is incredibly challenging. The PC must have access to an advanced scientific facility (and obviously the person being cloned), must spend 50,000 Credits (multiplied by the number of times the subject has been cloned, as described above), and must succeed a Hard Science (5) Test. Attempting to clone someone in this way takes one hour for the scanning process, and the usual time for the creation of the clone body. Failure on the Science Test means that you have created an invalid abomination it would be merciful to terminate: the credits are still spent. No character can manually create a clone of herself.
  • In addition to the scientific and technical limitations on how clones can be created, there are also numerous scientific, technical, and legal limitations in place on why clones can be created.
    1. Carter’s Laws of Biogenics prohibit duplicative cloning, i.e. it is entirely illegal for two instances of the same person to be active at one time. The entire government-military-medical-intelligence-communications infrastructure of the Republic is engineered to make duplicative cloning impossible. The primary limitation is in the InfoLink Implant which allows for recording of memories and continuity of consciousness (see p. XX). The implant’s hardware has been designed in such a way that none of the galaxy’s major known powers—the Republic, House Yamamoto, House Dresden, or House Dallas—can produce duplicative clones. Attempting duplicative cloning is the single most serious crime in the Republic’s legal clone, and carries more substantially more serious legal consequences than 1st degree murder.
    2. Carter’s Laws of Biogenics also prohibit reproductive cloning, i.e. it is illegal to use cloning technology to produce an offspring that is genetically identical to yourself. The legal consequences for attempting reproductive cloning are less serious than those associated with duplicative cloning, as long as the clone created is a fetus or an infant. Otherwise, this crime is treated the same as duplicative cloning.
    3. Finally, Carter’s Laws of Biogenics prohibit “longevity” cloning. For a human example, it is illegal to create a clone of yourself at the age of 30, with the intent of transferring your consciousness into that clone when you die of natural causes at the age of 76. Other treatments exist to extend the human life-span, but they cost even more than cloning, making them prohibitively expensive for all but the extremely wealthy.
      1. While modern nanomedicine can easily cure most cancers known to man, it is still worth noting that a clone made of a body with a systemic disease will still have that disease upon becoming active. In other words, a woman with Crohn’s Disease who purchases a clone now has a clone in storage that also has Crohn’s Disease.
    4. The only cloning actually permitted by Carter’s laws of biogenics is cloning as “life insurance”. In other words, it is only legal to create and store a clone as a form of insurance against death by violence or accident.
  • Cloning works exactly the same for Replicants as for characters of biological Origin with two minor exceptions.
    1. Replicant “Clones” are instead called “Backups”.
    2. Replicants needn’t worry about Purity loss from iterative cloning, as Replicants begin with 0 Purity and can never lose Purity.
  • To review, Carter’s Laws of Biogenics limit the function of clones in Systems Malfunction to that of “Extra Lives” for people who die by violence, accident, or suicide. (If a nasty fall breaks both of your legs or leaves you paralyzed from the waist down and you aren’t near an Autodoc or anyone who can help you to one, if you have a clone, it is legal to blow your brains out and wake up in your clone body 24 hours later.)


For a mixture of reasons that are around 70% in-universe and 30% game-balance. The early Presidents in the Carter “dynasty” had specific ideological reasons for creating the Laws of Biogenics and making their enforcement so air-tight and the penalties for violating them so severe. The rationale behind the policy making was as follows.

Duplicative cloning was criminalized to prevent anyone—including future Republic administrations—from creating clone armies. To do so, it was reasoned, would create an underclass of people so replaceable they would have effectively no rights, and to protect the stability of the Republic from an “attack of the clones” type scenario. (From a game balance perspective, a character with multiple duplicates of themselves would be both overpowered and slow down gameplay.)

Reproductive cloning was criminalized under the rationale that the human race had benefitted from the genetic diversity granted by “traditional” reproduction for its entire history. A non-stagnant gene pool was desired to populate the galaxy. Also, natural biological reproduction was simply cheaper and therefore more effective than reproductive cloning.

Finally, “longevity” cloning was criminalized to prevent the further growth of the gulf between the Galaxy’s haves and the have-nots by adding a major line item like immortality to the gifts the wealthy enjoy that the poor do not.

In general, Armand Carter’s children and their children and grand-children were very reticent to allow human scientists to “play God”. After all, it was their famous ancestor that had saved the human race from enslavement to the will of a machine god during the War Against the Gaia (see A Brief History Of The Future, p. XX).


“Coming” “Soooooooooooon”

The development of the first official game setting for the Singularity System, Setting Module 00: Systems Malfunction (based on my long-running LARP of the same name) has been pretty much a goddamn nightmare. A nightmare of the endlessly recurring kind. The reason for this is no mystery: this is the first time that End Transmission has sought to publish a work of which I was not the sole primary author, and I am far better at producing my own content than I am at managing the content ouput of others. The fact of the delays was no surprise either, but the scale of them is staggering.

Some history: in January of last year, I began developing the Sol Invictus setting for the Singularity System. I realized that I could not possibly develop BOTH the Sol Invictus setting and the Systems Malfunction setting for tabletop and meet a reasonable production schedule (i.e. a GenCon ’13 release), so I decided that I would outsource the development of the Systems Malfunction setting book to an independent contractor familiar with the universe and subject matter. It soon became clear that no matter what, the Sol Invictus setting would take years for me to bring to fruition (which should have clued me in to something), but the choice to put the Systems setting book in someone else’s hands had been made, and there was nothing to be done about it. (As of now, only 110 .doc pages and 36,000 words of Sol Invictus exist, meaning that the first draft is nowhere near complete.)

The project was assigned by February of 2013, but we did not issue a contract until May of that year due to general inexperience at business, and more importantly, we were working our butts off making games.

Our plan was for a GenCon 2013 release of the Systems setting book, following hot on the heels of the Singularity System which we managed to release at Origins 2013 to modest sales (we’d initially been planning on releasing THAT at Lunacon to substantially modester sales, but that’s another story and a far less outrageous one). Contracted deadlines were missed again and again throughout July, and things became increasingly quite tense. By the time we got anything resembling a completed manuscript, it was mid-September, two months behind schedule, and GenCon had come and gone. At that point we were dealing with the stress of moving, and neither of us was looking forward to rush-processing the draft for a Con on the Cob October release. We wound up calling in sick from Con on the Cob entirely last year.

It’s a good thing we didn’t try to go to print with that manuscript, because it wasn’t actually complete at all. It took me entirely too long to realize this, as I spent three months going and carefully editing (for content and format) the rules section, before I could take a month to carefully review the setting chapter (editing again for content and format) and realize that some of it in fact was missing. At this point, it was January of this year. I had gotten over the extreme rage at all the missed deadlines between July and September, and was feeling a bit live-and-let-live. So never one to realize that a fire tends to burn rather consistently so you shouldn’t thrust your hand in it twice, I reached out to the original author. Could he deliver all of the missing and incomplete content by February 8th, so that we could get the book to print for a March Lunacon release? Of course he could, he assured me, no problem.

As of this writing it is February 25th and I still do not have a complete manuscript for layout: it is completely impractical, if not impossible, to publish this book for a Lunacon release, since Lunacon is in less than three weeks and the layout-to-publishing-to-shipping process involves several proofing stages and is rather time consuming. The complete draft is, as of this writing, 225 days late, also equivalent to seven months and 10 days, also equivalent to 32 weeks and one day. Oh well, there is always Origins. Maybe we will have a book by then. Anything is possible. This cannot all be blamed on the contractor. The truth is that the sheer scale and enormity of the project, the book, and the content it contains has expanded and expanded with seemingly every other revision and addition that we’ve done recently. Even culling everything not absolutely necessary, which I have been doing for months now, this project has lost weeks and weeks to the phenomenon software developers identify as scope creep.

In all seriousness, I can’t say that I have only myself to blame for this. But I also can’t say I don’t blame myself.

And all of this is…OK. I’ll repeat that, all of this is OK, just growing pains (even if some are more painful than others), mistakes we can afford to make, and learn from, and not make again, like the shipping thing last year. The truth is, we are (fortunately) on steady enough financial footing that this doesn’t knock us out of business as a company, and (fortunately or unfortunately) at this point we’re still very much under the radar. This is a book almost no one has heard of being talked about in a blog post that almost no one is reading. There are no legions of fans crashing our gates with rage that this book is seven months late (something that, I understand, happens even to the biggest in the business) and I am, perversely enough, almost grateful for that at this stage. It is bad enough dealing with my own frustrated expectations.

One lives, and one learns, and one continues to make games.