Dateline – Storm Point

***SPOILER ALERT***

I’m running Tomb of Horrors for this leg of the Storm Point campaign. You may not want to read on if you’re playing the game yourself.

***SPOILER ALERT***

This past Storm Point game was pretty short. One of the players – the one who owns the space we pay at – developed a migraine, and we called it a night early.

We did get through the rest of the encounter, however. It was a tough slog, indeed, with the closely-matched antagonists. Of course, as with all battles, once one of the monsters dropped, the rest sort of cascaded as the characters were better able to concentrate their attacks. Some crappy rolls to distinguish friend from foe caused a few problems, but in the end, they made it through, and proceeded to take an extended rest.

So, that’s really all there is to say about that.

Dateline – Storm Point

***SPOILER ALERT***

I’m running Tomb of Horrors for this leg of the Storm Point campaign. You may not want to read on if you’re playing the game yourself.

***SPOILER ALERT***

The last Storm Point session was pretty much a wash. We hadn’t played in almost two months, summer scheduling being what it is, and spent most of the evening socializing rather than playing. We even had to stop the combat partway through when we wrapped for the evening.

The group made it through the secret door and into another oddly-shaped room. They entered carefully, mindful of traps, and everything went dark for a second. When the lights came back up, there was a duplicate of each of the characters standing near them. And, of course, the duplicates attacked.

The fight is tough. The monsters that are being used as the duplicates ((I’m not going to say what they are, yet, because the fight is ongoing, and at least three of my players read my blog.)) are well-chosen, and quite effective, even when I forget one of the powers. The mechanics for seeing if players attack their intended target or an ally have caused a couple of bad moments for the group ((And if they didn’t know that this adventure was The Tomb of Horrors, they would have been calling me out for such a dick move. Because they know what the adventure is, they take the boning almost in good humour.)), but I’ve been a little less stringent with that than I might, because it is a nasty thing to do to the players.

But at the end of the evening, we’d only got through three rounds of combat, and none of the enemy had been dropped, yet. I took a picture of the battlemap, and we called it a night.

I’m hoping for one more session before my Ireland trip, which should finish this encounter. After that, I expect one or two more sessions to wrap up the adventure. Then it’s on to the city-state of Belys.

Dateline – Storm Point

***SPOILER ALERT***

I’m running Tomb of Horrors for this leg of the Storm Point campaign. You may not want to read on if you’re playing the game yourself.

***SPOILER ALERT***

Yeah, I broke down and told the group what adventure we were playing. The combat this past session was extremely frustrating, with dazing auras and devastating attacks from the monsters, and one of the players commented that the punishment for failing to solve the puzzle on the first try – the monsters appearing – was really kind of out of proportion.

So I told them that they were playing the new Tomb of Horrors, and suddenly they understood. Punishment in this adventure is always going to be out of proportion to the infraction.

We picked up the game after an extended rest, and the party investigated the sundial and brazier. They had no idea what it was for, and eventually decided to move on. The way led outside, and across a bridge, into another large, strangely shaped building. This one, in addition to the runes, had a number of tapestries hanging on the walls.

Now, one of these tapestries was important, and described in detail, and had an illustration. The others were sort of glossed over. I didn’t like the idea of zeroing the players in on this one tapestry right off the hop, so I didn’t show them the illustration right away, and I made up a descriptions of each of the other tapestries that they looked at. This had mixed results; it made them have to work a little more to find the tapestry that was actually important, but it also made them pay a lot of extra attention to the other tapestries.

They discovered the important tapestry by going around the walls, ripping down tapestries, and the enchanted one wouldn’t come down. That’s when they got the illustration, and they pretty quickly figured out that puzzle, using the platinum key they had discovered earlier. They also discovered the two secret doors in the room, but were unable to open them.

Then it was into the other half of the room, with a tall torch and numbers arranged on the walls. They figured out that they needed to cast a shadow on a number, but got distracted by the tapestries, and picked a number that seemed to indicate a time represented in the tapestries. This got them a heaping helping of mad wraiths and a rather brutal combat.

