Continued from part 1.
Turn 1
Orders Phase
For the Orders phase, Nathan and Mark play three cards from each ship’s action hand onto each ship. We’ll see what cards they played in a moment. These action hands consist of seven cards – five of them are different actions (Defenses, Attack, Crew, Jump, and Thrust), and two of them are Repeat cards (Repeat slot 1 and Repeat slot 2). The repeat cards let you effectively play the same action twice, or even three times in a turn.
Many space combat games employ a system of phases where all ships move, then all ships fire, then all ships maybe perform damage control and so on. Silent Fury is different – a ship might do nothing but fire its weapons several times over the course of a turn, or it might not fire at all, instead focusing on its defenses, and with only three card slots no ship will perform every action on every turn.
Thematically, these cards are also Silent Fury’s power allocation rules. Rather than have a separate mechanic where you’d allocate more or less power to various ship systems, the cards handle everything – a ship that plays three ‘thrust’ actions is basically routing all power to its engines, and it will be able to adjust its velocity a good deal more than it would have with just one ‘thrust’ action, but it also won’t be firing any weapons this turn either.
The end result is that there are often more things that you would like to do with a ship than you are able to do, and you’ll have to decide what actions are most important for each ship on each turn.
All right – Nathan and Mark have played their cards, so the Orders phase is done. On to the Action Phase!
Action Phase
Both players flip the first card for every ship. One note – our cards are a version behind the rules and the new ones hadn’t arrived as of this playtest, so I’ll be posting the correct card images as we discuss them.
The number in the top-right of each card is its initiative number – lower cards execute first, so all of Mark’s defenses (Initiative 1) cards go before Nathan’s thrust (Initiative 5) cards.
Mark executes his Defenses cards now. Let’s have a look at that card:
When you execute an action card, you may choose ONE of the actions on it to execute. The defenses card has three actions, all designed to protect the ship – Evasive Maneuvers makes you harder to hit, Shields Up lets you raise or readjust your shields, and Harden Shields doubles your shield strength. To the right of each action there are reminders of the ship components that need to be operated to perform that action – on Evasive Maneuvers, you need to operate one engine, and if you can’t then you are unable to take that action.
Mark elects to take the ‘Shields Up’ action for each of his ships. This lets him place his shield cubes on whichever side of the ship’s armor hex he wants, and each shield cube adds 1 to the defense value of the hexside the shield is protecting. Let’s look at the Broadsword:

This arrangement changes the defense value of the front and front-left sides of the ship to ‘4’ instead of the base armor value of ‘3’. Mark could also have placed both cubes together and given one side a defense of ‘5’, but with the Raptor coming in from his left and Nathan’s other ships in the direction of the Cyclops, Mark decides to try and increase his protection from multiple angles.
Mark raises shields on all three of his ships and we move on to Nathan’s Thrust actions.

The curved arrow symbol means that Full Thrust is a ‘focused’ action. A focused action can only be taken once per turn – if Nathan were to repeat this Thrust card, he could Full Thrust on either this card or the Repeat card, but not both.
Nathan is taking the Full Thrust action with all three ships. Let’s look at the Dragon and the Firebird.

The initial position of the ships and their trailing vector tokens – Dragon is yellow, Firebird is red.
Dragon’s ship sheet for reference – note that the Dragon has three engines. Here’s the Dragon’s thrust chart:
Those numbers are the number of engines you need to operate to move your ship to that hex (so if the Dragon were to lose two engines and just had one left it could operate, it could only move into the hex directly in front of it). Nathan operates three engines and chooses the top-right ‘3’ hex. He moves takes the vector token underneath with the ship, and leaves the trailing vector token where it is.
The Firebird makes the same move – while it only has two engines, its thrust chart lets it move to the same hex on only two engines.
The thrust chart lets us customize how maneuverable a given ship is, and also let us solve a design problem we had, namely that bigger ships simply had more engine components. By making larger ships need to use more engines to move the same distance as a smaller ship with fewer engines, we can reflect the fact that the larger ship requires more power to change the velocity of its larger mass.
The Raptor moves closer to the enemy.
Nathan can Rotate his ships for free after a Thrust action but he’s happy with their facing and elects to not do so.
The first action card for every ship has been resolved. Time to flip the second card.

