Turn 3 begins with JHI in a bad spot – they’ve lost one ship and the Broadsword is damaged. They’re outnumbered on the Cyclops. Vandar ships have maneuvered or jumped into their hexes – and to make things worse, those ships stand ready to unleash their attacks, whereas the JHI ships are pretty much obligated to play a Crew action at some point if they’re going to get people on the Cyclops. JHI has the initiative chip.
The Raptor (just off-picture) is in the same hex as the Pike, and the Broadsword is in the same hex as the Firebird up north (note again the use of stacked vector tokens recording actual ship positions.)
Nathan briefly discusses an idea he’s considering – he could play a Jump card on the Cyclops. He’s got the ship’s reactor occupied and fully repaired. If JHI doesn’t play Crew actions as their first card, Vandar would be able to Jump the Cyclops out of their boarding range. The cost of doing so would be twofold – he would play one less crew action on the ship this turn and possibly suffer in the boarding action as a result, but perhaps even worse he would put a Field Disruption card on a ship in the middle of a firefight.
Mark’s got a decision point here too – he didn’t manage to adjust the Broadsword’s drift enough to get it adjacent to the Cyclops, but he’s close. He can board it from this distance, but it’s long range for an assault lance so he’d be rolling d20s for accuracy dice. He could play a Thrust card to move first and get adjacent, and he’d really like to move two hexes if he could (so he wouldn’t end up in the same space as the Dragon with its nasty Disruptor), but he’s down an engine – he can only get into the Dragon’s hex on that one engine, and the Firebird still gets his rear armor if he does that. I missed it during the game, but looking at the situation now, Nathan has even better positioning for his ships than I realized at the time. Plus he’s just heard Nathan’s plan to Jump the ship – getting adjacent on the first card will do Mark no good if the Cyclops isn’t there on the second card.
Cards are down – let’s do it.
Nathan’s choice for his ships is predictable, but effective – they all attack.
Mark feels the time pressure and plays his Crew cards first – fine for the Pike, a difficult choice for the Broadsword.
And on the Cyclops, Nathan elects to secure the ship rather than risk a field disruption card – the threat of jumping was enough to force Mark’s hand without actually carrying it out.
We have a bunch of attacks followed by crew actions, and nothing else!
The previously undamaged Pike faces Disruptor fire from both the Raptor and the Dragon.
The Raptor’s shot – 2 points with the Effect die is a Fire, and it hits component 1 and 4!
Burn baby burn! The marine and spacer in those components disrupt.
The follow up from the Dragon’s Disruptor scores 3 points and a special effect – a hull breach, the worst damage type in the game. Component 5 is hit.
A hull breach doesn’t disrupt crew – it kills them. The marine in the starboard engine dies.
Hull breaches are next to impossible to repair (you need 5 points on a repair roll to change it to Destroyed), and when you get one there’s a chance the whole ship is destroyed – you make a ship destruction roll with a number of impact dice equal to the hull breaches on the ship (in this case, one). If you beat the ship’s hull integrity, the ship is destroyed and removed from the game. The Pike’s hull integrity is one, so Nathan would have to roll 2 points on one die – and he rolls none. The Pike survives for now.
For comparison, the Raptor has a hull integrity of 0 – a single hull breach has a 50% chance of destroying the ship.
The Firebird’s attack causes Heavy Damage to the Broadsword’s other shield, and the attacks are concluded.
Mark’s ships have taken a severe beating.
Time for crew actions.
Mark’s Battlesuits are pretty much cornered on the Cyclops – Nathan has a chance to get both of them by charging all three crew from components 7 and 8 into a favorable melee in component 9, followed by a shot into component 12 if he wins the melee.
I ask Nathan if he’s going to seize the initiative.
“Really? Why not?”
“Because he’s about to get more boarders on from his other two ships – I want to wait and see where they land so I can react to them.”
That makes sense to me – having the initiative worked against Nathan earlier in the game when Mark first boarded the ship and he doesn’t want to repeat that experience.
Nathan leaves the initiative in Mark’s possession, and Mark’s crew cards execute first.
First, the difficult case of the Broadsword. Mark decides that the time has come to use the Forged in Battle card he drew, ‘Their Finest Hour’. I was expecting this card to be used on the Cyclops as it can cause a huge swing in the battle, but the space battle has resulted in enough disrupted crew on Mark’s other ships that he felt forced to use it now. The entire Broadsword crew rallies (four were currently disrupted), and he draws a Hero.
A gunnery-themed hero will help if Mark can get some attacks of his own going.
Rallied crew and the Hero figure (white base) that was added to the Broadsword. Mark didn’t bother sticking them in components because he’s sending nearly all of the into a boarding action.
But what shall Mark do with his boarding action? He has quite the choice here… he’s two hexes away from the Cyclops which means he’ll roll d20s for accuracy dice, and the Cyclops is the main scenario objective, but it’s not the only way to win the scenario – victory is determined by whoever controls the most ships in the end, with the Cyclops counting for two ships. The Broadsword is directly adjacent to both the Dragon and the Firebird…
Nathan sent not only the entire Prize crew, but a few of his ship’s ‘standard’ crew complement to secure the Cyclops. These ships are a bit thin on crew as a result…
Mark makes a choice that takes Nathan by surprise. He makes a boarding attempt on the Firebird, sending 6 crew and leaving just one back on the Broadsword (it’s a good idea to leave someone back on a ship when boarding – boarding crew with assault lances disrupt when you miss the target ship, and you want to leave someone they can rally to, otherwise they will surrender.)
The spacers all make it! Two wind up in the starboard engine, and one lands in the port engine.
The special crew on the other hand does not – the Marine, Engineer, and our recently revealed Hero all miss and are disrupted.
Mark loses the melee and disrupts one spacer, but he’s got two more on board to continue his assault! Mark’s crew on this ship are given a set of repeated crew actions – and Nathan has to live with whatever cards he’s played this turn.
Not bad, but Mark did have to give up an opportunity to get more crew on the Cyclops to pull this off.
When you have multiple actions of the same type, you choose the order – Mark will be boarding with the Pike next with its crew action, followed by his crew action on the Cyclops, so members of the Pike’s crew that get on board will be able to also activate as part of the Cyclops’ crew action.
The Pike’s rally roll is unimpressive and it’s only able to send two crew for the boarding action – one of the still-disrupted crew on the Pike dies. Both crewmen get dumped into highly unfavorable melees (one die vs two dice with a bonus). Mark is disrupted as expected in the melee in component 3….
But here’s the roll for the melee in component 6! Mark’s die is on the left, Nathan’s are on the right. Nathan gets a +1 bonus but it’s not enough! Mark’s 2 beat’s Nathan’s 1, and the losing side is disrupted – Mark gets a badly needed miracle!
Both battlesuits in component 6 disrupt, and as the Pike’s boarding action concludes, things suddenly look very different on the Cyclops – Mark rallies an Engineer as his crew action begins here.
Mark charges the Battlesuit and Engineer bravely into a single Marine and wins the melee.
Stop and have a look at the situation, because all of us at the table did. Mark’s little miracle where his spacer managed to surprise and defeat Nathan’s battlesuits has unhinged the relative safety of Nathan’s position as we enter shooting, and all of a sudden, despite everything that has happened so far, Mark has a chance to disrupt every one of Nathan’s remaining crew during shooting (One shot from component 8 to 5 is a given for a single disruption from the Battlesuit bonus, one shot from 9 to 7 will need to roll a single point plus the battlesuit bonus to disrupt both crew in the medbay, and the longshot is a single die from component 6 to 3, which would need to throw 2 points all by itself to disrupt both crew.) It’s not a great chance, but if he pulls it off then Nathan’s crew won’t have any active friendly crew to rally to and they will all surrender during the drift phase.
The bottom line is that with the right die rolls, Mark could take the ship right here and now.
I turned to Nathan.
“Do you regret not seizing the initiative?”
“Yes. Yes I do.”
But Mark’s dice? They crap out again. Nathan is down to 3 active crew, but is still able to fight for the ship.
Time for Nathan’s crew action – he wants those Battlesuits back but he botches the rally roll and gets nothing. He chooses one of his disrupted spacers for death.
He declines to go into melee, instead moving just the engineer in component 3 so he can get an additional die on a shot into component 6. The Engineer in component 7 has several options – he can help shoot into component 6 and make sure of the spacer, or he could shoot into component 9 and see if he can disrupt the battlesuit. Nathan chooses a third option…
Two dice turns out to be enough to disrupt the spacer in 6, and knowing that he can seize the initiative next turn and aware of how badly he needs to rally his crew, Nathan has the Engineer try to repair the medbay instead of shooting – no points on the die, but the bonus is enough to get it down to light damage – use at your own risk.
A repeated crew card for the Broadsword and a Thrust for the Pike – played before its engines were rendered inoperable, the Pike won’t be doing anything with that card.
Thrusts for the Firebird and Dragon – a costly card for the Firebird now that it’s been boarded (tip – if you think you’re likely to be boarded, a crew card of your own is the defensive play). The Raptor has been sporting some damage and Nathan thinks that it’s time to repair it – he fired a damaged Disruptor last card and may have been anticipating worse damage as a result, but he got off easy. The Cyclops and the battle raging on board is all crew all the time.
Crew actions are up first and Nathan immediately seizes the initiative this time.
The Raptor repairs its Vibration Disruptor with its crew action. On to the Cyclops!
I probably wouldn’t have done what Nathan does here – too risky. Nathan operates the damaged medbay to get a bonus on the rally roll. It pays off – 2 points on the dice plus the bonus rallies 3 crew – two battlesuits and a marine (and another spacer bites it). That part is all well and good (it’s easily worth risking the engineer for a guaranteed battlesuit), but when it comes to placing his rallied troops…
Nathan shows he has some big brass ones by placing one of his battlesuits right into the damaged medbay he just used and is about to roll damage on. If he gets 2 or more points on the impact dice, both crew will disrupt (or even die if he rolls a hull breach – unlikely, but possible.)
Just one point – Light damage, and only disrupt 1 crew! The bastard gets away with it – the engineer disrupts and the Battlesuit remains.
He charges in for an even melee.
He wins, and shoots into the component with Mark’s last active crew…
And scores in a big way – the single impact die is a 2, battlesuit bonus makes it a 3 – the component is destroyed and both Mark’s crew disrupt. If Mark doesn’t get any additional crew on this ship by the Drift phase, his crew will surrender and that’ll be all she wrote for this scenario.
Time for Mark’s crew action on the Broadsword. He has one active and two disrupted crew, but the Rally dice are kind and he rallies both disrupted crew, and sends them over. Despite rolling d20s, he lands them both – one on 3, and one on 12.
Mark’s marine lands on Nathan’s Marine. Mark loses the melee…
… and to make matters worse, he gets nothing on the Rally roll. (Remember that Forged in Battle card, ‘Their finest hour’? That would be really handy right about now…) None of his crew return to active status, and a spacer dies. The Engineer takes a shot at the Battlesuit and fails that too – but Mark still managed to get one active team on board. He’s hanging by a thread, but he’s still in this.
Meanwhile, on the Firebird….
Crew action begins!
Mark takes Nathan’s crew by surprise and captures the ship!
There are three Thrust actions played now, but only one actually works – the Pike has one but both its engines are inoperable. The Firebird has one but Nathan’s crew are all disrupted and thus also cannot operate the engines. Only the Dragon gets to use the thrust action played this round.
The Dragon maneuvers, slowing itself down and turning to face the Broadsword and the suddenly hostile Firebird.
The last card of the turn is a story of plans gone awry. The Pike and the Firebird have attacks that fail for the same reasons their last Thrust did, and the Raptor attack misses. The Broadsword has yet another crew action, but before it goes off the Dragon’s attack results in a Fire in the Broadsword’s last component with Active crew – she surrenders in the Drift phase. Mark’s boarders on the Firebird still have a crew action played in their automatic set, and use it to repair the power downs they caused. As for the Cyclops…
Mark seizes the initiative, rallies a battlesuit and a marine and charges them into Nathan’s battlesuit, winning the melee. Mark shoots into the empty medbay to try and deny its use to Nathan and gives it a power down.
Nathan counters by rallying the Battlesuit, moving several crew up and firing back, disrupting just Mark’s marine.
After Drift. We removed the surrendered Broadsword after this shot.
Also, the Pike has fires – during drift we check to see if the fire spreads or causes an explosion.
The Pike has fires in component 1 and 4.
Fire spreads checks are easy – you roll 2d20 accuracy dice. If you hit a component adjacent to a fire, the fire spreads there. If you hit a fire directly, there’s an explosion – you roll damage and that damage affects both the component on fire and all adjacent components. In this case, the ‘8’ is a miss, and the ‘5’ would spread the fire to the Engine, except that it’s already got a more severe damage type than Fire, so it just keeps its hull breach instead.
Initial positions for turn 4.
For once Nathan isn’t well position at the start of the turn – the Dragon only has its Vibration Disruptor in arc and range of the Firebird. The Raptor has drifted out of range (It could shoot the Cyclops in the front but its autocannon is too weak to hurt the front armor – Power 2 vs. Defense 6 doesn’t even match half the defense, so it can’t hurt the Cyclops at all), and while the Pike could turn and fire it’s engines and weapon are inoperable. Only the Firebird is positioned to fire all its weapons – one can hit the Cyclops, the other can hit the Dragon.
Mark’s major card decision for the turn concerns the Firebird – he desperately wants to start shooting the Cyclops to try and hurt Nathan’s crew there and give his last few crew in the fight a chance, but he only repaired the one weapon in arc to light damage – he could blaze away and risk the damage (and the two crew in the component), or try to spend the time to fix it with a crew card before shooting it. He’s also got a pretty good shot on the Dragon right now that Nathan may not give him if he waits a card to start firing.
The Pike’s cards are easy – it’s drifted away from the fight and it’s useless without engines or a weapon, so it’s a damage control turn – all crew actions will hopefully get the fires out.
Nathan will be trying to finish off Mark’s crew on the Cyclops.
The Dragon has a classic problem in Silent Fury – he does have the Firebird in his (generous) weapon arcs so he could attack now, but he’s got his weaker armor exposed. Depending on the situation sometimes you can play a Defenses card to reconfigure your shields and take care of the problem, but the Dragon only has 2 armor on the side – shifting the Dragon’s single shield for 3 defense won’t be any better than defense 2 against the Firebird’s power 3 weapons. So he choice comes down to either attacking now, or throw down a Thrust card, take the first attack in the side, and then rotate the better front armor to face the enemy.
The Dragon doesn’t have a reactor, so it can’t jump, which would be another option in this situation.
Aboard the Cyclops, Mark is still just hanging on by a thread, and he’s practically out of crew he can reinforce with.
We’ve transferred the Firebird’s sheet over to Mark’s side of the table. Mark decides to repair that light damage rather than just start blazing away – he can’t afford to lose two more crew at this point!
Since the Raptor isn’t in the fight this turn Nathan takes the opportunity to see about fixing its remaining damage. The Dragon will rotate to get its front defenses facing the Firebird.
Pretty simple turn – the Raptor and the Firebird both repaired their light damage, and the Pike rallied its one disrupted crew (there are only 2 left) and sent them both in to repair the Fire, but failed to roll the 2 points necessary to do so. Skipping ahead of the Cyclops for the moment, the Dragon again took advantage of it’s ability to thrust backwards and moved back one hex, turning its front against the Firebird.
Aboard the Cyclops:
Mark elects not to seize the initiative – he’s wary of giving Nathan more ‘double actions’, so he leaves the Initiative alone and allows Nathan to go first. Nathan flanks Mark’s battlesuit with his own. Disruption is guaranteed, but the dice have other plans….
Can you say overkill? The shot scores three points and the effect die comes up – hull breach! Mark’s battlesuit is fragged. The Cyclops has a Hull Integrity of 3 and thus can’t be destroyed from a single-die ship destruction roll, so we skip it.
That hull breach creates a serious tactical problem for Mark – not only does it kill crew when placed, it also kills crew which are disrupted inside one – it’s not a place Mark wants to have his crew in, so he just rallies and spreads out.
Second card! The Firebird and the Dragon attack each other but both fail to do damage (and Mark is getting frayed – after declining to seize the initiative for the crew action and costing himself a battlesuit, he then feared the Dragon would stop the Firebird’s attack so he seized the initiative at this point, thus fatally granting Nathan the chance to grab the initiative again for the next crew action) – the Firebird also shoots the Cyclops and succeeds in disrupting one of Nathan’s crew.
Nathan’s battlesuits move in for the kill.
Mark is cornered in the back of the ship and it’s not even a contest – the shooting bonus from the battlesuits auto-disrupts his remaining crew.
Mark threw in the towel at this point – there was no way he was going to be able to fight for control of the Cyclops now and his only functioning ship was the captured Firebird.
The death / captured toll at the end of the game tells the tale – this was a one sided fight. Mark’s hero didn’t end up being very heroic – during one of the Broadsword’s rally rolls Mark ended up having to decide to lose either the gunnery hero or an engineer, and he decided he needed the repairs more than he needed to shoot well.
Final ship positions.
Nathan nicely showed his skill as a player (he is at least the second best Silent Fury player in the world for the time being). He played to the strengths of his powerful, short range weapons and he got his crew on the Cyclops very quickly, which freed up all of his ships to attack Mark’s vessels as they attempted to drop their crews a turn later. The Raptor’s spoiling attack worked better than he had any right to hope for, getting its Vibration Disruptor in the same hex as two JHI ships in two turns was brutal, particularly for the Pike.
I think Mark had the unfortunate trifecta of a rough game – he was both out-rolled and out-played by a more experienced player, but as we discussed the aftermath of the scenario we also decided that the way in which I’d written the scenario and designed the ships likely favored the Vandar as well, putting another nail in Mark’s coffin. Despite all that we did see one tantalizing chance of victory appear for him, a hope the dice were quick to squash, and his little boarding surprise that captured the Firebird was a joy to beohold.
In terms of scenario imbalance, I think these all played their part in hurting Mark’s chances:
First, the scenario gives the initiative chip to the JHI (thematically they are just going to recover their own ship when the Vandar jump them), so Vandar has first opportunity to seize it at a time of their choosing. This greatly aided Nathan’s spoiling attack.
Second, Vandar sets up their ships after JHI. This let Nathan set up the spoiling attack in the first place, whereas JHI doesn’t get an equivalent opportunity to try to pull off something like that themselves.
Third, the JHI ships’ strength is in a head-to-head ranged battle – they have better defenses and weapon power than Vandar does, so they should be able to beat them in a straight-up shooting match if they can keep from getting outmaneuvered. In this scenario however, both sides need to get close to the Cyclops, which in turn means they have to get really close to each other – basically forcing JHI to come into Disruptor range, even without a spoiling attack.
So based on those I’m going to make some changes to the scenario and ships – Vandar can have the initiative chip to start. I don’t know exactly what I’ll do with setup yet, but it won’t be one side first, other side second – perhaps I’ll stagger it so both sides alternate setting up ships with prize crew first, then add in any ships without prize crew second.
As for the JHI being forced to close range issue, I don’t want to re-jigger things too much just because the tactical situation is unpleasant for JHI ships – Nathan and I discussed it and we think we can kill two birds with one stone. Vandar has a nice mix of longer range lasers and those short-range disruptors that compliments their maneuverability nicely, and they feel pretty good to play as a result – you can either use your better ranged lasers to try and poke at your enemy’s weak sides from a distance, or you can do what Nathan did and make close-range disruptor passes.
JHI is pretty much cannons all day every day, without much of an interesting secondary option – so we’re going to try giving the Broadsword’s scatter cannon the ‘Area 1’ special, which means that it’ll pick a hex to attack instead of a ship, and every ship in or adjacent to that hex will suffer that same attack. In the game above, this would have meant that the Broadsword could have simultaneously attacked the Dragon, the Firebird, AND the Cyclops (and the troops just deposited on it) on turn 2 – and with repeated attacks it could do so more than once. That won’t make the approach to the Cyclops any less scary for JHI against Vandar disruptors, but it makes it far scarier for Vandar, so now both sides face an unpleasant tactical situation. Thematically we’re now thinking of making JHI a ‘Cannons and Area Effect’ weapons faction, especially since the Terminus in Nemesis Day already sports its own extremely nasty area effect weapons.
Oh, and those stupid aliens that did practically nothing – they’re meant to be at least an inconvenience for the first side to board the ship. I put them in there to give the late-boarding side a little breathing room (the big version of this scenario is our first convention game for Fall In, and we can’t expect new players to be making masterful plays their first game so I don’t want the one smart cookie from Vandar to get on the Cyclops and just fly or jump it out before the other side figures out this inertia thing enough to land their own troops). I’m going to try having the aliens roll two dice in melee (still with a bonus), and perhaps add a third alien – they’ll still be gone pretty quickly no matter how nasty I make their offense since they still die on disruption, but I need to strike a balance so they’re not so nasty that nobody wants to be the first ones on the ship (of course at our convention game, we’re not going to tell our players about the aliens in advance – they’ll be an exciting mid-turn discovery).
If you’ve read all this, thank you and I hope you enjoyed it! We’ve got some exciting things around the bend and we’re hoping to bring the most impressive-looking version of the game we’ve ever done to Fall In this year, hopefully I’ll be posting pictures of some new ships and a grand space map soon.