I have a sort of love/hate relationship with puzzles like this in games. When they’re fun, they can be a lot of fun, but eventually, they stop being fun and just become frustrating. As a GM, I find myself having to watch the players carefully, and judge when the puzzle is starting to shift from interesting to annoying. At that point, it’s best to give little clues and nudge the characters in the right direction. I mis-timed this one, and wound up having to be much more explicit than I would have liked in order to head off the frustration and annoyance.

Still, the fact that they party had to go back and play with the sundial to find the right number to cast the shadow on should – I hope – illustrate the fact that the solution to a given puzzle is not always immediately present in the room where the puzzle is. We’ll see.

That’s where we left it that evening, after the revelation about the adventure’s identity. There was more exploration and problem-solving this game than combat, which is certainly something I want to encourage, but the combat was pretty long and brutal. The fact that we were down two players also slowed things somewhat.

But it was fun, and we’re looking forward to the next one.

Dateline – Storm Point

***SPOILER ALERT***

Two things.

First, I’m using a published adventure for this leg of the campaign, but the group doesn’t know what that adventure is. Please don’t tell them if you recognize it.

Second, because this is a published adventure, my accounts are going to have spoilers in them. If you start to recognize this as the adventure you’re playing – or going to play – you may want to avoid reading on.

***SPOILER ALERT***

Last night was the latest installment of the Storm Point campaign. Once again, I had a full house of players ((I’m starting to get spoiled, having everyone show up to every game! This makes all three of the restarted campaign.)), and once again, I’m pretty happy with the progress we made through the adventure. We did, however, wind up going later than we normally do.

We rejoined our valiant heroes as they were standing on a rickety rope bridge. The crossing was somewhat challenging, and a couple of them failed their checks and began to fall. I was rolling falling damage when Milo, the swordmage, decided to use Lightning Lure to snag his plummeting team mate and pull him back to the bridge, figuring a little lightning scorch is better than falling sixty feet. They all looked at me as if they expected me to say no to this idea, but I said, “Hell, yeah! That’s cool!”

Because it was, y’see.

And that kind of thinking is what I want to encourage in the game – using powers outside of combat, going for the cinematic approach. I always want to say yes to those kinds of ideas, as long as they’re not stupid ((Sometimes even if they are. Enough cool will outweigh stupid on the scales of GM Judgment.)). If it would look cool in a movie action scene, odds are I’ll say yes.

He managed to catch everyone that fell ((Though he almost missed Thrun; that dwarf has an extremely high Fortitude.)), doing around 10 points of damage to each of them, rather than the 33 points that an average 60-foot fall will do. Everyone was singed but grateful.

Once across the bridge, they entered an oddly-shaped building that contained a diorama of the site. They were able to identify the building they were currently in, and the little garden area below the cliffs where they first entered, but the rest of the structures were completely changed. Galvanys recognized the layout of the diorama as a graveyard for the high eladrin ((“So, we’re in a desecrated graveyard in the Feywild. Great. Is there anywhere worse we could be?” “Dude, shut up! The DM can hear you!”)), being eladrin himself.

Finding nothing else of interest here, they went out the other doorway of the building, across another rope bridge ((Couple more falls, couple more Lightning Lures)), and into the oddly-shaped structure on the other side. This building was more obviously constructed of several smaller buildings that had been cannibalized for building materials, and the inside was covered in deeply-carved runes. Investigation showed them similar to the ones that the group had found on the bodies of the harpies and dryads who had attacked them. Again, they seemed to be catching the energy of death, and channeling it somewhere nearby. Milo and Faran realized that this was definitely something bad, as the death energy should be flowing to the Raven Queen, the goddess of death, but was instead being siphoned off for other purposes.

The next room they entered had an overflowing pool with a key in the bottom ((“Does 4E have water weirds?” “I don’t think so.”)). Reaching into the pool for the key caused the water to rear up in the form of a serpent and strike at Galvanys, who had tried to take the key ((“See? Water weird!” “Actually, no. It’s just a magical effect.”)), teleporting him out into the nearby river right near the top of the falls. He managed to swim to shore, and made it back into the room inside a couple of minutes.

After some trial and error (and a few more dips in the river), the group teamed up to distract the trap while Ssudai, the dragonborn monk, snatched the key and ran for the door. Once he was past the doorway, the serpent collapsed back into the pool, and everyone cheered.