Nathan plays ‘repeat slot 1’ on every ship, thus repeating his Thrust card for each ship. He already took the focused ‘Full Thrust’ action on every ship this turn, so all of these actions will have to be ‘Maneuver’ actions.
‘Crew’ goes before ‘Thrust’ in initiative order, so Mark’s Crew card on the Pike resolves first. This is a strange card to play at this point – the Crew card lets you board other ships, rally disrupted crew and repair damage, but there are no ships in boarding range, and he has no disrupted crew to rally and no damage to repair. I ask Mark why he played the card and he said it was because he wasn’t planning to do anything with the ship on that card slot. Something Mark didn’t realize due to his lack of familiarity with the game is that you can always elect to take ‘no action’ instead of executing your played card, so you may as well always play something that could potentially be useful (a Thrust / repeat slot 2 combo would have served Mark better for his last two cards on the Pike).
So, on to the Thrust cards. These all go on the same initiative (5), and both sides have played them, so the tie is resolved by the Initiative chip. Since Mark has it, he will execute his thrusts first.
These ships could move farther, but Mark says he is wary of ‘going too fast in this game’ and doesn’t want to overshoot the Cyclops. This is an entirely reasonable concern – I’ve seen many newbies underestimate how much velocity their ships can build up and end up overshooting their objectives, and I did it plenty myself while developing the game. Even an experienced player like Nathan can fall victim to speed and circumstance – in our last playtest of Nemesis Day, one of his ships slammed into the planet when I sent a small raiding party on board and prevented him from using his reactor to save himself. In this scenario however, there is some level of urgency in getting to the Cyclops, and if Mark takes too long then Vandar may be able to board the ship and get her underway before JHI arrives.
Nathan now executes his Thrusts, which must now be maneuver actions since he took the focused ‘Full Thrust’ action with all his ships earlier. Maneuver lets you adjust your trailing vector token by 1 hex, which will affect where you drift.

Nathan moves the Dragon’s yellow token north 1 hex. He’s happy with the Firebird’s token and leaves it alone.

And the Raptor does something really unusual! Nathan leaves the trailing vector token alone, but then uses his rotate to turn the ship so it’s facing away from the Broadsword!
What is Nathan doing? The Raptor carries two weapons, a low-power autocannon with a max range of five hexes and a high-power disruptor with a max range of two – he was both in range and in the weapon arc to shoot the autocannon weapon at the Broadsword and he might have done damage, but it’s not a great shot due to being at long range and the Broadsword’s comparatively high defenses. Nathan could have played an attack card to fire his weapon, but he’s got other plans – this maneuver both takes that weapon out of arc and exposes the Raptor’s weaker armor to the Broadsword, but he’s taking a risk now to set something up for next turn.
All second cards executed, the players turn over the final card of turn 1.
Nathan’s Defense cards activate first. On the Dragon he uses it to raise his shields (he has all of one) and increases his front defense to 4. On the Raptor he takes Evasive Maneuvers – this means that all attacks that hit the ship are re-rolled, and on a size 4 ship that’s a very effective way to not be hit.
Next the Attack cards resolve, and since Mark still has the initiative his attacks resolve first. The Pike has a range 6 weapon and the nearest enemy ship is 10 hexes away, so the Pike is out of range. The Broadsword on the other hand…
Time to lock weapons and go through the attack rules!
The Attack card has two actions – you can either operate all your weapons (a focused action, so you can only do it once), or you can operate one weapon (which is repeatable, so you can do it every time you play or repeat the attack card). This is the only Attack card in Mark’s set so he will shoot all his weapons.
First we’ll check to see if the target (the Raptor) is in the weapon arc. The weapon arcs are those triangles printed directly on the weapon components – you can see the Scatter Cannon has a more generous arc than the Meteor cannon.
So we’re in arc for both weapons. Are we in range? Note there are two range numbers in the ‘RNG’ column separated by a slash – this is the weapon’s short / long range. If you are within short range, you get to roll d12s as your accuracy dice, making you more likely to hit. If you are at long range your accuracy dice are d20s.
The Raptor is 4 hexes away, so we’re at long range for the Meteor cannon – we’ll be rolling d20s. The accuracy value of the weapon is 2, so we’ll be rolling two of them.
Now we figure out the Impact dice by comparing the weapon’s power (POW) against the target’s defense. The weapon’s power is 4. To determine the target’s defense, we first need to figure out which side of the target is being attacked.

