December 2017 - Roll For Combat: A Starfinder Actual Play Podcast

Talking Combat 012: Always Spay and Neuter Your Space Dogs

Akata

Jason recaps the events from Roll For Combat, Episode 012: Who Let the Dogs Out?

I’m not going to spend a lot of time on Steve’s rules tips, but I’ll throw my two cents about whether Steve is “for the monsters” or not.

There’s Rational Me, and there’s Emotional Me.

Rational Me recognizes that what Steve is “for” is good story moments and that sometimes comes across as being pro-monster. Steve gets excited when something interesting is about to happen, and a lot of times, what’s “interesting” is the party getting pushed to its limits by an encounter. So he’s not explicitly pro-monster; he just knows some big moment is coming and gets excited to see how it all plays out. The fact that it occasionally comes across as being happy we’re about to die? Pure coincidence.

Emotional Me? Full disclosure – Emotional Me sometimes wants to reach through the screen and strangle him. Every time he says “you’re not going to like this” with a gleeful twinkle in his voice (usually right before a crit) I lose a few millimeters of enamel grinding my teeth waiting for him to get it over with. Basically, I turn into Arnold in Predator: “JUST DOOOOO EEET! I’M RIGHT HEAAAAAH!”.

To summarize: most of the time, I recognize that Steve’s not bad, he’s just drawn that way. But sometimes, in the moment, I forget. We’re only human. Or ysoki, in this case.

So anyway… on to the game action. Dogfights. Last week, it was a Snoopy vs. Red Baron space-combat dogfight; this week, it’s actually fighting against space dogs. DO YOU EVEN WORDPLAY, BRO?

Big picture, it’s nice to see some actual monsters. Up until this point, we’ve been dealing mostly with humanoid types, so there’s been a little bit of a nagging feeling that we haven’t been squeezing every last drop out of the sci-fi setting. The undead guys pushed the envelope a little, but space dogs that hibernate in cocoons and then come out to feed? Now THAT’S what I’m talkin’ about.

I’ll also admit it’s nice to get back to the concept of a “dungeon” crawl, which is what this sweep-the-ship mission is shaping up as. Mixing it up with the gangs and investigating the murder was fun, but there’s nothing like exploring a labyrinth room-by-room, kicking asses and claiming treasure.

And yes, it dawns on me that those are two almost completely contradictory sentiments – on the one hand, I want more of the unknown regarding what we’re fighting; on the other hand, I want the familiarity regarding the general structure of the mission. Don’t ask me to explain it rationally — I’m not sure I can.

Anyhow… the good news? Well, the space puppies don’t seem to have any sort of ranged attacks, so selfishly, it’s mostly a matter of keeping Mo or CHDRR between Tuttle and the dogs. And definitely put me down as pro-“creatures whose husks are a form of currency”. I tip my cap to you, Paizo.

The bad news: they’re resistant to fire, so my gun isn’t much good, and space rabies. Yeah, yeah, I know… “void death”… it’s SPACE RABIES, dammit! I REALLY don’t want to have to get in there and mix it up with the knife – aside from the damage itself, to borrow from Austin Powers, fortitude saves aren’t my bag, baby.

The fight doesn’t go too badly, but it’s a little unnerving that Mo seems like the only one able to score major damage against them. I’m not sure how it’s going to go if we run into more of them at a time – picking them off one or two at a time seems tolerable, but “packs of 3 to 11” gives me a little shiver down the spine.

Grenades seem like they’d be the great equalizer in this sort of fight, but they only do 1d6 of damage, and if they’re strength-based, that’s going to be kind of rough for everyone except Mo.

And that doesn’t even count for the disease – if we start failing some fort saves, we could find ourselves in a mess pretty quick. I’m not sure which is scarier – the disease itself or the lack of tools to deal with it. I know they de-emphasized the role of a dedicated healer, but disease seems like one of the few places where it would still be nice to have one.

At least we now have some sense of what happened on board the ship. I assume the space dogs killed the crew, or maybe there are survivors locked in some other part of the ship that we have yet to discover. The fact that controls are locked out on the bridge makes it feel like maybe someone was waiting to be rescued, but I guess we’ll just have to work our way to the bridge and find out. Though that still doesn’t explain how the dogs got on board. Accident? Did someone smuggle them on board to scuttle the mission?

So there’s our marching orders for next time – continue to work our way to the bridge, try and find further signs of what happened, maybe look for survivors. I assume while doing all of that, we’ll also come across Gevalarsk Nor’s cargo and more detailed information about the Drift Rock in the process. We still have a job to do, after all.

As usual, feel free to drop us a line and let us know your thoughts. Are you looking forward to getting your first disease?  (Boy, let me find another way to phrase that….) Do you have a GM who’s a little too pro-monster for your liking? Give us a holler and join the conversation!