In the next chamber, they found a brazier hanging above a sundial, more of the strange runes, and a captive eladrin woman, who turned out to be a lamia.

This was a tough fight, made tougher by two things: first of all, the group didn’t have a controller, so very few close and area attacks. Second, I didn’t read the encounter closely enough, and dropped in both scarab swarms at the start of combat, instead of waiting until the lamia was bloodied to bring the second one in. The first point meant that, by and large, the group was doing half-damage to the lamia and the swarms, and the second point meant that they had more fronts to fight on, splitting attacks and damage more.

Still, though the fight was long and grueling ((And the first part pretty boring for Thrun, who spent the first three or four rounds alternately dazed and stunned.)), they managed to survive and triumph. Ssudai dumped burning coals from the brazier on some of the scarabs, and Faran dropped his blade barrier in a narrow point so that everyone could just keep hitting the lamia and pushing her back into the zone for more damage.

At that point, it was ten o’clock, which is about an hour later than we usually game on a Sunday evening, so I wrapped it up before letting them explore the room. That’s where we’ll pick it up next time. No one minded, because I told them they’d each get enough experience points to go up to tenth level.

But we got through two combat-ish encounters, and a total of five encounter areas, so I think we did pretty good for one evening. I like this quicker pace.

We’ll see if we can keep it up.

Dateline – Storm Point

***SPOILER ALERT***

Two things.

First, I’m using a published adventure for this leg of the campaign, but the group doesn’t know what that adventure is. Please don’t tell them if you recognize it.

Second, because this is a published adventure, my accounts are going to have spoilers in them. If you start to recognize this as the adventure you’re playing – or going to play – you may want to avoid reading on.

***SPOILER ALERT***

Last Sunday ((Yes, a full week ago – I’m almost caught up now.)) was the latest session of the Storm Point campaign. Two sessions in a row with a full roster of players – I’m going to get spoiled if this keeps up ((Not a bad problem to have.)).

I’m continuing to run the published adventure for the group, and I have to say, I’m kinda liking the freedom it gives me and the players. That may seem like a kind of counter-intuitive sentiment, but it’s true. Normally, I only have time to prep a couple of encounters per session, and I then funnel the party towards them. I try to keep a pool of three or four generic encounters on hand for when the party goes completely off my map, but those often don’t fit the story as well as I might like, and prove distractions. With the published adventure, if the party goes somewhere I wasn’t ready for ((As they did this session.)), it’s still right there in the book, and I just ask for a couple of minutes to read it over and refresh my memory.

That means that, not only am I ready to game with minimal prep time, but also that I don’t have to funnel the party towards the adventure in the same way. They get to go where they want, and find the adventure waiting there for them. This may not be news to anyone else, but it’s been a long time since I’ve run a published D&D adventure that works this well ((Most of the published ones I’ve run in the past three or four years that have required almost as much prep and herding as a home-built adventure.)), so it’s a pleasant surprise.

Anyway, when we left our heroes, they had just crossed over into the Feywild. That’s where we picked up this time, and they followed the trail they found through the strange, dark woods to a ridge of dark rock. On top of the ridge was a jumble of buildings, and a cave cut into the base of the ridge. Beside the cave was a strange, taunting poem carved into the stone.

After deciphering the poem, and talking things over – all the while keeping watch for the monsters they were sure were going to pop up at any moment – they went into the cave, where they found three statues – Maiden, Mother, and Crone – blocking the route through. Each statue had a hand extended.

This prompted some more discussion – statues in dungeons almost inevitably come to life and hit you, after all – and Milo finally decided to put a silver piece in the hand of the Crone statue. Sure enough, the statues came to life, but only to step aside and allow the party to pass. The cave opened out into an overgrown garden in at the bottom of the cliffs that supported the buildings high above them.

Instead of pushing on through the garden and discovering the main way into the building complex, they scouted around and found a tunnel into the cliff face that I had overlooked when prepping for the session. It led them up to a building that I hadn’t read over since the first time I had read the whole adventure, but I asked for a bit of a pause while I quickly looked over the description of the area, and then on we went ((This is what I mean by the freedom. No extra prep for me, no false restrictions on player action.)).

