This time-tested fantasy RPG has come to market in e-form and hardcover. I was developmental editor.
Randy is a friend of nearly forty years going back to our college days. He’s an interesting guy. Many people talk about doing things; Randy goes out and does things. He wanted to be a successful financial advisor, and he became one. He wanted to play in a rock band, and he does. He wanted to learn SCA-style medieval combat, and he has done so. He wanted to be an officer in the Army, and he was.
He also wanted to play a fantasy role-playing game that was as realistic as one can be and still have profound supernatural mechanics. One always needs that qualifier for the obvious reason that “realistic” doesn’t normally imply magical fireballs and summoning ogres. For our purposes, realistic means that the physical movement and combat are plausible. Randy had done enough SCA fighting to see the fundamental problems with physical combat as presented in most RPGs and movies. And yes, there is a school of thought that says: “Hell with realism, it’s fantasy, I want to do epic things.” And to that I think Randy might say: ‘To each their own. But over the years my players have done quite a few epic things. Not every system is for everyone, and I get that.’
When we got back in touch in life after a long stretch of doing our own things, Randy showed an interest in building his writing skills. He wasn’t bad, but he could improve, and we worked on his fiction writing techniques. Some of the fiction involved stories from his RPG gaming world, tales played out by his merry band of tabletop players. That was fine, and Randy made rapid strides. While all of his group had made contributions and suggested refinements, two seemed most involved: Mike Cook, one of our old cronies from UW, and Keith Slawson. Keith was not well, but wanted with all his heart to assist with the layout and graphics. Here’s the kind of friend Randy is: He could have just punted and gone seeking those services elsewhere, but so long as a chance existed that Keith might be able to offer them when the rulebook was ready, Randy kept that hope alive for him. I had the pleasure of brief correspondence with Keith before his passing in late 2020. Randy, of course, visited him to the very end.
As for Mike, he aspired to publish fiction based on the LoC world, and the same drive that once put colonel’s eagles on his shoulders was in refined evidence with his work. This resulted in Out of their Depth, an excellent hard fantasy novel I had the pleasure of midwifing. I am not sure I’ve ever seen a client improve as fast as Mike did, and his medieval vocabulary taught me some new words along the way.
It was a process. This might sound odd, but rulebook editing is technical editing. I do some tech editing here and there, and even though Randy’s project was a game guide, the mentality is similar. While humor and style matter, the heart of the project is how it organizes and presents information. I have done a lot of RPGing in my life, but have never played a moment of LoC, so in some ways I was the perfect guinea pig. Randy was very receptive to rules modifications and procedural clarifications. He laughed over my developmental editing style, which is to explain a problem, make a couple of sample corrections, then let the client hunt up and fix the rest. It would be sort of drill sergeanty on my part, except that I’m not raising my voice or pointing someone’s genetic shortcomings in an attempt to motivate them to do a proper about-face.
For Randy, the hardest part was something many authors experience on long-term projects: One cannot forget what one knows, nor easily put oneself in the place of not knowing. Let us imagine a fight scene in a novel. The author has worked on the novel off and on for twenty years. She has complete mental video memory of how the fight “happened.” She knows how she pictures her characters, how they maneuvered, what their voices sounded like. Her reader has none of the above, and knows only what he learns from her portrayal. Does it matter that the room has a table in the middle? Maybe; probably; depends. It’s probably an obstacle in the fight, in which case at least enough description is wanted to help the reader picture the scene. Does it matter that it’s oak or walnut? Probably not right then. Her challenge is to keep the readercam steady, furnish enough description that her reader can follow the action, and avoid overdescription. It’s difficult to strike the balance between too much description and not enough.
This also applies to such areas as RPG rules. Randy has developed the rules for so long he can hardly remember what it is like not knowing them, so my ignorance was a help. If an experienced RPGer with reasonable comprehension skills couldn’t figure out how something worked, this raised valid questions whether something had been left out, described ambiguously, and so on. We changed quite a bit of the basic terminology because I thought some of it created confusion, and added a Game Concepts section in the front so that players had a quick reference for the terms one must understand in order to play the system. Randy came up with a genius way to present descriptions of the character skills: He created a ne’er-do-well elf named Potlatch, assigned him one point in each skill, and had him walk through a (somewhat contrived but not entirely implausible) story in short installments that involved one skill at a time. It’s hilarious, especially with Randy’s wry style of infantryman humor. As with anything Randy cares about–which means most of what he spends his time on–he took the time to do a really good job.
Another example is how the game handles the common low-value loot that characters tend to accumulate in the course of adventuring (vanquished foes’ weapons, load-bearing equipment, doodads that don’t do anything special). Randy doesn’t think the game should be Lords of Bookkeeping. Therefore, the rule is that players are assumed to gather up and sell whatever useful when possible. In turn, players do not have to keep track of and replenish consumable supplies of arrows, bolts, rations, and so forth. The selling process is presumed to sustain the common consumables; anything special or valuable is not considered common, of course, and gets valued separately. What a fantastic idea, right? One abstraction kills off two annoyances that few players would miss.
One notable aspect of the game is the lack of character classes. A player may define their character as whatever, but the game doesn’t bless or curse that choice. If you’ve always felt shackled by class restrictions, this is the open road.
This rulebook process took maybe three years. It came into final form, with areas of confusion ironed out and graphics added. Things happened. A pandemic came and sort of went. We pimped it at two Orycons and got some minor interest. Keith passed. Mike published his book while giving important input. Artists flaked. Artists delivered. Now here we are.
Randy has a bunch of online playing aids that supplement the book. If you’ve been looking for an RPG system that is designed for plausible melee and missile combat, one well refined through decades of play and experimentation, this could be just what you’ve long been looking for.
Later addendum: I have received my copy and it’s a beauty. Great layout, professional artwork, solid production. If you’re like me, and want to pick up the physical book and read relevant sections, you will appreciate this.