recursal/Fanatic-Fandom huggingface dataset:
I'll Save You! No, I Will! (SH264)

## I'll Save You! No, I Will!

The neutral zone between the Gorn Confederation and the Romulan Star Empire is not bereft of civilization, but most of the life-bearing planets were not worth what it would have taken in terms of combat to absorb them into the economy. The result was that both empires tacitly traded with these planets for what goods they could get, and occasionally tried to disrupt the others’ trade (there was no “Organian” agreement in this region).

This situation changed, somewhat, during the early stages of the Confederation’s involvement in the General War, but by Y185 much of the Gorn and Romulan front line was more or less stabilized along their original frontiers. While what the various neutral civilizations had to offer was still not very much, keeping it from the other side was only slightly less important than acquiring as much of it as you could for your own economy.

One of these worlds was in an otherwise nondescript system on the eastern end of the zone (closer to Inter-Stellar Concordium space than to either empire’s capital). In this case, the planet had put out a distress call: a Sun Snake had been sighted heading for their sun, and they had no technology to stop it.

Both the Gorns and Romulans dispatched their nearest ships to save the civilization. It would be nice to believe they were acting from purely altruistic reasons, but the truth was that saving the planet would allow the flow of goods from it to continue, and perhaps the grateful civilization would give trade benefits to their benefactors.

Of course to accrue those benefits it would be necessary to be the ones that destroyed the Sun Snake, and that meant stopping the other side from doing so.

## Aftermath

In a victory for civilization, the Sun Snake was destroyed before it could enter the sun. It was not, however, a shining example of cooperation. The ships of both empires were heavily damaged, but no ships were lost (except the Gorn Pterodactyl was destroyed). The civilization was unimpressed with the squabbling and bloodshed, even though grateful that they had been saved, and invited the Inter-Stellar Concordium to occupy their system. Some believe it was this invitation that actually triggered the pacification campaign.

## References

1. ↑ Various (2010). *Star Fleet Battles Module R12 – Unusual Ships*. (Amarillo Design Bureau), pp. 47–9.
Into the Rings (SH35)

## Into the Rings

After the Third Klingo-Hydran War, the two empires had very little contact with each other and covert intelligence was hard to come by for basic anatomical reasons. Both empires used a variety of means to keep track of the other.

The Klingons dispatched an F5S scout-frigate to the ringed gas giant Wyskoon to see if the Hydrans had set up a base there. The frigate launched probe drones toward the planet, but departed (to avoid contact with a Hydran patrol) before it received their transmissions. The probe drones collected the information and ejected their memory canisters at various pre-selected locations for later pickup.

Feeling it to be important that their interest in the system remain unknown, the Klingons contracted with an Orion group to pick up their memory canisters for examination.

As luck would have it, a Hydran freighter, visiting the system to scoop gas from the giant’s atmosphere, detected the approach of the Orion ship and summoned the local police patrol.

## Aftermath

The LR was able to destroy the first Gendarme with a “lucky” volley and escape before the second Gendarme arrived. This scenario became part of the
final exam for Hydran Police Ship captains.
A Kzinti with a Mission (SH118)

## A Kzinti with a MissionPart of War of Return

The small WYN squadron of X-ships was a constant thorn in the side of the Crown Prince, moving across the theater at high speed to counter a riposte here and raid a planet there. Several operations were launched to engage and destroy the squadron, but none succeeded.

As the situation became critical, the Crown Prince planned one last attempt to destroy the squadron, but it failed before it began when the designated ships had to be diverted to solve another crisis.

One assigned ship, however, remained available, and Admiral Fifth Rank Cat-who-is Resolved (commander of one of the few Kzinti X-ships and absolutely loyal to the Crown Prince) decided to conduct the operation anyway. Admiral Resolved reasoned that if he could cripple or destroy the CAX, the two DDXs would not be an insurmountable problem. The original ruse to draw the X-squadron into range went ahead as planned, and succeeded.

## Aftermath

The Kzinti ship was destroyed, but the CAX was badly crippled and knocked out of the campaign. After a heroic voyage, it returned to the WYN Cluster where it was rebuilt and served as the WYN flagship for the next decade. The lack of this ship, however, reduced the X-squadron from a mailed fist reserve to a fast raiding force and weakened the Usurper's campaign.

## References

1. ↑ Various (2017). *Star Fleet Battles Module C3 - New Worlds III*. (Amarillo Design Bureau), pp. 50–1.
2. ↑ Various (2017). *Star Fleet Battles Module C3 - New Worlds III*. (Amarillo Design Bureau), pp. 50–1.
3. ↑ Various (2017). *Star Fleet Battles Module C3 - New Worlds III*. (Amarillo Design Bureau), pp. 50–1.
Ain’t No Free Lunch (SH72)

## Ain't No Free LunchPart of Operations on the Lyran Border

During the fighting on the Kzinti border during Y181, the Alliance forces managed to lure a small Lyran squadron into an asteroid belt. The Lyran forces were cleverly divided, with each ship chasing a single Kzinti ship.

The entire point of the operation was to maneuver the Lyran flagship, the Wildcat-class battlecruiser *Bloodshedder*, into a trap. The Lyrans were unaware that a small Federation force was in the area.

## Aftermath

The *Bloodshedder* and *Reaper* were severely damaged, but managed to make their way out of the trap. The damage, however, was so severe that it would be several months before either ship could return to active service.

All four of the Lyran PFs were destroyed.

The Alliance lost several fighters and two PFs, but otherwise sustained no significant damage in the encounter.

