News from Essen

Spiel Essen, the world's largest and most prestigious game fair, took place in Essen Germany last weekend. I'd been hoping that Railways of the Western U.S. would be ready in time to be shown there, and it was—just barely!

It seems to be standard practice for the initial printing of a new game product to be very small. This gives the publisher a chance to check the finished product for problems before paying to have thousands of copies made; and if there are no serious problems, the publisher has a few advance copies to show off and/or sell. The first shipment of Railways of the Western U.S. arrived in Essen on the morning of the first day of the show, just in time. It was 60 copies, and they immediately opened one copy and set it up to be shown off.

The BoardGameGeek web site (one of my favorite web destinations) had a presence at the show: they were interviewing publishers, and live-streaming video demos of the new games. Keith Blume demoed RotWUS for them on that first day, and if you're interested you can watch the video here. It's quick, only about three minutes.

The game sold out quickly; all 60 copies were gone by the second day of the show.

There was indeed one problem with those first few copies: there were no Fuel Depot tokens in the boxes. Fortunately those are not necessary components; they are used only with an optional rule, and you can play just fine without them. The people who purchased those copies can get replacement Fuel Depot tokens by contacting FRED Distribution customer service. If you are not one of the lucky few who got to go to Essen you won't have to worry about this, because it will be fixed for the first full print run.