We draw a line from the attacker to the target and see which hex-side it crosses. In this case it goes across a hex spine – so the defender will get to choose which of those two sides is attacked.
In the Raptor’s case however, it doesn’t matter. Both the rear and the rear-right armor value is 1 and it has no shields to increase that value, so the target’s defense is 1.
Since the attack’s power of 4 is double (it’s more but doubling is the best you can do) the defense of 1, the attack will roll three black Impact dice. We’re using custom dice for this game but there are rules for using regular d6s and converting their rolls into 0, 1 or 2 points.
Finally, you need red Effect dice as well. The weapon chart has two pictured for the Meteor cannon, so we roll two.
Mark rolls all the dice for the attack together – 2d20 accuracy dice, three black Impact dice, and two red Effect dice.

The Raptor is a size 4 ship, so the d20 result of ‘4’ here would cause a hit. Since the Raptor is currently evading we would normally re-roll that hit, but the black Impact dice have scored 0 points, resulting in no damage, so there’s no need to re-roll – the attack does not harm the Raptor.
So that didn’t work, how about the Scatter cannon? It’s also in arc and in long range (it has no short range but its long range is also 6), it has 3 accuracy so we’ll roll 3d20 this time, it has power 4 vs. defense 1 so we get 3 Impact dice, and it rolls two Effect dice.

This time we get some damage on the Impact dice but no hits on the accuracy dice – we’re trying to hit a size 4 ship so we want a ‘4’ or less on the d20s. This attack misses.
That concludes the Broadsword’s attack and the Raptor survives unscathed.
One thing to note here is that Nathan played his cards well and had his Evasive Maneuvers go off at the same time as Mark’s Attack card, so even if that first attack had done damage, the re-roll likely would have caused it to miss anyway. Now, back in the Orders phase Mark played Defense, Thrust, Attack with the Broadsword, but he didn’t have to play those cards in that order – he could have played Thrust, Attack, Defense, and his Attack card would have gone off on Nathan’s ship while he was Maneuvering and thus would have been more likely to cause damage. In addition, he had an extra hex of Thrust available to him and could have gotten into short range with the Meteor cannon by using it, which would have let him roll d12s for the Meteor Cannon’s accuracy dice. He chose not to due to his concern about building up too much velocity.
Nathan’s Attack from the Firebird goes now, and it’s also out of range of enemy ships – he played it on the off chance that one of Mark’s ships jumped into range.
Finally, Mark’s ‘Crew’ action on the Stiletto goes – another ‘didn’t want to do anything with the ship’ play. As a newer player we did discuss the merits (or lack thereof) of these crew cards and I offered him a chance to change his cards, but he decided to soldier on and live with his mistakes. This one will cost him.
Drift Phase
You might have been wondering what those trailing vector tokens are for. We wanted ships to have inertia in the game and feature ‘objects in motion remain in motion’ newtonian movement, and those tokens effectively keep track of a ship’s velocity, including changes in velocity as you thrust and maneuver each ship.
During the drift phase we have a few ‘every turn’ maintenance tasks, such as maintaining shields – every ship can currently operate all their shield generators so no shield drop this turn.
Now ships drift according to their vector tokens. Here’s the Pike’s drift.

Position at start of drift phase – the Pike didn’t change its initial vector so it’s the slowest ship in the game at the moment. We start Drift by tracing a path from the trailing vector token to the ship – in this case a straight 2-hex path north-west.

We then ‘leap-frog’ the trailing vector token: Starting from the ship, trace the same path to a new hex (again, two hexes north-west for the Pike). Place the trailing vector token there.

Finally, move the ship miniature (and not the vector token that was underneath it) to the hex we just leap-frogged to. The token previously underneath the ship becomes the new trailing vector token. If the Pike were to not change its velocity again next turn, the drift would be exactly the same – two hexes north-west. Objects in motion remain in motion.
Note that the direction in which you drift is entirely dependent on where the vector tokens are located and completely independent of your ship’s current facing – even though the Raptor has turned to face north-west, it’s still drifting south.

This is what Nathan was setting up – the Raptor’s drift and the Stiletto’s drift carry them into the same hex.

