For the last two years the Hydran Navy has been able to ambush damaged Coalition ships and booms leaving the combat zone. With its escorts, it would take a position near a battle sector and, when ordered to do so, would activate its sensors to sweep the area and send its fighters on an immediate strike against an unsuspecting Coalition ship.
This worked for two years before the tactic was analyzed and a Klingon D5 squadron was ordered into the area to take revenge against the Revenge.

Can be done as a campaign with varaible targets. Source is CL25 Hydran Pegasus Class History.

HMS Winged Revenge: The second of the PGVs, it entered service in Y175 and was used for a series of ambush raids. With its escorts, it would take a position near a battle sector and, when ordered to do so, would activate its sensors to sweep the area and send its fighters on an immediate strike against an unsuspecting Coalition ship. This worked for two years but the tactic was eventually analyzed and the ship was destroyed by a Klingon D5 squadron that had lain in wait for such an opportunity

By Ryan Opel (Ryan) on Thursday, April 12, 2012 - 08:59 pm: Edit

SHORTSWORD CVD-8 was built as the only Kzinti Interdiction Carrier in Y173, using a battlecruiser hull to save money. Originally intended to feed fighters to other carriers, the loss of other carriers forced the Shortsword into the front lines. The ship was sent on repeated deep strike missions, ravaging the Klingon and Lyran logistical networks. The ship survived until Y184 when it was caught between Klingon and Lyran PF groups and shot to pieces and left as a lifeless hulk.

Ideas include the logistics strikes as well as it's final battle.

By Ryan Opel (Ryan) on Thursday, April 12, 2012 - 09:00 pm: Edit

RAPIER CV-4 was completed in Y167 and assigned to the Home Fleet. It fought the Lyrans in Y168-170 as the Kzinti defenses collapsed and the homeworlds were devastated. Refitted as a CVS, it remained with the Home Fleet and was equipped with experimental Streak Fighters in Y172; these fighters proved less effective in combat and were replaced after the pilots refused to engage a Klingon frigate squadron. Rapier fought during the entire General War, was converted to carry heavy fighters in Y179, and was destroyed by the Klingon C7 Decimation only a week before the ceasefire.

I like the Raiper vs the Decimation battle.

By Ryan Opel (Ryan) on Thursday, April 12, 2012 - 09:03 pm: Edit

USS Star Leopard in cooperation with the Kzinti BF attack the Lyran supply convoy supporting the Lyran forces about to deploy to the Federation Front

By Ryan Opel (Ryan) on Thursday, April 12, 2012 - 09:04 pm: Edit

(R2.135) SCOUT POD (P-SC): This pod was a curious pre-General War design, from a time period when no one knew what role long-range scanners and electronic warfare would play in the coming conflict. It was championed by budget minded members of the Federation Council because of its multiple uses. In peacetime, it could temporarily improve the sensor network in a given area, helping to stop piracy and smuggling. (This proved of little help.) In wartime, it could be deposited in open space and used by an admiral to coordinate ships and other forces over a wide area. (The only attempt to actually do this proved disastrous as a Klingon fast raider destroyed the pod, disrupting control over a wide area.)

Pod desperately trying to call in help before the Fast Raider arrives.

By Terry O'Carroll (Terryoc) on Saturday, April 14, 2012 - 01:15 am: Edit

THREE BROKEN OATHS
Submitted by Terry O'Carroll

In Y181, Star Fleet's main effort was focused on the Romulans and the Operation Remus campaign. The Klingons took advantage of the Alliance's diversion of ships to the Romulan front to launch aggressive raids on Federation and Kzinti targets. The Federation feared that the Klingons might launch an offensive while their largest carriers were committed elsewhere and performed a series of deep raids to disrupt Klingon logistics. A squadron of Klingon drone bombardment cruisers, which had recently completed a raid of their own, was ambushed by while awaiting rendezvous with their ammunition tender. Historically, the squadron commander, Captain Zutalors, ordered the squadron to scatter. The raider pursued Oath of Service and destroyed it, but the other two ships escaped. This was done in accordance with Klingon standard doctrine, but Zutalors was (posthumously) criticized for not "fighting his ships to their utmost" by a board of review. A student at the DSF academy created a simulation to discover whether Captain Zutalors had been right or wrong.