The room they found themselves in was an irregular cave-like structure with walls made of the jumbled bones of thousands of creatures. There was a statue in the middle of the room ((This one didn’t come to life. Just sayin’.)), and a grey angel ((I couldn’t remember what these are supposed to look like, so I described it as looking like the death creature from Hellboy II.)). Well, the angel got the drop on the party, and then his buddy showed up. The necrotic attacks, coupled with the life-draining magic of the room, made the fight somewhat tougher than I think either side was anticipating, but they managed to defeat the evil creatures and make it out of the room to a rope bridge where they could rest a little.

And that’s where we left it.

I’ve been trying to boost the pace of these games a little, so that we get more, and more varied, things done in a single session. In that respect, I’m pretty happy with this session. There was exploration, puzzle-solving, and a combat, and we got it all in in about three and a half hours. Ideally, I’d like to speed up the pace of combat, but that would require everyone actually paying attention to the game when it’s not their turn, so I don’t think that’s terribly realistic in this group.

Still, a GM can dream…

Dateline – Storm Point

***SPOILER ALERT***

Two things.

First, I’m using a published adventure for this leg of the campaign, but he group doesn’t know what that adventure is. Please don’t tell them if you recognize it.

Second, because this is a published adventure, my accounts are going to have spoilers in them. If you start to recognize this as the adventure you’re playing – or going to play – you may want to avoid reading on.

***SPOILER ALERT***

This past Sunday saw our return to the Storm Point campaign, after a hiatus of five months, when I ran the Gammatoba mini-campaign. I was gratified to have a full house for this first session back, and was very pleased to get back to the game.

Anyway, the gang is almost tenth level, so I want to move them out and away from Storm Point, into the wider world and beyond. To that end, I decreed that a year and a half had gone by in the downtime, and started the session with a description of how things had changed in the area: the town of Storm Point prospering, the dwarven city of Silverfalls being resettled now that the heroes had cleansed it, and a little village growing up around the hospital the players had constructed. I emphasized the way things were pretty tame in the neighbourhood, now, and that, prosperous as the town was becoming, it still couldn’t match a larger city for the purposes of selling loot or buying stuff.

With that done, the party was primed and ready when a dwarven merchant asked them to look into missing caravans between Silverfalls and the city-state of Belys, on the far side of the Bitter Mountains. They haggled with the merchant, getting him to make them shareholders in his company and providing them with letters of introduction to merchants in Belys in return for their assistance. Then they tried to get him to give them the carts, horses, and provisions they would need to create a fake caravan to try and trap whoever was responsible, but he wasn’t having that – he was paying them to do a job, they were responsible for getting the job done.

Our heroes took that in stride, however, and outfitted their own one-wagon caravan, and set off through the mountains. The trip took them about a week to get through the pass, and then they reached the Gloaming Wood, a crescent-shaped wood that circled about half the plains that surrounded Belys. A couple of days traveling through that wood, and they could tell that the Feywild was very close. Galvanys had heard tales of the Gloaming Court, one of the minor factions of the eladrin, that he thought held sway here, but didn’t remember too much else.

About a day away from leaving the wood, they spotted some suspicious piles of leaves in a clearing by the side of the road – suspicious in that one had a bloodied arm sticking out of it. They stopped the wagon, got out, and Ssudai crept up on the piles stealthily, while the rest of the group advanced more openly. That’s when they spotted the harpies in the trees, and Thrun decided to try and scare them off.

At this point, the corpses in the piles of leaves revealed themselves as dryads, we rolled initiative. The fight had some interesting movement in it, with things being swept back and forth across the battlefield, and some tree climbing by Ssudai. It took a pretty long time to get through, though, mainly because everyone was trying to remember how to play their characters during the Gammatoba hiatus. Things got a little tense, but really there wasn’t that much danger overall.

The point at which they decided they might really be in trouble was when they killed the first dryad. Her eyes rolled back, she convulsed, her bark and wood turned grey, and mist started to rise from her eyes, mouth, and fingertips. She only stuck around for another round, getting in one more attack before crumbling to rotted wood, but the rest of the monsters followed the same pattern, which weirded the party out a bit – as it was supposed to.

After the fight, the group examined the bones and wood of their opponents and found runes carved on them, still leaking the grey mist. Milo analyzed the markings, and determined that they were necromantic sigils meant to drain off and channel the life energy of whatever the creatures killed, and Faran determined that they called on the power of old, dead gods.