## References

1. ↑ Various (2010). *Star Fleet Battles Module R12 – Unusual Ships*. (Amarillo Design Bureau), pp. 43–5.
Operation Tribune (SH187)

## Operation TribunePart of A\_Brief\_History\_of\_the\_General\_War#THE\_ROMULAN\_CAMPAIGN\_PLAN\_OF\_Y180

In Y180, Romulan Proconsul Octavianus Scipio launched a major fleet operation against the Gorns. The object of the operation was to bring the Gorn Fleet, under Flag Admiral S’Teken, to a decisive battle. The bait was the rich mining planet Hokan, just inside the Gorn lines.

Proconsul Scipio’s plan was to take the planet with a small force, then send in additional squadrons only in response to Gorn arrivals. He feared that if his fleet outnumbered the Gorns too drastically at any point, they would disengage, leaving him with the planet (not an inconsiderable prize) but without a victory.

## Aftermath

The first elements of the Romulan Second Star Legion let themselves be trapped at low speed too close to the planet. Reinforcements moved to join them. When the *Imperator* was destroyed, the Romulan command structure collapsed, as each Cohort tried to fight its way out of the trap on its own. The result was a disaster. Besides the *Imperator*, the Romulans lost the cruisers *Loyal Hawk*, *Intrepid*, *Havoc*, and *Impavidus*; the mauler *Spear*; and the support ships *F12*, *Talon*, *Bravery*, *Steadfast*, and *Sword*. The Gorns lost the base (which was annihilated when the Romulans briefly took the planet); the cruisers *Tricericon* and *Unity*; and the destroyers *Coil*, *Black Vigil*, and *Zilzar*. Both sides lost most of their fighters and interceptors. Most of the Romulan ground troops were annihilated or captured.

## References

1. ↑ Various (2007). *Star Fleet Battles Module M – Star Fleet Marines*. (Amarillo Design Bureau), pp. 40–2.
Constabulary Patrol (SH24)

## Constabulary Patrol

The ISC considered themselves the peacekeepers and saviours of the galaxy. Their announced policy was to prevent further wars and maintain order by preventing each race from sending military units outside of their own areas.

Few races were able to accept this service with good grace. The Federation claimed, with considerable justification, that they needed to patrol their outer areas to prevent pirates, other powers (who they did not trust the ISC to control), and the ISC itself from appropriating the wealth of the frontier colonies. Other races felt the same.

This scenario depicts a fairly typical battle in the Fornax star system. The ISC had declared the system, which had been established as a Federation colony, to be “independent” and under ISC “protection.” A small scratch Federation force arrived to relieve the ISC detachment of their duties.

## Aftermath

Heavily pressed, the ISC squadron found it necessary to abandon the Fornax system to the Federation. However, once the Federation task force left, the ISC moved in and reestablished their “protection.” Several more engagements would be fought around this, and other systems, before the Andromedans finally settled the matter once and for all.

## References

1. ↑ Various (1992). *Star Fleet Battles - Scenario Book 1*. (Amarillo Design Bureau), pp. 29–30.
Lapiz

**Lapiz** is the chief's daughter of the Star Rabbit demon tribe as well as the Demon King candidate from her tribe.

## Profile

### Appearance

Lapiz is a beautiful young girl with a buxom hourglass figure. She has red eyes, silver curvy long hair and has white bunny ears on her head. She wores a cofee "bunny girl leothard" with sime gold and pink decorations, matching high leg stockings and pink pantyhouse. She also uses a white simple coat and white headkerchief that cover the top of her head.

During her time afflicted by her illness she has her full body covered by bandanges to cover the wounds on her skin and her swollen flesh, who make very painful for her speak or open her eyes.

### Personality

Lapiz has a kind and naive personality, loving too much her father and her tribe and feeling guilty for making them suffer along her with her illness since they have to take care of her. At the same time she feel ashamed of her illed appearence and miss the looks of her face before the illness since it remembered her the times were she was free to move and was not afflicted by pain. During her meetings with Keyaru she show great interest for the stories of the outer world and legends that he told her, acting as an excited child while hearing hero tales.

## Plot

Lapiz appears with a very contagious serious illness from which she cannot get out of bed and is covered with bandages, she is analyzed by Keyaru realizing that her illness is actually a type of poison which she had been drinking daily instead of medicine having been administered by someone else. Keyaru decides to heal her, she began to feel good and cry with joy realizing that she could speak without hurting her throat, having also recovered her vision and her skin was no longer swollen, she asks for a mirror to be able to see herself again and hugs her father Carol.

## Power & Abilities

As the same way that her fellow star rabbit tribesmen she must have supeior leg strength that allow her great agility and speed to move and a great power strike while using leg attacks. Also as the Demon King candidate from her tribe she's believed to have great potential and high stats as the same way that Eve Reese.

## Relationships

* Keyaru.- For Lapiz Keyaru is a kind man that make her company in her solitude and told her majectis histories about the outside world. She feel deeply grateful with him for curing her from her illness and returing her her original looks and freedom. The two became lovers after Keyaru seduces her and she get attached to him, visiting him after he conquered Jioral Kingdom.
* Carol.- Carol is Lapiz father and the person that she most loved and trusted before meeting Keyaru. She feel guilty for making him take care of her so much and wanted him to be free from that burden.
Deadfall (SH167)

## Deadfall

In Y143, the Klingon Empire successfully rooted out and destroyed a Jindarian Caravan operating in the asteroid belt of the Selnar System. Flushed with this success, the Klingon fleet departed to look for more glory.

