The Alexandrian

Tagline:In the spirit of Capture the Flag and Paintball, but with twists all its own, Killer definitely deserves the title of Best LARP of All Time.

Running Just as I’ve never had a chance to run the Darkness Revealed trilogy, I’ve also never managed to get a proper game of Killer set-up. Yet another some day…

Killer: The Game of Assassination - Steve JacksonThe history of Killer: The Game of Assassination dates all the way back to 1981. This new edition, released in 1998, continues the nearly 20 year tradition admirably.

Killer’s basic concept can be summed up very simply (in the words of SJG): “Wipe out your friends.” Basically Killer gives you a set of guidelines for setting up a competitive structure in which, yes, you go around killing your friends. This shouldn’t be confused with something like Paintball – where you go out into the wilderness and spend a few hours blowing each other away in a fairly harmless manner. No, as the full title (“The Game of Assassination”) suggests this is more subtle than that – a typical game can stretch over weeks, months, or even (although I pale to think of it) years. You don’t walk up to somebody and shoot them, instead you have to plot ingenious and crafty ways of knocking them off. You’re not a soldier, you’re an Assassin.

With such a simple concept, you might think, you don’t have to even buy the book. And why is it 80 pages long – there must be a lot of fluff, huh?

Wrong.

This is a great manual giving you giving a set of guidelines and a handbook to playing the game. It starts by giving you a general set of rules which you can use to vary the specific nature of your game (examples vary between allowing access to living places or times of day when killing is allowed). From there it gives an exhaustive list of fake weapons which can be constructed and used (and cautionary notes against many which should not be used) – from guns to bombs to poisons to sci-fi contraptions.

From these basics the book provides several optional versions of the game, some general words of advice and caution, some pre-built scenarios which can be used, a scoring system, and a set of photocopiable faux documents for the use of the playing group. And let’s not forget the hilarious illustrations which accompany the text.

All in all by the time I finished reading this manual I was itching to set up a game. Definitely give this book a try, at only fifteen bucks you won’t be disappointed.

Style: 4
Substance: 5

Author: Steve Jackson
Company/Publisher: Steve Jackson Games
Cost: $14.95
Page count: 80
ISBN: 1-55634-351-5
Originally Posted: 1998/12/14

I actually had no memory of reading this book or writing this review until I started converting it for the website; then a flood of memories came rushing back. It was after a few experiences like this that I started keeping a log of books as I read them. Human memory is a really fickle thing.

I do remember now that my interest in this book grew as a direct result of my first experiences with paintball (which I was properly introduced to by members of my D&D group at the time). I was never able to get that group interested in Killer, though.

Has anybody reading this participated in a round of assassination? How was it? Worth the time for me to try to get one set-up?

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

Legends & Labyrinths - Art Logo 1

Dungeon Encounter - Alex Drummond

Smoky torches? Check. Worn stairs? Check. Black-mawed doors? Check. Inexplicable carvings? Check. Vapors of a worrisome nature? Check and check.

Nothing more exciting than a good dungeoncrawl.

Note, too, how the central figures are dwarfed by the enigma of the locale. They could be anybody. They could be you.

Which way will you turn?

Technoir: The Untouched Core

January 18th, 2012

Technoir - Jeremy KellerHad an interesting experience with a plot map in Technoir last night and wanted to share it: I generated a mission seed, figured out what was going on, and then hooked the PCs.

But during the actual session, the PCs never got anywhere near the core of the plot map (the heart of the conspiracy defined by the original mission seed). Instead, they became completely wrapped up in a complex periphery of events that were being influenced or instigated by the conspiracy without actually being a part of it.

I’m now referring to this as the “untouched core”. Let me give a hypothetical example of what I’m talking about:

I generate a conspiracy focusing around a complex alliance of interests working to rig the presidential election in Ohio. The first impulse is that the PCs will work their contacts, shake a few trees, and eventually find a way to unmask (or at least de-fang) the conspiracy (presumably preventing the election from being rigged). But when the campaign takes the form of the “untouched core”, that’s not what happens: Instead, the PCs get tangled up in the street warfare of a small gang that murdered a campaign worker. Or end up investigating the illegal medical testing of one of the companies involved in the election rigging. Or wrangle a contract to protect one of the down-ticket candidates.

The point is that you end up with his sort of “cloud of activity” surrounding the conspiracy at the center of your plot map, and it’s fully possible for the PCs to get completely (and compellingly) tangled up in this cloud without ever worming their way into the heart of the matter.

This isn’t necessarily something that I could force to happen. (And I wouldn’t want to.) But it’s something I’m going to make a point of leaving myself open to and being all right with if it happens in the future.