Help Roll For Combat Name Their Skittermander!

roll-for-combat-skittermander

The guys at Roll For Combat are about to start playing some Starfinder Society and we managed to get our hands on a Skittermander boon (listen to future shows to learn how you can get a Skittermander SFS of your own!). We need your help in naming our Skittermander character.

Check him out! Isn’t he cute! Wouldn’t you like to hear a rough voice of one of our regulars playing a cute little Skittermander?

If you have an idea for a name for our Skittermander, please send your Skittermander name to:
contact@rollforcombat.com
. You can also enter your Skittermander name here as well. If you name is chosen, we’ll send you a custom Roll For Combat t-shirt and use your name on the show! Good luck!

012: Who Let the Dogs Out?

Akata Battle

The team boards the Arceon and gets a rude welcome from the new inhabitants, a pack of what can loosely be described as space dogs. Rusty’s ability to stay out of the thick of the fight finally runs out, and the team has their first encounter with Starfinder’s new disease system. That’s right… space rabies!

Plus this week we announce the start of a brand new contest! And don’t forget to become a supporter of the podcast at our Patreon page: https://www.patreon.com/rollforcombat where you can help us while unlocking fun exclusive rewards for yourself!

Talking Combat 011: The First Starfighter

roll-for-combat-starfinder-starship-combat

Jason recaps the events from Roll For Combat, Episode 011: Spaceship!

I’ll start, as usual, by adding a few comments to Steve’s GM tips, regarding how far one should “dumb down” powerful bad guys. When you combine an enemy, who is a lot higher level and hits a lot harder with the perfect information the GM has access to… yeah, sometimes it can feel a little unfair. And up to a point, that’s part of the challenge – beating those long-ish odds is how you get that sense of accomplishment; that’s where that story you’re still remembering months later comes from. But sometimes, the party just doesn’t have the right mix of skills or something gets missed along the way to that pivotal encounter, and asking players to charge into a slaughter because that’s what’s on the page doesn’t make sense either.

As a player, I guess what I look for is one of two things: either give me an honest chance to win the fight, or offer me an “out” – either find a way to drop a hint before the battle that this is going to go badly, or maybe offer a window during the fight where the bad guy lets up and gives the party a chance to run. If I ignore the hint and get killed… that’s on me for being stupid. But if I walk into a buzzsaw encounter with NO indication and no way to get out of it, that doesn’t just kill the game currently being played, but it can feel arbitrary and sour the player-GM relationship overall.

The fight Steve mentioned in Carrion Crown was a slightly different problem insofar as it reached a boring stalemate. We couldn’t beat the guy because he could phase into the wall and even when he was in the open, we didn’t have enough tools to hit incorporeal creatures consistently (I think we had access to Ghostbane Dirge, but at one round per level, it just wasn’t enough). On the other hand, the bad guy couldn’t finish us because he ultimately couldn’t leave the room he was in, and all we had to do was run back down a hall and rest up. To frame it terms of my model – Steve DID give us the out, but then instead of trying something new, we kept coming back and trying the same basic thing (with a few small variations) a few times in a row. So I actually put that on us as the players, but Chris did not see it that way at the time.

So… spaceship combat.

Maybe I’ve been guilty of overselling it a little, but I have to admit I’ve been looking forward to this because, more than anything, this is what’s new about Starfinder. I mean, yes, some of the various D&D editions have rules sketched out for vehicle combat, but they tended not to get used too often because, for the most part, vehicles tended to be too far outside the fantasy box.

Yet, while it’s new, there’s also something classic about it too. While we were playing this session I had flashbacks to some of the old Avalon Hill wargames my brother and I used to play – Bismarck leaps to mind as one I played a lot – as well as games like Car Wars and Ogre. Similarly, some of the older naval combat games I played on the PC… The Ancient Art of War At Sea, Sid Meyer’s Pirates, and so on. Yeah, it’s space instead of water, and there’s not nearly as much emphasis on setting up a perfect broadside (at least until Steve gives us the keys to Galactica), but it felt familiar in that way.

What didn’t feel familiar? Being excited about going second. It’s a weird sensation. There, I said it.

Since Day One, there was never really any doubt Tuttle was going to be the engineer/science officer, so I studied those rules pretty carefully. “Science Rat” was the character concept; might as well lean into it all the way. My initial read was that the Science Officer is the more useful position early in fights, and Engineer becomes more useful later once you start taking damage. I think that’s still basically accurate, with a few minor revisions, as well as just learning to play it smarter.