The City Rotor tokens, the other new optional feature in the expansion, were included and apparently are pretty cool. I say "apparently" because I haven't seen them myself. Helen and I didn't go to Essen (we talked about going, but couldn't swing it this year) and so now there are some 60 people in the world who have actual copies of Railways of the Western U.S., and I'm not one of them! I've never even seen a copy I didn't make myself. There's something cosmically unfair about this, or so I keep telling myself.

But FRED says that the first real shipment will arrive soon, in just a couple of weeks. Then I should have my own copy at last, and they'll be available in both brick-and-mortar and online stores. Can't wait!

Coast-to-coast live!

This weekend we held the first live playtest of Continental Rottweiler: "live" means that we had four actual human beings playing the game, as opposed to just me, or Helen and me, pretending to be more than one person each. I'm pleased to report that it went very well.

The game lasted about six hours, and was contentious from beginning to end. I had been hoping for a fifth player, but the game worked quite well with four. The fact that everyone wanted to cross the "border" between the east and west tended to crowd players together; on the Western board, the Rockies were another barrier that focused nearly everyone's efforts. I think there's room for a fifth player, but surprisingly, six may turn out to be too many.

The new rules for handling the "income trough" seemed to work well. We used a rule that Helen had proposed: at mid-game, players may give back any number of the bonds they've taken out at a penalty of 2 VPs per bond. This rule is intended to walk a careful tightrope. I want players to be able to take out lots of shares without worrying about surviving the income troughs later on. On the other hand, it should cost something to get rid of a bond at mid-game; otherwise, it is too easy to take out bonds just before mid-game, knowing that you will soon be rid of them. In addition, it gives players another interesting decision to make: keep the bonds and avoid the extra VP penalty, or dump them and avoid the income penalty?

I have one reservation about giving back the bonds: in this session nearly everyone gave back all their bonds, and the one player who didn't regretted it. It may be that 2 VP is too cheap, and at that price you should nearly always give back all your bonds. But I'm going to let a few more games go by before I try increasing the penalty. That will tell me whether the cost is really too low, or whether it was just the way this one game played out.

My other concern is the Rail Baron cards. I put together a set specific to the Continental game, having found in previous playtests that the ones from the Eastern and Western games don't work as well on the combined boards. For the most part the new barons were good, but there were a couple of false notes. One is that the VP bonuses in the base game and its other expansions are about 10% of a typical final score. But final scores in the Continental game are much higher; if the Rail Baron bonuses aren't increased to match, players will not have much incentive to try to achieve their Baron goals. I think therefore that the Continental Baron bonuses need to be significantly larger than those for the base game. The other issue is ensuring that those bonuses are balanced. There were indications that some of the goals are much harder to achieve than others. A little of that is okay, but the differences shouldn't be huge.

All along I've been worried that the Continental game would take too long, and outlast its welcome. But the players stayed after the game for well over an hour, vigorously discussing their strategies and the reasons for their decisions. Nobody got bored, and they all want to play it again. Whew! Obviously, not everyone will want to play a six-hour game no matter how good it is, but I think we've got something that at least a real RotW enthusiast will enjoy.

More playtests will follow, as soon as I can get them together!

Coast-to-coast again

This weekend we tried another coast-to-coast session of Rottweiler. This was only the second such session. Because of the holidays and nearly two months (and counting) of major home renovation, I haven't had the time or the table space to lay out so large and long a game.

But on Saturday we managed it. And it was a pretty good session, in two senses. First, lessons learned from the first session led to noticeable improvements. And second, we learned a lot about what still needs work.

The first session had two major problems. One was that it didn't last long enough; the far coast was barely reached and wasn't developed, which didn't feel right. We solved that this time with a tweak to the end-game trigger rule. The other was the issue of the "income trough", as follows.

We have been using the score/income track from the base game. In Railways of the World, your income is tied to your current score. It rises for most of the game, then begins to fall again at a point somewhere after midgame. Typically it never rises again, but if you score above 100 points you wrap the scoreboard and you begin to repeat the cycle.

For the base game, this works just fine. The income curve is calibrated to keep money tight throughout the game, so that players must always think about their budgets. For much of the game you need money for expansion and development, but in the end game you are usually busy milking what you have already built rather than spending on new track, so you don't need as much money.

For the coast-to-coast game, this falls apart. The high score in this weekend's session was a whopping 240 points: that player wrapped the scoreboard twice. This means that his income started at zero, rose to a high point, then fell to zero again, and then did it all over a second time, finishing with a rise to a third high point. The trouble with this is simple: the coast-to-coast game requires players to continue to expand for at least twice as many rounds as the base game. Unless you have managed to become rich, you're going to be starving for money when you are in the "income trough". You can even get into a horrible debt spiral if you have issued very many bonds, because you must pay dividends on them and this can exceed your income by quite a bit.

In the first session, I saw this as a problem that might be acceptable as part of the strategy of the coast-to-coast game: you need to build up a fund of cash during times of high income, so that it will see you through the low-income periods. But in both sessions, at least one player failed in this; and the consequences are severe. Such a player falls badly behind and cannot catch up, and has to play for another three hours not only unable to win, but even unable to make any progress. The fact that the second session lasted through two income troughs makes it even worse.

So I'm going to have to think about the income curve for the coast-to-coast game. A number of solutions have been proposed, but I haven't had time to think them all through yet. The ideal solution will be one in which most players must budget carefully throughout the game, but without quite such severe penalties for failure; and it will allow players to issue plenty of bonds if they need to. (If you think I'm being too soft-hearted toward my players, think again. It's one thing to lose; it's quite another to be so wedged that you can hardly even play, especially in so long a game.)

When I've got a good-sounding solution for the income problem, I may be ready to try a "live" game with a full table of real players. So far it's just been Helen and me, each pretending to be two different people in order to make up four simulated players. Helen is tolerant, but I don't want to burden my other playtesters with a six-hour unplayable horror of a game, so I want to get this smoothed out at home before taking it out in public.

Rottweiler: Coast-to-Coast

I see I've been lax about blogging lately. That's mostly because I haven't been doing much that I felt would be of interest: some gaming, some music, a nice Thanksgiving with the family. Recently we've begun remodeling the house, and that may prompt some commentary at some point.

But last weekend, Helen and I pushed the Rottweiler map edge-to-edge with its matching previously-published map, and we played our first "continental" game. I'd cobbled together a rule set for what would clearly be a long game, and knew that it would need playtesting to get right. The results were mixed: some good news, some bad.

The good news is that it was an interesting game. It definitely felt different from any other RotW game we've played (and we've played them all), and the new strategies it evoked were challenging and fun. I also felt that it wouldn't need much tuning to really get it right—although that may be unjustified optimism. But there were a few issues that will have to be addressed.

One issue is the income/score track. RotW and Railroad Tycoon veterans know that your income goes up as your score goes up, until a bit after mid-game when your income begins to decline as your score continues to rise. Thematically this represents the overhead of running a large railroad; from a game design standpoint it's to keep cash scarce and make players budget. If you perform well, you can wrap the scoring track and your income begins to rise again. Normally this happens late or not at all, but in the continental game it will happen at about mid-game. It's a bad time to be short of cash.

In our one playtest (Helen and I managing two players each) one player hit the trough just wrong, with no saved cash and no cheap prospects for getting out of the trough; that player finished last. Another player had to build track aggressively, to delay entering the trough until he could rush past it in a sudden flurry of deliveries; that player finished second-to-last. The other two players were either already past the trough or had enough cash on hand that it wasn't an issue; they finished first and second.

The continental game is long, and I don't want miring players in the income trough to be a frequent occurrence. They'd have to spend a couple more hours finishing the game with no prospect of winning. But it may be that it's never necessary for an experienced player to be stuck, if you know to plan ahead. One simple solution is an optional rule for beginners: once your income first climbs above $10 or $15, it never falls below that level. Experienced players can use the unmodified income/score track for a more challenging game.

The biggest actual problem we encountered was a shortage of pieces. There are simply not enough goods cubes, track tiles, or even control locos in a single base set. I'll be talking with the publisher about how to handle this. The decision will be up to them, but the obvious possibilities include putting the extra bits in the expansion, making a "Continental Pack" available separately, or simply requiring the bits from two base games.

Progress! I hope to try the continental game again soon with real players, but Christmas may intervene. When it happens, I'll post again.

Pacificon 2009: Rottweiler

This Labor Day weekend Helen and I trekked off to Pacificon for three days of intensive gaming. Happily, Pacificon really isn't much of a trek for us: it's about 10 minutes from home, so we could spend all day and half the night at the con and still sleep in our own beds. But because we did game late every night, we we're pretty bushed by the end. (That, and an unexpectedly busy week, makes this a late posting.)

A primary goal for me was to get in a few live playtests of Rottweiler. I'd hoped for three, but got two, which wasn't bad at all. (Lesson learned for future: schedule stuff like this in advance. Trying to get pickup sessions together is unreliable and time-wasteful.) Both sessions went very well, all things considered. I had some experienced players and some newbies; some but not all of the experienced players had seen a prior version of the Rottweiler map. Overall, both sessions "worked": nothing was clearly broken. The balance of the various starting positions wasn't perfect, but of course I don't expect or need it to be; I just need it to not be too horribly unbalanced. Game lengths were a bit shorter than I expected, lasting about two hours or a little less each. I am considering adding a few more empty city markers to extend the game another round or two.

There were some parts that didn't work as well as I'd like. One new feature continues to be troublesome. I've tried a number of variations for it. One such sounds good on paper, but is rarely used in practice—and given that, why bother having the feature at all? Another does get used simply because its rules pretty much require it; but it does not foster competition or interaction among the players, so again it feels pretty pointless to me. I would happily abandon the whole notion, but it's something the publishers are interested in, so I feel that I must make a strong effort to make it work. Then if I fail, I can at least list all the reasons why the feature should be dropped.

A few other items need tweaking or abandonment. There are some Rail Baron and Railroad Operations cards that I added for historical theme; there I may be trying too hard. Some are specific to certain historical locations and events, and wind up feeling like unjustified gifts to those players who build in the area. That's okay as a general rule—Service Bounties are like that—but I have to be careful not to make them too powerful (which is unfair) or too weak (which is pointless). It's surprisingly difficult to balance these things: the granularity of VPs and achievements seems too coarse at times. If I lower the difficulty, the reward is suddenly too great. If I raise the reward, it's too much advantage for the player who achieves the goal. Argh! But I have some other knobs I can tweak, so I think I may yet be able to salvage these items. The map itself seems to be much improved. I didn't find anything in these sessions to suggest any urgent changes, although I did find a couple of "typos" to fix up.

I think the next step is to run a few more solo playtests, to try some tweaks to the troublesome issues. If I can make significant improvements, I'll look for more opportunities for live playtests. The publisher has some groups they want to sic onto Rottweiler, and they seemed to want to start this process in September, so I'll try to get something together for them soon.

Rottweiler: Learning to Heel

Last night was the first live playtest of Rottweiler, following four solo playtests over the last couple of weeks. I learn more with every play.

Although I've been playing RotW games (under their original "Railroad Tycoon" name) for several years now, this is the first time I've done so while taking a global view. Instead of concentrating on my own plans and paying attention to others only to the degree that they might interfere with me, I am now watching what every player does, and why. It's been very instructive.

I've learned what should have been obvious from the beginning: that the various bonus-scoring opportunities—Major Lines, Service Bounties, and Baron cards—have a large effect in shaping the game. (Major Lines are bonuses for laying track between specified pairs of cities; other bonuses may have similar effects.) For my first cut, I set up the bonuses to motivate players to re-create the historical rail routes. Two plays showed me why that was wrong: it allowed as many as five players to each carve out a separate empire, with little need to get in each other's way. This makes for a boring game.

So I've had to throw out some of the history. I re-worked the Major Lines, removing a couple that routed around the edges of the board, and adding some to draw players together at a couple of central nexuses. The improvement in the game was immediate and marked: suddenly there was contention in these targeted areas, and players had to start worrying about their opponents' plans and activities much earlier in the game.

Last night's playtest went very well. Everyone seemed to enjoy the game, and there was nothing that was clearly broken. But there is certainly room for improvement, and I happily received some good analysis and a number of excellent suggestions. My next steps are to extend some mountains here, reduce some cube counts there, and tweak the Major Lines some more. Then print the new map and run some more solo tests before taking taking it to Pacificon over Labor Day weekend for more live playtests.

The news is not all wonderful. Part of the motivation for Rottweiler is to add a couple of the innovative features from my Hammer and Spike game to this RotW expansion. One of those features is working well, but the other one is not throwing the same kind of sparks. I need to find some way to improve it. I'd like to have a better revision in time for Pacificon, if I can swing it.

Code Name Rottweiler!

It's not much of a code name if everybody knows what it means, but I've taken to thinking of my expansion for RotW (the abbreviation of "Railways of the World") as "rottweiler". This comes purely from the letters; for the record, I see no particular parallels between the dog breed (or any dog breed!) and the game system. And I wouldn't have bothered mentioning it here, but I couldn't resist the hyper-dramatic "Code Name Rottweiler!" title for the post. Sounds like a bad spy movie!

I should make up for the preceding blather with some meaningful news, so here's the current status of... Code Name Rottweiler! (Okay, I'll stop now, I promise.)

