Star Fleet Universe

A blog for all subjects related to the Star Fleet Universe from ADB Inc. Talking about the games, the background, or its relationship with regular [i]Star Trek[/i].

1 , 2 , 3 , 4 , 5  Next »  [11]

Recommend
12 
 Thumb up
 tip
 Hide

T3 The Lone Gray Wolf Y160 S3

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
[Scenarios 1 & 2]

Mark and I returned to the "Lone Gray Wolf" mini campaign a bit ago, as my C6 dreadnought continued making its way back to friendly lines. This time was a proper challenge, as the pursuit group came up '4', which is the second-best Kzinti group. In the original, this is a CVL+ carrier group (basically modified BC, CL, FF with nine fighters); in this Y160 variant, there's no fighters (of course), and the ships are their regular unrefitted equivalents of a CS, CL, and FF. By straight BPV, this is 195 vs 262 (and by F&E ratings 10-12 vs 17-18), though there are some serious advantages to having one large ship instead of three smaller ones (it being easier to punch through a shield to destroy weapons on a smaller ship being the main one).

As ever with this campaign, setup is the C6 in the middle of the board, with the Kzinti 14 hexes behind it; in this case Mark started his ships one hex apart, with the CS in the middle. I started at speed 20 and no EW, while the Kzintis all went speed 18 with 1 ECCM running. The first few impulses got us going, and I slipped and then turned on Impulse 5. The Kzinti generally slipped over to keep in line with me, and I turned in late in the turn, and used the good arcs on the ph-1s to hit the FF's shield #1 for 8 points at range 12 (5 registered).

With the range staying closer than I might have liked, and Kzintis turning to intercept on impulse 32, I decided on a somewhat risky maneuver: going down to speed 12, and launching an ECM drone (actually done on Impulse 32). The Kzinti went to speed 21 (except the FF, which stayed at 18), and used varying amounts of ECCM, while I generated 6 ECM (with another three from drone when it came on-line during impulse 4).

I turned in at the start of the turn, and Mark tried to clear the ECM drone with a pair ph-3s on impulse 7, but failed to get any hits at range. He launched drones on 8, the FF slipped out, and the CS turned in for nose-to-nose confrontation. I tried tractoring the CS on 10, but gave it up after three points of power. The CS then launched from its remaining two drone racks, and I launched two drones, and then we unloaded into each other (with the CL adding in). Phasers knocked down all the just-launched drones and the ECM drone, and the CS and CL boosted ECCM enough to get the shift down to a +2. Two of four of his disruptors missed, and mixed phaser performance added up to 23 damage, or just over half my shield #1. One of my disruptors missed, but three overloads, 4xph-1 and 2xph-2 did a total of 50 damage, crashing through the #1 for 24 internals. This ripped through the forward hull, and took out the batteries, along with the usual scattering of weapons and power.

External image
Turn 2, Impulse 10, showing movement for the first 16 impulses.

On 11 various ships moved forward and the CS slipped to the left. I tractored the latest two CS drones, and launched another drone at one of the ones further out. The CS fired all available (6!) ph-3s, doing 22 damage to shield #5. On Impulse 13, the CL slipped in behind me and fired two ph-3s on #5 for 7 damage (one blocked by a battery), while I downfired a phaser to knock down a drone (and then the other one of that pair was destroyed my drone the next impulse). On 15 the FF turned to parallel the other Kzinti ships and fired its 360-ph1, doing 2 points to exactly bring shield #5 down. On 16, I finally turned (now that the drones to my starboard were gone), getting that shield away from everyone, and then spent the rest of the turn dodging the remaining drones and pulling away from the Kzinti.

The Kzinti turned again on Impulse 20, I turned to parallel them on on 27, and the Kzinti turned in on 28 so that the closest ships (CL & C6) were at range 5 at the end of the turn. I boosted to speed 16 for turn 3, while the CS went 14 and the other two ships went 15, and all of us dropped all EW. I turned in on Impulse 4, and the CL and CS both launched a pair of drones. The next impulse, the CL turned in, and the FF launched a pair of drones. On 6, the CS launched another pair of drones, and I launched a pair, both targeted on the CL, but pointed in different directions, to cut down his maneuvering options. The Kzinti fired all bearing weapons, with the CL and CS's disruptors missing, and the FF's hitting. All told, I took another 4 points on shield 1, and and 13 on #2.

External image
Turn 3, Impulse 5, showing movement from Impulses 1-16.

On Impulse 6, I slipped out, and fired all four disruptors at the CL, while Mark fired ph-3s at my drones to kill one and damage the other (finishing it off with another ph-3 next impulse). Three disruptors hit, doing 12 damage, nine of which registered on the CL's #2 shield. I started turning off, with the drones in pursuit, and on Impulse 12, the FF fired ph-1 and disruptor at range 3 to do 6 damage to the #4 shield. It slipped closer the next impulse, and I fired 2xph-2 at it, for 8 damage, 5 of which registered on its #2 shield. Two impulses later, I followed that up with two more ph-2s, for another 8 damage, which knocked down the #2 and did a forward hull to the FF.

By Impulse 23, both the CL and FF had turned in pursuit of me, and the CS was paralleling me three hexes off my shield #2, so transported a dummy transporter bomb two hexes in front of the CL, and dropped a real one out the shuttle hatch. On Impulse 27 I transported out a real TB in front of the CL and FF. The Kzinti overran the dummy, but the FF turned off rather than hit the one I dropped. The CL and FF were able to avoid the third mine as well, but only with a bunch of slipping, and they started falling behind, which was largely the point. Drones encountered the dropped mine on Impulse 32, which detonated destroying one pair.

External image
Turn 4, Impulse 1, showing movement from Turn 3, Impulse 23, through Turn 4, Impulse 6.

I repaired two boxes on my #5 at the end of the turn, and went speed 18, with the Kzintis spread from 18 (CL) to 21 (FF). Mark continued with no EW, but I put up two points of ECM. I turned towards the CS on impulse 2, and it turned away, with the CL and FF still getting around the third transporter bomb. On Impulse 6 I fired two disruptors (the only ones I'd charged) at the CS, hitting with one to do 4 points to shield #5.

I continued turning, keeping ahead of the CL and FF's turn radius, and on Impulse 15 the CL fired its disruptors and ph-1s at range 5 with one disruptor hit and good phaser rolls to do 11 points on the #3 shield. On Impulse 24 the CL managed to turn inside me, and it took some slipping to get it back behind me again. On 27, I fired a pair of ph-2 at the FF, but poor rolls meant I did no damage. The FF turned in pursuit and fired 2xph-1 and ph-3 on 28 to do 7 points to my #3. I turned again on 29 and tractored the CL (at range 2, spending all the batteries on a 4-point tractor).

The CL and I then launched pairs of drones at each other, and I launched the suicide shuttle that I'd spent the first three turns preparing. The CL fired 2xph-3, doing 8 points of damage to #3, while I fired 3xph-1 and 2xph-2 (with overall poor rolls) to do 20 points, which knocked down shield #2 and did 13 internals, costing him two power, two phasers and a drone rack. Sadly, I'd done the movement wrong, and my seeking weapons ended up going past in front of the CL on their first move (when they have to go straight).

I repaired one box each on my #4 and #5 shields, and budgeted for a fairly strong tractor attempt on the CL in EA, and went over my budget, and still didn't manage to hold it. I burned 18 power on a range-2 tractor attempt, leaving me with no weapons charging (and three energy in the capacitors), and only two energy going back into batteries, but at speed 20 with 1 ECM running. The CS and FF were a few hexes behind me (range 5), and the CL had spent nine power resisting the tractor (out of twenty-one available), so it wouldn't be able to fire and keep up with me.

The CS and FF went speed 18 for turn five, while the CL went 12, meaning that my EA had worked: I would pull away a bit this turn into moderate-close range. Better, Mark didn't use any EW, and my +1 shift would help keep me from taking much damage. The real saga of the turn was the CL, which was going speed 12 with a speed-6 shuttle, a speed-8 drone, and a speed-12 drone targeted on it, and adjacent. The CL ended up slipping away from me (his first thought was to give chase, but that'd end up with range one and his down shield to me). My drones HETed, and then went forward, temporarily putting them directly between me and the CL. This caused the CL to be herded away from the action by the speed-12 drone, as it was always hanging off his starboard, and would hit if turned in. He finally shot it with a ph-3 on impulse 17 and killed it (if I'd known how this'd end up, it might have been an armored drone...), and then turned toward the rest of the action.

I went back towards my transporter bombs from a couple turns ago, mostly hoping to give Mark trouble avoiding them as he perused me. Mark went around the mines, but the bulk of the drones had ended up collected into one big mass, and eight of them tripped the third mine on Impulse 32, destroying them, and just left the last two drones from the CL, which were following two hexes behind the rest.

For turn 6, I dropped to speed 17, while all the Kzintis boosted to 21. Mark stayed with no EW, while I put up 4 ECM. I continued a look around the remaining (dummy) transporter bomb. On Impulse 5, the CS fired a overloaded disruptor and ph-1 at range 4, missing with the disruptor, and only doing 2 points through the ECM, which was exactly countered with the reinforcement I'd allocated on my #5. On Impulse 11, the FF fired both ph-1s and its disruptor at range 3, collapsing the weak #5 and doing four internals, knocking out one power and three hull. The CL was approaching from the front, and as I prepared to pass off it's starboard side, I came upon its drones from last turn, which I killed with a pair of downfired phasers on Impulse 12.