MAP: Map is fixed, with a small gas giant centered in 2215.

Klingons: 3x E7D Warrior's Oath, Oath of Allegience, Oath of Service
Federation: 1x DNL

Special Rules:
1. The Klingon ships have just finished launching a series of drone raids and their racks are nearly empty. For each drone rack on each ship, roll one die and subtract two from the result. The rack contains that many spaces of drones. The ship has no other reloads of any sort. Extra drones may not be purchased as Commander's Options.

2. The Klingons have been ordered to delay the raider until other ships can arrive. Any Klingon ship which leaves the map is considered destroyed. The Federation ship must disengage by turn X or it is considered destroyed by arriving reinforcements.

Victory Conditions: The goal of both players is to do better than the historical commander. Victory is determined by the number of points scored by the Federation player.

0 or less: Klingon victory
1 : Klingon marginal victory
2 : Draw (historical outcome)
3 : Federation marginal victory
4+ : Federation victory

Score 1 point for crippling one of the E7Ds, 2 points for destruction, 4 points for capture. If the DNL is crippled, lose 2 points (it will probably be run down and destroyed). If it is destroyed, lose 4 points. If captured, this is an automatic Klingon victory.

Variations: Use a C5 and a Federation or Kzinti defending force. Or add a guardship (does not count for victory purposes) and use a B9 as the attacker!

Notes: this scenario was inspired by a note in Captain's Log #35, the Class History of the E5 and E7, page 33, last paragraph.

By Gary Carney (Nerroth) on Tuesday, May 08, 2012 - 02:27 am: Edit

According to the Early Years timeline in SFB Modue Y1, the first starships used by the Klingon Empire in Y2 (or thereabouts) were old sublight hulls left behind by the Old Kings; their first recognisably "Klingon" ships had to wait until Y17 before they started sailing off the production lines.

However, it is the lines themselves which I wanted to refer to; specifically, those which the Klingons inherited from their former masters. According to the R-section for the Klingon D3 (YR3.2) the Empire at the time had been able to build a fleet larger than that of any other Alpha Octant empire thanks to Old King leftovers. One in particular is noted in (YR3.4); a shipyard important enough for its loss (due to "a devastating Kzinti raid") to combine with the losses in the Tholian wars to reduce the Klingons to "merely the equal of their enemies".

Where on the F&E map was this Old King yard? What kind of technology did it contain, and would it have still been of use to the Empire in the modern era?

And given the technical imitations of the time, how interesting might a scenario be that shows just how the Kzintis were able to pull off such a feat?

By Terry O'Carroll (Terryoc) on Friday, August 10, 2012 - 12:14 am: Edit

I have an idea for a scenario that will make Jean's eyes cross when she proofreads it. It features a half-flotilla of Orion gunboats in combat against an Andromedan cargo variant of the Intruder, which is carrying cargo pods filled with highly explosive fuel. The title is...

"Three Bucs, a Galleon".

By Jean Sexton (Jsexton) on Friday, August 10, 2012 - 09:25 pm: Edit

* Looks at Terry *

By Steve Petrick (Petrick) on Tuesday, August 14, 2012 - 04:26 pm: Edit

Ryan Opel:

In re: HMS Winged Revenge

