Foresworn Confessions — Week Two

I worked more than 55 hours this week. Plus the standard “taking care of the family” obligations. And my temptress of a wife is upstairs saying “there’s a retelling of Taming of the Shrew on BBC America.” These are the things that stand between me and a finished game. But the overtime is the truly the biggest culprit. Thus:

Forgive me, Foresworn, for I have slaved. It’s been one week since my last confession.

My goals for this week were:

  • Settle on a list of resources and stats (i.e., be able to write up game stats for a character)
  • Stat out two example characters
  • Self-test the die-rolling mechanic with said characters

I only got the first two done this week. The self-testing will move to goals for next week. Life happens.

Here’s a little more about Foresworn. It’s a game about knights and feudal society. But not about chivalry. It’s about upholding one’s oaths when the only code of behavior is the one you make for yourself.

Being me, I’m not interested in details of Setting and evocative Color. I want Situation. All. The. Time.

Characters have a number of Oaths, that give them certain abilities, but if you break your Oath, you lose said ability. Foresworn will require the players to manage Resources (finite, expendable dice that are generated by villages, manors, orders, and other social groups) and their own Stats (reusable dice that belong to an individual character) to acheive the goals required of them by their Oaths. Here are the Resources and the Stats:


Color Description Resource Stat
Green physical needs Food Body
Yellow wealth of the world Goods Skill
Blue the pull of society and the approval of one’s peers Standing Charisma
Red violence Might Ferocity
White spirituality and insight Wisdom Soul

I also statted up Sir Stone, a young knight in love with Agnes, the youngest daughter of the head of his order, and Sir Will, the head of the order who has promised that Agnes will enter the local nunnery. You don’t get to see them, yet.

In the coming week I intend to:

  • Self-test the die-rolling mechanic with Sir Stone and Sir Will (probably w/ Agnes thrown in for luck)
  • Write up at least ten different Oaths, one focusing most heavily on each of the 5 Stats and 5 Resources.

Next weekend is Labor Day, so I may hold off on updating this until Monday.

Foresworn Confessions — Week One

I’ve been thinking about what I’ve commited myself to: Reporting on my progress week after week. It brings flashbacks of my Catholic boyhood. And thus:

Forgive me, Foresworn, for I have slacked. This is my first confession.

In the past week I have:

  • Announced my intention to design and publish Foresworn
  • Devised a schedule of writing, playtesting, editing, layout, and printing that will enable me to complete the game.
  • Felt my way through some preliminary explanatory text about the rules
  • Narrowed the list of potential resources and sketched out brief definitions

In the coming week I intend to:

  • Settle on a list of resources and stats (i.e., be able to write up game stats for a character)
  • Stat out two example characters
  • Self-test the die-rolling mechanic with said characters

I had to put in five hours today, and work looks worse for the coming week, so we’ll see how well reality matches up with my intentions. But I’ve got less than a month to start internal playtesting!
See ya in 7!

Foresworn Development Schedule

I heard so many exciting little bits of stuff at GenCon. One that stuck with me was someone (I forget who) complimenting Luke on how good Dictionary of Mu looks. Luke’s response was something like this: “I didn’t do anything. All I did was send Judd an e-mail every week asking how it was going. Eventually, he started sending me the e-mail about how it was going.” That’s it. A little nag about a little progress. Those small measures of progress add up.

I thought to myself “I could do that. I don’t even have to single out one of my friends to nag me about it. I can just use my blog.” So that’s what I’m going to do. Every Sunday, I’ll be posting what progress I’ve made in the previous week on Foresworn, my game-in-development. It’s not as big and involved as John Wick’s excellent Game Designer’s Journal from the days when he was developing Orkworld. However, I hope it can generate some of the same enthusiasm that column did. It will also keep me moving. It’s one thing to let yourself down. It’s another to let yourself down and tell all your friends about it.

That said, I’m sure that there will be weeks when my only report will be: “Worked an insane number of hours this week. Didn’t work on the game at all.” I hope those weeks will be at a minimum and that I’ve left enough room in my schedule for them.

Let me fill you in on some of my goals for Foresworn. I want this game to create and play out multi-player, conflict-ridden situations. In watching my wife write her Everway LARP, in playing Luke’s BW convention games, in watching a lot of Shakespeare, I’ve found that I like the excitement that comes from everyone having their own agenda and pushing hard to achieve it. I also know that setting up such conflict-intense situations is a skill. I want to make a game out of it. I see the game working in two phases. The Setup Phase is where you create the characters, their interrelationships, their resources, and their agendas. By the end of Setup Phase, you’ll have a situation primed to blow with juicy conflict. Then, in Resolution Phase you play out the results of that setup.

Since Resolution Phase will play more like a traditional RPG/resource management game, I’m going to playtest that part first. Once that is pretty well set, then I’ll move into the relatively-uncharted territory of the situation Setup Phase.

Oh, and I’d like to have it out by Origins. Why? Less new hotness hits the shelves at Origins, so my game would get more notice. It would have a few weeks to get played and discussed before GenCon. Plus, if I do end up missing my deadlines, I can still make a GenCon release.

Foresworn Tentative Schedule:

June 26, 2007: Finished books due back from printer
May 28, 2007: Complete interior & cover due to printer
May 1, 2007: Complete text & art due to layout
April 15, 2007: Final draft text due to editing
April 15, 2007: Final art due
March 31, 2007: Complete external playtesting feedback due
February 15, 2007: Complete external playtesting document out to playtesters
February 1, 2007: Complete internal playtesting feedback due
January 1, 2007: Begin Complete internal playtesting
November 15, 2006: Begin Setup Phase internal playtesting-Setup Phase first draft due
November 1, 2006: Complete Resolution Phase internal playtesting
September 15, 2006: Begin Resolution Phase internal playtesting-Resolution Phase first draft due

What I’ve Got

I’ve got 200 freshly-printed copies of With Great Power… in the trunk of my car.

I’ve got between 2 and 3 dozen boxes of IPR game books in my garage.

I’ve got a reservation for a rental minivan to pick up tomorrow evening.

I’ve got an feeling in my gut that’s a mix of excitement and nervousness.

I’ve got an awesome wife who’s got her own excitement and nervousness.

I’ve got an awesome daughter who’s none too sure about this whole “game convention” thing.

I’ve got about thirty-six and a half hours before I hit the road for GenCon….

…and counting.