On 13, the CL got to range 3 on its down shield, and I fired 3 disruptors (all I'd powered, in case one was lost to internals), of which one hit, 4 ph-1s, which did 12 damage on some poor rolls, and 2 ph-2s, which did 7 damage on average rolls, to do 22 internals and gut the CL.

External image
Turn 6, Impulse 13, showing movement from 1-27.

On Impulse 14, I went forward while the CL slipped away, and, still on the #2 shield, I fired another ph-2s for eight more internals. The CL and the C6 both continued straight after the pass, with the CS and FF coming back around in pursuit, and about five hexes behind the C6.

For turn 7, the CS and FF maintained speed 21, while the CL dropped to speed 9, while the C6 sprinted at speed 26. This involved shutting down everything but 2 ECM, full damage control on shield #3, charging five batteries, and charging one phaser (and the capacitors were otherwise dry). Mark fired on Impulse 2, doing a total of 10 damage to shield #4 with a pair of disruptor hits, and one good ph-1 roll (the FFs ph-1 shot missed entirely). On Impulse 14, the CL was 36 hexes away from the C6, and my seeking weapons (one drone and the suicide shuttle) lost tracking and went inert. On 28, the CL was 51 hexes away from the C6 and disengaged by separation.

At the end of the turn, I was ten hexes in the lead of the CS and FF, and did the second part of my plan. I went speed 0, and allocated for the maximum of four tactical warp maneuvers and one impulse tactical while charging everything to full (except for one disruptor kept off line), and put five points of reinforcement on the weak #3 shield in case Mark should fire before I could turn it away. Mark was expecting more high-speed chase, going 22 in the CS and 24 with the FF, and no EW.

Mark turned off and did not try to engage, circling around a bit near the end, and we were at range 17 at the end of the turn. The CS shifted down to speed 14, and the FF to 15 for turn 9. I went my maximum speed of 10, with 14 points of reinforcement on the #1 shield, and standard loads on all disruptors. The Kzinti effectively crossed my 'T' during the turn, and the FF started turning to maintain an orbit around my position, and I turned towards it. I fired disruptors at range 13 on Impulse 25, getting three hits for nine damage to the #6. The FF then turned off, paralleling the CS again. At the end of the turn, I continued repairing shields (#1 and 2 this time), and the Kzintis each repaired one box on down shields.

For turn 10, I boosted to speed 18, while the Kzinti went 15. I had a bit of a quandary at this point. I would have dearly loved to actually destroy one of the group-4 ships, but Mark was now generally playing keep-away, and it looked like I wasn't going to be able to force another close pass at any time soon. I could try peppering him with moderate-range disruptor shots, but even against the FF, that would take time to take effect, and in another 10 turns, he would get to roll to see if another pursuit group showed up. Even the damaged FA-L of group 6 would be a help, and the pair of FFs in group 5 could be dangerous at this point.

So I shadowed the Kzinti for a bit, then turned towards them. After a few impulses the Kzinti turned away, I fired disruptors at the FF for one hit to do four damage to it's #4. The Kzinti turned off of my course... and the turn ended with us back down to about range 11.

On turn 11, I went 19 while the Kzintis went 24, and both launched drones on impulse 1. The Kzinti turned away again, and I fired disruptors at the FF for all for to hit at range 12, and do five internals (after five shields and two reinforcement), which got one warp and two batteries. I turned to go around the drones, and the FF turned to get the down #4 away from me. The CS turned to stay with the FF... and I turned the opposite way.

This was an opportunity I had been looking for. We were now headed directly away from each other, and the range would open up dramatically before Mark could turn back around and give chase. In fact, we ended the turn at range 25, and I plotted to sprint at speed 31 to keep opening up the range. I had five more turns allowed at speed 21+, and the CS was only capable of 24 at best, giving me at least three hexes per turn, and it still had to finish turning around. ...I had forgotten at that point that separation is range 50 (instead of the 35 of losing seeking weapon tracking). On the other hand, I'm not sure how practical even speed 24 was with the need to power other systems, and certainly me dropping speed suddenly again was a possibility. Even at 24, that's six hexes times 5 turns to open up the range at least another thirty hexes and disengage by separation around turn 16 or 17.

External image


After the scenario, I was able to repair what damage I had taken, but I am down six drones, two transporter bombs, one dummy bomb, and one shuttle (that last one hurts the most, I had been hoping to drive him off and recover it). The FF was able to repair everything but two forward hull boxes. The CS is down all its forward hull, two rear hull, a tractor, a transporter, a bridge box, a RS ph-3, and the topmost sensor '6' box. Even after repairs, the CL is a mess, still out three center warp, two impulse, an APR, all the batteries, all hull, two lab, a tractor, a transporter, both drone racks, the RS ph-3 and RF+R ph-1.

Mark's initial mistakes came during the the turn 2 pass. First, he fired on the ECM drone two early, as the ph-3s just didn't have the range, and they missed. Then he killed it while doing his big strike, instead of an impulse before (or even ignoring it, and letting me worry about being stuck at speed 12 or abandon it). Also, the FF didn't come in with the other two ships. He needed the extra firepower, and he needed to distract me from the CS. Even losing the FF outright (which he was rightfully worried about) would be worth having the CS in good shape for the rest of the battle.

Admittedly, that pass went better than I thought even with all of that. I expected to take a lot more than half of my #1 on that shot. The +3 shift from the ECM drone helped, but it's just that the CS is a lackluster cruiser. Trying that against the Kzinti CC (which leads group #1) would end a lot differently, as it has a lot more firepower. It still might not get through the shield, but there would be very little left. (It also has three more warp power, so my end-game sprint wouldn't work against it.)

The CL also was mismanaged. First, it should also have followed the CS in on turn 2 for a centerline shot. On 5, it needed to kill my speed-12 drone a lot sooner so it could maneuver. Second, he needed to make me work for the turn 6 shot at it. Turning across my path would have worked. I could overrun it and then fire the (lots of) rear phasers after going by it, but getting the shield #2 shot might have been tricky, and the disruptors wouldn't have a shot. Instead, I'd probably take the approach shot, leaving it with two down shields but fewer internals. Also, the intact left-side weapons would get to fire at close range.

We're off to other things for the moment, but we'll be checking on scenario 4 soon!
Twitter Facebook
4 Comments
Wed Dec 2, 2020 8:23 pm
Post Rolls
  • [+] Dice rolls
Recommend
10 
 Thumb up
 tip
 Hide

SG33 Treasure Ship

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
Looking things over, I had noticed there were a few 'general' SFB scenarios that are geared to around the current play date of our group (instead of ~Y175) shortly before Patch suggested a Star Fleet Battles game. I put together a package of possibilities, and we went with "Treasure Ship", where a freighter on robot controls emerges from the WYN cluster, and two of their neighbors fight over who gets to take the prize home. (One of them paid for the valuable resources on board, but the WYN are not above promoting fights by sending the freighter out in range of two ships.)

Of the options, we kept the scenario as small as possible, with Patch taking a Lyran FF and me taking a Kzinti FF, with a small freighter (F-S) up for grabs. (Patch called it 'two kids fighting over a candy bar.') Effectively, it's a frigate-duel, but the freighter is worth two points per intact cargo box to whoever ends up with control of it. The two ships set up on opposite sides of the board, with the freighter in between, running in a straight line at speed 4.

I decided to make a fast grab for the F-S, and try to steer the fight away from it, and possibly disengage (which it can only do by distance), and went speed 28, while Patch went a more sedate 18. Most of the turn was spent running up, and on Impulse 23 I came adjacent and tractored the freighter, then launched a drone, fired the disruptor at Patch, and fired a phaser-1 at the F-S for five points of damage. Which would be perfect for knocking down the shield, except the robot controls put up one point of general reinforcement, and the battery as a second reinforcement, leaving two boxes of shields up. Patch fired both disruptors back on the next impulse, and hit with both for six points on my #6 before turning off. I turned the opposite direction, and Patch turned back a few impulses later. I then fired a Ph-3 into the freighter for three points to knock down the shield, and do one cargo (doh!) internal, and then transported a boarding party and crew unit (prize crew) aboard the next impulse.

Patch stayed at 18, while I boosted to 30 (halved, since I kept the F-S in tractor). This meant skipping the disruptor, and skimping on battery and phaser charging. I ran for half the turn, while trying to figure out how I wanted to get more boarding parties on to the freighter. On impulse 15 I dropped the tractor, and launched a second drone, and then turned the F-S and sideslipped the FF so that it could drop a shield and beam three more BPs onto the freighter through its down shield, with nothing pointing Patch's way. (Some of this was delayed because I allocated a box of General Reinforcement on the F-S, which blocked the transport, and/or a shuttle, and landing a shuttle aboard was the original plan. Half a turn gave me some time to look things up and realize I could drop the reinforcement for a bit without having to announce it.) Once that was done, I realized I only had one boarding party left on the FF. Hopefully, I wouldn't give Patch any chances to board me....

On impulse 18, I launched another drone, this time going speed 12. Patch continued towards the freighter/me, with range to the drones dropping fast, and on 22 he fired both disruptors and a phaser-2 at range three to the F-S to do 8 points (one disruptor missed), for two internals (the general reinforcement had recently come back up), one of which was a cargo box. Patch turned off to avoid drone #2, and I turned the opposite way (now that the shield was back up). On 32, he turned back towards me, and fired on drone #3, which had closed to one hex... rolling a 6 with a phaser-3 to let it live.

Patch stayed at 18 again, while I dropped to speed 19, which allowed me to charge the disruptor, get the phasers fully charged, and start shield repairs, but only trickle a little power into the batteries. The F-S picked up to speed 5, while it finished charging its battery. Both frigates ran with one point of ECM. Patch finished off drone #3 on impulse 1, and I spent the first few impulses finishing a turn back towards Patch, hoping to keep him distracted from the F-S, and get the ESG to deploy so I wouldn't be facing it and all the phasers in what I hoped would be a main battle pass later. On 8, he turned in, somewhat to my surprise, given how cautious he'd been earlier.

Sadly, I once again forgot to save a log, so I don't have a direct record of what happened for the rest of turn 3. However, as ranges came down, and I carefully sideslipped for a slightly off-center run, the ESG was announced on impulse 9, and I had a very tense time of trying to get close while being able to maneuver around it... at whatever range Patch set it at. On 13 it came up at range 2, while I was at 3. I fired my disruptor and turned off, while Patch fired the following impulse. On 17, I dropped a (fake) transporter bomb out the shuttle hatch to discourage him from pursuing me while I got a little distance and turned myself back around. Patch sideslipped the opposite way to keep away from it while the two drones shortcutted near it. Patch turned wide around it (thanks to the ESG), and headed for the F-S, ending the turn with the ESG one hex from it.

The F-S, seeing it coming, dropped to speed 3, and put up three reinforcement on shield #4. After that, and blowing the battery, it lost two hull, the phaser (never charged), two cargo, and three out of four warp (ironically, after losing all but two power, it still doesn't count as crippled, as that requires only having 10% warp power left, not 25%), on impulse 2, when the ESG hit. Oh, and combined with our earlier shots, it had no rear shields left.

Meanwhile, I'd kept at speed 19, overloading the disruptor and putting a point each into ECM and ECCM (the batteries were still getting a trickle of power, and were finally over 2 energy again). Patch stayed at 18 and also had a point each in ECM and ECCM. He turned away on impulse 6, while I was still turning around (Patch mentioned that he had nearly turned in, which would have been a better decision at this point, though I'm not sure how it would have gone). Patch wondered about the mine, as I went by it while turning after him. I pointed out that I could just set it to explode on size classes that weren't present (say SC 2 dreadnoughts), so that an ESG collision would be the only thing to set it off ("Evil!"), or it could just be a fake ("Also evil!").