Unfortunately, the Klingons did not know that they had missed one Jindarian ship, although they had badly damaged it in the campaign.

Deprived of the support of their caravan, and with a virtually inactive warp drive, the Jindarian crew decided on a hideous act of revenge. They placed their crippled ship on a collision course with the main Klingon colony in the system. The Klingons became aware of the danger when a police ship sent to divert the asteroid (which has taken nearly two years to reach its current location) vanished in a hail of rail gun fire at nearly point-blank range.

The Klingon governor called for assistance, and the nearest imperial units responded.

## Aftermath

The Jindarian ship, heavily damaged, slammed into the Klingon colony's capital city and chief production center. The impact and resulting dust cloud had an extremely negative reaction on the planet's climate, forcing the Klingons to evacuate the surviving colonists. Only a few key personnel were saved by transporter from the capital, although the Imperial governor and his staff chose to remain with the city. The Klingons took the lesson to heart and suspended searches for asteroid ships in inhabited systems until a better means of detecting them could be found.

## References

1. ↑ Various (2005). *Star Fleet Battles Module F1 – The Jindarians*. (Amarillo Design Bureau), p. 31.
All our plans torn asunder (SL351)

## All Our Plans Torn AsunderPart of 2nd Federation-Kzinti War

In late Y138 the Kzinti advance into the Federation had slowed due to the distances involved. On one front they had planned to establish a base of supply by either capturing a Federation base station or destroying it and establishing one of their own nearby. With that in mind, the Kzintis assembled a task force and conducted drone bombardment in support of the attack. However, the Federation managed to partially disrupt the bombardment and defended the base with a stronger force than Kzinti estimates had predicted.

## Aftermath

The Federation and Kzinti units savaged each other with repeated overload volleys. Badly damaged, the *Thunder Song* docked with the base station attempting to capture it but was lost when the severely crippled base self-destructed. It was a Pyrrhic victory for the Kzintis, (fleet crippled/destroyed) as the Federation was at this point in a better position to repair damaged ships from the battle as well as replace lost units. *Theodoric the Great* was badly damaged in this battle but survived to fight in other battles before being destroyed by the Kzintis later in the war.

## References

1. ↑ Various (21 June 2019). *Captain's Log 53*. Edited by Stephen V. Cole. (Amarillo Design Bureau, Inc.), pp. pp. 54–55.
2. ↑ Various (21 June 2019). *Captain's Log 53*. Edited by Stephen V. Cole. (Amarillo Design Bureau, Inc.), pp. pp. 54–55.
3. ↑ Various (21 June 2019). *Captain's Log 53*. Edited by Stephen V. Cole. (Amarillo Design Bureau, Inc.), pp. pp. 54–55.
Federation Political Parties

There are usually about a half-dozen smaller parties which pick up enough votes to have a few seats in the Assembly. These parties change over time, are sometimes absorbed into the larger parties or simply disappear, and are often closely tied with the specific concerns of member planets. When the Federation was drawn into the General War in Y171, small parties with seats in the Assembly included the Collective Rights Party (mainly based on Andor), the Peace and Bread League (popular on Rigel), and the Justice Party (based on Earth and Mars) on the left end of the political spectrum, with the Originalists (mainly based on Earth, Mars, and Alpha Centauri), the Independence Party (popular on Andor), and the Freedom Party (Antares and Tellar) on the right. The Orion Pride Party has significant strength within the Orion Enclave. The OPP is non-ideological and focuses mainly on maintaining Orion interests. The Fundamentalist Faith Party tends to support political policies based on their understanding of “moral law” regardless of how impractical these policies may be. As this party includes many faiths, they do not always all agree on any given point.

It should be noted that not every politician or member of a party thinks the same about every issue, especially among the Federalists and Unionists. Generally speaking, the larger the party, the less monolithic and ideological it is; both the Federalists and Unionists are in some ways more akin to political coalitions than ideological parties, no matter what their opponents may say in election season. The average Federalist politician probably has more in common with his fellow Unionist Assembly member than he does with an Originalist or Freedom League member. Most politicians in the major parties are pragmatists, rather than ideologues, even if they paint cartoonish caricatures of their opponents on trivideo campaign commercials.
In The Open (SH170)

## In the Open