At this point, it was getting a little late in the evening, and  wanted to move things on to a specific stopping point, so instead of making it a big puzzle to figure out where these fey creatures had come from, I let the party follow the grey mist rising off the remains of their foes. It led them into a glade where the trees were dark and twisted, and in the midst of it all, two ancient, half-dead oak trees had grown into a portal to the Feywild, and the next stage of the adventure.

There was a brief moment of panic on my part, as the party started talking about how they could just close the portal, and how stupid they’d have to be to pass through it. My initial response was to force them through somehow, but then I just calmed down and decided that, if they didn’t go through this one, I could get them to the party some other way, and let them decide what they were going to do. In the end, they decided to go through the portal after all, so I needn’t have worried.

And that was the point I stopped things.

It was good to get back to Storm Point after the hiatus, but the hiatus was nice. It let me recharge my enthusiasm for the game, and to think about what’s working and what’s not. In general, I’m happy with the game, but I want to bring in more variety of play – make it less of a fight-of-the-week game. To do that, I’m looking at ways to encourage other types of adventure, more exploration, and more interaction. I’m also trying to make the fights move more quickly, but that’s an uphill battle with this group’s attention span. I’ve got some ideas in that area, though.

Still, it’s good to be back.

Dateline – Storm Point

Been a while since we visited the fellows in Storm Point. The last session, the focus just wasn’t there. I spent an hour trying to get the group to make a single Stealth check before giving up and teaching them to play Fiasco instead ((Used the Lucky Strike playset, and everyone had a great time.)). The time before that, the game was the fifth one I was running in four days, and I wimped out to run the Gamma World game day adventure for them, instead ((A mistake. I was tired and stressed and short-tempered. I should have just canceled the game.)).

This meant that it had been about two months since the previous session, and the Silverfalls adventure had gone on far longer than I had planned. I wanted to wrap it up, which meant unleashing the beholder on them.

See, I’d been carrying around the beholder ultimate tyrant miniature for the previous several sessions, and taunting my players with it. They all know by now ((Or think they do, anyway.)) that I’d never throw something like that at them at their level. Well, I was planning to do just that, but using the stats of a bloodkiss beholder. This was just the only beholder miniature I had.

The release of the Beholders Collector Set fixed that problem, and the release of Monster Vault provided a stat block for a level 9 solo beholder, so that all just worked perfectly. I bumped the level of the beholder up to 10, to take into account the fact that I’ve got six players, and went to town.

I’d never used a beholder in a game before. Honestly, I think they’re kind of silly monsters. But they are iconic, and the ones in 4E are much simpler to run than in previous editions, so I was looking forward to how it played out. For the first round, I became very afraid that I had built a TPK – most of the characters had their encounter and daily powers stripped by the central eye, and the petrify eye had locked down the main tank. Things looked grim.

But they rallied ((Most of them, anyway. The guy playing the cleric spent pretty much the entire combat either petrified or immobilized after only a single petrify ray attack. Sorry, Mark.)), and came on strong. The whole fight was about as good as it could have been, with the party pretty much terrified that they were going to die, and horrific eye rays firing off like a disco laser show. The mechanism for having an eye-ray fire at the start of each character’s turn is a great way to make the beholder feel like a whirling ball of death.

They managed to put it down without losing anyone, though there were several close calls. And then they found the bones of the dwarven ancestor they had come to retrieve, and decided to call it a day.

I didn’t like that ending, though. It lacked the sense of achievement and heroism that I thought the lengthy adventure deserved. So, I had the ghosts of the dwarven warriors appear and ask to be bound to defend the home they had died for. The group used a skill challenge to throw together an impromptu binding ritual, and I described how the ghosts of all those who had died in Silverfalls came back to drive out the drow, troglodytes, minotaurs, and their mind flayer masters ((I had a mind flayer encounter prepped and ready to go if I needed it, but it would have been really nasty to throw it at them right after the beholder fight.)).

So, now Silverfalls is cleansed of the evil invaders and open to resettlement. And the gang are even more heroic than they thought they’d be.

I call it a win.