An unintentional side-effect of the vector tokens was that it made it easier to handle ships in the same hex – we can stack the vector tokens on top of each other as the ‘true’ position of the ship, and put minis that otherwise wouldn’t fit nearby – I’ve shifted the Stiletto’s vector token so its more visible for the camera.
This is the price of Mark’s mistake with the crew card on the Stiletto earlier – had he instead played, for example, a repeated Thrust card, he could have maneuvered to slow down on the third action card of turn 1. The Raptor was busy evading and couldn’t have matched the maneuver – the Stiletto would have drifted into the hex south-east of its current position, completely out of the Raptor’s weapon arcs and poised to ream it in the rear as the Raptor slid in front of it. Now however, he’s in the same hex as a ship with a weapon specially made for same-hex attacks.

The Dragon and the Firebird’s drift also carry them into the same hex – and they’ve managed to put themselves adjacent to the Cyclops! Mark’s closest ships are still 4 hexes away. Note that we’ve now exposed the ‘marked’ vector tokens – this aids in determining which ships have drifted in a turn and which have not.
All ships have drifted and this concludes turn 1.
Turn 2
Orders Phase
I discuss the state of the game with the players. Nathan is feeling good at this point – he says his main target for the Raptor’s attack run was the Broadsword but he’ll happily settle for a great attack on the Stiletto, and his other ships are all set to board the Cyclops.
Mark on the other hand is very concerned – he’s worried about the Stiletto (he’s got both his Battlesuits on there and he’s going to need them in the Cyclops fight) and seems alarmed that Nathan’s ships are already able to board the Cyclops. He has to get on board too, and fast.
We spent a little time discussing Mark’s options for the Stiletto.
He could play an attack of his own and fight it out – the problem being that with Nathan able to seize the initiative, Nathan will attack first – plus Nathan has two weapons on his ship to Mark’s one, and Nathan can better afford the loss of the lightly crewed Raptor than Mark could afford losing all the crew he’s put on the Stiletto.
Sometimes you can Thrust out of a bad situation, but Nathan’s rotation on the approach made this a bad idea – the Raptor is facing the same way as the Stiletto and the Stiletto can only go forward, so he’d stay in the Raptor’s weapon arcs. Mark is also concerned with his overall velocity and if he does thrust now he will overshoot the Cyclops.
He could Jump, which would mean he’d have to take one action’s worth of fire from the Raptor along with putting a dangerous Field Disruption card on the ship, but after that he’d be out of the hex.
He could pull the Evade maneuver that Nathan did, but he’d still be in the same hex and it would be less reliable against repeated d12 accuracy attacks. Even so, one valid option would be to repeat evasions and dodge fire like crazy while the nearby Pike or Broadsword tries to shoot the Raptor. One major downside is that if he does nothing but evade, he won’t end up adjacent to the Cyclops – he’d have to risk at least a Maneuver attempt in there somewhere.
We also look at Mark’s other ships and discuss how he can get them to the Cyclops at the end of this turn’s drift. The Pike can do it with a simple thrust forward, the Broadsword’s trajectory on the other hand is taking it somewhat off course but it could still make it with a Maneuver / Full Thrust combination somewhere in its card set.

Nathan lays out his cards menacingly as Mark tries to figure out how to handle his unpleasant situation.
Action Phase
First card!

The Raptor’s action is a predictable attack. The other ships play Crew cards so they can board the Cyclops.
The Raptor’s attack resolves first (Had Mark played an attack with one of his other ships, Nathan later commented that he would have been hard pressed to Seize the Initiative here to make sure his attack struck first – he’s not evading this time, so allowing Mark’s attack to go first could knock out one of his weapons before he gets to use it, but since there’s no other attacks there’s no need to do so. The Broadsword’s weapons were out of arc at this point, but the Pike did have a long range shot).
The Raptor carries two weapons – an auto cannon with relatively low power and a high-powered, short-range disruptor. At a range of 0, both weapons are at short range.
When firing at a target in the same hex, things get nasty – for one, all weapon arcs include the hex you are in, so you get to fire everything you’ve got. For another, the attacker gets to choose which side of the ship he hits (thematically you’re close enough to target weaker areas of the ship). The Stiletto has better overall armor than the Raptor, but it’s direct rear armor is only 1, and that’s the side Nathan will attack. The Fenris Autocannon gets 3d12 accuracy dice, three impact dice (power 2 vs. defense 1), and two Effect dice. The Vibration Disruptor also gets 3d12 accuracy dice, three impact dice (power 6 vs. defense 1), and also sports a full three effect dice.