I have a first cut at the map nearly complete. I just need to add starting cube counts to the towns and cities, and make sure it will print okay in black and white. (Why? See below.)

I have a first cut at the Railroad Ops cards designed. I still need to make the deck, either by laying out some mocked-up cards on the computer and printing them out, or by just scribbling on paper. Either way, I'll stick the EUS deck into card sleeves, then slip in the paper cards over the real ones. I've also finished the first cut at the Rail Baron cards. I have a good selection of Barons and (I hope) a good set of bonuses.

I'll need to tune a VP/income track for the game, but I can start with the one from the main game. I can use the modular scoring track boards that Helen made for our copy of the original Railroad Tycoon until I decide what tweaks I want to make. (If you play RRT on the big board and hate that scoring track, you can download Helen's modular scoring track from BoardGameGeek. Be sure to give her a thumb if you like it!)

Acting on a tip from an experienced developer, I discovered that I can print out a full-size board on a single sheet of paper at Kinko's, for just $0.75 per square foot! That comes to all of $6 for one copy, which is dirt cheap. I'd always looked at the color prices which are significantly higher, and I had never realized that black and white is so inexpensive. A RotW board doesn't need much color; what little it needs can be added in five minutes with a set of felt pens.

The bottom line: I plan to print my first board tomorrow and be doing my first solo playtests this weekend! That's an exciting thought.