We’re talking about running a more extended Gamma World adventure next, so it may be a while before we come back to Storm Point. But I’ve got some plans for when we do.

Mutants! Mutants Everywhere!

I’m finally starting to dig myself out from under the backlog produced by two very full weeks of gaming. I’ve got a few things that I’m going to be writing about over the next several days, but I’m starting with my thoughts on Gamma World after finally getting to run it. Twice, as it turned out.

You may recall that I ran the Gamma World Game Day for Imagine Games. That was on Saturday. On Sunday, I decided I had too little energy to do the prep work necessary for the next Storm Point installment that evening, so I ran the Gamma World Game Day adventure again, for my Storm Point group. I think it was very useful to run the same adventure twice, with completely different people, and totally different mutants. It illuminated some interesting things about the game.

First off, everyone at the Game Day had a lot of fun, and enjoyed the game. At the Sunday game, it wasn’t as successful, primarily because I was pretty burnt out after running games on Thursday, Friday, and Saturday, and it left me distracted and testy ((As my players will attest. Sorry again, guys.)). Still, it wasn’t a complete wash – I think the game went fine, it just didn’t show itself off to best effect because of my mental state.

The Game Day crowd was a table of four, and I almost killed them all in the first encounter. And again in the last encounter ((For the record, the other group playing did wipe in the final encounter.)). The middle encounter turned out to be a cakewalk, even with the addition of some sentrybots from the other table ((This is how that happened. In the middle of the fight with the Klickies in the underground parking garage, the GM from the other table comes over with a handful of sentrybot standees and big grin. A couple of the players from that table are behind him. He says, “One of the players just teleported these sentrybots five miles in a random direction. I’ve decided they end up on your table.” My players kind of chuckled, and then I said, “Sounds good,” and started setting up the standees. I did it mainly to see the look on their faces. And it was worth it. And yes, I did make them fight the sentrybots and the Klickies at the same time.)). On the other hand, the Sunday game was a table of six, and they pretty much walked through the entire adventure, except for a few close calls in the final encounter.

Now, I’ve said before that the mortality rate in Gamma World is pretty daunting, and may be a barrier to longterm campaign play. What these two run-throughs of the same adventure taught me is that the mortality rate skews a fair bit based on a number of factors. I was surprised that it wasn’t the size of the group that seemed to have the greatest impact; it was the types of mutants.

The first encounter in the Game Day adventure includes a pretty powerful monster – a blood bird swarm. This is a level 4 soldier, with a damaging radioactive aura, in addition to some pretty nasty attacks ((To be fair, most of the monsters in Gamma World have some pretty nasty attacks. Genghis Tangh and his hoop barbarian are truly frightening when they get rolling.)), and it was responsible for doing the most damage to the Game Day group. On the other hand, they were no problem for the Sunday group. Why? Because two of the Sunday group had a Radioactive origin ((We wound up with a few doubles in the groups. At first, this surprised me, but then I realized it’s another example of the Birthday Problem with a smaller set of possible options.)), and were therefor immune to the damaging aura.

Given the random character generation method, and the random Alpha Mutations, this means that it can be trickier to judge an appropriate encounter absent the knowledge of the player characters. Not necessarily a bad thing, but something you need to be aware of if you’re designing your own adventures.

Another interesting thing I noticed in the game is that the players, even those who were skeptical about the card-based system and the rapidly changing powers and tech, really got into the whole random draw thing. It was like a mini-lottery every encounter, with all the anticipation, exaltation, and disappointment you could ask for. And the fact that rolling a 1 meant Alpha Flux, players who drew crappy mutations for the situation kept trying stuff on their turns, hoping for that 1. It made for a very dynamic, interesting game.

I still don’t think that the game is designed to make things easy for longterm campaign play, but I have a better feel for it now, and some basic ideas of how to go about tweaking it to make it work a little better for that. If I were going to run a full campaign – which I would never do ((This is an in-joke. My players get it.)) – here’s what I would change:

  1. Allow the player to pick at least one of his or her origins.
  2. Use an ability array instead of random rolls to complete the other abilities.
  3. Allow the player to pick his or her third trained skill.
  4. Give each character 10 extra hit points at 1st level.
  5. Change the Alpha Mutation mechanic in one of two ways:
    • Reduce the frequency of Alpha Mutation change, either to every extended rest or to only when there is Alpha Flux, OR
    • Build a themed deck of powers for each character.