The autocannon craps out on the Impact dice – for your statistical reference half the sides are blank, so there’s a 1 in 8 chance of doing no damage on three dice – the average result is 2 points. Mark is lucky here – component ‘4’ is his reactor, and if he had taken damage there it would have either interfered with or completely prevented his Jump action.

The Vibration Disruptor scores a hit! The accuracy dice tell you if you hit AND where, so component 3 (the Stiletto’s engine) is hit. None of the Effect dice have a result so it’s a standard damage type – light, heavy, or destroyed. The Impact dice show one point so it’s light damage (2 would be heavy, 3+ would be destroyed).

Light damage is placed on component 3 of the Stiletto, it’s engine. There was a battlesuit occupying the component, and damage types that result from 1-point hits make you disrupt 1 crew in the component, so the battlesuit is placed in the Disrupted Crew box. If there had been another crew occupying the component Mark could have disrupted one of his choice.
Considering what could have happened, the Stiletto got off…. lightly.
Nathan’s crew cards resolve now and he boards the Cyclops with both ships. All the ships in this scenario have Assault Lances, with a short range of 1 hex and a long range of 2, so if you can get adjacent to a ship your boarders get to roll d12 accuracy dice rather than d20s at 2 hexes.
When you board another ship, you gather up all the crew you are boarding with (send as many as you like) and roll one accuracy die per crewman (you can split them into crew types and roll them in groups.) If you miss the crew are disrupted, but that won’t be an issue this time – since the Cyclops is a size 12 ship, you can’t miss at close range. As with weapon attacks, the accuracy die result corresponds to the component you land in.
But first, the scenario states that when the Cyclops is first boarded, a pair of feral aliens are revealed on board. I roll their position now.

Nathan boards the Cyclops with 3 spacers.

Nathan hasn’t landed anyone near the engines at all, which is unfortunate when the objective is to fly the ship off the map. He also didn’t land directly on an alien which would have produced an immediate melee.

This technically should have happened later in the turn (after card 1 resolved) but the result would have been the same – the aliens attack the humans!
Melee combat is resolved with the Impact dice – you get one die per crewman you have in the melee, and a Marine or a Battlesuit gives you a +1 to the roll result. The aliens are treated as marines in this scenario. I roll for the aliens since I’m not otherwise playing.
In component 6 I’m facing a marine and a spacer – I get one die and Nathan gets two. We both manage to roll 0 points, +1 each since we both have a ‘marine’, and the result is a tie. On a tie, you disrupt 1 crew from each side (and roll again if both sides are still around), so my alien and one of Nathan’s crew (he chooses the spacer) disrupt. A disrupted alien is killed, so that’s one down. In component 7 I’m against an engineer and a spacer – we get the same dice as last time, but Nathan won’t get the +1 bonus he got last time. It doesn’t matter though – I roll 0 points again and Nathan rolls 2 points, beating me 2-1 after my +1. If you lose a melee the entire losing side is disrupted (and in the alien’s case, killed). That’s all she wrote for the aliens…

One spacer disrupted? The aliens did a whole lot of nothing. Also, boarding crew get their own set of repeated crew cards, thus automatically entering the flow of the turn with crew actions of their own. On future turns Nathan will be able to play any set of cards he likes on the Cyclops.
Nathan has left a few crew back on his other ships to keep them in the action. You can technically run a whole ship with just one crew, but doing so makes you very vulnerable.
The Stiletto’s Jump is up next.
Jump has two actions – one lets you jump the ship and move it 3 hexes, and it also stops the ship (we found this was a newbie-friendly option to handle ships that were careening away from the battle). That tactical versatility comes at a price – you also draw a face-down field disruption card (most of which are Very Bad), and if your reactor takes damage while you have that card, you then flip it and do whatever it says.
The other action lets you get rid of that card. All it costs you is the time it takes, but in these battles time is a precious resource…

The Stiletto’s jump just barely gets it adjacent to the Cyclops. It rotates its vulnerable rear away from the Raptor and keeps it’s best defense (forward) pointed towards Nathan’s other two ships.
If the situation on the Cyclops weren’t so urgent and this were a straight space battle, the better jump would be to get behind the Raptor, further away from Nathan’s ships and out of the Raptors weapon arcs, but Mark will lose the scenario if he doesn’t contest control of the the Cyclops soon.

Mark’s remaining ships have Thrust actions. The Pike moves forward two hexes, setting it’s drift to carry it adjacent to the Cyclops.
Second card!