Getting Rolling

It's been three weeks since my last post. The major reason for this is that I've been asked not to be too forthcoming with details about the Railways of the World expansion I'm working on. This has put a crimp in my blogging style.

But I suppose I can get away with some generalities. For one thing, I was mistaken in thinking that the expansion would be mostly designed by others; turns out it's mainly in my lap. The board, the cards, the variant rules, all of it. I'll have help and advice from the publisher's developers, of course.

This is not how I foresaw my first publication contract! I thought I'd design a game, get it mostly finished, then get it licensed. After that, just playtest and tweak until the publisher is happy; the rest would be the publisher's problem. I didn't expect to have much left to do at this point. Instead I have to start almost from scratch!

Okay, it's not really "from scratch." The RotW system is well-defined and so are the Hammer and Spike features that I will be adding in; I'm not inventing a whole new game. But I still have to draw the map, define the cards, tune a scoring track (the scoring track in RRT/RotW is also the income track, so it affects the whole game economy), and fine-tune the H&S features (which, after all, were not originally designed for RotW). That's a lot to do. Fortunately I think it will be tremendous fun, and I've definitely been enjoying the process so far.

I've been told what part of the world the map must cover. Given that, I've been studying the history of the region, to see how the railroads grew there and what special conditions obtained. RotW is not a simulation game, so most of the historical detail is pretty useless; but I've gotten some ideas for the cards, and some notions on how to lay out the map (for example, the towns that were important to the railroads back then aren't always the ones that are largest or most important now). In fact I have more ideas than I'm going to be able to use. That's a good thing: it's better to have too much than to not have enough!

I've also been asked to try to make the H&S features into an optional variant that can be used with any RotW map, if you've got the rules and bits from my expansion. I've been testing that out on the Europe map, and I'm pleased to say that I think they will work.