The only other factor that might need to be addressed is the silliness factor, and that can be handled through play style and the choices players and GMs make for character types, monster types, and adventures.

So, in short, yay Gamma World. We’re probably going to revisit it in the Storm Point group as a bit of a vacation between Heroic and Paragon tiers. I’m looking forward to it.

Gamma World: First Impressions

So, like every other gaming fan-boy, I grabbed my copy of Gamma World on Friday night. Not only am I running the Gamma World Game Day on October 23 at Imagine Games and Hobbies, but the Storm Point campaign is looking at taking a short D&D hiatus to play a little Gamma World. I’ve spent some time over the weekend reading through the game and generating some characters, just to try things out, and I’ve got some initial thoughts on the game.

It looks like a lot of fun, but it is pretty fine-tuned for a very specific kind of play experience. The game is designed to be rather crazy, with strange mutations, bizarre landscapes and situations, weird tech, and high mortality rates among PCs. The mechanics are based on D&D 4e, with things tweaked a little bit for the new style of play. The healing rules, the level-based bonuses, and a few other things have been altered to reinforce the free-wheeling, beer-and-pretzels, absurd style of play that the game fosters.

Like pretty much all Gamma World editions, character creation is random ((Admittedly, it may be a little more random in this version than in some others.)), and you can wind up with some very strange characters to play. When you factor in the idea of Alpha Flux, and the changing mutations reflected in the Alpha Mutation cards, characters can – and do – change from one encounter to another. The random rolls can create some very strange origin combinations, and the Alpha Mutation deck adds another layer of weirdness as you try to figure out how your gravity-bending android suddenly has the power to read minds or grow tentacles ((The baseline explanation, of course, is provided by the explanation of the Big Mistake, with the mixing and merging of alternate universes still ongoing, re-editing the characters from time to time.)).

Most powers and weapons ((Especially Omega Tech items.)) do pretty impressive amounts of damage, and hit points are about on a par with 4e. This means that characters are not as durable as you might expect them to be, especially as healing is pretty thin on the ground. No more healing surges – instead, everyone can take a second wind action once per encounter and heal up to full after each encounter for free. Second wind has been beefed up, healing half your hit points, instead of a quarter, and it’s only a minor action. On the down side, there are fewer powers and items that I’ve seen that offer healing. This can lead to a pretty high mortality rate during play.

The game touts this as – well, if not actually a feature, per se, at least a design goal. Characters are pretty quick to generate, so dying means you’re out of play for maybe fifteen minutes as you whip up your new mutant to wander by and join the fun. Because so much of the game is focused on the experience of playing your character changing so often, this is less jarring than it might be in a more… serious, I guess… game.

I have to admit that I was a little leery about the use of cards and deckbuilding in the game. It struck me as injecting a lot of what I don’t like about CCGs into my RPG fix – you need to buy more and more cards for your character to be viable. After reading the game, I am less troubled by it. The game comes with enough cards that you won’t ever need to buy a booster pack. They are completely superfluous to play. Having said that, they do add some real coolness to the game, with neat new powers and toys to make the game even crazier than before. The guides to deckbuilding are very loose and, while they can let you tailor your mutations to fit a little more with your character concept, I can actually see a carefully constructed deck removing a lot of the weird, unexpected awesome that the cards can contribute. If you’re always pulling the same four Psi mutations and Xi items, you’ll never have the wild, giddy joy that comes of suddenly growing mandibles for no readily apparent reason and going to town with your newly discovered force pike ((In addition to this, Gabe over at Penny Arcade makes a very telling point: “If you decide that you would like to build your own decks to draw from then yes, you can go and purchase booster packs. You are not at a disadvantage if you don’t though because this is not a competitive game. In MTG you are pitting your deck against your opponents. If you don’t buy booster packs you don’t have a deck and that will making winning very difficult. In Gamma World you are playing with your friends and against the DM who does not get to draw any cards. The cards are just for fun and to help you kick the shit out of whatever the DM throws at you.” Thanks, Gabe!)).

