Ripped from the pages of my Ptolus campaign, this beasty was created by chaos cultists using an artifact known as the Idol of Ravvan. He was an early test of the monster creation system from Legends & Labyrinths and was specifically designed to take advantage of the Gemini figure from McFarlane’s Warriors of the Zodiac toy line (pictured below).

GEMINI BEAST (CR 8+2*): 256 hp (HD 11d8+40), AC 20, claws +14/+14 (2d8+2d6+4), Save +11, Ability DC 18, Size Gargantuan, Speed 60 ft., Reach 20 ft.

Str 30, Dex 11, Con 18, Int 6, Wis 5, Cha 10
Skills: Climb +24, Intimidate +14, Listen +11, Spot +11
Blindsense 60 ft.

SPECIAL: The Gemini Beast is actually two creatures joined together (each possessing the stat block above). Like a mounted combatant, they take their actions simultaneously. If either moves (as a move action, full action, or 5-ft. step) they are both considered to have taken that action.

If one of the Gemini Beasts is slain, that half of the creature simply becomes inert and dead. The other half can continue taking actions normally, although it suffers a -30 ft. penalty to its speed (due to hauling the dead carcass of its twin behind it).

* Potentate.

Tagline: The first game designed by Richard Garfield and released to the public, RoboRally shows the intriguing conceptual ideas and addictive game play which have since become Garfield’s stock in trade. Like so many games released by Wizards of the Coast I first picked this product up because the description just sounded too intriguing to miss. Like every product I have ever picked up from the Wizards, I was anything but disappointed.

“Like every product I have ever picked up from the Wizards, I was anything but disappointed.” Ah, 1998. How I miss ye. RoboRally remains one of my favorite games. Unfortunately, my original copy was lost in a move and later turned up in the bottom of a box that was being stored in a pole barn. Although sadly water-damaged, it is still tremendous fun. Anyone know what Richard Garfield is up to these days?

GAME CONCEPT

In the future the widget factories of the world are controlled by the mightiest artificial intelligences ever created by man. Capable of solving any problem which might arise and controlling the entire factory from top to bottom to compensate for any problems and keep production right on schedule, these mighty machines suffered from only a single problem: Boredom.

Then one day a processing robot fried a circuit and went careening onto a conveyor belt, which sent him spinning through the high-powered laser systems and dropped him off just in time for his broken and decaying programming databanks to send him plummeting down a bottomless disposal bit on the factory floor.

The computers were … amused.

Immediately they created the game of RoboRally – each computer controlled a single robot and, using a limited set of data registers, was required to send the robots through a specially converted section of the factory floor.

In the boardgame RoboRally you are the computer, programming your robot to cross the factory floor and reach a set of checkpoints in a specific sequence in order to win the game. In your way are conveyor belts, bottomless pits, gears, crushers, pushers, and laser beams… not to mention the robots of your fellow players.

RULES

The game comes with six gameboards which can be played individually or arranged in any combination you want. The checkpoints you must reach are represented by six counters numbered from 1 to 6 – you can place these counters anywhere on the gameboards you want and in any order you choose. The options are practically infinite.

On each turn you are dealt nine program cards. From these you must select five cards and “program” your robot by assigning one card to each of five programming registers. When all the players have completed programming their robots the turn begins – each register is considered in order and your robot moves.

This sounds simple, but in truth you’ll find yourself making bonehead mistakes – especially when you come in contact with the board elements. “Okay, first I’ll move forward, which will put me on the conveyor belt which will move me there, then I’ll turn left, and the conveyor belt will move me again, turning me as I go, so that when I move backwards on the next phase I’ll end up…” And, of course, you can always be pushed around by the other robots on the board so that your preciously planned sequence of movements will suddenly all be off by one square … and the results cascade through the rest of the turn.

Plus, your robot can take damage and be destroyed by various game elements on the board. Plus, your robot and the robots of the other players are all outfitted with lasers – allowing you to whittle away. What can be worse than getting blasted out of existence and having to start over from the beginning (there is also a way of “archiving” a copy of your robot at certain waypoints on the board)? Well, as you take damage the number of program cards you dealt to select from are decreased. If you take enough damage some of your robot’s programming registers may become locked – meaning that the cards you have assigned to those registers will have to stay the same until you can get your robot repaired.

Finally there are ways of retrofitting your robot with special abilities.

STRENGTHS