Jindarian Caravans change their locations quite frequently (at least considering the "fixed" nature of most fleets' operations). These movements are periods of maximum vulnerability and are almost always done after periods of preparation and reconnaissance.

Unfortunately, the best laid plans of mice and Jinbaros will sometimes go awry. A case in point occurred in Y172 when a Jindarian caravan was caught in deep space by a large force of Gorn warships gathered for an offensive.

## Aftermath

The Gorn and Jindarian forces savaged each other. Each side had one small ship destroyed, and several others were crippled and damaged. The Gorn admiral was forced to resign because he allowed his force to become involved in an unnecessary battle.

## References

1. ↑ Various (2005). *Star Fleet Battles Module F1 – The Jindarians*. (Amarillo Design Bureau), pp. 34–5.
Annox

This colony was the site of an important battle between the Klingons and Federation during the General War. The G4V star has no planets. An asteroid mining colony here was originally established by an Alpha-Centauran corporation in Y102 as an industrial fabrication facility, but like many colonies it expanded its operations into other fields as time advanced.

Location: Sector 2209.

## Reference

1. ↑ John Sickels (30 March 2011). *GURPS Federation, Fourth Edition*. Edited by Jean Sexton. (Amarillo Design Bureau, Inc.), p. 97. ISBN 978-1-58564-155-0.
PSS John Walsh

## Notable Commanders and Crewmembers

Bailiff \* Bobby \* Constabulary \* Deputy \* Dragnet \* Gatekeeper \* Gendarme \* Justice \* Lawman \* Militia \* Mountie \* Pacifier \* Peacekeeper \* Peacemaker \* Peaceofficer \* Posse \* Summons \* Texas Ranger \* Trooper \* Tucker \* Lt Oleg Babak \* Behan \* Callahan\* \* Deckard \* Alejandro Dominguez \* Morgan Earp \* Virgil Earp \* Wyatt Earp \* Doc Holiday \* Holmes \* Kojak \* LeBeau \* Mackie \* Malloy \* Magnum \* Mark Majors \* Masterson \* McKeehan \* Elliot Ness \* John Oliver \* Osterhout \* Darius Quimby \* Texas John Slaughter \* Richard Simms \* Sipowicz \* Sorenson \* **John Walsh** \* Watson \* White \* Williams \* Willis \* Jimmy Wilson \* Drebin \* Nordberg and about 130 others.
Negotiate! (SH130)

## Negotiate!

In Y160, the Tholians had begun deploying more powerful ship classes. In an effort to gain more information, several Federation scouts were assigned to patrol the border, scanning Tholian territory with long-range sensors.

In Y165, the scout Bowie, in a carefully planned clandestine operation, actually penetrated Tholian territory. Due to a misjudgment of Tholian deployments, the Bowie was trapped. Federation officials immediately began negotiating with the Tholians, patiently explaining that it was a navigational error, not an intentional border violation. As part of the negotiations, Captain Philip Kosnett and his command cruiser Kongo were dispatched to the scene as a show of force. Kosnett was given authority to act on his own judgment, and did so.

## Aftermath

Kosnett's diplomatic skills and the desire of the Tholians to avoid a direct military confrontation with the Federation (their border with the Klingons was a continuous bleeding ulcer of combat) defused the situation with the release of the Bowie. These negotiations, and subsequent meetings by diplomats resulted in the delivery of Federation photon torpedo technology to the Tholians a few years later.

## References

1. ↑ Various (1994). *Star Fleet Battles Module Scenario Book 2*. (Amarillo Design Bureau), pp. 30–2.
Lessons (SH115)

## LessonsPart of Seltorian Attacks on the Tholians

By the time the Seltorians began their operations against their old foes, most of the non-Tholian forces had been withdrawn for operations in other sectors. There were still a few Gorn and Kzinti ships in Tholian space, however, and despite Klingon warnings, their appearance would give the Seltorians much to consider.

## Aftermath

The Kzinti drones and Tholian photons administered a bloody nose to the Seltorians, but not a fatal one. They would consider their lessons and return.

## References

1. ↑ Various (2017). *Star Fleet Battles Module C3 - New Worlds III*. (Amarillo Design Bureau), pp. 47–8.
2. ↑ Various (2017). *Star Fleet Battles Module C3 - New Worlds III*. (Amarillo Design Bureau), pp. 47–8.
3. ↑ Various (2017). *Star Fleet Battles Module C3 - New Worlds III*. (Amarillo Design Bureau), pp. 47–8.
Heartcleaver (SH160)

## Heartcleaver

In Y184, a strong Hydran squadron broke through the Lyran screening forces and headed towards a minor, but important, Lyran colony in the Bloody Claw County. The Lyran forces in this area had been stripped of reserves by other Hydran operations and the continuing need to supply ships to defend against the burgeoning Kzinti and Federation forces as well. The Lyran Sector Commander found he had only one ship that could possibly make the interception.

The *Heartcleaver* was soon on her way.

## Aftermath

The *Heartcleaver* crippled the *Assassin* and destroyed the *Strongbow*. The Hydran Commander opted to withdraw, leaving the *Heartcleaver* in command of the contested space.

## References

1. ↑ Various (1994). *Star Fleet Battles Module X1*. (Amarillo Design Bureau), pp. 46–7.
Frontier Patrol (SL37)

## Frontier Patrol

The border areas of major empires are always active, even more so in wartime. Standard procedure was to send fighters, and later fast patrol ships, to investigate any interesting ships moving on the other side of the border.

This incident, in Y180, was typical of the more interesting such interceptions.

## References

1. ↑ Various (1984). *Captain's Log 2*. (Task Force Games), p. 30.
Long Shot (SH145)

## Long Shot

During a short-lived counteroffensive in Y180, the Lyrans re-captured several systems in Kzinti-occupied territory. While unimportant economically, these systems represented a step backwards for the Kzintis if Lyran control could be maintained. The Lyrans were, of course, aware of this and made an attempt to construct a base in the system. They began this effort by establishing a mobile base which would, eventually, be upgraded to battle station status, securing the Lyran foothold in the region.

The Kzintis, of course, could not allow this, but they had far greater objectives elsewhere and could ill afford to spare the ships to attack this base. Instead, they used long-range bombardment from a nearby drone frigate to assault the mobile base and prevent its activation. Using a series of feints, the Kzintis used most of their available ships to draw off the defending Lyran ships. As the drone assault began (it had actually been launched some time before using "wild boar" targeting systems), the Kzintis were able to send a single war destroyer to observe the success of the attack and render whatever aid was necessary. Unfortunately, a Lyran ship arrived at the mobile base just as the assault commenced.

## Aftermath

The Lyrans managed to save the base at the cost of one of the PFs being destroyed.

## References

1. ↑ Various (1994). *Star Fleet Battles Module S2 – Scenario Book 2*. (Amarillo Design Bureau), pp. 51–2.
Grab for Glory (SH254)

## Grab for GloryPart of Kzinti Civil War

<ref>

As the Usurper was closing in on his prize, one of his spies reported that the Patriarch was receiving supplies via a barely-defended tug. The Patriarch had apparently reasoned that since the Usurper had no ships in the area, there was little threat. The Usurper, after considering several options for a raid was forced to conclude that the Patriarch was right, the tug was safe from attack.

He was right, except that a petty noble, “Cat of Poor Grooming”, decided that if he could stop that tug, and thereby help the Usurper to win, he would be owed big time by the Usurper. So he took the only ships at his disposal and headed out to intercept the tug.

## Aftermath

Grooming failed to stop or badly damage the *WTG-4*, and the cargo was successfully delivered. Grooming died when the *Pelt-taker* and *YFF26* both exploded in the course of exchanging point-blank drone strikes. The Patriarch, in the aftermath of the war’s conclusion, decided not to punish Grooming’s family deeming his traitorous death punishment enough, and needing to show some magnanimity as he tried to re-solidify his hold on the Hegemony.
Kripney at War (SH178)

## Kripney at WarPart of Federation-Klingon Neutral Zone

As tensions built up around the Neutral Zone planet Adanerg, the Klingons decided (early in Y167) to attempt to seize it with a minimum-force assault. The F5G commando frigate Senior Sergeant Korl was sent to eliminate the Federation colony. The Federation, detecting the attack and wanting to respond with a similar force, sent the commando frigate Kripney.

As part of the Neutral Zone treaty, the Federation had allowed the Klingons to place a small group of their people with the colony, including a trade representative (who ran a small store selling imported Klingon goods) and some agricultural specialists to observe the viability of crops on the planet. The Klingons claimed that the lives of these representatives were at stake due to anti-Klingon riots by the racist Federation colonists. (To be fair, there were weekly demonstrations demanding that the “Klingons go home!”) In response to this “threat” the Klingons intended to land “civilian police” to protect their personnel, with the secret intention of accidentally burning the colony to the ground during the anticipated riot that would “spontaneously” break out when the Klingon “police” appeared.

## Aftermath

After a sharp skirmish, the Klingons were forced to concede control of Adanerg to the Federation, at least for the time being.

## References

1. ↑ Various (2007). *Star Fleet Battles Module M – Star Fleet Marines*. (Amarillo Design Bureau), p. 29.
2. ↑ Various (21 June 2019). *Captain's Log 53*. Edited by Stephen V. Cole. (Amarillo Design Bureau, Inc.), pp. 3–28.
Gettysburg class heavy command cruiser

The first of these improved command cruisers appeared in Y175. The new design provided a 20% increase in phaser firepower, a 100% increase in drone capability, a 25% increase in reserve power, and a 7.5% increase in warp power (resulting in a warp-capable saucer when separated).

The heavy command cruiser is a variant of the heavy cruiser.

*Warp pack:* The two box center warp engine in the saucer can be used to generate power but cannot be used to generate movement points unless the saucer has been separated.

*Seeking weapons:* The heavy command cruiser can control a number of seeking weapons equal to its sensor rating.

*Refits:* None.

***Gettysburg* class heavy command cruisers**, (CB)
 Gettysburg \* Kadesh \* Thermopylae \* Cannae \* Alesia \* lsandhlwana \* Gravelotte \* Tannenberg \* Kursk \* Coral Sea \* Inchon \* Khe Son \* Golan \* Affeld \* Austerlitz \* Panjsher \* Suomussalmi \* Rocroi \* Poltava \* Rossbach \* Gaugamela \* Vincennes \* Basra
Into the Hive (SH246)

## Into the HivePart of ISC Pacification

Having determined that the cause of the dispute between the Tholians and the Seltorians was the aggression of the Seltorians, and that the Seltorians absolutely refused to cease and desist, the Concordium determined to visit judgment on them. Recognizing that the Hive ship was the key to Seltorian logistics, and without it the Seltorians would be completely unable to sustain offensive operations, the Concordium sent the Echelon of Judgment to clean out “the hive”. Various other Concordium units initiated a series of holding actions to prevent the Seltorians from recalling their ships to the defense of the Hive Ship.

Curiously, the Klingons tacitly accepted a Concordium demand that they “not interfere”.

For the Seltorians, the assault came as a bolt out of the blue as they had never previously encountered such a large number of advanced technology ships in one single unit.

## Aftermath

The Torch was extinguished at heavy cost in casualties among the ISC PF crews. With no ability to construct new ships, the Seltorians had no choice but to go on the defensive and adopt a survival mode while asking the Klingons to help them build a new shipyard. The Klingons, having discovered the history of the Seltorian revolt, in which the Seltorians had murdered hundreds of billions of Tholians, declined. Even the Klingons could not contemplate mass genocide on this scale. They launched a campaign to confiscate the Seltorian ships. Eventually, all Seltorian ships were destroyed or captured. The last five Seltorian ships were sold to the WYN Star Cluster.

## References

1. ↑ Various (2008). *Star Fleet Battles Module X1R*. (Amarillo Design Bureau), pp. 51–2.
Objective Juggernaut (SL1)

## Objective Juggernaut

In Y168 the Command Cruiser Excalibur intercepted an intruder, later identified as a Juggernaut, along the Federation-Klingon-Tholian Treaty Zone. While following the intruder the Tholian cruiser Arrrakk, and the Klingon command cruise IKV Darkslyer arrive. With the arrival of the the other ships the Juggernaut attacked all three ships.

Still trailing the Juggernaut and trying to figure out how to prevent the Juggernaut from destroying their colonies along the border area the Orion pirate cruiser Gossamer Phoenix arrived. The captains eventually agree that they must destroy the alien ship and attack.

## Aftermath

The joint attack by the three major powers assisted by the a surprise move by the Gossamer Phenix managed to destroy the juggernaut but with heavy losses. The Tholian cruiser self destructed and the Darkslayer was destroyed as well, with the boom eventually recovered by arriving Klingon ships.

## References

1. ↑ Various (1983). *Captain's Log 1*. (Task Force Games), pp. 4–17.
First Sting Of The Hornet (SH137)

## The First Sting of the Hornet

In the spring of Y173, the Klingons learned that the CVS *Yamamoto* was to be refitted and equipped with improved fighters. Before this could be done, however, the *Yamamoto* was scheduled to execute a patrol in a quiet sector of the front line. The Klingons decided to ambush the ship before it could make its refit rendezvous.

Unfortunately for the Klingons, the intercepted message, while correct in content, was misdated. The Klingon squadron moving in for the ambush did not know that the Yamamoto had already completed its refit the previous month and been joined by other ships. Worse, her Hornets were ready to fly.

## Aftermath

The two groups pounded each other savagely, but gradually the superior Federation firepower told the story, and the Klingons withdrew. Tactically, the action was a draw. Operationally, it was a Federation victory and proved the Hornets as effective fighter shuttles more than worth their cost. The Klingons, examining the tapes of the battle, shortly after produced the very similar Z-Y.

## References

1. ↑ Various (1994). *Star Fleet Battles Module S2 – Scenario Book 2*. (Amarillo Design Bureau), pp. 40–1.
...And Settle Their Hash (SH54)

## ... and Settle Their HashPart of Fourth Klingon-Kzinti War

During the Fourth Klingo-Kzinti War, the Kzintis found that they needed more firepower to fight their enemies. One solution to this problem was the introduction of a special version of the drone frigate design intended to provide the long-range targeting needed to bombard enemy fleets with cruise drones. The new scout drone frigate design enabled the diminutive but easier to produce drone frigate to supplement the limited numbers of drone cruisers in providing drone fire support and conducting independent drone bombardment missions. In a pinch, it could perform as a scout.

The Kzinti formed bombardment squadrons of two drone frigates with one of the new scout drone frigates for this purpose. The new tactical grouping worked well enough until that fateful day in Y161 when one of these groupings, launching cruise drones at a Klingon fleet five million kilometers away, was surprised by a fast detachment sent out to “settle” the score.

## Aftermath

The Klingons destroyed two of the drone frigates and forced the third to disengage. Kolandian’s performance was not regarded as entirely satisfactory, and while he was retained in command, he was not promoted. His desire to prove himself would lead him to an engagement with the Kzinti Carrier Cutlass in Y166. The Kzinti commander, who survived the battle, was disgraced and reduced in rank. He died almost a decade later while in command of a freighter.

## References

1. ↑ Various (1992). *Star Fleet Battles - Scenario Book 1*. (Amarillo Design Bureau), pp. 55–6.
PSS Deputy

## Notable Commanders and Crewmembers

Bailiff \* Bobby \* Constabulary \* **Deputy** \* Dragnet \* Gatekeeper \* Gendarme \* Justice \* Lawman \* Militia \* Mountie \* Pacifier \* Peacekeeper \* Peacemaker \* Peaceofficer \* Posse \* Summons \* Texas Ranger \* Trooper \* Tucker \* Lt Oleg Babak \* Behan \* Callahan\* \* Deckard \* Alejandro Dominguez \* Morgan Earp \* Virgil Earp \* Wyatt Earp \* Doc Holiday \* Holmes \* Kojak \* LeBeau \* Mackie \* Malloy \* Magnum \* Mark Majors \* Masterson \* McKeehan \* Elliot Ness \* John Oliver \* Osterhout \* Darius Quimby \* Texas John Slaughter \* Richard Simms \* Sipowicz \* Sorenson \* John Walsh \* Watson \* White \* Williams \* Willis \* Jimmy Wilson \* Drebin \* Nordberg and about 130 others.
Meanwhile, Back at the Planet (T4S4)

## Meanwhilw, Back at the PlanetPart of Piracy Patrol (T4)

While the carrier group was away on patrol, the Pirates (who had learned that a major drug shipment had been left at the Commercial Platform as a result of damage to a freighter in their earlier raid) decided to raid Ponderosa IV. Summoned to protect the planet, the carrier group empires to the scene.
Encounter at Denebola (SL89)

## Encounter at DenebolaPart of Day of the Eagle

In Y173, the Romulans entered the General War by initiating a massive offensive against the Federation. A multitude of Romulan ships came swarming across the Neutral Zone, striking at major Federation fleet units all along the border. One such battle took place in the Denebola system as a Federation squadron under Rear Admiral Williams arrived to negotiate with an Orion base. Unknown to Williams, the Orions had already made a deal with the Romulans, and Romulan forces were prepared to ambush the squadron.
Li Zhaoxing

The first Chairman of the Federation, Li Zhaoxing was a native of Hong Kong in China and had served as Earth’s ambassador to Rigel after contact with that species. Deeply involved in the drafting of the Federation Charter, Li Zhaoxing provided stable and intelligent leadership as the Federation found its footing and was easily reelected in Y14. He retired from the chairmanship before the Y20 elections, and was then elected President of the Federation by the Assembly.

1. ↑ John Sickels (30 March 2011). *GURPS Federation, Fourth Edition*. Edited by Jean Sexton. (Amarillo Design Bureau, Inc.), p. 15. ISBN 978-1-58564-155-0.
Coalition Warfare (SL355)

## Coalition Warfare

As the Alliance began strategic planning for operations in the coming years, Star Fleet analysts studied the lessons learned during previous campaigns. Chief among these lessons was the difficulties inherent in coalition warfare, particularly the varying levels of commitment occasionally displayed by members of both interstellar power blocs.

It was noted that while the Lyrans always fought with savage ferocity against the Kzintis, they did not always show the same level of combat intensity in battles with the Federation, despite the entreaties of their Klingon allies. The Alliance war effort itself was certainly hampered during the Remus campaign by problems of coordination between the Federation and Gorns, both strongly supportive of the attack, and less-enthusiastic Kzintis.

While the vagaries of Klingon/Lyran relations were well-understood by Federation analysts, the arrival of the Seltorians and the growing prominence of the Vudar Enclave within the Klingon Empire added unknown elements to power relations within the Coalition. It was clear that the Seltorians were fanatically devoted to destroying the Tholians. However, some analysts feared that the Seltorians could become formal members of the Coalition with a treaty obligation to defend Klingon territory, rather than just sharing co-belligerence with the Klingons against the Tholians.

The position of the Vudar was even more opaque. Based on limited information, some analysts believed that the Vudar were moving towards quasi-independence from the Empire. But the majority of experts felt that the Vudar were merely taking on a larger patrol and policing role within the distant rimward regions of the empire near Hydran space, freeing Imperial Klingon units for combat missions and frontier defense against the Federation and Kzintis. It was uncertain if the Vudar would send ships to help the Klingons stave off an Alliance offensive, but the planning staffs had to assume that they might do so.

Given these uncertainties, Star Fleet produced a series of simulator scenarios to prepare fleet commanders and individual starship captains to face the potential of combined operations between the Klingon, Seltorian, and Vudar forces. The following simulation emphasized the potential of varying levels of commitment among the forces of both sides during a fleet battle.

## Aftermath

Historically, no Seltorian or Vudar units directly participated in the defense of the Klingon Empire against Alliance forces during the General War. Vudar forces did conduct operations against Hydran forces to "defend" territory claimed by the enclave and the Seltorians sometimes responded to Federation operations that appeared, to them, aimed at interfering with their efforts to eradicate the Tholians. This simulation and similar studies did prepare Star Fleet officers for these possibilities, and in the event stimulated their thinking about the tactical possibilities in preparing for the unexpected.

## References

1. ↑ Various (2020). *Captain's Log 54*. Edited by Stephen V. Cole. (Amarillo Design Bureau, Inc.), pp. 44–46.
Admiral Kumerian's Last Battle (SL2)

## Admiral Kumerian's Last BattlePart of Operation Cavalry

Admiral Kumerian escaped from the "cavalry" with his hide and part of his dreadnaught (the boom). Driven mad by the defeat, and the "treachery" of the Lyrans (who would not stay around to be blasted into scrap iron), Kumerian stubbornly refused to leave the fleeing boom. Alliance forces closed in.

## Aftermath

Kumerian was missing in action after the battle.

## References

1. ↑ Various (1983). *Captain's Log 1*. (Task Force Games), pp. 17–8.
Desperate Days (SH142)

## Desperate DaysPart of Operation Nutcracker

During the height of Operation Nutcracker, the Tholian Defense Fleet allowed Kzinti and Gorn vessels into Holdfast territory to defend against the Klingon and Romulan assaults. Also at this time, the 312th Battle Fleet arrived in Holdfast Territory. During those desperate days, elements of the 312th were used to react to several Romulan and Klingon forays, often with allied support. The action depicted here is a raid on an identified Romulan assembly area, the Alliance force attacking just as the advanced elements of the Romulan strike force begin to arrive.

## Aftermath

The Romulan force was repelled by the Tholians, primarily due to ruthless use of their Gorn and Kzinti allies. The Agreement was never particularly strong, and this engagement (and Tholian distrust) kept it from getting stronger.

## References

1. ↑ Various (1994). *Star Fleet Battles Module S2 – Scenario Book 2*. (Amarillo Design Bureau), pp. 47–8.
Border Security (SH163)

## Border Security

With the General War over and the ISC not yet a factor, the Hydrans took steps to restore their borders. While they did not desire to start another major conflict (at least, not yet), they felt it necessary to resolve some disputes with the LDR on just where their mutual border was. The result was a number of small clashes of little significance. The exception was this battle in which an X-ship from both sides arrived to demonstrate their respective nation's resolve.

## Aftermath

The Presidium successfully drove off the Hydran ship. Both had sustained minor damage, but the Hydran ship was clearly getting the worst of the encounter when its commander decided to withdraw.

## References

1. ↑ Various (1994). *Star Fleet Battles Module X1*. (Amarillo Design Bureau), pp. 49–50.
Decapitation (SL308)

## DecapitationPart of Klingon Invasion of the Federation

After the first Klingon attack on the Federation's core star systems had been driven away, Star Fleet settled down for a long, difficult war. New ships were coming from the slipways and the reserve ships had been activated. Many savage battles remained ahead.

Admiral Kobain of the Fourth Fleet (which had guarded the Kzinti Border before the war) was covering the right wing of the frontline. Struggling to deal with continuing Klingon attacks, he sought a way to gain some kind of edge, some advantage, some tactic or strategy that would give his forces just enough of an edge that they would win the war.

Based on faulty intelligence estimates, he believed that the Klingons had only a few really good commanders and that they shifted these back and forth between various fleets and fronts. He reasoned that if he could, in effect, assassinate such individuals, the entire Klingon war machine might be derailed. His plan was to take advantage of the Federation's primary weapons, the photon torpedo, by having his entire fleet target all of its weapons on the Klingon flagship in any given battle. If that ship could be destroyed quickly enough, the "ace" on board would be killed before he could transport to another ship. Three or four such successful attacks might leave the Klingons "aceless" and (under Star Fleet's mistaken theory held) the replacement commanders would be far less effective.