So. As I said, the game is very focused on a certain kind of loose, rollicking, wahoo style of play by default. In doing some thinking, there are a couple of things that I think you could tweak with house rules to turn it into something better able to sustain long-term campaigns, or turn it into a more serious type of game.

Less Random Characters

If you’re not a fan of the very, very random character generation, it’s pretty easy to change it to allow for more designed characters. Allowing players to pick and choose their origins – even if you only let them choose one of their two origins – can go a long way toward letting people play the kind of character they want. And you can bypass the random roll of attributes for those not set by origins, allowing players to use an array, similar to in D&D. Easy.

Now, I found the random character generation I tried this weekend produced some interesting and very playable characters. The three I rolled up include a robot powered by a contained quantum singularity (Android/Gravity Manipulator), a colony of psychic Moebius Newts (Mind Breaker/Rat Swarm), and a Mi-Go (Plant/Cockroach). I think the random elements can really spark creativity, especially when you’re trying to reconcile two apparently contradictory origins.

This will also lead to a longer character creation time, so if you’re going to do this, you need to also address the next issue.

Lower Character Mortality ((I almost typed “Lower Character Morality,” which is a completely different kind of game.))

Allowing characters to take a third wind in combat might be all that’s required to balance this. That and maybe making some healing potion analogue readily available during play. If you’re looking for something more complex, you can revamp the damage of the various weapons and attacks so that they’re more in line with 4e values.

Stable Mutations

First off, everyone gets a couple of powers based on their origins that are consistent no matter what happens with the Alpha Mutations cards, so it’s not like everything about your character changes when you draw new mutations. But some of the weird things that happen with Alpha Mutation cards kind of strain credulity when they come up outta nowhere ((“What do you mean, now I’m aquatic? When the hell have we been near any water? This is a desert!”)). Allowing characters to build their own Alpha Mutation deck is one answer – they can pick options that fit their character concepts a little better, and focus on certain types of powers. Another option is to give each character a permanent card (or two, or more, if they’re of sufficient level) that they don’t have to discard after use. You can then decide if they get to pick the card or if it’s random. You can even do a combination – they get three random cards, and have to pick one to keep.

Those are just some thoughts after reading the game. Having looked at some of the buzz online, though, I’m going to encourage the Storm Point geeks to play it as written, at least for our first game.

I’ll let you know how it goes.

Dateline – Storm Point

Last Sunday was the latest installment of the Storm Point campaign, and it wound up being a bit of a frustrating throw-back for me. This was all my fault: first of all, I was late to the game, so we were kind of rushed. Secondly, I put together a pretty big fight, which I knew would take a fair bit of time, and the late start, along with the big fight, made things drag at a couple of points.

Now, I mentioned in previous posts that I was trying to use smaller combat encounters, to get through more in a single session. I deliberately used a larger one this time because I realized that, although the group had just hit 9th level, I still had not given out the bulk of the treasure for 8th level. Rather than just exacerbate that problem, I put all the treasure in a big pile and gave it some tough guardians.

The game-reason I came up with for the encounter is that, though Silverfalls had been taken by invaders centuries ago, and looted at that time, there were still periodic scavenging parties going through the many, many mansions, tunnels, and buildings. This one party had accumulated a pretty good haul, and were gathering it at a staging point to carry it down deeper into the dwarven ruins.

So, the party is not all that stealthy. The bad guys figured out pretty quickly that there were interlopers, and set up a bit of an ambush. Our heroes found the pile of booty, guarded by a gang of troglodytes and a single drow. Once they were engaged, a few more drow popped out of the scummy pool of water where they had been hiding, and a drider dropped out of the shadows to join the fun ((7 troglodyte maulers, 1 drow cleric of Lolth, 3 drow adventurers, 1 drider fanglord – 3725 xp, an 11th-level encounter for 6 characters.)).

I could tell early in the game that the fight was going to stretch longer than I had anticipated, so I ignored some of the more complex ((And, unfortunately, more interesting.)) abilities of some of the combatants – the drows’ darkfire, for instance. Still, it went on longer than I really wanted it to.

But we got through it, and now the gang is looking at pressing into the Lower City, still searching for the bones of Thrun’s ancestor, which should lie where he fell defending the evacuees.

And what could go wrong with that, right?