This game is a tremendous amount of fun. If you’ve ever played Paranoia and gotten great laughs out of watching your characters getting fried you’ll already understand the appeal this game carries with it – nothing is more hilarious then when one of your fellow players suddenly groans, “Oh nooooo…” and you know he’s made a mistake in his plans and his robot is about to go cascading off-course and into jeopardy.

The game is beautifully designed by Phil Foglio – the cover illustration of a ZIP 550 looking nervously over his shoulder as he enters the factory is absolutely perfect at setting the tone of the game. Foglio also designed the miniatures which come with the game.

WEAKNESSES

The learning curve is pretty simple, but there are some rules which could so with better explanation. Wizards of the Coast has posted the complete rules and a FAQ at their website, and from what I’ve seen they have not fixed these problems.

The confusion over these rules is quickly eliminated however by some practical familiarity with the game. Play your first game on a single board and establish up front that rule interpretations could fluctuate wildly during the course of the game as you figure out some of the nuances.

There are several handy reference sheets and the rulebook is laid out in such a fashion that information is easy to find when you need it. This is not an overwhelming problem, merely one of having to play the game first before you can see what some rules mean.

CONCLUSION

This game is great. The idea is great, the carry-through is great, the rules are great, the entertainment value is great. You simply can’t go wrong.

There are also several expansion sets for the game (Armed and Dangerous, Grand Prix, and (coming later in 1998) Radioactive). I hope to own and review both these and the second make of this game in the near future here on RPGNet.

Style: 5 (Excellent!)
Substance: 5 (Excellent!)

Author: Richard Garfield
Company/Publisher: Wizards of the Coast
Cost: $34.95
Page count: n/a
ISBN: 1-57530-088-5
Originally Published: 1998/06/19

[ This is a review of the first make of the RoboRally game. The second make of the game (which I do not yet own), slightly altered the lay-out of the rules and changed the design of the miniatures included with the game. However, to my knowledge, game play was not affected to any serious degree. The ISBN product code above refers to the second make of RoboRally, as that is the one which you can still order from Wizards of the Coast. ]

For an explanation of where these reviews came from and why you can no longer find them at RPGNet, click here.

Over on Lamentations of the Flame Princess, Mr. Raggi wrote a really good piece on Toybox Style Play.

Check it out.

Basically, he’s talking about a principle of design in which you include elements which (a) aren’t designed to be interacted with mechanically and (b) don’t actually have any pre-designed purpose (or, at least, no “meaningful” one).

In other words, make it a point to include randomly cool shit in your adventures.

I really couldn’t agree more strongly with this. My 101 Curious Items are  an example of this. Similarly, whenever I’m keying a room, I’ll try to make it a point to include at least one detail that is interesting-but-irrelevant. These aren’t always things that the PCs can interact with, but they frequently are. (For example, in one “empty” room I littered the floor with shards of shattered pottery… which could be reassembled with a mend spell to reveal several crude busts. In another case I put “age-old scratches” on a door. )

If you’ve been reading the Alexandrian for awhile, you know that I make it a very specific point to design scenarios in which I really have no idea what the outcome will be. I want to be surprised by the actions of my players and to be just as surprised by what happens in play as they are. Stuff like Don’t Prep Plots and Node-Based Scenario Design describe some of the ways I achieve that at a macro-level. But this “toybox” design is one of the ways I exercise the same principle on the micro-scale: If you include enough randomly cool shit, eventually the players are going to grab onto it and do something ridiculously cool with it.

From At Home: A Short History of Private Life by Bill Bryson:

Two other vitamins — pantothenic acid and biotin — don’t have numbers or, come to that, much profile, but that is largely because they never cause us problems. No human has yet been found with insufficient quantities of either.

Poking around suggests that Bryson’s statement is not completely true. Isolated cases have been observed (usually due to a wider incidence of starvation) and the condition has been studied in mice. Intriguingly, some subjects have reported a “burning sensation” in their feet.

Which is, it turns out, the first symptom of “space scurvy”. On the first long journeys through the solar system, it was discovered that some curious interaction of solar radiation and rotationally induced “gravity” caused a breakdown of pantothenic acid. The resulting vitamin deficiency causes nausea, vomiting, and impaired mental faculties. Worse yet, victims manifest severe sleep disturbances: Think of the severe “sleep driving” side-effects of Ambien, crank them up a couple hundred degrees, and unleash them on a spaceship. Victims have been known to sleepwalk their way out of airlocks, damage ship reactors (some suggest victims of space scurvy actually have an unnatural attraction to sources of radioactivity), or simply pilot their ships into the nearest planets.