The strategy was not without cost. If firing at long range (usable when the Klingon flagship was smaller), this left the Federation fleet headed into a melee with unloaded weapons against faster firing disruptors. If he held his fire to short range (improving accuracy and generating more hits) his ships would take more damage. He tried this style of attack several times (at considerable cost) until Star Fleet Intelligence discovered the error and the strategy was abandoned.

## Aftermath

This was based on a mistaken translation of Klingon names. Star Fleet's computers translated four different Klingon letters as "k" resulting in dozens of different Klingon officers being thought to be only a handful of individuals. Star Fleet assumed that the Klingons shifted these "ace" commanders around like Star Fleet Medical might call in a brilliant surgeon for one difficult surgical procedure, then send him back to his home hospital. For example, Captains Kormak, Captain Kormakg, Captain Khormak, Captain Krormakh, and Captain Kgormak were all thought to be one single officer named Kormak, and reports of each one were thought to mean that "he" had been sent to a new ship in a different sector. That would be an insane way to run a navy, but the Federation thought it might be part of the Klingon culture, or that perhaps only some commanders were considered "politically reliable" by the Emperor.

## References

1. ↑ Various (5 December 2011). *Captain's Log 44*. Edited by Stephen V. Cole. (Amarillo Design Bureau, Inc.), p. 55. ISBN 978-1-58564-165-9.
2. ↑ Various (21 June 2009). *Captain's Log 39*. Edited by Stephen V. Cole. (Amarillo Design Bureau, Inc.), p. 20. ISBN 978-1-58564-130-7.
Here There Be Demons (SH86)