On impulse 12, I got to range 8 and fired the disruptor, hitting to do five damage to his #4. On impulse 21 I fired the forward phaser to do another 4 points (rolled a 1!), getting through the shield, and doing a single forward hull. Patch started fighting to get me off his #4, which left me with the problem of possibly getting too close to him this turn, as I started cutting inside. Drone #1 quietly ran out of endurance on impulse 23... the first time I've seen that happen in quite a while.

External image
Turn 4, Impulse 12, showing movement for the full turn.

For turn five, I kept to speed 19, with much the same setup as last turn, but dropping ECM to recharge the one phaser I fired. The F-S continued to crawl off at speed three while starting repairs on a warp engine. Patch went speed 12 with 1/1 electronic warfare, indicating preparations for a close-range pass with two overloaded disruptors, and possibly pumping all he could back into the ESG....

I launched another speed 12 drone (#4) on impulse 1, and Patch turned on 3, with me just outside the forward arc. I turned in, and on impulse 7 got back onto shield 4, doing three points (lousy roll) with the 360 phaser-1 to get a ph-3, a disruptor and a warp. On 8 the new drone got to range one and Patch fired the remaining RS phaser, and a poor roll let it live with three points of damage again. On 9 he finished it off with a downfired ph-2, but I turned to get my FA arc to bear and fired the forward ph-1 and overloaded disruptor to do thirteen internals, at which point Patch conceded.

External image


Afterword

The addition of the freighter does certainly add interest to an otherwise standard small duel. Also, the small ships are always interesting to work with, as they can maneuver, but just don't have a lot of guts.

I rattled Patch by going fast and grabbing the prize early, but it could have easily backfired. I burned 1.2 battery power on those transporters, and was only putting 1/6 point back into batteries each turn. Also, I inadvertently left myself open to a boarding action if Patch had ever gotten a good pass to knock down a shield. And I largely broke up his best chance with a fake T-bomb.

If things had gotten serious from there, I would have dropped the real one (I only bought one). They're an extra thing for Lyrans to be wary of, since an ESG will set them off on contact, and apply its damage to the field... or straight to the facing shield (even from three hexes away) if there's not enough in the ESG to take it. But, it is only 10 points, and it often won't get past the ESG at that point, though it does compromise its drone defense.

It turned out that Patch had missed the ESG power storage from the WS-III start, so he'd been blowing power on it it he didn't need to. I was mostly worried we'd have a close range pass, where he had twice as many disruptors (...and similar power, so maybe he couldn't overload them, but I can miss with one overloaded disruptor a lot easier than he can miss with two standards), just as many main phasers (2s instead of 1s, admittedly), twice as many ph-3s, and could use his ESG to knock down my drones with strength left over (or use the ph-3s for that and hit me with a full ESG ram).

I took half of my drones as type-IIs, and the mix served me well. The two speed-8 drones made good terrain, and the speed-12s got in close and forced him to kill them.