There is not much of a scenario here. Basically a PGV (with two DWAs) and their 14 Stinger-2s (might have Mega Packs, might not) and two Stinger-Hs, tangle with three Klingon D5s (might be a D5L and two D5s, or a D5L and two D5Ks, or a D5L, D5K and D5D, possibly D5FKs). Might add some casual fast patrol ships to each side (up to six for either side). Your problem is that the scenario would pretty much have to have the PGV unable to run for some reason (if it was on a strike, staying to fight the D5s would be stupid as it allows time for other units to gather and interdict the ship's escape).

Since it used its sensors for a sweep to find a target for its fighters, you are not going to find it sitting still waiting to be attacked. So I am not sure how the D5 squadron gets close enough to do enough damage to keep it from getting away.

SHORTSWORD CVD-8

This is a group with a MAC and (at worst) an AFF. Being attacked by PFs. Normal rules provide for only three flotillas in a battle, which is complicated by the presence of both Klingon and Lyran PFs. In Y184 the Kzintis had restored their border, and the Lyrans had largely withdrawn their forces from Klingon space to defend their own frontiers. The WYN cluster being where it is creates a dilemma for the strategic background to explain where the "odd" flotilla came from (whether a Klingon flotilla in Lyran space or a Lyran Flotilla in Klingon space). Again there is the problem of why the Kzintis did not run. If the Kzintis are at WS-II or better, they should be able to "breakout" from an encirclement, even if it costs them a lot of fighters.

RAPIER CV-4

While the ship was destroyed by a C7, it was obviously not done in single combat. The C7 is a standard one (not a C7S or C7V), so it was clearly leading some kind of task force. The Rapier by definition had a MAC and at least an AFF with it, in addition to six LKFs. A C7 is not beating that kind of force on its own, and would be destroyed itself if it tried.

USS Star Leopard in cooperation with the Kzinti BF

Pretty much a raid by two ships on a convoy. Okay, it happened, what makes it interesting? An Orion CA robbed my Large freighter, is this interesting enough for a scenario?

(R2.135) SCOUT POD (P-SC):

The amount of time an FD7 would need to destroy a scout pod is quantifiable (point blank overrun). If you put something there that might make the FD7 think twice about such a move, you have changed history.

By Steve Petrick (Petrick) on Wednesday, August 15, 2012 - 03:50 pm: Edit

Please understand that there is more than just "this is listed." I can find "this is listed," I need something that can be created that exceeds a "force list and historical outcome." Something that (to take the case of the PGV) explains how the "D5 squadron" was able to bounce the PGV without the PGV simply running. What made the Klingon action possible? Obviously to "win" the Klingons have to destroy the PGV, if it escapes history is changed and the Hydrans win. The fate of the escorts is irrelevant. So how are the Klingons bouncing this scout carrier?

By Stewart W Frazier (Frazikar2) on Wednesday, August 15, 2012 - 07:18 pm: Edit

Pure luck...

The only thing I see is that the PGV ran close to a 'dead to the universe' squadron in hideable terrain...[instructed to 'cold camp' the area]...

By Steve Petrick (Petrick) on Wednesday, August 15, 2012 - 07:27 pm: Edit

Stewart W. Frazier:

The background makes pure luck untenable:

"This worked for two years but the tactic was eventually analyzed and the ship was destroyed by a Klingon D5 squadron that had lain in wait for such an opportunity"

The above HAS to part of the scenario set up because it is the history that is being worked from. There has to be some failure that brings the PGV into where the Klingons are waiting because they analyzed the pattern and were Johnny on the spot, but if the PGV is in motion, acceleration and ECM is likely to get it out of this problem even if you box it in with the D5s. If the D5s are lying doggo, they will be to slow to run down the PGV before it hits disengagement speed.

By Jim Davies (Mudfoot) on Wednesday, August 15, 2012 - 08:31 pm: Edit

The PGV had deployed its fighters and was hiding in something orrible like an asteroid, dust & radiation zone until they came back. Whilst this blocked its sensors, it also made it much harder to be found. But the Klingons were there first, having predicted that it might choose this location to hide.

Of course the PGV & escort(s) are still likely to run, except that they start at speed 0, can't disengage by acceleration because of the dust and want to recover the fighters, which reappear on turns 5, 6 and 7 (undamaged but without fusions).

The nature of the D5 squadron wasn't specified, but including a D5S makes it reasonable for the Klingons to find the Hydrans.

The Klingons turn up on separate map edges on turns 1, 2 and 3, having been dispersed around the zone.

By Dal Downing (3deez) on Thursday, August 16, 2012 - 12:08 am: Edit

Just throwing this out there for thought. The Klingons know there is a Carrier lying in wait out there. What if they turned the tables. What if instead of the Klingons lying in wait they actually played possium to sucker the carrier in.

After some minor skirmish the klingons made some radio chatter to the effect that a couple of thier cruiser were shot up to bad to make it out of the combat area and were arranging for a Repair Freighter to meet them.

They had actually done this a couple of times before they finally got lucky. The Carrier picks up 3 cruisers limping to a remote area to rendevoue with a repair ship. The cruisers played the role to the hilt, they made sure to leak a little atmosphere, rigg thier impulse engines to give of higher than normal radiation reading just to make it look good. Is the Freighter just a Freight, a Q Ship, An Auxillary Carrier who knows.

The Hydrians can't resist so they charge. The klingons act like they are trying to scatter just to to make sure the PGV steps too far into the snare.

Terrain is option whatever you think makes a good backdrop. The point is the Hydrans don't know the moment they launch thier fighter the fight was already over.

Victory conditons for the Hydran is how much does it cost the klingons to kill them.

By Steve Petrick (Petrick) on Thursday, August 16, 2012 - 01:12 pm: Edit

One problem is that apparently the PGV background data as given in CL#25 is wrong in any case. Apparently when CL#25 was done, someone forgot to look at the SSD of the PGV (R9.90) and note that it does not have special sensors.

By Thomas Mathews (Turtle) on Thursday, August 16, 2012 - 01:27 pm: Edit

SPP, add a little scout to the Hydrans and a 4th D5 to the Klingons. The Klingon force consisted of a 2xD5s, D5L, and a D5S. The D5S could be a F5S or E4S if needed for balance. I certianly like Dal's line of thinking.

By Terry O'Carroll (Terryoc) on Monday, August 27, 2012 - 10:57 pm: Edit

In Captain's Log #40, on page 100, (R4.A22) notes that the Federation and Klingons cooperated to provide the Romulans with newly-built Klingon ships to convert in Y192.

The proposed scenario assumes that the Klingons completed construction of the ships without installing weapons or security stations, since the Romulans would just rip these out and replace them with Romulan systems in any case. Leaving the weapons out saved desperately needed time and money. Instead, dummy disruptors were installed and the ships were sent to one of the remaining Romulan starbases for conversion as they were completed, along with a convoy of KR spare parts. As the convoy neared its destination, it was attacked by Andromedan marauders.

Klingon force (set up first) 1xF5W (see special rules below), standard convoy consisting of 4x F-S and 2x F-L.
Andromedan force: [Not sure, 1x Python? Conquistador without satellite ship?]

Special rules: Historically, the Andromedan commander did not know that the "escorts" lacked heavy weapons, and assumed that they did. Before the game starts, take an ordinary deck of cards (including jokers). The Klingon player draws one card, looks at it, and sets it aside. If the card is black, his ship is a normal F5W. If it is red, it is a K5W but the plasma-G torpedoes are marked destroyed and cannot be repaired by any means during the scenario (the systems are completely missing). If the card is a joker, the systems are missing but the convoy has either two small Q-ships OR one large q-ship replacing the appropriate freighters.

The Andromedan ship can only gain information about the Klingon ship by what it does or does not do. (Alternatively, tactical intelligence rules could be used).

The Andromedan force has only a limited amount of time before overwhelming Romulan reinforcements arrive. (I don't know what a realistic but short amount of time is for the Andromedan).

The freighters must keep moving, if they "circle the wagons" it is likely that more Andromedans will show up via the RTN.

Victory Conditions: Klingon: Preserve your own ship and as much of the convoy as possible.

Andromedan: inflict as much damage on the freighters as you can, then escape. Damage on the escort ship is not important, your mission is to sink freighters.

Tactics: The Klingon player must bluff the Andromedan player into thinking that he has disruptors, or thinking that he doesn't when he does, or just that he's got a Q-ship. The Andromedan player must aggressively attack the convoy but avoid getting a point-blank blast of overloaded disruptors when you least expect it.

By Steve Petrick (Petrick) on Wednesday, October 31, 2012 - 04:02 pm: Edit

I said: "Please understand that there is more than just "this is listed." I can find "this is listed," I need something that can be created that exceeds a "force list and historical outcome." Something that (to take the case of the PGV) explains how the "D5 squadron" was able to bounce the PGV without the PGV simply running. What made the Klingon action possible? Obviously to "win" the Klingons have to destroy the PGV, if it escapes history is changed and the Hydrans win. The fate of the escorts is irrelevant. So how are the Klingons bouncing this scout carrier? "

HMS Winged Revenge Scenario Concept:

The Winged Revenge would perform its missions in company with a scout. The scout would withdraw once the fighters were launched because the scout itself is a valuable asset. The Scout, however, would continue to perform sweeps as it withdrew in order to decoy Coalition forces, i.e., draw them into chasing the scout which is heading for the safety of Hydran lines.

The Winged Revenge would launch its strike, and after recovering the fighters, would withdraw on a different track, thus not running afoul of Coalition forces futily chasing the scout.

The Commander of the Klingon D5 squadron figured out what was going on, and instead of chasing the scout (as he had been tricked into doing twice before), instead deploys his ships to cut off the retreat of the Winged Revenge.

The scenario begins with the Winged Revenge group waiting for its strike to return, however, the strike will never return. The Winged Revenge cannot wait for them, and must somehow break through the Klingon force and escape. A dozen fighters and their 13 lives (12 pilots and one GIB on the EWF) are easier to replace than the Winged Revenge and/or its escorts.

Hydrans: Winged Revenge and two DWAs (each 2xStinger-2) set up first within two hexes of hex 0115, heading A or B, Speed 10, WS-I.

Klingons: Set up D5L in hex 4215, heading E or F, Speed Max, WS-III.
Set up D5K in hex 4201, heading E, Speed Max, WS-III.
Set up D5k in hex 4230, heading F, Speed Max, WS-III.

If Winged Victory exits the 42xx map edge with 50% or more of its warp power intact, the Hydrans win a Marginal Victory irrespective of any other outcome. The Hydran Victory level is raised by one for each Hydran escort that also exits the map edge with at least 50% of its warp power remaining, and by one for each Klingon ship crippled, and by two for any Klingon ship destroyed.
If Winged Victory exits the map with less than half of its warp power, the Klingons win a marginal victory, otherwise the Klingons have lost. The Klingon victory level is raised by one for each additional Hydran ship that exits the map with less than 50% of its warp power remaining, or which is destroyed. The Klingon victory is raised two levels if the Winged Victory is captured, and by one level if any other Hydran ship has been captured.

Balance Factors: Replace one DWA with an AH, in this option the Stinger-2s of the replaced DWA are retained and moved to the Winged Victory at start.
Add one or more G1 Gunboats (and appropriate mech-link refits) to the Klingon force (no PF shield refits).
Add one or more Harrier Gunboats (and appropriate mech-link refits) to the Hydran force (no PF shield refits).
Delete the K-refits from one or more Klingon ships.
Add mega-packs to one, two, three or all of the Stinger-2s.
Move the Hydran "At Start Hex" (the one they must set up within two hexes of) closer to the 42xx map edge, but be careful as this will make it harder for the Klingons to link up and mass fires and easier for the Hydrans to just run off the map.

By Steve Petrick (Petrick) on Wednesday, October 31, 2012 - 07:00 pm: Edit

Change #1 to the above.

The background pretty much indicates that the Winged Victory was destroyed in Y177 (entered service in Y175, used for raids for two years). So mega packs are not available as a balance factor, nor are Hydrans PFs OR Interceptors. Klingons have H1 Inteceptors available as a balance factor. So use of PFs by either side (Klingons can still use Interceptors as a balance factor) would have to be a Variation, and not a Balance Factor. (Same for Megapacks on Hydran fighters.)

A Variation might be to "trick out" the Hydran carrier group. Add up to six PFs, but some would be "variants." A Valkyrie Fi-Con for fetching replacement fighters (maybe two?) and launching more distant strikes and a Cargo PF for fetching other stores. The other three or four could be combat variants. Mega-fighters might be added (on the escorts). (This Variation would have to, for balance, add G1s to the Klingns.)

Another variant might have the Winged Victory having already recovered (but not rearmed) its fighters when it starts running, and add H1 inteceptor to the Klingon force.

You can of course (as a variation) replace the Klingons with Lyrans.

By Steve Petrick (Petrick) on Tuesday, November 13, 2012 - 05:02 pm: Edit

Seriously guys.

Take the "hooks" and suggest what you think would be a good, interesting, and balanced scenario.

Note, scenario balance does not have to be something where both sides have a chance to kill the other guy, but the victory conditions should allow both sides a chance to win.

Sometimes you win even if you are destroyed. A victory condition that simply requires the weaker force to hold out until Turn #3 (when an arriving larger force will then crush the enemy raiding force because you kept them from escaping, or forced the raiders to turn back and not reach the valuable convoy behind you).

Look at the hooks and see if you can suggest why the battle happened.

The Kzinti CV Rapier fought a C7. Why? What would make such a battle both balanced and interesting? A C7 by itself cannot fight a full CV group. If it was just the C7 and the CV fighting, what was going on? Why did the carrier accept a one-on-one (no escorts, maybe no fighters or less than its normal complement) fight with a C7? Did its captain simply assume he would win the duel? Was there some strategic reason for his carrier to have to make that stand? (Was the C7 damaged and trying to get back to Klingon lines when the CV intercepted it, and the CV itself was fresh from a battle which had left its escorts too crippled to accompany it, but the chance of destroying the C7 was too good to pass up?)

The purpose here is not for you to just say "these are hooks, please make a scenario." The purpose is for you to say "this is a hook, this is what I imagine based on what is known of the game background, does this work? I think it would be an interesting scenario." And for me to say "well, we need to resolve this or that issue." or perhaps "I see where you are going, this works, let me think about it and see if I can work soemthing up." Do not forget to consider terrain (not just strategic terrain, i.e., where the borders/fronts are, but maybe tactical terrain might make the fight interesting), but do not simply use terrain as a crutch, add it when it will help make the battle interesting.

Many hands make for light work, and many minds working on scenario concepts might come up with far more interesting things than my one poor one can.

By Stewart W Frazier (Frazikar2) on Tuesday, November 13, 2012 - 07:34 pm: Edit

Hmmm, carrier without escorts -

Previous battle, light escort destroyed, heavy escort crippled. Move to rally/repair point. Nearby healthy ships pulled to deal with emergency (carrier/fighters remains for 'patrol' duty). Carrier may not be 100% (storage fighters broken out), stores are variable (what was left after emergency called)

[Emergency deepens, rally point being moved (bug out), carrier detects one enemy ship on/near intercept course, moves to block/deflect?]

C7 going on raid (with PFs?) moving through 'empty' area / returning from raid with damage (may have wounded PF)

[Carrier called to deflect raiding C7 toward intercepting elements / slow to allow for better interception]?

Just off the top of the head stuff...

By Thomas Mathews (Turtle) on Wednesday, November 14, 2012 - 12:08 am: Edit

C7 with PF's Certainly a good thought.
CVS has 4 - 6 fighters (balance with C7 and PFs)

FCR on way arrives turn x with fighters to replenish the CVS and act as light escort to CVS.

CVS blocking route to repair ship, FRD, convoy other such vitally important asset for the Kzinti to defend and defend at the chance of losing a vital ship.

By Thomas Mathews (Turtle) on Wednesday, November 14, 2012 - 12:09 pm: Edit

further thoughts
the CVS has minor internal damage, 5% of it's total boxes maybe? all repair rules already used so no additional repairs can be made to the CVS.

The Kzintis don't know the C7 is carrying PF's.

The Klingons win by destoying the CVS.

The Kzintis win by staying in the game until turn 10 or so in order to allow reinforcements to move into a better blocking position between the above mentioned strategic target of the C7 raid.

By Shawn Hantke (Shantke) on Wednesday, November 14, 2012 - 12:17 pm: Edit

How about a simulator battle tribute to the attack on Pearl harbor? In the SFB version you could have a fleet surprised in orbit by a cloaked Romulan CVA group. In Federation Commander you could add more ships to both sides to make the fleets bigger and in Starmada or ACTASF you could have all the historical ships represented by SFU ships. For starters 8 BBs, 2 CAs, 6 CLs, 30 DDs etc. The attacker would win by destroying the most ships possible and the defender would win by having the least destroyed.