By contrast, I think I inadvertently mucked up the first Technoir adventure I ran by pushing too hard for the revelation of the central conspiracy. I think I would have been better off simply letting the PCs resolve the local squabble they were tangled up in and letting the deeper conspiracy either pass them by or come back for a second pass in a different form further down the road.

A quick walk through the history of the saving throw mechanic:

(1) OD&D offered an incomplete, source/type-based array of saving throws. This created a couple of problems, one of which was that many effects would actually fall into multiple categories. Did the DM simply make a ruling for which applied? Did a character always use the best-applicable saving throw? Or should they always use the worst-applicable saving throw?

(2) AD&D eliminated that problem by establishing a fairly clear hierarchy of which saving throw category should be applied first. But it didn’t fix the other problem, which is that many effects which required saving throws didn’t conveniently fall into any particular category. There were two possible solutions: Create a new category every time you needed one or simply arbitrarily assign one of the existing saving throw categories. In general, designers and DMs did the latter. This assignation was often based on a rough approximation of “method of avoidance” (you avoid dragon breath by ducking out of the the way, this effect could be avoided by ducking out of the way, so let’s make it a save vs. dragon breath) or “similarity of effect” (dragon breath is a big blast of fire, this trap is creating a big blast of fire, so let’s make it a save vs. dragon breath). (These methods often overlapped.)

(3) D&D3 eliminated that problem by swapping to a universal system based on method-of-avoidance. In some corner-case situations, this system actually reintroduces the lack-of-hierarchy problems from OD&D (“do I duck out of the way or do I tough it out?”), but most of the time there is a clear and obvious saving throw for any given effect.

(4) 4E, of course, took the term “saving throw” and applied it to a completely different mechanic. But if you look at the mechanic which actually derives from pre-2008’s saving throws, 4E did two things with it: First, it inverted the facing of the mechanic. Instead of the defender making the saving throw roll, it’s the attacker rolling against the save.

This is an interesting choice. And to understand why, let’s consider the fact that they could have done the exact opposite with AC: Instead of the attacker rolling vs. AC, they could have swapped AC so that it works like old school saving throws (with the defender rolling against the attacker’s static score).

It’s important to understand that, in terms of mathematics and game balance, this change is completely irrelevant. It has no effect whatsoever.

In my (admittedly anecdotal) experience, however, the psychological effect of this mechanic is to make the person initiating the action feel passive: They announce the action their character is taking in the game world, but they take no “action” in the real world. Instead, the target takes the real world action.

Or, to put it another way: If you roll for an attack, the emphasis of the game becomes trying to hit people with your sword. If you roll for defense, the emphasis of the game becomes trying to dodge or deflect the blows of others. (If you roll for both, no such emphasis occurs. But this becomes too swingy with D&D’s d20-based mechanics.)

As a result, in 4E, you are always active on your turn and always passive on every other character’s turn. In 3E, on the other hand, the differentiation between the facing of attack rolls and the facing of saving throws mixes the experience up: Spellcasters generally feel more “passive” than fighters on their turn. Meanwhile, players frequently become “active” on other characters’ turns because saving throws will be called for.

Here, as with many of its design choices, 4E is flattening the game experience into something more “consistent”, but also blander and less varied. No player will ever feel as if they “didn’t do anything” on their turn, but the trade-off is that they literally do nothing while everyone else is taking their turn. (Theoretically this is then balanced out with the plethora of immediate actions that 4E adds. BID.)

The second major change 4E implemented, however, was to basically eradicate any clear connection between the action in the game world and the save/defense being used. (For example, a cleric can use his weapon vs. AC, vs. Fort, and vs. Will. Why? Because the mechanics say so.) They embrace this dissociation of the mechanics because it allows them to give every character class the ability to target different defenses without having them actually take different types of actions.

Laying aside the general effects of dissociated mechanics for the moment, this second change has the practical effect of watering down the actual meaning of the various defense scores. When Radiant Brilliance lets you charge your weapon with divine energy and trigger an explosion by hitting your target with a vs. Reflex attack and Holy Spark lets you do basically the same thing with a vs. Will attack… what’s the difference between Reflex and Will defenses? Absolutely nothing, of course. They’re just arbitrary categories that we drop various powers into for an “interesting” mechanical mix.

Legends & Labyrinths - Art Logo 1

Dove City - Alex Drummond

Dove City – Alex Drummond

So far we’ve been featuring fantasy heroes in this series, but of equal important, in my opinion, are the startling vistas of fantasy.

Alex Drummond‘s conception of a place called Dove City draws my eye into the misty depths of forgotten antiquity. I yearn to cross those bridges of stone and explore the byzantine chambers which lie behind those intricate walls of bas relief.

What do you think lies within?

Archives

Recent Posts

Recent Comments

Copyright © The Alexandrian. All rights reserved.