As for what did happen, thirteen internals would have gutted many of his systems, and the next impulse I'd probably follow up with the RS ph-3 for 1-4 more damage. Then I'd go sailing off past him, before lining up for a shot at the near-cripple next turn. Patch gets 6 points for the drones and T-bomb I took, while I get 42 for intact cargo and 15 for forcing a disengage (if not 32 for crippling him, but I don't think I would have quite gotten there). 57:6 is deep into Astounding Victory territory. If things had lasted longer with the same end result, that could have been chipped away at as the F-S got shot up further.
Twitter Facebook
4 Comments
Wed Sep 23, 2020 8:52 pm
Post Rolls
  • [+] Dice rolls
Recommend
12 
 Thumb up
10.00
 tip
 Hide

T3 The Lone Gray Wolf Y160 S1-S2

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
"The Lone Gray Wolf" is an interesting mini campaign for SFB that I've had some desire to play ever since the days of Commander's Edition. Back in Captain's Log #41, there was an 'update' to it, positing that this situation could have happened before, maybe an early version was even the reason why it was tried at the height of the General War. This provided for alternate versions of the campaign in each Klingo-Kzinti conflict, which works out to a W-era, Y-era, two 'middle years', and late-GW variants of it. The fourth one happens to be set in Y160, our group's current scenario date, so with our expanded Vassal playing time, I talked Mark into playing through it with me.

A Klingon dreadnought goes alone to the Kzinti capital to negotiate a peace. The talks break down, and the dreadnought is forced to make its lonely way back to Klingon lines, with Kzinti forces hunting for it. There are six Kzinti groups hunting for it, and the dreadnought must survive six scenarios to win through. But, this is not 'face each force in turn'. Instead, each scenario starts with a die roll to determine which force finds the dreadnought this time. Repeated rolls of the same number will bring up the same ships (worse for wear from the previous scenarios, just like the dreadnought, and if the Kzinti ship(s) were destroyed before, this becomes a 'free pass' for the Klingons). The Klingons must conserve fuel, and must stay to speed 20 or below most of the time, and can only disengage by acceleration once in the entire campaign.

Mark volunteered to take the Kzinti, and after some pondering over drone choices (especially for me, as they have to last for six battles), and deciding to try MRS shuttles (which added more drones to the mix), we started in mid-August. The first roll was a '6'... the weakest Kzinti group, a single FA-L (drone-armed freighter; also about the only ship unchanged from the original version). Against a C6 early dreadnought (this is the second time I've piloted one), Mark's main hope was to force me to at least expend consumables, either launching drones, or using T-bombs.

Setup is always with the Kzinti a half-map behind the C6, and Mark set up about six hexes off to one side. Initial speeds were 17 for me and 18 for the FA-L. I spent on 4 ECM and 1 ECCM while Mark didn't spend anything on EW. I spent half the turn getting turned around, while the FA-L first turned to parallel my initial turn, and then turned in. As I started setting up for an oblique attack, Mark fired his two bearing ph-2s at range 7 with a +2 shift to do one point of shield damage, and then turned off. Three impulses later, just short of the oblique, I fired all bearing weapons (4xph-1, 2xph-2, 4xdisruptors overloaded off of batteries) to do 11 internals through shield #5 with below average rolls (phasers never rolled under a 3, and two disruptors hit on a 2/3s chance). Internals were all over, taking out two of three control spaces, and reducing the sensor rating to '3' (making drones a really chancy weapon, as he had a 50-50 chance of losing lockons and all drone tracking next turn), but not taking out any weapons.

External image

Turn 1, Impulse 23, showing movement from Impulse 17 through 32.

Two impulses later, the left waist phasers were in arc, and better rolls did three points through the down shield, for two hull, and one sensor hit, reducing it to '0'. By the end of the turn I was six hexes away in a stern chase, and it was obvious that Mark would be trying to disengage by acceleration. I went down to speed 12, overloading the disruptors and recharging the phasers and batteries, while the FA-L went its maximum of 23 (...okay, 31, we forgot about the freighter's acceleration limits).

I immediately volleyed everything I had, trying to get it down to less than half its original warp power, and unable to disengage by acceleration. The phasers were a bit more mixed (with a 2 in the mix, but also two 6s), but all the disruptors hit, to do 17 internals through the #3 shield. This took out the last control space, two phasers, both impulse, and left just enough warp to disengage with. On impulse 4, I turned to get the right boom phasers into arc, and did two more points to take out the shuttle and a third phaser. After that, the distance opened up, and Mark got me off the down shields, so that I couldn't do any internals, even if I got the waist phasers to bear, and he disengaged.

External image


We checked what the next group would be after that. And it was... 6! again!

We set up and did a half turn in a short session, just to see if I could get internals before it fled. Between scenarios, all shields are regenerated, and limited repairs can be made (he repaired the sensors, a couple warp, and I don't recall what else). However, he set up smartly in a far corner, and I couldn't manage more than about two greater speed than him, and couldn't do more than dent a shield.

External image


We've started scenario 3, which should be much more of a challenge. (Spoiler: he got his second-best group.)

Mark was just too aggressive given the disparity in power between the ships. Of course, group #6 is probably best to see towards the end of the campaign, hopefully after something has done some real damage, and the Klingons have to be a lot more cautious. Catching me with a scatterpack could have been bad, but even that is unlikely to scare an intact C6 much (partially because of drone speeds, and partially because it doesn't have to give much credence to the FA-L's pop-guns).

The real goal would be to drag things out. It's unlikely to go anywhere near twenty turns (at which point he rolls again for another group to show up), but if he can get me thinking about it, I might make a mistake. And of course, short of hoping for that, the goal should be to get me to use T-bombs or drones, but with a fresh C6, the FA-L just couldn't force that either.
Twitter Facebook
5 Comments
Tue Sep 8, 2020 5:38 pm
Post Rolls
  • [+] Dice rolls
Recommend
21 
 Thumb up
5.00
 tip
 Hide

SH76 Quarantine

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
Mark and I are getting into weekly Vassal sessions to supplement our FtF gaming, and maybe finish off ones we can't do in a session. We started off with Star Fleet Battles scenario SH76, "Quarantine", which is part of the Y160 timeline we're in as a group.

Plague had broken out on a small planet near the Klingon Border. The planet had not been colonized and only had personnel who were surveying it for colonization. The CLH Refuge was sent to the planet to rescue them. The Refuge was accompanied by a single escort vessel because the Klingons were too involved in their current war with the Kzintis and Hydrans to interfere, or so it was thought.

A Klingon Commander serving a penance tour on a penal frigate became aware of the plight, and he arrived to "investigate possible biological warfare experiments" in hopes of earning a quick ticket off the penal ship.

This is something of a scenario to show off the hospital cruiser and the F5J. Mark took the Federation force, which has a POL and the CLH. The CLH is by far the bulkiest thing in the scenario, and has armor to boot, but it only has four ph-3s for armament, so all the fighting is on the POL. The action centers on a planet and a small moon, both of which have a small outpost on side B (they are shut down, and pure accounting exercises for if they get shot up) each with 8 crew units (the standard) who are infected and must be transported directly to the CLH (which has the facilities to contain them), and two crew units from the CLH (who are apparently not infected yet). The Federation needs to get the infected crew units up to the CLH and off-board (with a minimum of 10).

The Klingons have a single F5J, which is better armed than the Federation force put together, but is limited by ph-2s and a poor crew. It comes on board at the start of the game, and wants to get 10 information points on each station before all the infected crew units are removed (I didn't see anything about it, but I ruled that the EW system impacts the research table—it is a poor crew after all—which meant I generally had a +1 to my rolls), and kill one ship before leaving (which is likely to be the POL).

The Federation ships start in orbit of the planet, and Mark started up the CLH at speed 9, while the POL went 12 (thanks to being Nimble), and the F5J came in at 15, a speed I would largely stick to. The CLH was running 4 ECM (giving me 7 to burn through after my poor crew penalty), while the F5J put up 2. The CLH immediately beamed two crew units up from the planet (it also only has two transporters; I'd think an extra or two would make sense for a hospital ship). I got to range three of the planet at the end of the first turn, and a poor roll get me all of 2 points of info (1x2 labs...), while the Feds headed down, and regrouped.

Turn 2, the CLH went 12, and boosted to 6 ECM (giving a total of 9, or +2 for me if I didn't spend on ECCM), the POL used 2 ECM and everything else stayed the same. I cruised next to the planet and then headed for the moon, hoping to get decent info on both. Bad rolls continued, getting me 6 points on the planet (total 8) and 8 on the moon after having been adjacent to both.

Unfortunately, I didn't record full logs for turns 3 and 4, and turn three was where the main battle pass happened. I shifted down to speed 13 and overloaded both disruptors, heading back to the planet to get decent range to both during the turn, and get my information gathering finished off. The Feds had ended turn 2 near the planet again, and the CLH headed off to moon for turn 4 transports, while I went after the POL.

We ended up with a range 1 pass around impulse 10, with main weapons fire happening slightly earlier. Thanks to turn and sideslip restrictions, I was able to hit him with a drone as the pass ended, and if I had looked at the impulse chart earlier, could have gotten him with a suicide shuttle as well (as it was, it got crippled by phaser fire, and spent the rest of the scenario wandering around trying vainly to get to the POL. The F5J took two internals through the #2 shield (Hull & Aux Con), while a disruptor damaged the POL's #1, and the drone collapsed #2, followed by good close-range ph-2 fire to do a warp hit, take out the #1 phaser, and almost all the cargo and hull. Not still combat effective, but the padding was largely gone.

I spent turn four recharging phasers and starting work on the down shield, and keeping it away from the Feds drove me further out of the way than I intended. I dropped down to speed 11, and stayed there for turn 5, while the POL went up to 15, and the CLH to 14 (increasing to 17 for turn 5). The CLH kept to 6 ECM the entire time, making sure I had no good shots at it as it continued to transport up two crew units a turn. Towards the end of turn four, I got a phaser shot off at the POL to damage the #3 shield, and then missed with an overloaded disruptor on Impulse 1 of turn 5 as it pulled out of range.

At this point, it was time to pull down some extra power, and try to maneuver a bit more, as I wasn't getting any more solid shots at the POL; but that would cost overloads on the disruptors. However, things got interrupted by a too-hurried re-reading of the victory conditions, and we missed the 'all surviving' part of the Federation's victory condition, leaving us with the 'at least 10', which Mark was up to now. A quick look showed that I couldn't really intercept either ship if it went to disengage.

And yeah, that was wrong. Oops. On the other hand, Mark only had three turns of transports needed left (generally all at the moon, and the POL had picked up the uninfected crew there already too), and I was not going to get another close pass like the first one if Mark had anything to say about it. Overall, I needed to be a lot more aggressive of a Klingon commander. I concentrated on the information-gathering first, so I wouldn't need to worry about it, but even with the EW shift, I finished that off on turn 3 without trouble.

Of course, killing a CLH with a F5J takes a fair amount of work, and the POL is the one that can hurt you, so it's the only real viable target. But while it's not as well armed, being nimble and a regular crew makes up for a lot. Just don't get caught in a short-range tussle unless you need to save the CLH. I'll admit I wasn't as gung-ho going into this one as some of the other scenarios, as I find it only moderately interesting. But once again, I find just having a planet on the map can do a lot to change the nature of maneuvering, and this one gives a better reason to hang around it than most.

A turn 1 dash for the POL and anchor it... nah. Most likely you can't get there that fast. If the POL doesn't want to fight, you have have to force it to save the CLH, or force it towards a corner of the fixed map, and while possible, that's not something I normally think in terms of (I tend to prefer floating).
Twitter Facebook
6 Comments
Mon Mar 2, 2020 7:19 pm
Post Rolls
  • [+] Dice rolls
Recommend
18 
 Thumb up
 tip
 Hide

Konya wa Hurricane Alliance Turn 18

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
My ongoing F&E game with Byron continues to go slow; both of us have delays, though I'll admit to being the bigger source of them.

The overall Alliance economy grew 32EPs this turn (after exhaustion effects. The Kzinti capital came out from devastation to pump another 13 points into their economy (before exhaustion), the Federation is still liberating their territory and picked up 23 points, and the Gorns picked up a province. The Hydrans lost a point, but the situation there is becoming more and more untenable for the Coalition there, and there is now a Hydran BATS over the capital.

Builds:
Federation: DVL, BC, TG, NCA, 10xNCL, NVH, NSC, 3xDW, 2xDWA, 5xFF, 4xFFE, NCL->NSC
Kzinti: CV, NCA, 2xCM, MEC, 3xDW, 4xFKE, CV->CVH
Gorn: DNH, BC, CMV, HD, TG, LTT, BDE, 4xDD, CL->CLE
Hydran: LGE, RN, MKE, DWE, 3xCU, PGC, PDU

Despite having a couple B10s available, the heavy ship situation is sliding away from me with Byron building two excellent heavy raiders, and the Gorns already having their DNH. He's also getting into heavy fighters, though I have a few of those already thanks to the Lyran CSV.

The Hydrans moved the LGE and new PGC into the Raid Pool and concentrated on picking off garrisons in their space, killing a LTS, crippled F5, and F5S as well as disrupting a Lyran province. The Kzinti disrupted one Lyran province, one Klingon province as well as hitting a Lyran-held Kzinti province and killed a Lyran DW garrisoning Kzinti space. The Federation put the DVL into the Pool and hit three garrisons in their space and disrupted three Klingon provinces. The Gorns hit two ships in their space (one of which evaded, and the other was lost), and two more in Federation space. A DNL took a lucky hit from the Klingons to be crippled, while a WE reacted out of a Federation Raid to a Gorn one (targeting a SNB), the WE then evaded, but the SNB failed its cloak roll and was killed.

There is always some gratification in seeing a fair number of crippled enemy ships heading out of your space for repairs; sadly he has the money and facilities to make sure they return while I continue to struggle with my backlog. And another note to show how things are going is that Byron moved the Kzinti FRD in the Barony into the capital.

The Hydran fleet moved out to Klingon space, overwhelming my remaining pinning forces again, and hit the next BATS in line. The Kzinti mostly occupied themselves fighting in their own space on the supply line to 1407, but also sent a fleet back to the Klingon capital. Meanwhile, Federation moves concentrated in southern Klingon space, largely going after my depot in 2014 (original Klingon border BATS + Lyran BATS + auxiliaries), as well as the minor planet in 2216.

On the Romulan border, Federation forces shifted back northward (not everything shifted, but there were no offensives in the SW 'wing' of Romulan space), putting a large number of ships on the two Federation planets just within their border. The Gorns tried to draw the Romulans out with moves that stopped just short of the border. One happened late, and landed on the NZ planet with intent to take it, so I reacted out to defend it. Over in the east, he pinned a force on the last BATS in line while moving a fleet unopposed to the 4812 SB.

External image
Hydran theater.

External image
Kzinti theater.

External image
Klingon theater.

External image
Romulan theater.

While the Romulan priority has been to try and hold on to the planets at the corner of Federation space, the SB trumps that and two reserves went there, leaving only one to go to 3711. Similarly, two Klingon reserves went to their capital to try and keep the Kzinti out while the mess there is cleaned up. A Klingon and Lyran reserve went to save 1506, and one Lyran reserve was out of range of all combat (the third one was already at the Klingon capital).

Battles:
1505: SSC: Klingon: dest F5L
2515: SSC: Klingon retreat
3514: SSC: Romulan withdrawl + cloaked evasion
4009: Romulan: dest SN
1013: Klingon: dest F5; Hydran: dest CU
1214: Klingon: dest BATS, 2xcripF5
0916: Lyran: crip CW, DWG, FF; Hydran: dest CU
0816: Klingon: dest E4; Hydran: dest DG
1404: Lyran: dest DWS
1506: Lyran: dest FF; Kzinti: dest EFF
1411: Klingon: crip F5E; Kzinti: dest FFK
2216: Klingon: dest 2xPDU; planet captured
2213: Klingon: dest cripF5
2014: Klingon: dest BATS, LAV, 2xFTL, crip AD5, E4A, capture NCL; Lyran: dest BATS; Federation: dest NCL
2114: Klingon: dest D6; Gorn: crip CMC, capture D6
1914: Klingon: dest D7; Federation: dest FFE, crip FF
3515: Romulan: crip SKE; Federation: dest FF
3612: Romulan: dest KE; planet captured
3711: Romulan: dest NH, KRC, KE, 2xSP, SKE, 3xSN, crip SPB, SPM, SK; Federation: dest CF, crip 2xCA, 5xNCL, DW, DWA, FFB, FFE, planet recaptured; Gorn: dest DD, crip CLE, COM, 2xBD
4309: Romulan: dest SKG; Federation: dest 2xNCL
4710: Retreat after refused approach
4809: Romulan: dest CE
4812: Retreat after refused approach

The Gorns tried to pick off a pair of D5s in 2515 with a HD, BD, BDS squadron (giving me a -4 disadvantage in SSC), but the Gorns were way too overconfident ('2' on 2d6...) so the Klingons pulled out with no damage to find a better day to die.

Mostly the Hydran front was a bunch of walk overs where they sacrificed frigates (often with half their line consisting of such, including one ad hoced into the outer escort slot of a carrier) for better damage, but in 0816 a good Klingon force, good die rolls and a heavy EW advantage allowed me to kill a cruiser.

The Alliance's return visit to the Klingon capital took some thought. My reserves plus BG Harbinger was a good force, but the Kzinti fleet was also large (though bulked out with FFs) with good fighter reserves. I eventually decided to accept approach and try to do some damage before he came in to finish off the crippled secondary SB. I managed a denser line (B10V Insatiable was a big help), and a 1-5 split on the die rolls allowed me to do twice as much damage, and the Kzinti left. With my denser line, I had an advantage on approach, I had a D5M to kill ships, and if it went the full three rounds of approach, the Kzinti force wouldn't be very effective when he finally got to the defenses.

Klingon infrastructure continues to collapse with the Federation taking a planet in the southern Empire, and the loss of the dual BATS (Klingon/Lyran) in 2014. I still had a number of auxiliaries staged there and lost them all for little more than fighters. I did have enough to direct on an NCL the first round, and a lucky '2' captured it, and it survived pursuit. In the next battle, the Gorns returned the favor to capture a D6. Byron isn't too big on using captured ships (...and he is building enough already), so he may scrap it. Certainly the expense of turning it into something good like a D6S seems a bit excessive.

The Romulans aren't entirely out of Federation space yet, but Byron did a good job getting them off of the two planets there. I had a single small line at 3612, and retreated out rather than see half of it crippled, giving up a KE in the process (I had hoped to evade out, but the VUL failed on the first roll). The combined Fed/Gorn fleet over 3711 was a lot bigger than mine, though my fighter reserve was a little bigger. I stuck it out a few rounds, forcing him to take decent casualties with overall good rolls, while losing ships to the DNT. Byron crippled an entire SPB group on the first round, which gave me a real problem as it was going to be vulnerable in a retreat. Stuffing a BHF into the group and going for -3 leftover points helped, but I did also run him out of a lot of ships including parts of his carrier groups and all the fighters.

Meanwhile, in 4309 we had a round of combat that neither of us wanted over the neutral planet in the Gorn-Rom NZ. Byron was going to retreat out after offering approach, but I didn't want him stripping the defense PDUs to make seizing it easier later, so I accepted. I certainly came out ahead, but the Romulan navy is still feeling a bit fragile.

Coalition: 381.3 EP (x2) + 520 (bases) + 795 ships (/5)=1600.6
Alliance: 446.4 EP (x2) + 445 (bases) + 860 ships (/5)=1681.8

So not only has the tide turned, but the Alliance is now officially winning on VPs, much earlier than I had expected. This is a combination of the Coalition economy contracting at a furious pace, and the Alliance picking up about 100 VPs. Most of that is also the economy, and the fact that most of that is the unreduced Federation economy just makes it worse. Overall, my ship count is almost exactly the same as last turn, but the Romulans lost 8 ships overall, which was made up for by the Lyrans having a quiet turn. The Alliance has picked up 45 ships overall; more or less spread around, though the Federation alone is up by 23.

The good news is that I had no real disasters this time. Losing the double-BATS at 2014 for relatively cheap hurts some, but it was certainly an important target, and I do have bigger worries. I'm more surprised that the Kzinti did not spend any real effort trying to take half their space back from the Lyrans, or that if they were going to to go for the Klingon capital again, that there was no Federation help.
Twitter Facebook
0 Comments
Fri Jun 21, 2019 7:59 pm
Post Rolls
  • [+] Dice rolls
Recommend
21 
 Thumb up
6.00
 tip
 Hide

SH176 Kobol's Rock

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
A couple weeks ago, Mark came over for a day of SFB. I was originally hoping to squeeze in two small scenarios, but the first one turned out to be slightly bigger than we thought, and we needed to do a fairly thorough rules review first. We had a fairly long talk about all sorts of things afterward; there's lot for us to catch up on.

Module M expands the boarding party combat system in a number of ways, including a proper abstract system for combat on a planetary surface. To my surprise, a couple years back, Mark expressed interest in the scenario provided to showcase those rules. The Kzinti are besieging a Klingon-held planet, and are making one final push to take it. Normally, they could just slowly grind their way in, but previous assaults have failed, and a Klingon fleet is approaching to retake the system at large. As such, there is only ground combat. As that (and regular boarding party combat) only happens at the end of the turn, the entire impulse procedure is skipped, and instead there's an abbreviated sequence where the Kzinti move around their troops, then the Klingons can move theirs, and then it's time for the combat.

The general structure of ground combat is that each hexside of the planet (which ordinarily fills one SFB hex) is a separate 'combat location' (this ties into the normal ground base rules, where they are set up on particular hexsides). Each of those has three 'control stations', and, if it's a defended planet (as opposed to the 'defender' having beamed down just before you did), each of those has two defense systems. The control stations act a bit like the control systems on a ship; you can give them up instead of casualties (two casualties instead for a single station), and the other side can force the issue by expending four casualties they generated. Having at least two of the control stations generates a bonus in combat, and the defense systems have to be knocked out first, and they act as a pair of extra boarding parties (each).

It should be noted that despite the details, it all abstracts down to strength points. Ground combat uses the exact same boarding party combat results table, which is purely a 'fire' table, no odds, or anything like that are looked at. Shuttles can transport troops, and support the fighting directly, where they provide two extra strength points, and take two hits to kill (this translates to three of the normal combat hit points per ground combat hit; the Ground Attack Shuttle counts as four boarding parties, and its better armor only takes two hit points per ground combat hit, causing it to need to take four hits...). There's a whole bunch of other types of troops and shuttles that boil down the same way; in fact the other types of 'boarding parties' generally act the same as regular ones here, as the bonuses are just better results tables on specialized actions.

The Klingons are defending with 25 boarding parties per side of the planet, while the Kzinti have 200 boarding parties, and good mobility. Even with the single admin shuttle and GAS the Klingons have per side of the planet (which can move one hexside per turn while staying immune to fire from the ships up in orbit) adding another six effective BPs, it looks pretty grim. However, those six defense stations add another 12, which means the base setup is 25+6+12=43 equivalent BPs, and the scenario defines that only up to 50 strength can be used in any one location per turn. The Klingons also have a set of two tanks and four ground combat vehicles in one location.

I ended up taking the Kzinti, who can move 20 BPs per turn by transporters (more at the non-combat rate, which means they're nothing more than targets on the turn of arrival, but with the 'remote area' rules, it could have been worthwhile, as Mark would have to go hunting for them first), and have 12 admin shuttles and 16 GAS for 'airlift' and fire support. We pencil and papered everything with notes except the shuttles (and I found that a helpful planetary combat diagram had been printed in Captain's Log #17 a week later...), which we used counters for, and its been long enough that I don't have the best recollection of the sequence of events.

I started by organizing some of my shuttles into flights of one Admin and two GAS (which is 12 strength with the shuttles loaded with boarding parties), and put a set above each of three areas (with the hexsides labeled by the usual directional nomenclature of SFB, so that A-F are the six sides going clockwise around the planet; I put shuttles over B, C, and D, while the main Klingon defense was a A), and transported 20 boarding parties directly to C.

It was while we were working things out that we remembered the extra 12 strength from the defenses, and we realized this was indeed not going to a walkover. ...And I lost most of the initial party, for doing minimal damage. Though I did kill an Admin shuttle. In fact, that was a part of my early strategy. I spent 4 points to kill Admin shuttles, mostly to limit his mobility, so I had a better chance to isolate areas and pound them later. I'm not sure if it was worth it as opposed to just trying to burn out his defenses, but I don't think it hurt too much in the long run either.

Mark had adjusted some of his defenses too, so on turn 2 I aborted my landing at B, but kept the shuttles there, while sending out a second wave there and elsewhere, and of course sent more troops in. With a lot more on the ground, things started going better, and I really started straining Mark's defense of C. (I think I killed another shuttle or two.) After that, my pressure on him steadily mounted, with Mark taking a lot of damage on his various shuttles as combat raged across half the planet with my forces landing with more troops beaming down directly every turn. Mark just took partial damage on the shuttles, leaving them fragile, but still worth the same amount offensively.

I got lucky with two turns of relatively bad die rolls from Mark. However, the casualties in my troops were mounting quickly. In B, where there was some heavy fighting, I eventually pulled out (even beaming ten boarding parties back to orbit while the shuttles took off with the rest) and transferred over to C while grimly hanging on in D. I'd damaged some of my shuttles in this process, but mostly took it on my boarding parties so as to preserve my ability to move. In the end, Mark lost most of his assets, while I kept my shuttles, but the cost was high.

Once the defense finally cracked, I shifted back to B and mopped up in D while leaving a garrison in C. Eventually it went to a minimal 3 boarding parties (needed to hold the three control stations), but as the Klingons move last, I needed to avoid him moving in behind me. D, and then B fell, and I massed to take out E. With a better idea of what I was doing, and a lot of Klingon shuttles dead, I took it... and then declared the scenario over as a draw. I could defend against the limited Klingon ability to make counterattacks, but I'd taken 172 casualties, leaving me with 28 boarding parties to do that and then press on to F (avoiding all the nice tanks and armored cars in A). With all the shuttle cover, I probably could have taken F and held everything. By the victory conditions, the Klingons holding 5-10 control stations (with three per location) is a draw. If I took F, that'd get the Klingons down to three, and a Kzinti victory, but nearly 75% losses, and the prospect of losing most of my shuttles (which were all damaged) in the assault took the heart out of me.

Obviously, I could have planned and executed the invasion better. Probably transporting to a remote area at the non-combat rate on the first turn would have been better, even with some losses from patrols. Then a few shuttles could join them, and I'd hit the max of 50 in an area easy. I also parcelled the shuttles out over several turn instead of just putting everything out at the beginning. It did leave some much-needed flexibility, but threatening to swamp another area or two with a massive shuttle landing would keep him pinned down.

Looking at the tactics section now, there's some interesting notes. Mark basically fought to the last man, keeping the defenses intact until there was no other choice. Preserving a few boarding parties by running for the remote areas has possibilities (that we didn't even think of). I'll loose a few less men, as the combat breaks off a round early, but then I have to send out teams to hunt them down before I can strip the place to a minimal garrison, which keeps me distracted while working on the other locations.

At any rate, neither of us expected much from the scenario, but it definitely made us think, and got us very familiar with the ground combat section procedures. I wish there was another scenario or two like this (maybe not entirely focused on the surface) that used a greater variety of equipment. There's several shuttle types presented in Module M, but all you have here are normal Administrative shuttle and the GAS.
Twitter Facebook
0 Comments
Fri May 3, 2019 9:38 pm
Post Rolls
  • [+] Dice rolls
Recommend
18 
 Thumb up
 tip
 Hide

Konya wa Hurricane Coalition Turn 18

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
After the disaster and near-ending of the game last turn, this has slipped far down the priority list, but the game does continue. Bryon (and I, to be honest) is hoping we can get this to the introduction of PFs, which is getting close.

Income took a fairly deep cut this time, with the Klingons losing about 25 EP, and the Romulans down another 6. The Lyrans were up 1.3 EP due to a lack of raids into their space, for a total contraction of 30.7 EP (all before exhaustion), for a total income of 285.975 EP after exhaustion. Unlike last turn, I actually mostly prioritized new ships, planning to return to an emphasis on repairs next time.

Builds:
Klingon: B10, C7, D7, D5W, 5xD5, 2xAD5, F6, 2xFWE, 3xF5, F5J, B10->B10V
Romulan: NH, FHF, 4xSP, SPM, 3xSK, SEH, WE, [BC]->G-BC, WE->KE, SP->SPM, SK->SKE
Lyran: DN, TGP, NCA, CW, CSV, CWE, DW, 3xDWE, 3xFF, FRD, FTM

The Klingons cancelled their C8 for an extra roll on B10-3 (which got 5 & 1...) and it is now a couple turns from completion (34 points), while B10-2 Insatiable finished, and was converted to a B10V. Meanwhile, a D7 was substituted out for the first C7, starting the overall trend to bigger cruisers with CR 10. The Lyrans built a second scout-carrier, but the Romulans still need to find hulls and budget for their free fighters (another CNV would be nice, if expensive).

Both the Klingons and Romulans put a war cruiser into the the Raid Pool. Overall, raids did not go well. No raiders were damaged, much less destroyed, but called up POLs still managed to cause most of them to retreat. The Lyrans hit Kzinti space with both of their raids, and succeeded with one. All four Klingon raiders and three Romulans went for Federation space, and destroyed one FF, while disrupting three provinces. The SHR went after the Fed LTT in Gorn space again, along with another raider in Gorn space, but neither got anywhere.

The Klingons have a major cripple backlog to take care of, and the Romulans have a few more cripples than I'd like, so it was decided to keep their operations fairly minimal. The Lyrans meanwhile have worked through just about all their cripples, and went on the offensive, working to take a decent chunk of Kzinti space to force them off of an offensive deeper into Klingon space. Elsewhere, the Lyrans were limited to moving back towards supply, now that their grid in Klingon space had collapsed. The Romulans did a limited offensive, pinning a Federation reserve, while trying to retake some of their captured planets.

External image
Lyran offensives.

External image
Romulan counteroffensives.

The Federation only could move two reserves, and only used a couple ships from them, keeping me from taking 2106, and interfering with a Romulan sweep of ships out their space (I'd lost track of the fact that there was a reserve in range), while the Kzinti reserves went to the small fight in 1505.

Battles:
3318: SSC: Federation: crip FF
1410: SSC: Federation dest cripFF
2106: SSC: Klingon: dest 2xF5
1202: Kzinti: dest POL
1101: Kzinti: dest POL
0801: SSC: Kzinti: dest POL
1003: SSC: Kzinti: dest POL
1504: Retreat after denied approach
1505: Kzinti: dest CM, 2xDW; Klingon: dest E4A
3415: Federation: dest DWA, DE; Romulan: dest 2xSK, crip KE
3612: Romulan: crip WE, capture planet
3509: Federation: crip NCL, FF; Gorn: dest BDE; Romulan: dest VUL, K7R, crip 2xSK

Byron had left a single crippled Federation FF next to the Klingon capital, and I sent out a couple of cripples to finish it off, and retrograde back home. About a day later I remembered that the Federation 2nd Reserve was in range of the fight if he wanted to give me a big problem (...and himself a logistical problem), but the 2nd sent a CA and FFS to save 2106 instead, and my F5Ls took care of the intruder with no problem. The latter fight rolled 4 vs 11 in SSC, and I figure the Fed squadron just did a textbook Kaufman Retrograde to the poor F5s.

Part of the plan was to get the Kzinti Earl's and Duke's fleets on 1407 out of supply, and limit his options next turn. The reserves into 1505 threatened that, but I managed to retreat off of there (taking the planet, even temporarily would have been a good bonus, but not why I was there) onto the reserves, which weren't very big, and took losses trying to stand up to a full line.

Sadly, after all of this, the main plan failed, as I hadn't realized the Kzinti had one more POL to call up, which can restore supply to 1407 after a lot of effort to cut it off. If I'd actually taken 1504, it would have still worked, and I might have been able to do that, at a cost of notably more casualties, and probably fewer Kzinti casualties.
Twitter Facebook
4 Comments
Thu Dec 20, 2018 6:00 pm
Post Rolls
  • [+] Dice rolls
Recommend
21 
 Thumb up
3.50
 tip
 Hide

SH3 The Coming of the Meteor

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
Patch and I recently finished off a try at this old scenario (I think it's from the original pocket edition) in the Basic Set. It has some of the 'feel' of the Original Series adventures, and is a neat premise:

In Y160 a massive meteor was spotted headed for the industrial colony on Pollux IX. The Federation heavy cruiser Kongo, under the command of Captain Phillip Kosnett, was dispatched to avert the disaster. When Kongo arrived on the scene, however, Kosnett discovered that a Klingon frigate was shepherding the meteor.

The meteor starts 10 hexes away from the planet (and moves on the first impulse of every turn, so it's about nine turns away), with the F5 Khedive next to it, and Kongo 22 hexes from them. The asteroid can be towed by a ship facing away from it and tractoring it for 16 impulses (...speed does not matter). Victory is purely by how close to the planet the asteroid gets to the planet, with even two hexes being a danger as small fragments will still hit the colony, killing a tenth of the inhabitants, and causing a draw. The asteroid can be 'destroyed' (broken up into pieces by 400 points of damage), which does not affect the ability to tow it, and does make it less dangerous to the planet.

We had to have a bit of discussion about the MacGuffin, as while the scenario quite clearly calls it a 'large asteroid', it doesn't call out that section of the rules (which I hadn't known of, I remembered the general asteroid field rules, and the small moon rules...), and defines that it will destroy any unit in a hex the asteroid enters. Large asteroids don't prevent ships from entering its hex (and they can even land on it), or block fire, or anything you might expect of something large enough to crush whatever is in a hex 10,000 kilometers across. We did go with the large asteroid rules, and drop the normal asteroid 'dodge' rules as it is supposed to be a singular object instead of a debris field. It's one place where clearer instructions would help.

Patch volunteered to take the F5, and a few impulses in realized just what he was in for. (I had expected he'd stick me with figuring it out.) He went a reasonable speed of 16, while I went 18 to get near the asteroid on the first turn. The CA is at WS-2, or the second turn of arming of photons, and I fully overloaded one, while keeping the others standard, while the F5 is at WS-1 and had to charge up phasers, and it also put up 2 points of ECM to discourage longer-range shots.

On the first impulse, the asteroid moved, and Patch lowered shield #1 to put a transporter bomb in front of the meteor. This did change my initial approach plan, but we both commented later that while a great opener, a second mine behind the asteroid would have been much better, and forced more maneuvering from me (as it was, I just sideslipped enough to bring me around behind the meteor). As I headed in, the F5 got underway, and did a clockwise loop that ended with the disruptors out of arc until he turned directly in on Impulse 26, with the range 15 and closing. Patch fired at that point, hitting with one disruptor on shield #1, and we finished the turn at range 11.

Only being three hexes from the meteor, I slowed to speed 10, charged up a tractor beam, partially overloaded a second torpedo, set one for proximity fuse, and held a HET in reserve in case Patch got too close. Patch stayed at 16, and dropped all EW while I put up 6 ECM. Patch turned away on Impulse 2, and on Impulse 4, with him about to go out of arc, I hit him with the prox photon on the #3 shield. Patch then increased his ECM to 1, presumably to discourage any more of that....

On Impulse 13, I slipped in ahead of the asteroid, and attached the tractor beam. On 16 Patch started combing back in for a run at my rear, and I launched a shuttle to provide some cover and/or drone defense. On 20, Patch fired his overloaded disruptors at range 8 as he was about to go out of arc again; thanks to my ECM shift, only one hit on shield #3, partially countered by the one point of reinforcement I'd afforded there. On 26, he turned directly in, launched a drone the following impulse, and my towing took effect on 29 to get it out of line of a direct impact with the planet.

External image
Turn 2, Impulse 4, showing movement throughout the turn.

For the third turn, I kept up the tractor while still paying for speed 10 and an HET, and 5 ECM with 1 ECCM which left very little power for everything else. I finished overloading the second photon, and started reloading tube D, and had to pay a half point out of batteries to balance it all. Meanwhile, Patch's F5 dropped to speed 14 and didn't bother with EW.

I launched a second covering shuttle on Impulse 4 as Patch continued to come in. The first shuttle fired at the drone, but only did three points on a bad shot. Patch came in with a second drone following, and the second shuttle fired at him on 14, doing 2 points to #4 on another bad roll at range 2. On 16, the F5 passed directly behind the CA on the oblique, and unloaded it's best shot at range 1: with the +2 shift, one disruptor missed, and the five phasers did 18 damage, I blew the remaining batteries to take five internals, which knocked out two phasers and one power. I had fired back with two of the side phasers to do 11 to his #2, and the other two were used to shoot down the second drone and finish off the first one; which thankfully weren't Type-Vs. (Patch pointed out that it's really rough to take two-space drones when you only have one four-space rack.)

I seriously contemplated cutting the tractor as he came out of his pass, and burning the HET to pump three photons (two overloads) and two phaser 1s into a rear shield at point blank range (it was, after all, the general plan of all those expenditures), but I'd already had the second towing move, and the third one would come up before the end of the turn, and the F5 was empty. So, I stuck it out, got the third hex, which pulls the asteroid completely out of range on Impulse 29, and Patch basically conceded at the end of the turn.

Afterword

With the asteroid out of the way, I could basically go slow near it, and keep myself pointed at the F5. It would get pounded if it tried to tow the asteroid back into range. I could have pounded him during turn 3, but sticking with the asteroid meant I didn't need to go back to it later.

There were a few more options that Patch had: He could have put another TB into where I'd go when I towed, he could have powered up a suicide shuttle (though he was probably a bit thin on power) and launched it during his pass. I wasn't going anywhere, and it'd absorb even more of my fire. A scatterpack could have been interesting... but Patch still needs to get Advanced Missions.

I knew it was going to be an odd match, and wasn't sure how it would play out. One thing I finally realized is that it was written back when plotted movement was the norm, and that could give the F5 the edge it needs here. Even with plotting, the F5 knows where the CA is going eventually; the CA has fewer guarantees about the F5.

Suggestions:

There seems to be a habit of not going back and really reexamining older scenarios when republished in later editions. Along with plotting, it looks like this was written before 'speed is life' became a real mantra, and it's expected that things will proceed more slowly. Also, the asteroid really needs more clarifications in the rules. I've got a few ideas on how this scenario could be refitted, though I don't have any idea how balanced any of it might be.

First, I think the variation in SH3.62 might work a lot better. Adding a CL and D6 to the mix could be very interesting. It evens the firepower out a lot, and more importantly, the D6 and F5 can threaten to try and dodge around one Federation ship to get at whichever one's towing.

Second, it's too easy for the CA to park next to the asteroid and just put everything into reinforcement for a turn or two. I deliberately didn't do this, and kept to speed 10, but there was no reason go even that fast on Turn 3. It gets even worse if you use mid-turn speed changes to slow down right as you get to the asteroid, and speed up when it's time to break the tractor. My thought is instead of spending sixteen impulses towing, you must spend so many movement points (calculated off of Practical Speed) to move the asteroid one hex. This could allow faster towing, though getting a CA to go really fast takes some doing, and possibly means cutting power elsewhere. Eight movement seems like a likely base figure to try, since that means speed 16 for the same rate as the original, though if you're using mid-turns speed changes, it should definitely be something like 10 movement. (This could also be translated into energy expended if you want to make it harder for the F5 to tow back, or to make the CA and D6 the obvious towing candidates in the four-ship version.)

Lastly, this seems like a perfect situation to give the Federation some firing restrictions. Chasing down the F5, blowing it up, and then towing the asteroid out shouldn't be too hard (it is a fixed map), but it's not very Star Fleet. There's already a rule that the Klingon captain can claim "it was all a horrible mistake", and all combat halts. A simple solution would just be to use the Non-Violent Combat system (D6.4), which would allow the F5 to feel safer about losing a shield or two. (We've had a scenario where it was used once, and small ships can generally not worry about the big CA too much.) A more custom rule could be interesting though: Don't fire unless the Klingon has. Don't fire anything that could cause internals (on best rolls) unless the Klingon has done internals.
Twitter Facebook
2 Comments
Fri Nov 30, 2018 8:20 pm
Post Rolls
  • [+] Dice rolls
Recommend
19 
 Thumb up
4.00
 tip
 Hide

Konya wa Hurricane Alliance Turn 17

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
The Alliance economy climbed by forty points this turn, showing just how out of control the situation is. Even the Hydrans went up 14 EP before exhaustion (for an actual increase of 10.5 EP), with the Gorns showing the smallest improvement. After exhaustion, total income was 378.1, and repairs hit a new record, with the Gorns providing most of the increase. This was also helped by getting Orion back, which I just had had no chance to deal with last turn.

Builds:
Federation: DNG, CA, CF, NCA, 10xNCL, NCD, NSC, 3xDW, 2xDWA, FFB, 9xFF, BP+, 2xFF->FFB
Kzinti: NCA, 3xCM, 3xDW, 2xFFK, 2xFKE, FF, CVL->CVD
Gorn: CCH, BC, CM, 2xHD, LTT, BD, 2xBDE, BDS, DD, BD->BDS
Hydran: MKE, HR, DWE, 4xCU, MB->BATS

The good news is that Kzinti shipbuilding is curtailed, skipping both their CV and BC. The Hydrans are mostly treading water, but are installing a BATS on their capital, which I probably won't be able to dislodge. And of course, the Federation and Gorns are building ships much faster than I can.

Raids concentrated on the Klingons, with all four Kzinti raids hitting Klingon provinces near the capital, and three Federation raids just south of it. Five of these resulted in disruptions, and I lost a JGP and D5 and had a D5 crippled in the reaction fights. The Hydrans hit two Klingon garrisons in Hydran space, and part of the captured neutral zone. I didn't bother responding to the last, but the increased garrison groups paid off by destroying the single existing THR. Another Federation raid hit a D5 near the Kzinti border, but good rolls and a reacting F5L killed the DNL for no loss to the Klingons. The last two were in Federation space, one which killed a D5 while a WE cloaked away from the last one. The Gorns sent one raid into west Federation space to kill a garrisoning F5, and Romulans escaped from two attempts to kill garrisons just inside Gorn space, and a last raid disrupted a Romulan province.

The Hydrans naturally attacked toward the Lyran-Klingon corner again, and I intercepted a good amount of it, but he was still able to put a good fleet of about 20 ships on 1013.

The Kzinti started driving south immediately, scattering fleet elements on anything in their way, including sending a bunch of Auxes after the garrison on 1504. The North Fleet started a fight at the NZ planet in 1506 by reaction, but further reinforcements freed up the Kzinti garrison already there. Federation forces moved into to pick off various small forces, and partially pinned the Lyran and Klingon fleets at 1810 before the Kzinti sent another wave at the Northern Reserve SB and BG Harbinger at 1611.

Then the 3rd Fleet moved to the Klingon capital. Or tried to, as NE Fleet moved to intercept... which caused consternation. Byron had entirely missed that it was there underneath the Lyran Fire Squadron marker. Since it was a heck of a thing to miss, I let him go back and rework his moves some, but no matter what, he wasn't going to have nearly as much in the capital as he'd originally thought. Part of the original planned move was to pin the Klingon 1st Reserve on 1312 (assuming it didn't react), which he gave up on, but I reacted it into the capital at one point anyway, as he still had good opportunities to do so with the Kzinti, and it was to his advantage to keep the capital as lightly defended as possible (I'm not sure why he didn't spend some more effort on it, as well as the 3rd Reserve on 1209).

Over on the Romulan side of things, two major thrusts developed: one near Tholian space aimed at picking off the BATS in 3319 and retaking 3415 as well as threatening the SB, while Gorn and Federation forces also concentrated on the corner area near all three. One major thrust also went to 3612, which I stopped part of, but not enough to save the planet, since that would just make 3711 vulnerable.

External image
Second strike at 1013.

External image
The Kzinti flood.

External image
Federation tidal wave.

External image
Losing the rest of the are near the Tholians.

External image
Gorn border offensives.

Naturally, all available reserves (three: Klingon 2nd and 3rd, Lyran 3rd) went to the Klingon capital. The Lyran reserve in Hydran space went to help near the Hydran capital, and one in 0707 had nowhere to go. I had to think long and hard about how serious 3518 was, but sent both Romulan reserves in range to make sure of the SB. Meanwhile, the 2nd Reserve went to save BATS 4010.

Battles:
0916: SSC: Hydran: dest 2xCU
2008: SSC: Klingon: dest cripD5
2313: SSC: Klingon: crip F5; Federation: crip FF
2411: SSC: Klingon: dest 2xF5
2612: SSC: Klingon: crip F5
2514: SSC: mutual retreat
2613: SSC: Klingon: dest cripF5, F5S
3115: SSC: Romulan: crip WE
3412: SSC: mutual retreat
3609: SSC: cloaked evasion
4108: SSC: cloaked evasion
3319: Romulan: dest BATS; Federation; crip 2xFF
2308: Klingon: dest E4A
2309: Klingon retreat
2815: Klingon: crip D7C, F5; Gorn: crip HD
2012: Klingon: dest F5; Federation: crip FF
2215: Klingon: dest BATS, cripD5
2214: Klingon: dest FRD, SAV, cripD6, cripD5, crip F5E, E4A; Federation: dest DE, capture planet; Gorn: crip 2xCM
1507: Klingon: dest F5L
1809: Klingon: crip D6, F5; Federation: crip CA; Kzinti: crip CM
1810: Klingon: crip F5; Lyran: crip CW; Federation: dest CA
1611: Kzinti: dest FKE
1411: Klinshai: dest MB; Kangor: dest SB, 4xPDU, devastated; Kangorax: dest 2xPDU, devastated; Kangor-Ultra: dest 2xPDU, devastated; Kadrak: dest 4xPDU, crip SB, devastated; Drakis: dest 2xPDU, devastated; Shadrak: dest 2xPDU, devastated; Klardon: dest 4xPDU, devastated; Vordon: dest 2xPDU, devastated; Aradon: dest 2xPDU, devastated; Klingon: dest D5W, 2xD5, F5E, crip 3xD7C, 2xD6M, 6xD5, D5V, AD5, 3xF5, F5S, capture MEC; Lyran: dest CWE, DW, FF, crip STT, CW, CWE, DW, FCR; Federation: dest BT, NCA, CA, NCL, 3xCL, 7xFF, crip CA, 14xNCL, 5xDE, 2xDW, 8xFF; Kzinti: dest 2xMSC, CLD, 2xDW, FKE, SDF, crip CC, 5xCM, 5xMEC, CLE, DW, 3xFKE, 2xEFF, 3xSDF
1511: Kzinti: dest FF
1509: Retreat after declined approach
1504: Lyran: crip 2xCL; Kzinti: crip FF, capture planet
1506: Klingon: crip F5, F5E; Kzinti: dest 2xFFK, crip FFK
1013: Klingon: dest BATS, F5W, F5, F5J, crip D7, 2xD5; Lyran: dest MB, 2xDW, crip CW; Hydran: dest 3xRN, LN, crip RN
1815: Klingon: crip D5, 2xF5
0717: Klingon: dest F5L, E4, crip D7C, F5; Hydran: dest CU, crip HR
0816: Hydran: dest POL
2211: Lyran: dest DW; Gorn: dest BD
3518: Romulan: dest SKE; Federation: dest FFE
3612: Romulan: dest WE, SN, K5S; Federation: crip 2xNCL, capture planet
3415: Romulan: dest SP, SK, K5, crip KE; Federation: dest FFE, crip 3xNCL, capture K5, capture planet
3611: Romulan: crip SK, SKE; dest CL, crip FF
3413: Romulan: dest SNB; Federation: crip FFB
4110: Romulan: dest BATS; Federation: crip FF
4109: Romulan: dest SNB
4310: Retreat after refused approach
4411: Retreat after refused approach
4010: Retreat after refused approach

Some of the smaller combats went fairly well, including great rolls in 0916 to wipe out two CUs (who had little business taking on a DW and LTS to begin with...), but Byron managed to arrange for one retreating group to overrun the survivors of an earlier battle in 2613, and that wiped them out.

Byron put the entire pile of cripples from the destruction of the 3rd Fleet SB onto a patrolling F5V group in 2308, which sacrificed the escort to get away. This trick of finding battles for cripples so they can retrograde further has been getting common lately. The F5V was forced to retreat onto a waiting Gorn CM, but poor rolls allowed it to get away from that.

Overshadowed by other events, there was no real backup for my repair center on 2214. The Federation/Gorn force was bigger and better than what I had available, leaving me to pull some cripples out and a LAV.

I had the clever idea of using a fighting retreat to pour BG Harbinger into the capital from 1611, but of course Byron sensibly didn't resolve that fight until later. At the capital itself, I started fighting at one system per round, determined to extract the highest bill I could over my own defenses. The outer systems quickly got stripped, and then it turned into the real brawl as he started taking on the two non-capital SBs, with me putting a line in front of both. Byron directed the PDUs over a couple of rounds, (when he didn't drop damage on '6's to force auto-kills...) while leftover damage reduced my mobile fleet to less than two lines worth. (Later on, I realized that cripples could go to the static forces of any system; handy if I wanted to sacrifice a few ships for more rounds against him... but it took a while to wake up to that.)

Midway through, I used the capital SB's fighters to refill empty bays elsewhere on the same round that Byron captured a Lyran FF, and he took a round at Klinshai itself to blast the Lyran MB set up there, the FF aiding in a deception operation. I had command difficulties elsewhere, but but at the capital, I could bring out Insatiable, the almost-complete B10 that's worth 19 on the line (no crippled side, so it still needed protecting in form). Another '6' allowed him to kill the MB with 26 left over.... The Klingons mauled a MSC and dropped 61 with a mere '3' roll. A ground attack to kill a PDU while he was there failed, and I ended up capturing the MSC. (With that damage, other ships died, but the random roll came up with the best of all of them.)

To my surprise, Byron left after only crippling the second SB. He's correct that it'll be a problem to repair, and isn't worth a lot crippled, but I figured he'd want finish it off now rather than later. I picked off a couple things in pursuit, but both sides are pretty shattered. Of course, he has a lot more scattered around than I do, and the Klingon economy isn't worth a lot at the moment.... Even after going through the logs in detail, I don't know how many rounds this actually was, but it was probably in the mid-teens.

The fight in 1504 was interesting in that the Kzintis had 2xLAV, 3xSAV and no escorts. They ad-hoced a bunch of FFs so they couldn't just be directed on, but it meant there was very little capable of pursuing me when I retreated (especially since I directed on one of the few FFs not busy escorting a slow unit), and Byron only realized the problem at that point.

I had the advantage at planet 1506 (where the North Fleet had reacted to) but I wasn't entirely sure I wanted to tangle with a pair of CVDs with 24 fighters to punch through. But I went in, and picked off a couple FFKs in pursuit, though crippling the F5E is going to give me trouble, since the only spare light escorts there are E4As.

The Klingons rolled three better than the Hydran on approach to 1013, doing two less damage to a decidedly superior line. (If the Lyran STL hadn't shocked last turn in the same place, I probably would have won the approach; that round at any rate.) I forced him to go through the co-located Klingon BATS to kill the Lyran MB, and kept rolling well enough to kill ships, which is something I've been needing to do to the Hydrans. But now the Lyrans have almost no supply into Hydran space.

Planet 3612 was something of a disaster. The Federation force was slightly small, so I decided to damage it and retreat, but but I was a good group, and I ended up sacrificing half my group to keep the carrier group intact rather than slowly cycle it through the repair process. I should have just sacrificed one ship and left, which I had almost done.

Coalition: 413 EP (x2) + 530 (bases) + 793 ships (/5)=1673.2
Alliance: 409.4 EP (x2) + 435 (bases) + 815 ships (/5)=1579.8

Losing the Klingon capital was a near thing. I had set up last turn to try and hold as many Alliance ships out of that vulnerable location as I could, which is why it didn't happen. If I hadn't had the NE Fleet in the way (which hadn't moved on my turn because of its position in the way of the 3rd Fleet on 1910), the capital would have fallen, and I would have surrendered the game. There's no real recovery from losing the Klingon shipyard at the best of times, and there's certainly no SB that the Klingons can guarantee will be out of reach of a powerful Alliance force for six turns right now.

The last several turns has been me going from one disaster to the next, but this was the first one I was... partially ready for. I had hoped to hold the outer systems better than I did, and the economy is going to be a mess. The current plan is to go on a bit longer, but this game is on a short countdown to an end. There's not a lot I can do to push back on the large number of places that are falling apart, and those are staging points for ever-larger numbers of Federation ships to pound what's left. Worse, important Lyran bases have been taken out, so they will be largely useless next turn (and after unless I can re-establish some).
Twitter Facebook
1 Comment
Sun Oct 7, 2018 6:52 pm
Post Rolls
  • [+] Dice rolls
Recommend
15 
 Thumb up
2.00
 tip
 Hide

Konya wa Hurricane Coalition Turn 17

James Lowry
United States
Sunnyvale
California
flag msg tools
Avatar
Microbadge: Star Fleet Battles fanMicrobadge: Fascinating!Microbadge: Legendary Monthly Video Game Geek Review Contest winnerMicrobadge: KHAAAAAAANNNN!!!!!Microbadge: ASL fan
The overall Coalition economy continues to contract, with the Lyrans picking up a little bit of ground, which didn't make up for either Klingon or Romulan losses, which happened in spite of both of them surveying a new province. Adjusted income was 309.75 EP.

Builds:
Klingon: D7C, D7, D6J, D5W, 7xD5, AD5, F6, 6xF5, D6V->D6U
Romulan: CON, FHF, 3xSP, SPC, SPM, 2xSK, SKE, SEH, WE, SNB, WE->KE, SP->SPM
Lyran: BC, STT, NCA, CW, CWE, CWS, 2xDW, DWE, 2xFF, FCR

The Romulans worked through most of their cripples from last turn's SB assault, but the Klingons are still dealing with a large number of cripples, and are currently cancelling some of the smaller ships to deal with it. They did convert the last D6V to a D6U, as I had planned, which eliminates that class of odd 5-point carriers. B10-2 rolled well, and is all but guaranteed to come out next turn. B10-3 only rolled a '2'; by average rolls, it should come out on 21, but there's an outside chance that both could show up on 19, which might be a problem.

The Klingons put a repaired D5 back in the Raid Pool, and added an existing FD7 to start filling out the expanded pool. The Lyrans raided a Kzinti province, and killed a Federation FF that was holding a Klingon province, and preventing supply to BG Harbinger. The Klingons raided three Federation provinces, and the C5 was sent to try and crack the wall of ships built around the Orion Enclave, but all the raids were run off, with one D5 being crippled. The Romulans raided two Federation provinces, and one Gorn, and made another attempt to kill the supply LTT in 4007 (partially to draw out a ship from 4006, which was a likely target during the turn). Both Federation provinces were disrupted, but the LTT was merely forced to retreat, and a Gorn POL ran off a FFH to keep that province from being disrupted.

A primary problem was dealing with the solid wall of ships Byron had erected around the Orion Enclave to keep me from keeping supply to it, which would enable me to keep it neutral. There were a number of strong fleets nearby to complicate matters. The biggest problem was the fact that the Third Fleet had shifted forward to 1910 and stayed there, putting it in range of way too many important targets in Klingon space

But that meant the garrison on the 3rd Fleet SB was much reduced (consisting of the 4th Fleet, no longer needed near Kzinti space). So I started concentrating on tying down the reserves as best I could, and making one last try at it before the Federation started destroying everything I had left near it over the next few turns.

The Romulans had a heck of a time working their way out of the knot of Federation fleets near their border, but managed a good force to reclaim the NZ planet. To the north, they struck at the last Gorn border BATS, and had a decent fleet to take one of the Gorn-Fed border BATS while pinning a reserve there.

The Lyrans kept their activity light, going for 1504 in Kzinti space while backing up the Klingons elsewhere and keeping ships available.

External image
Limited goals.

External image
Limited goals.

External image
The big push (again).

External image
Trying to pull back more than a stump.

External image

More BATS destruction.

The small Hydran reserves split between reinforcing 0416, and the small fight in 0916, while both Kzinti reserves went to 1504 (the only fight in range). The Federation 1st R (the only one completely unpinned) went to 3210, and two of the 4th R ships freed up there went to 3111, and the end of the wall around the Orions. The 3rd R in 2610 still had five ships free, and they went to 2509, which allowed the 2nd R there to send five ships to SB 2211. One Gorn reserve was stuck in 2610 with the bulk of the Federation reserve, and the other was stuck in 4006.

Battles:
3511: SSC: Federation: crip FF
3111: SSC: Romulan: dest WE
3412: SSC: Federation retreat
3413: Federation: crip FF; Romulan: crip SN
0416: Hydran: dest TR; Lyran: dest CWG, 2xDW, crip CW, DW
0916: Hydran: crip CU; Lyran: DW
0717: Hydran: dest LNH; Klingon: dest E4
1504: Kzinti: dest FKE; Lyran: dest DWE
2012: SSC: Federation: dest POL
2211: Federation: dest SB, CA, 2xDE, crip BT, CA, 9xNCL, DE, 5xFF, FCR; Klingon: dest 2xD6, D6D, D6S, AD5, D5S, F5L, crip D7, 3xD6, AD5, D5G, MD5, D5S, 2xF5, F5E, wound PT; Lyran: dest DW, crip DW
2509: Retreat after declined approach
2610: Federation: crip CA, NCL; Gorn: dest BDE, crip LTB; Klingon: dest F5W, crip 3xD5, 3xF5
3210: Federation: crip NCA, NCL; Romulan: crip SP, SK
3415: Federation: crip 2xNCL; Romulan: crip 2xSP, 2xSK
3315: Romulan: dest SNB
4408: Gorn: dest BATS
4006: Gorn: dest BATS, crip COM, DD; Romulan: dest SKF, K4, crip SPF, WE

Given an initial 53-point difference in ComPot, I wasn't sure that I actually could take the 3rd Fleet SB, but it was the best shot I had to limit Byron's ability to strike into Klingon space. One weakness he had was a limited number of CR10 ships, so I destroyed escorts to drive the CVA off-line, and Byron did some of my work by self-crippling a battle tug. Sure, it's really efficient to repair, but my first goal was to get his line density down. By round 3, the difference was 17 ComPot, and I had the ships and fighters to take that, and some good rolls was helping. If he'd been willing to self-kill ships (and the Feds build enough), he might have squeezed another round out of it, but it probably wouldn't have been worth it.

Byron naturally accepted approach in front of 2610, where the Gorns are setting up a MB. Two '6's from the Alliance in a row kept me from getting at the base, and I didn't have what it took to go four rounds and have any sort of fleet left, so that job was left undone. Maybe I can get there again, but it's getting more and more unlikely....

The Federation rolled much better than the Romulans over 3415, but ran out all their fighters in the first round, and then gave up the NZ planet. But they gave better than they got, and overran a two-ship garrison next door on the way out.

I had just about given up all hope of killing the 3rd Fleet SB, and as the Federation offensive starts reaching into Klingon space, its presence was something I really couldn't afford. So killing it is a big win for me, and I got it for relatively cheap. It did leave me a bit out of position, and the cost of taking it out may still turn out to be excessive. But in the long run putting much of the south-center out of reach will pay off. I just have to survive the short term while reorganizing.

Meanwhile, the Romulans have finished off the Gorn border BATS, and hampered their reach that way. Federation pressure is mounting, but the Romulans can... mostly put up a stubborn defense. The Federation has a lot of strength near the rim of the galaxy now, and I expect a fair amount of havoc near Tholian space. This means I'm probably not reestablishing contact between the Klingons and Romulans, and the KR spare parts are winding down....
Twitter Facebook
0 Comments
Mon Aug 27, 2018 4:53 pm
Post Rolls
  • [+] Dice rolls

1 , 2 , 3 , 4 , 5  Next »  [11]