Nathan repeats the attack action for the Raptor (he really wanted to lay into the Stiletto). The Dragon attacks and the newly jumped Stiletto has wound up right in front of it, and we see a Jump for the Firebird.
Attacks go first – attacks are not simultaneous in Silent Fury, so if you get your weapon destroyed first then you won’t be able to use it. Nathan feels enough is at stake here to Seize the Initiative.
The Raptor played repeated attacks in the hope that the Stiletto would do something other than Jump away and still be around to beat on, but luckily it’s positioned so it still has valid attack options.
When to seize the initiative is a big decision in Silent Fury – for one, it’s not always a good thing to have. It means your actions go before your opponents actions, but for actions like Thrust it’s generally better to go second. For another, now that you have it, your opponent can seize it back whenever they want – and go first when it’s really important. Deciding whether to seize or not when two ships are set to attack each other is a big deal, obtaining an advantage now in exchange for conceding that advantage to your opponent later.
Now Nathan’s attack actions resolve before Mark’s.
The Raptor is up first.

The Pike (white striped) is out of arc, the Broadsword is in arc and long range of the Vibration Disruptor (but out of arc for the Autocannon), and the Stiletto is at short range for the Autocannon and out of range for the Vibration Disruptor.
The Raptor already used a Full Salvo and fired all its weapons, so on this repeated attack it can only operate one weapon, leaving a choice between a short range autocannon shot at the Stiletto or a long-range Vibration Disruptor shot at the Broadsword. Both attacks would roll two impact dice (Power 2 vs. Defense 2 against the Stiletto, you get two impact dice if you match or exceed the defense, and Power 6 vs. Defense 4 for the front of the Broadsword – the Broadsword’s shield comes into play here, its defense would be 3 without it and the Vibration Disruptor would get 3 impact dice if that were the case.)
Despite being the smaller ship, being at close range makes the Stiletto the easier target, but it’s close – d12s vs size 4 have a better hit rate than d20s at size 6, but just barely – we’re talking a 33% chance versus 30%.
The deciding factor for Nathan is that the Broadsword is about to shoot him. If he can knock out a weapon, that’s less incoming fire the Raptor would need to take. He attacks the Broadsword – and misses. None of the accuracy dice roll below a 12.
The Dragon attacks now.

There’s no ‘line of sight’ rules (real space is both huge and 3-D, making it difficult to hide behind something), so the Cyclops isn’t blocking the Dragon’s fire.
It has the next step up in the Disruptor line, the Gamma Disruptor – same range of 0 / 2, but the power has gone from 6 to 8 – the most powerful weapon in this scenario. Though the Stiletto has it’s shielded front turned towards the Dragon, it isn’t enough – Power 8 vs. Defense 4 gets you three impact dice.

The 4 component is hit (technically it’s hit twice, but it won’t matter in this case). 3 points on the Impact dice (with no special effect) mean the component is destroyed – and it just so happens to be the Stiletto’s reactor.

The reactor gets a destroyed marker and the Battlesuit inside is disrupted, joining his buddy in the disrupted crew box.
The reactor is technically hit twice by the attack (since two accuracy dice were both a ‘4’). Damage in Silent Fury doesn’t stack, you just use the worst damage type a component is affected by, so another ‘destroyed’ result doesn’t do anything further to the reactor. If there had been two or more Field Disruption cards on the ship however, we would resolve one card for each hit.

The reactor took damage with a field disruption card on the ship, so we flip and resolve that card now.

The fire disrupts the spacer in the autocannon (component 1). Fire is a more severe damage type than light damage, so the light damage in the engine (component 3) is removed and replaced by a fire.
Things are not looking good for the Stiletto.
The Dragon isn’t done – it’s still got a Talon laser to fire. At power 3 it’s not the scariest weapon, but it’s got good range at 4 / 7.
Nathan could elect to shoot the Stiletto again – if he nails that last component and disrupts all the crew, the whole ship would surrender – but he would have to hit that specific component, and at power 3 vs. defense 4 he’s only getting one impact die.
One of the unique aspects of Silent Fury’s damage system is that a ship that’s badly beaten up becomes more difficult to damage, because damage doesn’t stack – if half your target’s components are destroyed, then another result of ‘destroyed’ or lesser damage on those components doesn’t effectively damage the target further. This means that there comes a point where it’s better to not concentrate your fire and instead attack a relatively undamaged ship, because every component you could hit would actually suffer damage.
Nathan decides that the Stiletto is basically done for and not worth shooting again. Even though it’s a long range attack instead of a short range one for the Stiletto, he shoots at the Broadsword instead (Still power 3 vs defense 4, thanks to Mark’s spread shields from turn 1) – scoring one point on his single impact die for light damage, and ironically hitting the ‘2’ component, the Broadsword’s scatter cannon.