I do think Engineer remains mostly a role to shift into once the fight has started to develop. Two of the three skills (Patch and Hold It Together) revolve around mitigating critical damage, which… if you don’t have any damage to fix, you’re standing around with your thumb up your butt. But in fairness, the third skill (Divert) is pretty evergreen – among other things, you can use it to increase speed (engines), regenerate shields (shields… duh) or change 1s to 2s on damage rolls (weapons). And you get to scream CANNA GIVE YE ANYMORE, CAP’N!, which never gets old. Or maybe it will. I plan to find out at some point.

The science skills? Scan is pretty much an opener for a round or two and then you probably never use it again. It’s good to get some initial information about speed, hit points, weapons, etc. but it’s the definition of diminishing returns. If you’re scanning the contents of the cargo hold while people are shooting at you, you’re doing it wrong. (Tuttle had to get four doctorates to get that nugget of knowledge and you’re getting it for free. You’re welcome.) Balance Shields – basically equalizes the remaining shield points between all four quadrants — seems like it could be more useful on a more powerful ship; on the Hippo, where we’re only shuffling 5 points of shields per quadrant around? Not so much.

To satisfy my curiosity (and maybe yours), I took a look ahead at the advanced skills to see how they change the dynamic. Basically, each role gets new unlocks at 6 and 12 ranks in the core skill (Computers and Engineering). But they also cost a Resolve point, which the basic skills don’t.

For science officer: 6 ranks of Computers gets you Lock On, the reward being a blanket +2 to any gunners that turn; 12 gives you Improved Countermeasures, which gives a chance to force the enemy to roll twice and take the lower roll on gunnery checks.

For engineer: 6 gets you Overpower, which is a Divert you can apply to three systems at the same time, and 12 gets you Quick Fix, which removes ALL critical damage to a system for one hour.

Anyway, back to the action. I do think one “mistake” I made was that I should have been using the Science Officer ability Target System a lot more aggressively. Refresher: Target System increases the crit range from natural 20 to 19-20, but (more importantly) lets you choose the critted system, rather than rolling at random. Wasting two crits on the bad guy’s sensors was a tough way to learn the lesson, but I think hitting his engines to slow him down or weakening his weapons would’ve been far more worthwhile than those few rounds Tuttle jumped on a gun in the mid-fight. Especially since it was a front-facing gun, we could only fire if we won initiative.

I also probably should’ve read the rules on gunnery a little closer. I didn’t realize it took RANKS of Piloting, so I didn’t think to take a level of Piloting at Level 2. I have to think about whether that impacts my character build going forward – on one hand, it might be worth pushing more into Piloting to keep up as a gunner; on the other hand, it wouldn’t go up THAT much faster than Base Attack Bonus, so maybe it’s not an urgent need compared to other skills I could be taking.

So anyway… we won, and at a broad-strokes level, I don’t really feel like we were ever really in that much danger in that encounter – I assume that was by design, since this is going to be a lot of players’ first exposure to ship combat, but it felt like a “get your feet wet” encounter where things were meant to be stacked in the party’s favor. Yeah, the other ship was faster than us, and that was a little annoying, but it didn’t hit very hard, and the Hippo’s 360-degree turret kept us in the fight every round. It really felt like he would’ve had to hit a LOT of lucky rolls to put us in any real danger. Still, even lacking much real danger, it was still fun, and I look forward to the next time we get to do it.

Next up: quarantined derelict spaceship where one of the airlocks was open to space. There can’t possibly be anything bad aboard, right? (Let’s be honest… we all grew up with Alien as a formative experience… I’m waiting for the arrival of face-huggers until proven otherwise.)

Anyhow, that was our first taste of space combat. I hope it wasn’t too hard to follow and you guys found it interesting. Feel free to drop us a line with any questions or comments, and we’ll see you next week on board the Nostromo… err… Arceon.

011: Spaceship!

Starfinder Space Combat

The boys board the Hippocampus and leave the safety of Absalom Station for open space. At first, the biggest danger confronting the team is Rusty’s heavy-handed leadership style might cause a mutiny. But then, actual danger appears in the form of a one-man enemy fighter. Lock phasers on target, charge techno-babble emitters – it’s time to kick the tires on Starfinder’s spaceship combat!

Join the Roll For Combat crew as they stumble their way through life and death with a Starfinder starship combat tutorial. Will they live, die, or will Rusty get thrown out an airlock? Find out this week!

Plus, this is the week we announce the grand prize winners for the $1000 “Big Podcast Launch Giveaway”! Listen to find out if you won… and even if you didn’t we’ll have a brand new contest starting next week! And don’t forget to become a supporter of the podcast at our Patreon page: https://www.patreon.com/rollforcombat where you can help us while unlocking fun exclusive rewards for yourself!