Working on the board is going to be interesting. I've never made a prototype board this big before, and my usual cheap-and-dirty technique of printing it out on 8.5x11" sheets and taping them together may be too big a pain. I think this time I'm going to spend some money and have a print shop do it as a single big sheet, and then maybe have them laminate it so I can draw and erase on it easily. (No, it will not be as big as the original gargantuan RRT board. But it's not small either.)

Finally, and just to head off the questions: no, I don't know when it will be released. I just started working on it a couple of weeks ago! All I can tell you is that it will be a good long while, so there's no point in being impatient.

But yes, when I have it sufficiently developed, some of you will be able to playtest it. In fact, I'm counting on it!

Publishing Update

Spatial Delivery

The publisher who has been reviewing Spatial Delivery has (after a year!) finally tested it, and tells me that they are currently looking for lighter games. They haven't quite said "get lost" and the prototype will be tested further at their main office, but the news is not encouraging.

I have contacts at a couple of other publishers who may be interested in Spatial Delivery. My home and life are going to be in some disarray over the next few weeks (we are remodeling) but after that, and if the current publisher hasn't changed their mind, I will build yet another prototype and see if I can get someone else to look at it.

Hammer and Spike

This one got licensed! It's not quite what I had envisioned, because it will not be published as a stand-alone game the way I designed it. Instead, some of its unique features will be folded into a game already being designed by some of the publisher's other developers. But I am not too disappointed: the license is the same as it would have been for a stand-alone game; my name (among others) will be on the box; and the combined product sounds very exciting. I am sure I will someday see a game of my own published, and this is a good first step in that direction.

By the publisher's request, I am giving no details about the combined product for now. I'll post more information when I can.

Update to the update: I can now speak a bit more freely. Hammer and Spike will become a new expansion for the Railways of the World (RotW) game system. RotW is the new (and re-named) edition of Railroad Tycoon being published by FRED Distribution. I've been asked to design an expansion that will merge the unique features from Hammer and Spike with the familiar RotW system. If you've been following this blog, you know that Railroad Tycoon is my favorite game, so you can imagine how excited I am to be given this project!

JavaFX: Looking even better

I was surprised to get a quick response to my forum post, on a Sunday afternoon yet. The response contained a solution for my unresponsive-objects problem (see below), and almost completely fixed it. I've seen the symptom recur now just once or twice in a 90-minute session, and it never persisted for more than a minute. I suspect that these remaining minor glitches have a different cause, and quite possibly are just due to my system being busy doing something else for a moment.

My virtual gameboard is now actually usable, and I played a complete game of Hammer and Spike with it in just 90 minutes. I am very pleased.

I still have more work to do: adding features, cleaning up minor bugs, and finishing the documentation. But one of these days, hopefully soon, I will make it available for others to use.

JavaFX: Looking better, but...

I took vacation last week, and spent some of it working on my JavaFX virtual gameboard app (still inadequately named "Placer"). I've resolved some of the problems that were worrying me at the time of my last post: the exceptions are gone, the design and code are cleaner, the feature set and UI of the app itself have improved. I've figured out how it can be deployed, too, although unhappily it must use Java Web Start and requires the user to have a fast Internet connection (at every launch! Why won't Sun give us a better option?).

But my biggest problem remains unsolved. Sometimes, some of the objects in the window (cubes, banks, other clickable or draggable things) simply stop responding to mouse clicks for a while. This is mystifying because of the apparent inconsistency of the behavior. For example other objects in the same window remain perfectly responsive and well-behaved while the frozen ones continue to ignore the mouse. And a frozen object will often spontaneously unfreeze later on; but the period during which it remains frozen can be anywhere from a few seconds to many minutes. I have circumstantial evidence suggesting that a frozen object is more likely to unfreeze soon if I drag some other (and obviously more responsive) object over the frozen one; but this certainly does not always work, so it may be coincidence.

Until this issue is cleared up, the app is not viable. When objects freeze up like that, the app becomes effectively unusable. (It's okay if objects freeze up when you don't want to manipulate them. But you only notice that they're frozen when you do want to manipulate them, which means that your game is stopped until you can unfreeze the things you need to move.)

I've joined Sun's developer network, and posted in their JavaFX forum about my problem. And now I have yet another thing to wait for. I'm spending a lot of time sitting by my virtual phone these days, waiting to hear from game publishers, CD makers, and now helpful JavaFX gurus. It's getting old.

JavaFX FTW?

JavaFX is yet-another-scripting-language. It promises that you can quickly create Java applets and applications with fancy visual effects by writing simple little scripts instead of miserably complex Java code. Does it deliver?

I was sic'ed onto JavaFX at my day job, charged with whipping up some cool new UI mockups. I quickly became fascinated. You can accomplish a lot with a little, using JavaFX. But that's not enough; I need to find out whether it can create industrial-strength applications, and if so, whether the code is readable and maintainable, and whether the UI it produces runs quickly and is responsive to the user.

I won't go into my day-job's proprietary stuff here. But (just in order to learn, you understand) one of the first things I did was start building a virtual gameboard. It went so well and so quickly that I've kept working on the project at home on my own time.

What is a virtual gameboard? I wanted a tool to quickly prototype a new game idea on the computer, without having to spend time and money assembling physical pieces. I wanted to be able to play the game (by myself, as I always do with new game ideas), change the rules and pieces, then play again, with rapid turn-around time on the changes. I also wanted play to go at least as quick as it would with real materials. I called the tool "Placer" because it will let me place things on a virtual gameboard. (A lame name, but it doesn't need a better one at the moment.)

Placer lets you specify an image file for the gameboard, which it displays in a window. A tool-palette area is automatically provided to the left of the board. In the palette are templates: If you see a red cube in the palette, for example, you can click-and-drag on it. It will produce a copy of itself (another red cube) that gets dragged away under your mouse. You drop the copy (called a "token") anywhere you like on the board. The template stays put, in the palette, and can be used again and again to make more tokens. A template is therefore a sort of virtual, limitless pile of its particular kind of token.

Placer is configured from a text file, in which you can specify a wide variety of templates for the palette: squares and rectangles, circles and ovals, cubes, disks, and more. Each one can be given a color, so you can have (say) four templates for the cube supply of four different players: one template each in red, yellow, green, and blue.

Tokens on the board can be moved around as much as you like. They can also be rotated, and each has a little popup menu that lets you delete the token or get a little information about it.

There are a couple of fancier kinds of tokens. One is the Bank, which displays an amount of money. Click on it to make a withdrawal: a small text box appears, you type in the amount to withdraw, and the Bank creates a new Cash token under your mouse. The Cash token displays the amount of money that you withdrew, and you can drag the Cash off to wherever you want it to go. The Bank stays behind, now displaying the balance that remains after your withdrawal. If a game uses money, you can create a master bank for the game, and then give each player a bank of their own. When you drop a Cash token onto a Bank, the Cash disappears and its value is added to the Bank's balance, making it easy to transfer money among the players. (The image shows a $13 bill ready to be dropped onto the Red player's bank, which currently contains $42.)

So has it been all kittens and rainbows? Nope, it hasn't. As is always the case with Java or anything Java-related, layout (that is, getting everything to be in the right place) is a major pain. JavaFX features coordinate-system manipulations that you must use to get anything significant done; no doubt they are very powerful and carefully thought out, but it gets very difficult to keep it all straight in your head (and your code) when you're writing something complex. Event handling is a bit tricky, and seems not always to work as advertised: sometimes my tokens simply ignore clicks and drags, with no clue as to why. (I suspect the garbage collector, at the moment.) And then sometimes JavaFX just throws a huge exception, stopping my app cold. It seems to be because I've coded something wrong, but I don't (yet) understand why I can play half a game of Hammer and Spike before it suddenly decides it doesn't like me.

Another issue is deployment. Suppose I finish up Placer, and want you to use it: how do I give it to you, and how do you install it? JavaFX isn't really designed for building stand-alone apps. You're supposed to access JavaFX programs via the Internet: as browser applets, or mobile device apps. It does provide a way to use WebStart files to deliver a desktop app, but these may have Java sandbox problems, which would be a killer for Placer: it has to be able to read your config file and board art.

But we'll see. I'm not done playing with it yet!

My Designs at KublaCon 2009

Hammer and Spike suffered a setback recently, when we found a strategy that was successful, simple, and dead boring to play. To fix it I've adjusted the scoring. The bad news is that the scoring is now even more complex, but the good news is that the fix seems to be working. I hosted a four-player game at KublaCon that included a couple of new players and a couple of experienced train gamers, and I liked the way it played out. The winner was JC Lawrence, who also pointed out a problem I hadn't seen before (but which will be easily fixed, I think) and who gave some good feedback and advice.

And there is finally some news about the fate of Spatial Delivery. In our last episode (and the one before that, and the one before that...), the prototype had been sent off to a publisher shortly after winning the KublaCon game design contest in 2008. There followed nearly a full year of dead silence. I restrained myself from attempting to contact the publisher, reasoning that publishers were busy, they'd get to it when they had a chance, and there was no point in making a pest of myself. But this weekend I spoke to a company rep and learned that they'd recently had to fire a clerical worker for incompetence. This worker had made any number of bad-for-business mistakes, and one of them was losing my prototype (along with my contact info, of course). Fortunately the rep I spoke to was the very person who should have received the prototype in the first place. I had just built a new copy and had it with me hoping to play it, but instead I gave it to the rep. He told me it would be played next weekend and that I would hear something back within just a few weeks. So Spatial Delivery is back on track!

Now I just have to hope that the publisher actually likes it. But if they don't, I have a backup opportunity. The KublaCon contest director tells me that she has been talking the game up to a second publisher. I'm going to stick with the first until they make up their minds (at least, if it doesn't take another year for them to do so), but I would be perfectly happy to go with the second publisher if things fall out that way.

The lesson learned is obvious: keep in touch. I still think it's a bad idea to be a pest, but from now on any such publisher who hasn't contacted me within the last three months will hear from me. I don't intend to lose an entire year again.

And now I have two designs being actively evaluated by two publishers, and backup publishers for both. Cross your fingers for me! I'm hoping to have at least one game on its way to market, maybe two, by next year's KublaCon.

Fires and Recordings and In-laws

I've felt all this past week as if I should be blogging, but I've been too busy and too distracted. The Jesusita Fire in Santa Barbara has occupied much of my attention. The fire not only devastated the foothills, but threatened the town itself. The neighborhood where I grew up was within a mile or or of the fire's perimeter and was under mandatory evacuation for a while; some friends of mine were also prepared to evacuate. I am saddened by the damage to the Botanical Garden, which was one of my favorite places; but it wasn't completely destroyed and I hope the damaged areas will be rebuilt and replanted. The fire is still in progress and is less than 50% contained, but the threat now seems to have lessened and the fire has moved north and west rather than south towards the town and suburbs, so things are looking up.

The in-laws paid us a visit on Friday and Saturday. I'm always happy to see them, and this brief visit was in part to deliver a car we bought from them for our son to use at college next year. We had a couple of nice dinners, some good conversation, and some excellent games with Joan. Although I was feeling a bit overwhelmed and wished the visit could have come either last weekend or next, it all worked out. I even found time to practice.

Why practice? Because on Monday and Tuesday, I'll be recording with Ted Shafer's Jelly Roll Jazz Band. For most of the group, this is a "ho-hum, another recording" event, but for me it's a very big deal. I have recorded before, but never in such professional surroundings; and I have only rarely been privileged to play with such a fine group of musicians. I definitely feel like the junior member of the group (my actual age notwithstanding) and am mostly hoping not to embarrass myself. Fortunately for all concerned I'll be playing second cornet, and for good or ill my efforts won't be too prominent. This, along with the fire, has been the main thing on my mind all week. I've been working hard on it, both at rehearsals and at home.

On the game design front there is little news. I now have two designs in the hands of publishers, and I'm back in the "hurry up and wait" mode. I have nearly completed the Spatial Delivery prototype (still have to paint the spaceships) that I'm building just to have handy, and I finally got off the dime and sent Seth his promised copy of Hammer and Spike. I'm looking forward to his group's feedback on that one.

And that's all for now. I gotta go practice!

Progress Report: Not Much

It's been a while since my last post, so I thought I'd issue a brief update, to wit: not much news here. After the excitement of GameStorm and the rush to get a copy of Hammer and Spike off to certain interested parties, little has happened. I've made two new copies (one for me, one for Seth), but haven't had much time to actually play or work with the game.

I've also been building a new copy of Spatial Delivery. I haven't had one since I sent my last copy to a publisher, last June. Having heard nothing since then, I figure it's time to give it some attention. I have no immediate plans for it except to start playing it again, but I should at least have a copy of my own, yes?

Hammer and Spike did get another playtest today, at the Los Altos Games Day. The day was great fun, as always. Helen and I particularly enjoyed a session of Age of Empires III, an excellent game that we've neglected for too long. I finished the day with the four-player H&S session, which seemed to go well on the whole. It did run kind of long, but perhaps that can be chalked up to having three newbies in the game. They all picked it up pretty well, and by the end were building fuel depots and switchyards and making the long deliveries like veterans. Two of them said they would happily play it again sometime, which is always nice to hear (although you have to make allowances; sometimes people are just being polite to the game designer who, after all, is standing right there). A couple of folks who stopped by to watch also expressed interest in playing the game, so I can hope to have more guinea pigs playtesters soon.

It was a good day!

Terra Prime at GameStorm

Seth Jaffee brought a prototype of his game Terra Prime to GameStorm. Seth's been a real supporter and contributor to my own designs, and it's high time I said a word about one of his.

Terra Prime is a fun blend of the European and American styles of game design. (Those distinctions are really starting to blur these days.) In the game, Terra Prime is a station on the edge of explored space. Players are explorers who load their ships at Terra Prime with weapons, shields, and colonists, then head out into the unknown to establish colonies, placate or defeat hostile aliens, and bring goods back from the colonies to Terra Prime.

On the European side, Terra Prime has a nicely-done economic engine, where goods brought back can be exchanged for money, ship improvements, and Victory Points (VPs). Decisions about how best to spend your goods are a key part of the game.

On the American side, the game's mechanics are faithful to the theme, and include some fun dice-rolling and direct conflict (although the battles are against aliens provided by the game, rather than against your opponents).

There is no board per se; instead individual hex tiles are laid out in a spreading fan from the large Terra Prime tile. The hexes are face-down so that players initially can't see the hazards and opportunities on the tile faces; but the backs are color-coded so that the more dangerous (and lucrative) tiles are the farthest away. To see a tile's face, you must either visit its vicinity with your ship, or view it from a distance (costing an action but granting you an exclusive, secret peek).

The tiles plus the economic engine give the game a solid development arc. Players start with basic capabilities, and at first only need to cope with the easier neighborhood near Terra Prime. While the near neighborhood is explored and its potential realized, players improve their ships and become ready to head out to the dangerous, distant edge of space, where the real profits are.

I first played this game two years ago, at KublaCon 2007. Seth has been working on it steadily since then, and the game has acquired a lot of polish. It plays quickly, offering good depth in just 90 minutes or so. Players are given plenty to think about, and their decisions are important (as shown by the masterful way Seth trashed his opponents, including me, at GameStorm!), but the dice allow for push-your-luck opportunities for adventurous (or desperate) players.

Seth posted recently that Terra Prime will be published, and I'm delighted to hear it. I've been wanting a copy for two years, and now I can look forward to actually getting one!

GameStorm Fallout

GameStorm was a lot of fun, but I haven't had a chance to relax or breathe until now. Although I brought along Hammer and Spike mainly to show it to Seth, it wound up attracting a good deal more attention than I expected, and some of it was industry attention. The upshot was that after driving 13 hours to get home yesterday, we spent most of today frantically assembling another copy to send to someone who had requested it, and who needed it this weekend. We just got that done and shipped about an hour ago. Another person has also requested a copy, but less urgently, so we'll be making and shipping another in the near future.

This is all very gratifying, and quite astonishing to me. I simply did not expect it, and wasn't prepared for it. It was Helen who saved the day. She invented an amazing new way to make certain prototype bits, and got up this morning and drove around town collecting supplies and packing materials; then returned home and sewed up a couple of drawstring bags (emerging victorious over a cranky sewing machine), reviewed and corrected the rulebook, and finally drove us to the shipping office, just in time. We literally watched them slapping the last stickers on while the UPS guy held the box for them. I could not possibly have done all this without her, and would not have dared to try.

So now it's hurry up and wait again, I guess, just like it's been with Spatial Delivery for the last eight or nine months. If anything comes of it, I'll let y'all know. In the meantime I have to make two more prototypes (one's for me, as I cannibalized some of my original) and get in a lot more playtesting... oh yeah, and I have to run off to a rehearsal tonight.

Adventures in Prototyping

My game design blogging has a split personality; much of it goes here, but some also goes up at the Board Game Designers Forum. This weekend I made a more durable board for the Nameless Rail Game, and chronicled the effort in some detail in my journal there. I felt that the content was of more interest to hard-core designers than to the more general crowd that reads this site, but if you're interested, follow the link.

I made the board because a flat, stiff, foldable board is a lot easier to transport than the taped-together big sheets of paper I've been making for home use. Helen and I are about to head up to Oregon to visit family and attend GameStorm, where I hope to get more playtesting done.

And the beast may finally have a name. The new board is labeled Hammer and Spike, which may not be great but is not in use by any other games. It will serve until and unless I hear a distinctly better suggestion. My thanks to all those who suggested alternate names, but I have to live with Helen and she didn't like some of them, so Hammer and Spike it is.

Picking Up Steam

Two more live playtests, at the Los Altos Games Day! The game was well received, and I was quite pleased with the results.

The changes I made after last week's session worked well. Playtime came in at about two hours, and I suspect would be a bit shorter with experienced players. Players successfully built transcontinental networks and made coast-to-coast deliveries by the end of the game. A few switchyards were built in each game, but never all six. That all seemed just right.

On the down side, my long-standing worries that the scoring system is badly balanced were borne out. The reward for connecting all six cities is so high that a player who fails to do so is almost guaranteed to lose. This would be okay except that it's usually clear which players will fail by around halfway through the game. It's no fun being the goat in a game in which there is almost always one designated goat.

The way to fix that is probably to raise the VP reward for building switchyards. The trailing player has an advantage here, in a way: if he is flexible enough to give up on the six-city goal early enough, he will save several actions and a fair amount of cash. He can then devote those resources to switchyard building, and remain competitive with the six-city players.

I have also recently revised the simulator to play by the new rules, and run another couple hundred thousand simulations or so. These were, as before, mostly explorations of balance. It has become quite clear that an intelligent first player has a huge advantage over his opponents, because the choice of starting locations is not even remotely balanced. This isn't unusual for rail games. The simulations show that it can be balanced by giving the players differing amounts of starting cash. In the game rules, I expect I will express this in two ways: a "standard game" in which the starting cash is simply dictated by the rules, and an "advanced game" in which the players hold an initial auction for turn order. Players will use the standard rules until they feel qualified to judge fine differences in starting positions, and can then advance to the auction rules. (Unlike Age of Steam and Railroad Tycoon, I don't think this game needs a turn-order auction every round. One at the start of the game should be sufficient, and the turn order need not change after that.)

Finally, I came away with a clear understanding about the current inadequacies of the board graphics and the player aids. This is not part of game design (since I have no plans to self-publish), but a well-made prototype really helps newbies concentrate on the game instead of on decoding the board and remembering the rules. I have some ideas for improvements, and I will be playing around in Photoshop to try to turn those ideas into clear graphics.

I Got Game

Saturday the long-awaited live playtest of the nameless rail game finally happened, and I'm pleased to report that it went very well. My playtesters were Candy Weber, John Portley, Helen, and myself. (John and Candy brought designs of their own that we also tried, and those went well too. But I don't know if they want Internet coverage, so I'm just going to talk about mine for now.)

There was good news, and bad news. The good news was that all players agreed that the game presented interesting and difficult decisions; it wasn't just a matter of turning the crank. (I was worried about that.) The bad news was that it took over three and a half hours to play!

Everyone was very nice about the length of it, and pointed out that it was a learning game for everyone except me, and that we also stopped periodically to discuss the design. True, but I think those excuses only go so far. I don't want the game to last more than two hours. In my playtesting it usually takes only two hours. But you have to allow time for people to chat, and I also don't want a newbie's first experience to be a marathon. So I'm going to give some attention to speeding up play. This probably means reducing the number of rounds and tweaking things to allow players to get stuff done in fewer turns. I received some very good suggestions about how to accomplish that, and I intend to try them out. The best idea I heard was to change a couple of actions into non-actions, so that you can get a bit more done in your turn. I think that will not only speed things up, but also remove some of the major sources of player frustration that I observed.

Between those suggestions and a few tweaks of my own that I've been thinking about for a while, I have a laundry list of things to experiment with. But none of these items are major changes; they all amount to streamlining of one kind or another. I'll try them out in solo play over the next week or two, to see which ones help and which don't. In two weeks there's a Games Day, and I'll probably bring the latest version to that and see if I can get another live test. After that I can bring it to GameStorm in Portland at the end of March, and eventually KublaCon at the end of May. I can hope that by then it will be pretty stable.