## Here There Be Demons

Y179 was a good year for the Federation as they were able to drive the weakened Klingon formations back to the original borders. Here, however, a new problem was encountered. While it was obvious that offensive action was necessary to force the Klingons to the peace table, there were no reliable sources of information on just what the best routes into the Empire were. It was obvious that the few known routes (mostly used by the *Federation Express* company before the war) would be heavily defended. The Federation resorted to sending a series of probing forces to locate weaknesses in the Klingon lines that could be exploited to outflank the major defenses and to find area within their defensive sphere where logistics points could be established to support future operations. Because the areas behind the Klingon borders were "unknown" territory, a Federation intelligence officer had labeled them in accordance with the standards applied by ancient map makers on virtually all worlds. Many of the Federation probing forces would find that demons did indeed dwell there.

## Aftermath

The **Clancy** was severely damaged, but managed to escape. The **Minas Gerias** was destroyed, along with the Klingon **Fire Demon**. The Federation would be forced to send another probe to discover what, besides demons, was in this sector.

## References

1. ↑ Various (1992). *Star Fleet Battles Module R5*. (Amarillo Design Bureau), p. pg 35.
2. ↑ Various (1992). *Star Fleet Battles Module R5*. (Amarillo Design Bureau), p. pg 35.
3. ↑ Various (1992). *Star Fleet Battles Module R5*. (Amarillo Design Bureau), p. pg 35.
Federation Second Fleet