Since Mark is about to fire this weapon, that’s inconvenient damage. At least it’s only light damage – it could easily have been rendered inoperable, but you can use light or heavily damaged components with some degree of risk.
The Pike and Broadsword get to attack the Raptor, and the Accuracy dice giveth and the Impact dice taketh away – despite having three impact dice on three separate shots, he only managed to score light damage twice.

Had Nathan not seized the initiative, he would be the one rolling damage on his ship if he still chose to use the Vibration Disruptor after Mark’s attacks.
Mark operated a Lightly Damaged component (the scatter cannon) when he made his attacks, so after making that attack he makes a damage roll on his own scatter cannon. Fortunately his bad luck applies universally – he rolled no damage so the Scatter Cannon remained lightly damaged.
Attacks are done, crew actions are up – Mark had one played on the Stiletto, and Nathan had one automatically assigned on the Cyclops when he boarded it. Here’s where Nathan seizing the initiative for the Attack card concedes an advantage to Mark – the Stiletto is going to use its crew action to board the Cyclops. Since Nathan has the initiative, his crew action on the Cyclops will resolve before that boarding action. If the initiative had been left with Mark, then Mark’s crew would board first, and Nathan’s crew would have them on board and get to react to where they landed and start fighting them immediately.
So far we’ve just seen crew boarding actions – the ‘normal’ thing you do with the crew card moves them around the ship and you either shoot or repair damage.

Nathan rolls two impact dice to Rally (you always roll two for rallying, operating a medbay gives you a bonus point on the result). He scores 2 points (you rally one crew per point, but he only has one disrupted) and rallies the disrupted spacer – rallied crew must be placed with friendly crew so he puts it in component 7, the medbay.

Next you move 3 crew 1 space. Nathan moves two from component 1 into the reactor and sends the Engineer in the medbay into the shield, heading for the engines.

Then, three crew shoot or repair – he has nothing to shoot so he repairs. You get one impact die per crew repairing, and an engineer gives you a +1 to the result. Nathan rolls 0 points on the shield, but the bonus point from the engineer lets him change the power down to light damage.

The marine and spacer in the Reactor try to repair it as well – they roll two impact dice and score two points (no bonus for them) – it takes one point to change power down to light damage, and the second point removes the light damage entirely. The Reactor is repaired and the ship is ready to Jump.
The poor, stricken Stiletto’s crew action is next. This will be a boarding action, which also begins with a Rally roll.

but Mark decides to show that our custom dice actually do have pips on them! Not only does this rally all 3 of his disrupted crew, scoring 4 points on a rally (or repair or melee) roll lets you draw a Forged in Battle card!
Mark decides that the Stiletto is done for and the Cyclops is all that matters – he abandons the Stiletto and sends all her crew over with his boarding action.

He gets a great one for this scenario – Their Finest Hour lets you auto-rally all of your crew on any one ship, and draw a free Hero and add it to that crew to boot! Even better, you can do it anytime you want. Mark keeps the card secret until he chooses to use it.

Mark’s boarding action lands both battlesuits and a spacer in the starboard engine. Unfortunately, it also lands a couple crew in unfavorable melees up in the cannon section.

The melees resolve as expected – the one in component 3 with Mark’s engineer was a single die for Mark with no bonus against three dice for Nathan with a +2 bonus (one for the marine, one for the battlesuit – same types of crew do not stack bonuses, but different types do!)
We have one more second card to resolve – the Firebird’s jump.

Nathan anticipates that the Broadsword will need to maneuver again to get adjacent to the Cyclops during drift and chooses this position to hit it from.
Third card!

All of Mark’s ships attack! This may be costly for the Broadsword, as it hasn’t yet adjusted its vector enough to get adjacent to the Cyclops during drift.

Nathan’s ships have other plans – the Raptor (despite my expectations of a bloodthirsty triple attack) and Dragon play thrusts, and only the Firebird attacks. Nathan still has the initiative at this point.
The Firebird attacks the Broadsword first, only rolling one impact die (Power 3 v def 4) but it is within short range. The first attack causes light damage to component 4, which is promptly overwritten by the second shot:

Our first damage with a special effect (the effect die finally came up – you only need one). Special effects are Power Down, Fire, and Hull Breaches – one point on the impact dice scores a Power Down, and both components 4 and 6 are hit, so this attack powers both of them down.

The light damage just dealt to component 4 is replaced by a power down, and one crew in each component was disrupted.
Mark’s return fire at the Raptor craps out again – good accuracy and no damage. He’s racked up a lot of 1 in 8 shots, and not in his favor.
He also decides to take a shot at the Cyclops from the Pike at long range – his rationale being that there are plenty of spaces he could hit the ship that would hurt Nathan’s crew, and just one component that would hurt his own crew. He misses.
Mark is not happy with the dice, and I can hardly blame him – statistically the Raptor should be hurting at this point (if not destroyed – consider it’s the same size as the Stiletto with worse armor and has had about 3x the attacks rolled against it by now), but anyone who plays games knows the dice can do these things to you.
It’s time for Crew actions on the Cyclops – maybe things will go better! Mark is only holding a single component and seizes the initiative – Mark goes first.
Rally!

Not off to a great start. After rallying, if there are any crew left in the disrupted crew box, one of them dies (this is how crew are generally removed from the game.). This rallies no crew, and Mark chooses the spacer in the disrupted crew box to die.
Move 3 crew!

Mark moves the Battlesuit and a spacer to beat up a poor engineer. This time Mark rolls well, scoring 3 points on two dice and a bonus for the battlesuit. The engineer can’t roll more than a 2 on his one die, he loses and is disrupted.
Mark’s first inclination was to charge everyone in, but I advised him that since all crew can be disrupted by a hard enough hit that it was dangerous to do so – your troops are more powerful if you send more of them into a melee, but that also makes them more vulnerable to shooting, and Nathan will be able to get a flanking shot on his crew action. Mark decided to hold one Battlesuit back in the engine.
3 crew shoot (or repair, but nobody’s bothering with that now)!
This is the first crew shooting in the game, and it actually works just like ship weapons fire except you shoot into specific components – you always get one effect die, and you get one Impact die per corridor that you shoot the same component from. Mark is only able to shoot into the medbay from one corridor so he gets one impact die, plus a bonus point from the Battlesuit (they give a bonus to both melee and shooting).

Mark’s scores nothing on the shot, but does get one point from the battlesuit’s bonus and inflicts light damage on the medbay. This does not replace the power down since power down is more severe than light damage, but it does disrupt 1 crew.

Final positions after Mark’s crew action – some progress, but it’s unfortunate he couldn’t clear the Medbay.
Nathan’s crew action on the Cyclops sees him rally the engineer (he scored 1 point) – the spacer dies. He places the rallied Engineer in the medbay and moves the Marine down from the Reactor to flank Mark’s battlesuit. He can fire down two corridors and thus gets two impact dice for the shot, scoring 1 point – light damage, disrupt 1 (Mark chooses the spacer).
The 3-crew limit on movement and shooting means that this situation isn’t hopeless for Mark. He may be outnumbered, but in terms of offensive capability both sides are nearly equivalent if Mark can get some crew rallied and still be able to use 3 crew on his turn.

The Action phase ends on Nathan’s thrusts – the Dragon can actually move one hex backwards with all three engines and does so, turning itself around. The Raptor’s thrust chart is good enough to let it go two hexes on one engine, which it does. Nathan’s next target is clear – he feels the Firebird can handle the Broadsword, both the other ships are positioning for after-drift attacks on the undamaged Pike.
Drift Phase
The Broadsword can only operate one of its shield generators (the other is powered down and inoperable), so one of its shields drops.

After drift, every Vandar ship is sharing a hex with a JHI ship – this is the last place JHI wants to be to take advantage of their superior defenses.

The Stiletto is abandoned and we remove it from the game. Writing this up made me realize that we don’t have a formal rule for this, it’s just something we’ve just done without actually writing a rule for it. I’ll correct that in the next version.

The Broadsword didn’t make it adjacent to the Cyclops, and while the Pike is adjacent it’s also facing an attack run from the Raptor. Mark is outnumbered on the Cyclops and things are not looking good for JHI.
We’ve gotten though pretty much all the detailed rules explanations we’re likely to see, so I think part 3 will take us through to the conclusion of the game.