Some crazies in the Belt have actually been known to deliberately induce the deficiency disease, believing that the “pantothenic visions” have deep spiritual or religious meaning. In one well-known incident, the Bryson Colony broadcast its insane death throes throughout the entire system as a population of 166 souls commited ecstatic, prolonged suicide by way of holy vision.

Technoir uses a simple core mechanic in which verbs are used to push adjectives onto characters. (For example, you might use your character’s Hack verb to push the adjective “exploited” onto a gunrunner’s security system.) That may look a little gimmicky, but it actually seems like a really slick little system.

What I find particularly notable about this is that it mechanically articulates and reinforces a procedure that I use almost constantly when I’m refereeing in virtually any system: When a player proposes an action with an uncertain outcome, the action is mechanically resolved using the rules of the game. Then I consider how that outcome has shifted the status quo and carry that knowledge forward as additional actions are proposed and resolved. I’m intrigued to see how a system that feeds directly into this process will perform in play: Will it piggyback it? Reinforce it? Interfere with it? Enhance it?

I’ll probably have more to say about Technoir once I’ve had a chance to actually play it, but my read-thru of the rulebook actually got me thinking about something completely different that I want to touch on today: Skill challenges in 4th Edition.

Technoir structures its core mechanic into Sequences using a very simple system of turn-taking. The trick to resolving sequences is pretty simple: Because adjectives are meaningful, the GM can use his common sense to know when a sequence ends (because the adjectives that have been applied will either result in the players being successful or unsuccessful in achieving their goal). This works because you can’t just slap adjectives on willy-nilly; you need to establish the proper vector by which the adjective can be applied. (In other words, you need to explain what actions you’re taking to achieve the objective.)

The result is that adjectives both arise naturally from the game world and also strictly describe the game world. As a result, sequences build organically and logically to unforeseen conclusions.

The system is, as far as I can tell, incredibly flexible and can be applied to almost any conflict (or what Technoir refers to as a “contention”): Hacking, seduction, combat, interrogation, tracking, chases, etc.

In other words, Technoir‘s sequences have the same mechanical goal as 4th Edition’s skill challenges (resolving discrete chunks of action in a structured format). But skill challenges are the polar opposite of Technoir‘s sequences:

First, whereas Technoir trusts the creativity and common sense of the players at the table to determine when a goal has been achieved (or thwarted), 4th Edition’s skill challenges hard-code a success-or-failure condition which is completely dissociated from the game world. Or, as Technoir puts it:

After any turn is taken and an action is performed, everyone at the table should look at what’s happening in the fiction. As I said before, there’s no score. You have to decide for yourselves when this ends. Each player should respect the adjectives that have been applied and removed and decide what her protagonist wants now — no matter what hse came into the scene wanting. You should do the same for your antagonists. You might find that one side got what they cam for and is done. Or that the two sides are now willing to compromise. Or that there are no good vectors for attacks any more. Look for new ways out of the situation. Maybe it’s time to stop rolling dice and cut to a new scene.

But if there is still something to contend over, go on to the next turn and play out the next action.

Technoir cares intimately and enthusiastically about what your characters have done, why they’ve done it, and what they’ve accomplished by doing it. 4th Edition’s skill challenges, on the other hand, don’t give a crap about any of that: If you haven’t rolled four successes yet, then your characters haven’t succeeded (no matter what they’ve achieved with those checks). And if you have rolled four successes, then your characters have totally succeeded (even if their actions haven’t actually achieved that yet).

Second, Technoir‘s system inherently gives freedom of choice to the players. They set their goals, determine their actions, and even demand their outcomes. (Of course, those demands may not always be satisfied.) Despite several years of constant errata and house rules attempting to soften 4th Edition skill challenge’s away from the rigid railroad presented in the original Dungeon Master’s Guide, the system is still inherently antithetical to player choice. For example, here’s a key quote from the presentation of skill challenges in D&D Essentials Rules Compendium:

Each skill challenge has skills associated with it that adventurers can use during the challenge. (…) Whatever skills the DM chooses for a skill challenge, he or she designates them as primary or secondary. A typical skill challenge has a number of associated skills equal to the number of adventurers plus two.

Incredibly, skills that players want to use that the DM hasn’t pre-approved can never be considered primary skills and are automatically considered inferior (they can count for no more than one success and may not count for successes at all). By default, 4th Edition tells you that ideas originating from the players are not to be treated with the same respect as ideas originating from the DM. It’s hard-coded right into the rules.

The two approaches really are night and day: Technoir trusts the creativity of the players. 4th Edition shackles the creativity of the players.