The Second Fleet is the Federation's exploratory arm. Considered to be the premier assignment for officers who think exploration is the highest calling of the Federation. The fleets primary operating area is the area coreward of the capital area and the galactic core region. Even during the General War the majority of the fleet remained on survey duty finding resources to support the war effort. However, ships of the fleet can be found in any part of the Federation.

## Order of Battle

### August Y171

USS Byrd CVL to be reassigned to the Front.
USS Columbus
USS Darwin CVL to be reassigned to the Front.
USS Lewis & Clark
USS Magellan
USS Marco Polo
USS Costeau
USS Sagan COV to be reassigned to the Front.
USS Armstrong
USS Challenger
USS Columbia
USS Discovery CVL to be reassigned to the Front.
USS Viking
USS Voyager
## References

*Federation* Fleets

First Fleet \* **Second Fleet** \* Third Fleet \* Fourth Fleet \* Fifth Fleet \* Sixth Fleet \* Seventh Fleet \* Eighth Fleet \* Ninth Fleet \* Tenth Fleet \* Eleventh Fleet \* Twelfth Fleet \* Thirteenth Fleet \* Fourteenth Fleet
1. ↑ John Sickels (30 March 2011). *GURPS Federation, Fourth Edition*. Edited by Jean Sexton. (Amarillo Design Bureau, Inc.), p. 105. ISBN 978-1-58564-155-0.
2. ↑ Various (7 June 2010). *Captain's Log 41*. Edited by Stephen V. Cole. (Amarillo Design Bureau, Inc.), pp. 17–18. ISBN 978-1-58564-144-4.