Star Trek: Aftermath (Klingon Phase)

Distress In The Transwarp Domain
...please pass the duct tape...

THE CONDITION OF THE USS MARATHON: INITIAL DIAGNOSTICS

ENGINES:
Warp Drive: Unknown, inoperable
Transwarp Drive: Unknown, inoperable
Impulse Engines: 93% Port Engine Output, 96% Starboard Engine Output
Auxiliary Fusion Plants: 99.2% Port Plant, 99.6% Starboard Plant
Batteries: 97.2%

SENSORS:
Transwarp Sensors: Online, 56% Operational
Long Range Sensors: Online, 80% Operational
Short Range Sensors: Online, 88% Operational
SHIELDS: Online, 42% Operational
12 Points Shielding
19 Points Shielding With Impulse Engines
COMPUTER SYSTEMS: 88% Operational

WEAPON SYSTEMS:
Phasors: Offline, 16% (crushed emitters and tracks)
Photon Launchers: Offline, 48% (crushed housing)
Tractor/Presser Beams: Offline, 20% (crushed emitters)

SUPERSTRUCTURE: 25%
Warp Nacelles: Misaligned, EPS Damage, likely more
External Bulkheads: Serious damage, catastrophic failure likely at warp 6 and above
Internal Bulkheads: 68%, more damaged Port side than Starboard
Turbolifts: Online, 93% Operational
Transporters: Offline, 37%

CREW:
46% Total Casualties, 156 of 340 Total Crew Members. Breakdown:
|Crew Efficiency 54%|Enlisted|Officer|Civilian Specialist|
|Minor Injuries:|62|12|45|7|
|Serious Injuries:|68|33|22|12|
|Dead:|25|15|8|2|
|Total:|156|60|75|21|

PAINT: 82%, looks terrible

View
Session 27: 110 Hours Of Driveby Short Range Scanning Later....
Anyone got a deck of cards?

TRANSWARP APPLIED PHYSICS

GRAB AND PULL Vs. USING WARP ENGINES

Warp engines don’t work in TransWarp space:
*Transwarp engines move you in Transwarp space when cutting or in Transwarp flight
*Warp engines create power, but not movement, different physics

TransWarp engines are not to be used in existing TransWarp Conduits
*TransWarp Engines will disrupt the existing conduit and start ‘cutting’ a new conduit
*Warp engines are fine but buy you nothing, can’t affect the Conduit, different physics

The TransWarp Conduit will draw any object at the event horizon in. Let it, fighting it will cause serious structural and engine damage to the ship and could possibly (remote chance) cause damage to the ‘conduit’

A TransWarp Conduit is a pathway through TransWarp space that will flow one direction, the other direction, or both.
Starfleet needs 2-way conduits: Paired opposite one-way conduits are very rare as one-ways tend to flow the same direction.

Conduit Difficulty:

65% Conduit created collapses rapidly.
30% 1-way stable conduit, easiest to find and cut.
4.9998% 2-way stable conduit, difficult to find a long term conduit but with persistence is usually possible
0.0002% 1-way opposing paired stable conduit (theoretical). The first should be easy to find and cut, opposite is exceedingly rare

Difficulty tables to create stable Conduits:
Distance from star:

100 AU 99%
125 AU 90%
150 AU 78%
200 AU 40% Add This
300 AU 25%
500 AU No penalty

Particulate density in the area: (the emptier space is the better)

Very Low 0%
Low 5%
Moderate 15%
High 30% Plus This
Very High 50%

Sensor Probe Ping Strength Yields:
Penetration Difficulty:

0.01-0.03 0%
0.04-0.1 5% Plus This
0.11-0.15 15%
0.16-0.20 30%
0.21-0.25 50%
? = Chance of success
View
Session 26: A Day In The Life Of Transwarp Scanning
Lockdown, a brawl, and a drunk 1st Officer, oh my....

Where we left off:
The ship and crew have recently arrived at Starbase 134 orbiting Rigel 6.
Rigel_VI_-_Starbase_134.JPG
The 1st officer joined the Captain and 2nd officer for a briefing from Admiral Burtell and are on their way back to the ship now. Information from the Admiral’s briefing and the Captain’s orders package follow:

EXCERPT FROM STARFLEET TRANSWARP PROCEDURES MANUAL

(A DAY IN THE LIFE OF TRANSWARP SCANNING)

Since the Federation does not have the technology to physically fix and hold TransWarp Conduits (as the Borg do), finding areas of space that will support long-term, self-sustaining TWCs (Transwarp Conduits) are our best option at this time. It can be a lengthy process, but the payoff is substantial to the Starfleet and the Federation. This process has been developed and refined over the last several years. Used by a ship with TransWarp capabilities, it is the most effective method we know to establish STWCs (Stable Transwarp Conduits) at this time.

01 Begin long-range scans of the system to find the areas of weakest space/time threshold.
02 Mark the areas of weakness/instability as the ship executes a meticulous, all-axis scan from 100 AU out to roughly 250 AU (125 AU from the star), roughly a 38-hour process.
03 Plot a course to take you, as efficiently as possible, to all of the areas you marked for intensive short-range scans, hitting the areas of greatest weakness/ instability first to create a list of candidate points. This is roughly a 90 hour process.
04 Track the ease of penetration for each candidate point using sensors and TW probes (your ship has 200 of these, and can manufacture more with the engineering replicators), ranging from 1.00 to 0.01, ideally looking for something in the 0.10 to 0.01 range, but accept up to 0.25 if it’s within 200 AU of the STWC endpoint. Create list of cutting candidate sites. This is roughly a 12 hour process.
05 Report your findings to Starfleet and that you are about to begin TW tests. Notify the nearest Starbase Ops Center when you are about to enter TransWarp and again when you exit. Begin creating candidate TWC’s:
…A. Generate an EM triggering pulse with the main deflector, the frequency of which is the encoded frequency that must be used every time a non-TW ship opens the Conduit.
…B. Engage TW engines and begin to create the TW field, ensure shields are at maximum, and enter the new Conduit you are creating.
…C. Using long-range sensors to detect TW eddies and maintaining Main Deflector power until you are inside TW space, push into TW space and move towards your destination point to “carve” the conduit.
…D. Use the Main Deflector at the same frequency again to create an end point, dropping TW Drive power as you pass through it. Notify Starfleet.
…E. Turn, activate the new Conduit, enter from the new end point under standard warp power, and travel to the beginning point. Notify Starfleet.

06 Reenter the TW conduit. From the inside scan for TW Domain inconsistencies, fluctuations, and outside influences that may indicate instability of a long-term conduit. A safety margin of no more than 0.02% is acceptable.
07 Notify Starfleet of the detailed results.
08 Move to the next candidate point and repeat. Continue until all candidates have been explored. The best acceptable conduit and 2 alternates will be officially logged, assuming any are found.
09 If none can be found, repeat the process traveling to a shorter mid-point. Attempt to establish 2 short runs instead of a single longer run. This is an undesirable solution but acceptable.
10 Be on the lookout for anything that might indicate the fate of the other ships as you proceed. This will add to our understanding of what’s happening and will help improve safety margins.


Starfleet Transwarp Cutters
.

USS Narsil, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Ka’Tula to Starbase 241, cause: poor understanding of Transwarp physics.

USS Actium, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Starbase 234, cause: suspected Klingon aggression

USS Bull Run, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Starbase 234, cause: suspected Klingon aggression

USS Aries, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Bolarus to Starbase 241, cause: unknown

USS Pydna, Nebula Cruiser – Active, Operating along Romulan border vicinity of Starbase 241, cause: suspected Klingon aggression

USS Salamis, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Starbase 234, cause: suspected Klingon aggression

USS Onami, Nebula Cruiser – Lost, presumed Destroyed, vicinity of Starbase 234, cause: suspected Klingon aggression

USS Ipsus, Nebula Cruiser – Lost, presumed Destroyed, area of Starbase 234, cause: suspected Klingon aggression

USS MarathonActive, Operating along Klingon border vicinity of Starbase 234


USS MARATHON LONG RANGE OBJECTIVES

With the conclusion of the Starfleet Strategic Objective on Bolarus last week, final decisions were made and strategies engaged such that your long term orders are now available. You and your command crew are authorized access to this information, should you choose to inform them. This information, like everything else surrounding your ship and mission is classified, top secret clearance and need to know required.
At best possible pace, accomplish the following STWC paths (see map):
Phase I: Link up the main Federation territories with the Free Worlds of Klinzhai territories – west and east. Proceed in this order:

  • Regulus to Starbase 234
  • Starbase 234 to Starbase 84
  • Starbase 84 to Nimbus.
    Phase II: Link up the border defenses along the Klingon border of the main Federation territories. Proceed in this order:
  • Regulus to Kenda (Outpost 68)
  • Kenda to Deep Space K-7
  • Deep Space K-7 to Starbase 133
  • Starbase 133 to Toraz (Outpost 16)
  • Toraz to Boradis (outpost 48)
  • Boradis to Cestus (Outpost 26)
  • Cestus to Starbase 82
    Phase III: Link up the border defenses along the Free Worlds of Klinzhai territories. Proceed in this order:
  • Starbase 105 to Starbase 117
  • Starbaase 117 to Starbase 152
  • Starbase 105 to Bon Turani (Outpost 112)
  • Bon Turani to Vintara (Outpost 92)
  • Vintara to Starbase 123
  • Starbase 152 to Outpost 186
  • Outpost 186 to Veridian
  • Veridian to Luzaera
  • Starbase 123 to Zalda (Outpost 74)
  • Zalda to Junon (Cold Station Theta)
    Phase IV: Link up the border defenses along the Romulan neutral zone. Proceed in this order:
  • Starbase 84 to Outpost 23
  • Outpost to Tomed (Outpost 17)
  • Tomed to Qualor (Outpost 14)
  • Qualor to Kaleb (Outpost 11)
  • Kaleb to Kolaran (Outpost 95)
  • Kolaran to Dessica (Outpost 7)
  • Dessica to Bolarus

Authorized this stardate by my signature,
Rear Admiral Thora Burtell,
Starfleet Special Operations Fleet 3, Commanding


BATTLEGROUP 28

Battlegroup 28 under the command of Captain Harlan Mattix on the USS Lynx, an Akira class cruiser. With him are the USS Huntley and the USS Ivanhoe, both Streamrunner class destroyers, and the USS Voodoo and the USS Wrath, both Spitfire class destroyers.
Organization: Battlegroup 28 – Commander: Harlan Mattix,

Captain Ship Type
Captain Harlan Mattix USS Lynx Akira Cruiser
Captain Masuus Eashan USS Huntley Streamrunner Destroyer
Captain T’Lairan USS Ivanhoe Streamrunner Destroyer
Captain Dewrnot Saine USS Voodoo Spitfire Destroyer
Captain Murali Kilaru USS Wrath Spitfire Destroyer

Even though it’s only 5 ships, the group is assigned Battlegroup status to establish its priority when making requests, receiving conflicting orders, and enforcing the safety of the USS Marathon and crew answering directly, and only, to Admiral Thoris Burtell, Starbase 234 Starfleet Special Operations.


What happened?

The Captain, XO, and SO left the meeting with Admiral Burtell to head back to the transport point and back to the Marathon chatting as they went. It was soon apparent that the XO was quite drunk. It seems he had just spent the last 2 days ‘entertaining’ the Admiral while they both awaited the arrival of the Marathon. After arriving back onboard ship, the Captain ordered the XO to an out of the way lounge to sober up after a few stern words about decorum and proper respect to the Captain and setting an example and making good decisions, etc….

A shuttlepod from Starbase 134 flew over to the USS Marathon with orders from Admiral Burtell to collect the saboteur and the devices and materials related to her crimes but were locked out of docking with the airlock they were approaching and told to standby while he clarified orders with the Captain, who told him not to release the prisoner. The shuttle crew sulked in their shuttle waiting for orders from someone telling them what to do.

Starbase 134, Rigel 6
Starbase_134.jpg

The Captain communicated with Admiral Burtell who suggested (ordered) that he turn over the prisoner and materials to the shuttle, countering with the information that he had ordered that the ship be placed in ‘lock down’, no one in or out without his permission while they finish the security sweeps and searches already underway. ADM Burtell’s offer of personnel and tech to assist were turned down, and she ordered the Captain to be underway on his mission in 12 hours or turn the ship over to Starbase 134 technicians for a full sweep.

Doctor Sellers forwarded a report to the Captain during this conversation (but read later) stating that the saboteur was genetically modified, it was subtly done, and so thorough that he couldn’t be sure what race or sex the individual had originally been.

Lt Stilicho Th’Azyron received an urgent communication from his Assistant Sec/Tac officer at this point, telling him, “Sir, there is a brawl outside of lab 12!”. He arrived rapidly, greeted by the sight of 5 people in labcoats, 1 male and 4 females (1 female was vulcan), brawling (slap-fighting and scratching) with each other and the security team trying to break it up without hurting anyone. To the side was another female in a labcoat displaying poor bladder control and clearly frozen in panic, and LtJG Louisette Nørup, acting Asst Sec/Tac Officer, who was pointing a phaser at the melee in general. When Lt Th’Azyron appeared she requested, “Sir, permission to stun everyone?”, clearly in over her head and close to panic herself. Lt Th’Azyron bellowed a very intimidating couple of sentences to the effect of, “Knock it off and act like grown ups!”, which were largely ignored. At this point, for reasons that are still murky, Nørup opened fire on all individuals in the conflict pile of bodies using heavy stun setting, and the melee ended.

It looked a lot like this….
It_Looked_A_Lot_Like_This.jpeg

Lt Th’Azyron backed Nørup’s play, officially anyway, and sickbay was notified and starship services was notified – the mess was soon cleaned up. After a quick investigation, it was discovered that these were two groups from the pool of 30 civilian specialists the ship was to receive from at this starbase, and they had both independently arrived at the conclusion that they needed to get a jump on lab assignments and talked/bribed/intimidated/charmed their way into a beam over to the ship with their equipment. They both had their sights set on lab 12 because of it’s specialized equipment and they wanted to plant their flag of ownership upon it.

Ordering the CivSpecs escorted from Sickbay to a nearby conference room (without windows) Lt Th’Azyron had a ‘meeting’ with them where he laid down the law with them. There was clarity among them when he was done. Someone wet themselves again. It is notable that the CSO (Chief Science Officer) didn’t assign either team to that lab (Vulcan spite?).

The now sober first officer got roped into an unfortunate long term activity.

The Captain took it upon himself to write to Admiral Burtell’s superior officer, not realizing that she reported directly to the Admiralty Directive’s Council, the body that sits directly beneath the Federation Joint Chiefs of Staff and puts their decisions into orders issued to all of Starfleet. The Captain’s answer was short, terse, and came from the Chief of Military Operations, Fleet Admiral J. Crog (that’s right, that J. Crog, the old Andorian warhorse himself) making the communique an immediate collector’s item and also extremely classified. He referred the Captain back to Admiral Burtell who, it seems, had stuck her neck out to specifically have him assigned to this position.

Following that, the searches continued, yielding nothing and concluding (coincidentally) with Burtell’s 12 hour deadline. Beginning initial scans, the Marathon crew found a higher concentration of potential areas of weakness or instability to investigate in their 38 hour sweep. They additionally took the opportunity to run a battle simulation, destroying the Klingon B’rel Cruiser they were up against at short range and damaging themselves in the process. Lessons were learned, there were jokes, there was crying. One crewman had fun.
Klingon_Emblem.jpg

View
Session 25: Taking Command
USS Marathon, Refit and a new crew….

toboldlygobanner.jpg

Transwarp domain space – the new final frontier. These are the voyages of the USS Marathon. Her multi-year mission is to seek out optimal entry locations, exit locations, build Stable Transwarp Conduits (STWC) between them, and do so without getting killed. To boldly go where most such ships have disappeared without a trace. Pulsar_Class_Exploration_Cruiser.JPG Her crew is made up of the finest minds with relation to all phases of the STWC building process available. The officers and crewpersons of the Marathon are supplemented by 30 civilian specialists, support personnel to assist the Marathon in any potential encounters with the unknown. Together they will strive to create a vast network throughout the United Federation of Planets which will facilitate travel, trade, defense, and greatly reduce the environmental load the warp drives are placing on normal space.

TransWarp_II_System_Diagram.JPG


Theater Briefing

Klingon relations reached an all time high at the moment of the Dominion surrender and have been deteriorating at a progressively rapid pace ever since. Several incidents in Cardassian space have led to shooting matches between Klingon forces and Star Fleet.
Star Fleet’s diplomatic intervention in the Klingon/Romulan conflict following the “Nemesis” incident were viewed by the hawks among the Klingon Empire as interference in their “right to make war” and portrayed Chancellor Martok as a weakling in the pocket of the Federation. Their masterful use of propaganda related to the event led directly to the ascension of Chancellor Kur’gek to the head of the Klingon Council after killing Chancellor Martok in a dual. The loss of Martok was a strong blow to Federation/Klingon relations and Kur’gek has ridden higher and higher on the political capital he and his cronies manufacture at the expense of the Federation.

Having fully consolidated his power, the imminent supernova of the Hobus star was a gift on a silver platter for Kur’gek. Roughly 50% of Klingon forces had secretly assembled along the border, ready for the moment of greatest weakness and assaulted across shortly before the supernova event of the Hobus star. They overwhelmed the Romulan border defenses and plunged deeply into Romulan territory, attempting to take the new Romulan capital of Remii.
Joint Romulan/Vulcan and some Federation forces held the system from the Klingons after a protracted and viscous battle. At Romulas and Remus the Klingon forces attacked every non-Klingon ship that came within weapons range, including many unarmed Federation transport vessels providing humanitarian assistance. Thanks to the warning of the Romulan border defenses, enough warning was received for 2/3 of the Federation forces to vacate the system prior to the Klingon forces arrival.

While the future is unclear, what is clear is that the Klingons mean to end the Romulans as a power in the quadrant and have made their move at the worst possible time from the perspective of the Romulans. Without help, the Klingon gambit is likely to succeed and the Romulan Star Empire will fall.


Captain’s Orders:

GRADE ADVANCEMENT: Commander Morgan, as of stardate 2387.082 at 11:05 hours you are hereby promoted to the rank of Captain in the service of the Star Fleet of the United Federation of Planets, and accorded all the rights and privileges associated with this position. Congratulations. (If you fail you die. – Addendum for Klingon officers, if applicable).

ORDERS: Captain Morgan, you are hereby ordered to travel to the Cardassia Prime, Federation Drydock Facility 4, to arrive by Stardate 2387.0904, there to report to Facility Commander Captain Terrance Finstadd, and take command of USS Marathon NCC-72002, currently under refit at said facility. Complete such remaining refit and repair as is necessary and be underway no more than 2 days from accepting command. Move with rapidity to Starbase 74, there to take on additional crew and officers. The USS Marathon will undergo minor refit while at Starbase 74, receiving a type 36 sensor array modification to further its capabilities to complete the mission. Upon completion of sensor installation, move with rapidity to Rigel, and there take on remaining crew and officers. Report via subspace to Admiral Thoris Burtell, Starfleet Special Operations, Starbase 234 for assignment and official duties.


Ship’s orders:

STWC Exploration: USS Marathon, NCC-72002, is hereby transferred to Starfleet Special Operations Fleet 3 based at Starbase 234, under command of Admiral Thoris Burtell as of stardate 2387.0904 at 11:05 hours. USS Marathon is hereby ordered to proceed immediately to Rigel, there to begin without delay to conduct exhaustive surveys of space in the vicinity of Rigel and Starbase 234 and, if necessary, points in between towards the goal of establishing a Stable Transwarp Conduit between Regulus and Starbase 234. This mission is of highest priority to Starfleet, and the warp 6 speed restriction does not apply to the USS Marathon for the purposes of accomplishing this mission. Unlimited first priority access to the Federation Stable Transwarp Conduit Network is authorized for the duration of the missions of the USS Marathon.

STANDING ORDERS:
1. Observing the prime directive where it applies is the highest priority.
2. Protect the citizens, property, ships, trade, and sovereign territory of the Federation in the area of operation is the second highest priority.
3. Use diplomacy to resolve situations unless given no other choice, and then use the least amount of force possible to accomplish the above directives.
4. Seek a point in the Regulus system as close as possible to the Rigel/Regulus STWC endpoint from which to establish a STWC endpoint.
5. Seek a point near Starbase 234 from which to establish a STWC endpoint.
6. Create a STWC between these endpoints and verify stability and safety of said STWC.
7. Additional mission specific directives will be cut on an as needed basis through the office of Starfleet Special Operations Fleet 3 Adjutant, BAdm Fintes.
8. Under no circumstances will you allow this technology and/or related materials and records to fall into the possession of non-Starfleet hands and you will take any and all necessary measures, regardless of how dire, to ensure this.
9. Observe the following Rules Of Engagement:
..A. Federation ships shall not fire upon another ship unless first fired upon.
..B. This supersedes Rule of Engagement A in the event that engaging another vessel is necessary to accomplish the directives above, and then Federation ships shall use the least force necessary to accomplish the directive(s).
..C. When encountering superior numbers Federation ships will avoid contact, break contact, and/or withdraw from conflict if there are no considerations towards the directives above.
..D. When engaged in combat in the accomplishment of the directives above, Star Fleet vessels shall do their utmost to ensure they are meeting these directives, and shall not withdraw from conflict unless their continued presence can make no difference in the outcome. Captains shall exercise prudence to protect their ship and crews balanced against the accomplishment of directives.
..E. With all other directives satisfied, protect the ship and its crew above all other considerations.

Starfleet_Special_Operations_AOE_SB234.JPG

What Happened:

The Chief Engineer, Lt Cmdr Vegga Aece, Was the first senior officer to board the USS Marathon, arriving a full 9 days ahead of the others. He was greeted enthusiastically, if abruptly, by Captain Terrance Finstadd, commander of the Starfleet refit facility at Cardassia (yes, really) Prime. Cpt Finstadd had just finished dressing down (screaming at) one of his ratings, a very young (and smallish) caitian named Phipps for some alleged grievance that Phipps had committed.

The Starfleet refit facility consisted of a very small mobile habitat/office and 9 mobile docking facilities plus a number of enormous Starfleet shipping containers used for warehousing. The USS Marathon was in Dock #4.

Cpt Finstadd gave Vegga’s orders a cursory once over and had Phipps fly him over to the ship on a ‘Worker Bee’ construction pod. Phipps gave the Lieutenant Commander the full external tour of the ship, doing a full orbit around and then over and under the ship. The only real surprises were the pod in the ‘Roll Bar’ above the ship was clearly empty, and the bottom of the secondary hull where one would normally see the warp core ejection port was cored out in a circle through 4 decks and 9 meters across, leaving main engineering open to space.

Upon boarding Vegga made his way to the bridge, assumed on-board command as he was the ranking officer, and made his was to Main Engineering. There he met the Transwarp Engine Crew and the Transwarp Sensor Crew, technically part of engineering, who promptly introduced themselves and then informed him that they were not in his chain of command. They further briefed him that they would work efficiently with the engineering crew, but that now one in the engineering department, including him, had the clearance to be briefed on, read up on, touch, of interfere in any way with them performing their duties regarding either the Transwarp engines or the Transwarp sensor systems. This is when it became apparent to Vegga that this ship was to be equipped with Transwarp capabilities, as his orders and briefing had made no mention of it in any way.

Over the next several days the ship was tweaked, tuned, painted, polished, and given a new warp core. It was mounted to the decking that had been cored out from the secondary hull, and the entire thing was mounted to the Marathon as a single piece. An anti sensor field was placed around the core and decks and a tarp of some kind tossed over the core itself to prevent prying eyes. Installation was smooth and by the numbers, except for the parts that were not.

Things were starting to run smoothly when, suddenly, the Captain showed up, precisely on time. No one perished, though it was a near thing with Phipps.

The only incident was when Lt. Stilicho Th’azyron of Keth Idrani, the Security/Tactical Chief reported in. Captain Finstadd was again chewing out Phipps, whose fur on the left back side of his head was heavily smoking from some sort of burn. Not paying complete attention to what was happening in the worker bee shuttle with the stench of the still smoking Phipps, and Phipps being distracted for some reason, he delivered Lt Stilicho Th’azyron of Keth Idrani to the USS McKinley. Closely observing his surroundings Th’azyron noticed that this did not seem to be his ship. After a quick conversation with Captain Harkness, Phipps departed and delivered the LT to the Marathon after the obligatory fly around.

Worker_Bee_class_Shuttle_Pod.jpg

1. Meet and greet: PC’s arrive, Chief Engineer first, Meet Facility Commander Terrance Finstadd, get refit briefing (cover the ship upgrades) if authorized, meet 3rd assistant Shipwright Phipps (very small very young caitian), tour ship, meet other PC’s and important NPC’s present, gets updates on crew arrival ETA’s at destinations.

There was much meeting and greeting and backgrounds were compared to see if the PC’s may have served together at any time. It seems the Captain and Lt Christina Williams, the Assistant Chief Engineer, um, did serve together and know each other at some point. It also seems that the Chief Engineer and Assistant Chief Engineer had met at a training school and did not much care for each other.

2. Refit complete end of first day, roughly 2am. Basic shakedown testing of new systems takes 1/2 day

The shields are tested under phaser fire from USS McKinley, starting at very low levels and progressing to higher levels with diagnostics in-between. Photon & Quantum torpedoes are launched at large asteroids (4 total are destroyed) designated for munitions testing. Systems check out, diagnostics are all in the green.

After receiving this news, and anxious to have the Dock #4 available for the next ship, Cpt Finstadd, with Phipps looking surly in the background, addressed the Captain via comms. “Cardassia Prime, Federation Drydock Facility 4, Terrance Finstadd commanding. I do hereby release the USS Marathon, NCC-72002, from this facilities care for Active Operations, transferring control to its Captain and crew so they may make for Starbase 74 in the Tarsus system. Smooth operations to you Marathon. Finstadd, out.”

Cpt Finstadd transfers the USS Marathon to Burtell after successful systems test

Arriving via tightbeam transmission from Cpt Finstadd’s “office”, Ship’s orders:
STWC Exploration: USS Marathon, NCC-72002, is hereby transferred to Starfleet Special Operations Fleet 3 based at Starbase 234, under command of Admiral Thoris Burtell as of stardate 2387.0904 at 11:05 hours. USS Marathon is hereby ordered to proceed immediately to Rigel, there to begin without delay to conduct exhaustive surveys of space in the vicinity of Rigel and Starbase 234 and, if necessary, points in between towards the goal of establishing a Stable Transwarp Conduit between Regulus and Starbase 234. This mission is of highest priority to Starfleet, and the warp 6 speed restriction does not apply to the USS Marathon for the purposes of accomplishing this mission. Unlimited first priority access to the Federation Stable Transwarp Conduit Network is authorized for the duration of the missions of the USS Marathon.

3. Set course for Starbase 134 via STWC chain with skeleton (mostly engineers) crew. A. 1.5 hours travel at Warp 2 (general speed limit within most star systems), 108.83 AU, to STWC entrance in Cardassia system and drop in, 1.24 hours to exit in Bajor system 6 LY Distance. B. 3 hours travel in Bajor system at Warp 2, 217.66 AU, to reach next STWC entrance, 4.33 hours to exit in Trill system 21 LY distance. C. 1 hour travel in Trill system at Warp 2, 72.55 AU, to reach next STWC entrance, 3.09 hours to exit in Draylon system, 15 LY distance. D. 2 hours travel in Draylon system at Warp 2, 145.11 AU, to reach next STWC entrance, 2.72 hours to exit in Tarsus system, 13.2 LY, near Starbase 74.

4. Layover here for 6 hours and receive sensor pod upgrade as per secondary order set, pick up 1/3 crew (various enlisted specialists), Department Heads, & 2nd Officer. Continue on journey.

Crisis of equipment failure, or was it?
Much of what took place is classified. The essence is that a device was used to disrupt the power systems and emergency forcefield system aboard the Marathon in Coridan space, traveling at warp 1 across that system towards the STWC to Rigel. The ship was stopped while repairs repairs were made, the device was disarmed and disconnected, and the ship was searched. Other devices were found, the investigation revealed the saboteur, and the devices were found to be of REDACTED origin.

Charlie, the ship’s counselor had a conversation with the suspect yielding the location of other devices that weren’t found. The work of the Chief SEC/TAC officer, with assistance from LtJG Curtix Na Zach, the Assistant Chief Science officer uncovered the identity of the suspect, and the captain and the chief engineer were both very involved in the quick resolution of the situation. An additional device was uncovered in the investigation that was not placed by the saboteur and it’s unclear whether all devices are found at this time.

5. Travel to Starbase 134 in Rigel. There meet Admiral Thoris Burtell in via subspace upon arrival at Starbase 134. Receive Captain’s briefing along with 1st officer.

Surprising the captain and officers of the Marathon, Admiral Burtell was waiting at Starbase 134 and comms the Marathon as they enter their holding position. This gives the officers no time to work on their investigation before the Captain and SO have to beam to the Starbase and meet with the Admiral.

The captain and SO are met at the beamdown point by Admiral Burtell’s officious little Adjutant, Branch Admiral Izzy Lefler (no image available), who escorted them to a meeting room where the Admiral and the ship’s XO, Cmdr Ano Merzek (image not available), was waiting for them.

Captain’s Briefing:
Transcribed from the logs of Admiral Burtell, Special Operations, Starbase 234 from her briefing of Cpt Morgan and command crew at Starbase 134. After meeting and greeting and typical pleasantries Burtell begins:

“There’s no sense in candy coating this gentlemen; your mission is extremely hazardous. You should know that, though we officially claim it to be 3, we’ve lost 5 ships already in this area attempting to do exactly the mission you’ve been assigned. The Klingons are a direct threat to you – they don’t want us in the Romulan/Klingon war. They know that if we enter, we’ll come in on the Romulans side of things. God, I can’t believe I just said that… Sorry, Captain. To continue…

“As much as they do not desire the Federation in the fight, they are preparing for the worst. They know what we’re up to out here, and in particular, what you’re up to out here. They know what a Transwarp Pulsar Class is and what it means if you succeed: It means a direct, high speed pipeline of Federation ships, personnel, and materials arriving on their doorstep, rolling in from the heart of the Federation to reinforce in a matter of a couple of days instead of several weeks. They are not enthused.

“With that sort of threat a distinct possibility, they can’t allow it to happen, but they can’t get caught doing it or they’ll push us towards an alliance with the Romulans. Therefore, there is every reason to believe that there are cloaked Klingon vessels in the area you’ll be working. Furthermore, there is every reason to believe that they had a hand in the disappearance of your 5 missing Transwarp sister ships.

“Your crew was selected for their capability, not their compatibility. You have some, ah, personalities among them, especially among your senior officers. They are all very skilled at what they do, the exact skills you’ll need to make this mission a success and help you overcome the unexpected. However, that typically carries with it an ego to match. It should be an eventful tour for your first command, and a strong challenge for your leadership and that of your command crew.

“Your ship is one of only 2 Transwarp vessels currently in Starfleet. In order to give you every chance of actually succeeding and not sharing the fate of your predecessors, you’ve had some upgrades to your vessel. The engines, of course, you know about. However, in addition to those, your shields are the very best available that we could fit on a ship of your class. Your computer cores have been updated to the most advanced systems in Starfleet, which is necessary for the last major upgrade, your sensors. From what we’ve been learning from your sister ship, the USS Pydna, operating out of Starbase 241, our closest star base to the Romulus system, we’ve made upgrades that will make your scanning much more effective and hopefully let you complete your mission more quickly.

“Support is available. This mission is critical and we are prepared to support you all we can. However, as you are moving through Transwarp space you’ll be outrunning any support we can give you and we’ll have no idea where you’ll re-emerge into normal space, or what will be awaiting you there. In the Regulus area is battlegroup 28 under the command of Captain Harlan Mattix on the USS Lynx, an Akira class cruiser. With him are the USS Huntley and the USS Ivanhoe, both Streamrunner class destroyers, and the USS Voodoo and the USS Wrath, both Spitfire class destroyers. As you can see, we’re making a strong commitment of hardware to your cause, for what it’s worth. Yes, we expect success, but more than that, it’s absolutely vital that we have it! Captain, can you get this done, are you the Captain for the job?”

“I wouldn’t be here if you and Starfleet didn’t think I was, Admiral”, was the captain’s cocky answer.

Ignoring the disrespectful attitude, the gallant admiral continued, “The star systems briefing transferred to your computer have the latest Starfleet Intelligence on the systems in the area – please avail yourself of it. If you need anything don’t be shy. You’ve got a priority ship on a priority mission – it doesn’t happen often, so enjoy it Captain! What are your questions? Very well, brief your people and go to work Captain. Questions?”

The situation with the people in engineering that aren’t officially under the chief engineer’s command was raised, and Burtell was surprised that Starfleet Intelligence was playing this in such a heavy handed manner. She confirmed that they are actually techs from Starfleet Intelligence, and that they are under the command of whomever the captain says they are under, though they didn’t bother to disclose that to anyone, nor did their orders require them to. Not to worry, she would address proper protocols when cutting orders with the SI Admiral in question, and the captain is free to operate his ship as he sees fit.

The situation with the sabotage was then brought up and the Admiral promised the Captain that he would be provided with whatever help he wanted, and to just let her know what he wanted.

“Very well then, good luck to you. Dismissed.”


Following the briefing with the admiral, the Captain, XO, and SO all had the opportunity to, at long last, meet each other.

View
Session 24: Phase II Character Building, Player Greetings, Learning the System
Wow, there's a lot of setup to this....

OFFICIAL LAUNCH DATE: 11/11/2017 3:00PM GMT-6
.
.

GAME FREQUENCY: BI-WEEKLY (else we’re without our chief engineer)
.
.

To Get Started….
.

Step 1: You already did it (it was joining Discord! If you didn’t, please go to Star Trek: Aftermath on Roll20
Step 2: You already did it (it was joining Obsidian Portal!)
Step 3: Join Roll 20
Step 4: Sign Up For a Free Box.com Account (no one makes any money on this, but it’s a free 10GB for you and gives you access to the gaming stuff and a lot more) then send the GM the email you used to sign up with so he can give you permission to access things
Step 5: Download the Character Generator tool (which you can’t do if you don’t do step 4)
Step 6: Choose your position on the ship (Again, step 4 required)
Step 7: Go through a character generation walk through to learn how to use the tool (don’t fall in love with your first try!)
Step 8: Develop your character concept, use the CG tool, and build your Starfleet Officer. Go nuts with it! Write up details, hopes, dreams, an ugly divorce, a whirlwind romance, and why you have that artificial arm and an overpowering fear of shrimp. Or do nothing,
Step 9: Select a secondary position (not department head or higher) that you will occasionally play, but not your main. Follow steps 6 and 8.
Step 10: Grouse with the other players about what a jerk the GM is (meet and greet and have fun). We’re ready to go on the next game.

At this point we can debate the best time to play if my posted schedule doesn’t work for everyone.

View
Session 23: Phase 1 Wrap Up
People, Places, and Events

Here’s the quick and dirty of what was to go down during the last 2 sessions (the plan anyway) represented as well as I understand character motivations.

Phase 1 Wrap Up Events

Discussion with Kssevose on the Endurance (last session)

Drop off prisoners and victims at Atbar

Seren confronts Gamble, orders him and the Endurance to butt out of the slaver situation

Gamble sends a report up the chain to protest the orders, is loudly not replied to

Endurance heads out of Atbar en-route to Sonebr with a fleet of cardassian transports hauling relief supplies fights off a few pirates that weren’t expecting a Star Fleet presence – they run

On Sonebr Starrbon tracks down Buva and threatens him with having Raife deported (Kssvosse tip), Buva talks (See below for details)

On Sonebr Wash comes across a dire medical case while assisting in their local clinic. The patient turns out to be her old tormentor, badly mauled by some beast, no eyes (or face really), she treats him anyway, but leaves word so that he doesn’t know it was her who treated him. She may have accidentally rendered him permanently impotent as well.

Leaving Sonebr, the Claymore ambushes the Endurance, wounding her, but the Claymore is also badly damaged as the Endurance fights back, driving her into retreat

The Endurance makes repairs and limps towards Atbar, Gamble filing a formal complaint with Flanagan, who strongly advises Gamble to reconsider strongly, sleep on it, then make his decision (all via coded channel), the stakes here are insanely high, there will be no backing out of it, and the Claymore has filed no report at all.

While pondering, the Romulans uncloak at Atbar and transmit 5 separate views of the combat between the Claymore and the Endurance, corroborating the Endurance’s view with sworn testimony from the commander of the Romulan task group.

End of Phase I

Starrbon confronts Buva who refuses to answer questions. Starrbon explains to Buva that all he has to do is call a guard over and point out that Raife is off world from Cardassia and without papers and she will be captured and deported. Buva is hostile but relents. It’s still like pulling teeth to get anything from him. Excerpts from his statement to Starrbon:

“How do you most easily control a star faring state? With hostages, of course. Good ones – nothing but the best! Why were all the important Cardassians and their families moved back to Cardassia, do you think? Of course, individuals come and go all the time, even ships full of individuals, all leaving loved ones behind on Cardassia, unable to leave. Travel restrictions due to terrorist activities indeed.

“The True Way were captured, were conquered, were dead, but back from the ashes they came. Killed again, but back again. How? Who stands to gain from a terrorist organization being active in Cardassian space? Not the Cardassians. Not the Klingons or Romulans, they grabbed territory and worlds and wealth. No, the ones with their fingers on the buttons, and the will to push them, use this terrorist threat to keep all their lovely hostages right where they want them, right on Cardassia ‘where it’s safe’.
“With their families here and under threat, the new Detapa Council is controlled. With their families here the military is controlled. They use key people in specific places to keep us just strong enough to continue and just weak enough to remain under their control. Only those that have to know are told the price Cardassia will pay if they fail to comply.

“This is not paranoia, it’s real. You know Tathon’s family is on Cardassia. We’re the only ones he could get out, so he did what he could. Our work here is to engineer a means to rescue his wife and child. You coming here and drawing attention to us is not helping!

After Raife’s identification and deportation is dangled again, Buva explains. “Fine. You want me to say it? I’ll say it: Your Admiral Koderman implanted 28 tri-cobalt devices into the deep continental crust of Cardassia Prime. 28! 3 are enough to make the surface uninhabitable for thousands of years! It seems he didn’t want any special operations forces to be able to find and destroy or disable just a few. He put in 28 of the damned things. 28 that we know of! There are other countermeasures in place as well, on both the planet and installed on each of our ships. And apparently he’s kept it secret from Star Fleet Intelligence and the Federation Council as well. How? Everyone is in on it, so how? It’s the most bizarre thing I’ve ever seen.

“If you want to know more you’ll have to take it up with Kssvosse, he knows a hell of a lot more than he told you, I guarantee that. Here’s a little payback from me to him – do some research, find out how old he really is. And what species. You’ll love what you discover. Now leave me, and Raife, the hell alone. I see you again, I’ll kill you. We clear?”

In the meantime, Major Jackson had a little girl talk with Raife, perhaps a little rougher than most, but girl talk nonetheless. The follow is the Major’s synopsis of the conversation:

  • Buva was a master spy for Tathon, Raife was his assassin, pushed a button, boom, dead Ferengi.
  • Buva and Tathon grew up together, maintained illusion of master/servant, were best friends.
  • Tathon’s wife and child are on Cardassia as hostages.
  • High command knows everyone on Cardassia is a hostage.
  • After end of Dominion war new government began consolidating all people of power and influence on Cardassia to control them to include government, military, industry, along with their families.
  • People enter Cardassia but do not leave, fear of assassins used to keep them in place.
  • Taking advantage of this, the Federation mined Cardassia with Tri-Cobalt warheads (at least 28, exact number unknown).
  • Raife is a good fighter, but not better than me.
View
Session 22: Revolting Slaves, And The People Who Sell them
Brunch with an old acquaintance

We pick up where we ended last session having just enjoyed the departure of first the Klingons and then the Romulans. Cpt. Aponte and the Redan went after the retreating slaver ship, the Hiewan, reaching it easily and blocking any transmissions it would have made in the process. They returned to the Endurance shortly with the ship in tow.

The Hiewan
Orion_Freighter_Batris.jpg

Meanwhile, upon the Girma, the Marines were dealing with the prisoners, all cardassians from Eisae (captured in a local bar after end of shift) who were harnessed into some type of pain booth thingy. They released the first prisoner from it, and he became agitated according to the onsite commander, Marine 1st LT Kaita Joole so they strapped him back in. (in actually it was later discovered that he had a seizure from being released without the proper protocol, placing him back into the pain field solved the seizure problem until medical could deal with it). None the less, Major Jackson was not amused and, um, expressed herself in the LT’s general direction.

The Girma
Orion_Freighter_-_Girma.jpg

After a little planning, the prisoners were transported to the Endurance to receive immediate medical treatment after their release into the emergency care unit (a converted cargo bay that the crew has gotten so skilled at setting up recently). It is interesting to note that none of the prisoners seemed to object in any way to Lt Peren’s ritual scar of shame.

From the computers the exact destination of both ships was determined to be a large, vaguely spherical asteroid of roughly 350 meters diameter. Plans with unloading instructions were also acquired.

Orion Slave Base
Prison_Asteroid.png

Thus began the planning. They planned, oh how they planned. LT CMDR Samuel L. Starrbon promotion to Lt. Commander came through. Still they planned. The Starrbon was elevated to 1st Officer of the Endurance. Every detail was eventually planned for. Lt Meda Zoalki was named Second Officer. The final details were ironed out. It took a few minutes. Then the plan was scrapped in favor of a frontal assault.

In essence, the base was running an internal scattering field to prevent transport and to prevent emission of electronic signals that would give the base away. The base has (it’s ours now, and they are still there) extremely rudimentary sensory apparatus consisting of passive devices not much more sophisticated than a CCTV setup. Sensor probes were used to pinpoint the controls for for the scattering field, all at a single console in their engineering room with a single person monitoring and operating it (poor bastard).

Captain Aponte from the Redan called about then to let the Endurance know that another ship matching Kssvosse was in the area as well, and Wash made a call to him and had a brief chat and worked out a trade and somehow involved the captain in a 3-way (conversation).

The Marines were loaded on transporter pads to be beamed to the asteroid via relays that CWO Ssscritcha, (unpronounceable) Bob the Edoan Transporter Chief, had cobbled together with pattern enhancers strapped to sensor probes with old shoelaces (yes, still used in the 24th century) launched to 4 specific points along the way. The officers had fresh promotions and new command positions in hand. Medical was ready for more action. That’s when the Captain, whose player was high on drugs from a dog induced awkward tumble resulting in the near amputation of his leg, gave the order, “Uh, you guys can go now if you want to.” Just like that, it was on.

Starrbon fired the Endurance’s lone phaser shot with ludicrous accuracy (really), punching through the Asteroid’s outer layer and powered just right to not erupt out the other side of the asteroid, voiding the atmosphere, thus killing everyone inside and robbing the Endurance crew of any possibility of entertaining prisoners. It destroyed the console and power relays for the scattering field, somehow not entirely killing the person operating the system who was RIGHT FREAKING THERE when the beam hit. He has most of an upper torso and a bit of one of his arms left, not much left of his face though, but technically still alive and with exciting brain activity, particularly in his pain center.

Marines began to cycle through the transporter system 6 at a time and Bob was heard to mutter, “I’ve always wanted to try this….” as he poured sentient flesh and minds through his hastily assembled and completely untested transporter relay system. Upon arrival on the asteroid, intact as far as any else knew, they immediately began to marine about. Which is to say, ass was kicked, then kicked again for good measure, harsh language was flung about, and the pantry was raided – not necessarily in that order. The area was secured in less than a minute as the 50 residents of the asteroid were still recovering from the phaser strike and the scattering field system overload and thinking they had been hit by another large space rock.

Large Space Rock
Large_Space_Rock.jpg

Having secured the asteroid and the prisoners, the GM was tired and stopped writing until tomorrow (or later) when he will regale you with tales of Brunch-like conversations with Kssvosse in part II of our exciting recap of today’s events.


Refreshed, rejuvenated, filled with memory enhancing drugs (thank you coffee!), and prompted by the wise counsel of senior members of our group (though clearly not senior enough to suffer my memory issues) the semi-dauntless, but partially-dauntable GM has returned at long last to finish his post (no offense to the people of Finland).

The Captain, having dangled a massive carrot

Massive_Carrot.jpg

in front of Kssvose (in the form of 2 captured medium Orion freighters that needed new ownership and somehow were listed as scuttled), had Wash invite him to enjoy a meal with the Captain and his senior officers. Not wishing to endanger what he was clearly so close to obtaining, the Orion smuggler was quite cooperative and happily answered all questions put to him. In fact, he intended to answer more fully than he actually did as the questions came in faster than he could distribute his information, and the questions were so basic that most of the answers were of no threat to anyone. That was not true of all the answers.

Kssvose tried several times to warn the Captain off of his line of questions. He asked, repeatedly, is these were things he really wanted to know and that he would not be happier or more secure if he knew these answers. That he really should consider continuing as he had, business as usual. When the Captain did not relent Kssvose became…informative.

This time with Kssvose was used by the Captain and senior officers to gain an inside ‘lay of the land’ of the TF21 operations area, what was going on behind a lot of the movement being seen, who the players were, and so on. The first of these gems of knowledge was the scope of the slave trade and the relationship of the Breen to the slavers as the primary buyers of Cardassian ‘stock’. Taken from unprotected and unpatrolled systems, the slavers were farming the area to meet a contract to supply a certain number of slaves to the Breen. Whether this was to be a one time contract or a continual supply remains unknown as does the purposes the Breen have for the slaves they are purchasing. The Breen are paying over the market value for this commodity, and much of this extra amount is going towards the Klingons in the area who are facilitating safe passage for the Orions and using the funds to employ smugglers to shore up their own supply situation.

Breen
Breen_Male.png

Nothing of this has appeared in Starfleet reports indicating either ignorance, which is unforgivable, neglect, which is also unforgivable, or intentional withholding of information, though a viable purpose for doing so defies imagination. Intel being the most heavily indicated as having issues of some sort, it was not alone as Starfleet and Federation activities, goals, and operations, even diplomatic activities all show odd inconsistencies.

Starfleet Intelligence (unofficial Logo)
starfleet_intelligence_pinup_by_startrekadmiral.jpg

Cardassian behaviors were also brought into question. It was indicated that Buva, Tathon’s former attendant, might be of use in that regard. Kssvose did say that questioning him directly was unlikely to yield results, but he could be leveraged.

Kssvose made no secret of both the fact that he used to be an intelligence operative (which the Endurance officers already knew, which Kssevose already knew they knew, etc) or that he had served with Captain Seran of the Claymore (which was definitely NOT common knowledge).

The meal ended before Kssevose was fully interrogated due to his anxiousness to take command of his 2 new Orion freighters, the players running out of time that day, and one of the players being pain medicated to what the GM assumes was well into the hallucinogenic realm (he kept calling himself Captain and giving commands to people!).

View
Session 21: Return, Reinforce, Retaliate
Unexpected Allies

We begin at Atbar where the USS Endurance has arrived for a day of downtime to refurbish its systems after stressing them heavily at Sonebr. Some work was done in Taggrut while a few more buoys were deployed (2/3 done now) but more needs doing. Facilities are together enough to allow 24 hours in a spacedock to work on the stress points the old girl suffered while operating in atmosphere. She’ll occupy one of the 2 slips currently operational. Shoreleave is still restricted on Atbar at this time.

Atbar_II.jpg Atbar II

Taggrut_IV.JPG Taggrut IV

Additionally, the Endurance is taking on new officers and crew, saying goodbye to their engineer and Ensign Ricky, who has been promoted to LtJG and is being sent to the Romulan front lines. We wish him luck and will (more or less) miss him.

Lt Medi Zoalki, Bajoran, is the newly assigned Chief Engineer will be joining the crew along with LtJG Iala, Edoan, the new Computer Chief who is replacing LtJG Frae (who was transported out along with her belongings as soon as Atbar was in range, but all recordings and sensor logs seem to have no record of the event.)

Joined by the Redan, ready to return to Taggrut and finish the buoy chore, the Endurance receives a message from Buva, still on Sonebr. In it he relays information regarding a large slaver fleet that picked up a shipment of 1,200 ‘livestock’ that were in stasis on the planet and departed with them under cover of Klingon protection. Cardassians have arrived in more force at this time, mining is expected to get underway in a weeks time (using the Dominion tech spider bot things), and the refugees are doing much better with hardly any additional losses thanks to the endurance. At this time the Klingons seem to have abandoned the system.

Present concerns:
The information from Daimon Ult on the slavers needs to be checked out.
The information pulled from the pirate vessels needs to be checked out.
The sensor Buoys need to be deployed.
There’s always that haunted prison.
The Huaco system needs to be checked out.
Sonebr has been added to your patrol area.
The Azrael is inbound and will be here in roughly a day. It has applied for the slip Endurance is vacating to make its own repairs.

-——————————————————————-

LtJG FRAE, ISARA
Assistant Science Officer
USS Endurance
TF21, PG5, Cardassian Theater Military Command

FINAL REPORT

Disposition of the slave trade in our patrol area: Using the data acquired from the Ferengi, and matching it up with our movement and data stores, the map of locations and routes should be fairly accurate and the Ferengi data is validated. Additionally, Atbar has been marked as a likely center for command and control activities. It probably will be a small base hidden in one of the asteroid belts, likely the closest, where it can keep a watch on the goings on of the inner system, particularly Atbar II, aka Thrombo. Size and disposition of ships remains to be confirmed. In essence, they are moving roughly 25,000 people a year to Breen space.

Disposition of the pirates in our patrol area: Active Orion organizations include Monas, Silkassi, Miskoval, Krast Vokassik, Orion Syndicate, and Green Trade (slavers), with the axis of power between Orion Syndicate and Green trade and the others falling into line. They seem to be pursuing a larger goal and they are operating in an organized fashion, but appear to be quite random by using multiple organizations and many of the other pirate factions as hired guns. Derot is the only major Cardassian player and doesn’t seem to be on Team Orion, and neither does Fownd Merris, our lone Bajoran player. They actively avoid each other. The others can be found occasionally in the employ of the Orion faction, but mostly stick to their own rackets. These include, in order largest to smallest, Quantum Vengeance, Spite Clan, Silent Steel, Mist Assembly, Entropy, Oasis Transport, and Dire Leviathan bringing up the rear. Finally, the Maquis seem quite happy with piracy and include Jansie Mellor, Consuala Brekenridge, and Fintelx. They will often fight each over easy pickings, but will turn and act together against any arriving authority.

Disposition of the Maquis in our patrol area: As per above, they seem to have settled into a role as simple pirates, albeit some very high tech ones with very solid training. They will likely be a threat to the area for quite some time, at least until a concerted effort to root them out is undertaken.

Disposition of the Klingons in our patrol area: All sensor logs clearly indicate that the Klingons are routinely in the TF21 area. Our actions and those of the Claymore seem to have blunted a strong move on Taggrut as we did much better than they were expecting. I do not believe that they are through with Taggrut, and will play cat and mouse with the Cardassians both there and at Sonebr to force them to commit more forces to the area. I can’t say with certainty where they will be pulled from but my expectations are that this is a feint to focus attention while they strike in another area.

Disposition of the Romulans in our patrol area: I have little to offer other than they do seem to be actively monitoring us and the other ships of TF21. So far we are the only ones they have ‘communicated’ with or allowed us to realize that they were there. My projections suggest they will be making a move, most likely an overture of cooperation in the next month, if not sooner.

Disposition of the True Way in our patrol area: They are almost certainly holed up in the Huaco system where they have constructed ship manufacturing capabilities. Their prior activities seem mostly to be propaganda actions to demonstrate that they are still a force to be reckoned with, likely to drive recruits. The action in Atbar strongly indicates this. All indications are that they were disposing of older ships in favor of newer ones they have been building and they didn’t want the Cardassians to have any chance of returning them to service (though they did recover 4 of them in Atbar, 2 of which were in orbit with us at Sonebr). They may well have rid themselves of rivals to their command, those that wanted action now and had no patience to wait. The interrogations are proceeding and seem to bear that presumption out so far. There is definite momentum towards something in the near future that we are not going to like.

End Of Report

-——————————————————————-

Mersoh_Slaver_Encounter.JPG

In Mersoh (the entire system is basically a gigantic asteroid field with strong radioactive particle fields scattered throughout) 2 slaver ships are tracked, one coming in from C52 (and likely Eisae before that), another from the red dwarf designated C47, the two of them looking very much like they will rendezvous. Captain Gamble ordered Captain Aponte and the Redan to intercept the one from C47 (the Hiewan) while he and the Endurance would engage the ship from C52 (the Girma). Using the Endurance’s newly tweaked sensors (recently tuned to better read life signs) these ships were revealed despite their quite sneaky tactics of traveling through areas that normally would hide them from sensor scans very efficiently.

Of course, the Orions were not enthusiastic about heaving to, The marines had some fun onboard and were preparing to transport the entire crew and all slaves (115 personnel, 10 crew 105 slaves held in ‘pain fields’ for mental conditioning) when the Klingons uncloaked.

Vor_Cha_Image.jpg

The particulars of the area of space the Orions were traveling in made it much easier for the Klingons to sneak up and surround the Endurance and the Girma with 5 Vor’cha Type A’s (88 ss, 138 power). Led by Captain Kerrogh of IKS Mangghom Bey, the Klingons uncloaked and locked on to the Endurance, ordering them to lower their shields and surrender. The Endurance refused, maneuvered in tight with the Girma surrounded her with their shields and called the Redan to warp to them to provide support. There was posturing. New and improved posturing, in fact.

Things got ugly for a bit, then it started to look like the Klingons would attack, in spite of the arrival of the Redan. The Hiewan (no slaves on board by the way) got its engines back online and started to move away under half impulse (likely working on improving that speed) after the Redan moved to assist the Endurance. As things reached a high degree of tension and weapons locked all around, fully loaded and charged, and Captain Kerrogh had acquired a sufficient degree of crazy in his expression to indicate that ‘this was a good day to die’, or at least murder some Starfleet chumps, the Romulans uncloaked.

D_Deridex_Class_Battleship.JPG

The 5 Romulan D’Deridex Leviathans (110 ss, 148 power) (sensor analysis confirmed these were the same ships the Endurance had been observed by and had tracked on several occasions) uncloaked around the Klingons, powered and locked their weapons on them. Anger, posturing, and bluster ensue, but no one is really enthusiastic to pull the trigger because no one here can get out of it without losing ships they can’t replace. The Klingons don’t manage to blow up the transport vessel, and eventually cloak and leave. The Federation and Romulan ships let them. The Endurance recovers its people and more entertaining computer data on ships, personnel, and movements associated with this particular Orion Slaver ship. The Redan takes off to recapture the Hiewan when it’s clear that the Endurance is under no immediate threat, providing another ship computer core to pillage for intel.

The Romulans stay behind and the Endurance captain and crew gets to meet Commander Tacranaal (Tac-ra-naal), “Greetings Captain Gamble, officers and crew of the Endurance. We are happy to have been of assistance to you. We have no wish to further interfere in your operations. Please, be aware that we will be in the area should those savages choose to return. Our assistance is available should you happen to call for it, and in return we certainly hope to be able to call upon you as well. As you no doubt realize, we are the ships that have been observing you from a… discrete distance for some time now and we are most impressed with how you choose to comport yourselves. I wish the same could be said for all Starfleet vessels in the area.” Captain Gamble inflicted his diplomacy upon Tacranaal for a brief time. After this short visit with Gamble, Tacranall said, “Well, we have business to attend to and you most likely do as well, so we’ll have to save the, um, [looks off-screen, seems to be reading a cue-card] tea and cakes [looks back] for another time. Good Day Captain.”

The Romulans cloaked and left in the direction the Klingons went.

End of Session (please add things I missed in the comments)

SIDE NOTE: Campaign Objectives Achieved So Far….

ADVENTURE LIST:
1. BUILD YOUR SHIP AND MEET THE CREW
2. GETTING TO CARDASSIA
3. MEET THE TRUE WAY – A WARM WELCOME
4. SPACEDOCK/LIAISON
5. TATHON’S MISSION
6. GETTING TO KNOW YOUR OPERATIONS AREAMEET THE MAQUIS
7. TAGGRUT SITUATION
8. ATBAR ATTACK
9. SERAN TAKES OVER
10. MEET THE KLINGONS
11. REINFORCEMENTS
12. MEET THE PIRATES
13. SONEBR RETURNED
14. MEET THE SLAVERS
15. MEET THE ROMULANS

View
Session 20: Rebuilding A Planet
The priorities of survival are the priority

Still on Sonebr, picking up where we left off last week.

We begin with Dr. Shaw (aka Wash) on the planet doing triage. At various times she is doing life saving surgery, and it’s not pretty. Her commbadge fell off at one point and into a patient and was not noticed, but was later beamed out and back to her, none the worse for wear. She was assisted by various medics while on Sonebr, particularly 3 cardassian medics following behind her and euthanizing patients she had saved because they would be an unwarranted drain on medical resources, they would serve no useful function in society due to their wounds, were mentally unstable, etc, calling it ‘mercy’ in the custom of their people. Wash initiated a confrontation and they became more…restricted…with their mercy, but did continue.

As she worked, Wash was seen speaking with a Tall human of Indian descent who was assisting her. He did make a few statements and ask her a few questions:
You do get around Lt. Shaw. Isn’t it curious how the Klingons just up and left? What a mess they’ve made. The Cardassians will be pouring resources down this hole for some time to come, don’t you think? Won’t it be fun for them to guard? I wonder what will get left unguarded?

Shaw grunted a few non-committal answers to him as she was rather busy, and he continued.

Well, I have a bit of information for you to chew on while you work. Not to come off like Charles Dickens, but your captain and crew will be visited by three Ferengi this eve. Let’s call them the Ferengi of business past, the Ferengi of business present, and the Ferengi of business future. Each of them will offer a different deal, and they should be listened to. Sadly, there will not be a life lesson from these encounters:

The Ferengi of Business Past turned out to be none other than former, now restored, Daimon Zort and Taar Meski, now 49% shareholder of Trakon Supplies (Grutos Prut owns 51%, new board of directors), wants to build out the mines on Sonebr and there isn’t a moment to lose. The Cardassians are eager for this deal and are more interested in it than they are in helping their people (at the command level). They can offer the Endurance detailed intel on the Klingon forces in the area, how they are deployed, conditions of the other planets, and the nature of their relations with the pirates in the area plus evidence of the planning to create the ‘crisis in Sonebr’ naming names, dates, places, and recordings of conversations. The entire affair in “Meeting the Guv’nor” was really a carefully orchestrated ploy by Zort to arrange for him to be in this position at this critical moment. Surely you can see that hoo-mon?

The Ferengi of Business Present: It’s the Captain’s old friend, Daimon Girn of the Mretek. From the Taggrut incident. He’s doing well, really well. He has the missing key components, including the very large parts, needed to put the cities power systems and water purification plant back online. They are stored in the 5 terribly delicate Ferengi Cargo Liners with the overpowered engines and ludicrously heavy shields. He would simply appreciate fair compensation for having safeguarded the critical pieces of such vital systems from the Klingon’s plans to permanently destroy this infrastructure: compensation for their costs plus a healthy plus bonus plus negotiation fee plus storage fee plus security deposit plus a long term (50 years) contract to supply food, clothing, luxury goods, alcohol, fuels, and other such supplies as are needed or may be needed. He also brings:
1. Water desalination and purification system.
2. Pieces and parts (incomplete, can replicate the rest) for a civic basic food replicator system.
3. 200,000 non-diseased blankets, 500,000 rations, 10,000 cargo units of drinking water, medicinal supplies.
4. The Cardassians have some but not enough of all that and simply want to take it by force from the Ferengi who ‘stole’ it to begin with.

The Ferengi of business Future: Daimon Ult of the Ferengi Salvage Confederation has all the inexpensive, well-loved and cared for, slightly used products that would be needed to put a world like Sonebr back on it’s feet in no time (3 months more or less). He has a cousin that specializes in low cost dome construction as well to give the citizens a nice-ish place to live. He can be here in a week and have a city level dome in place in roughly a month if people aren’t sentimental about existing structures. He very much wishes an introduction and recommendation of his services from Starfleet to the Cardassians to help them solve their problems. He would be willing to part with information regarding the Orion slave network in the bottleneck area, where their operations are located, who the players are, the routes they like to take, who they are selling to and where the slaves are being taken. He really doesn’t mind since he was cut out of the deal.
1. If the Captain will help with this situation (help him get in to see the Legates, out alive, and make a profit) he will give the Captain the most precious thing the Captain could possibly want: Information.
2. He knows the slavers bases of operations, ships warp signatures, who is who, how their network is laid out, and how much they stiffed him for.

In other news: Reports of hostilities between Claymore Vs. Klingons and Pirates working together. Azrael assaulted by a similar force while en route to meet up with the Claymore suffered a systems glitch and the pirates got a few shots in. Claymore continues to sport it’s special markings.

Sonebr Problems – The crew suffered through and found solutions to the problems listed below (full details can be found in their individual logs):
A. Engineering: Clean water source. Air is mildly toxic and progressively becoming moreso, this is the garden spot of Sonebr IV. Power – there is none and no infrastructure.
B. Tactical: Track various pirates, Klingons, slaver strike groups, and unknowns still in system. Fight off a couple of sneakies. How can this planet best be attacked and how to defend against that? There’s an old Cardassian defense satellite net around the planet, but it’s unpowered and non-functional at this time….
C. Medical: Save as many as you can. It’s massively overwhelming.
1) Those who won’t/can’t release their dead children/loved ones.
2) Those who insist they are fine but aren’t at all.
3) The dying that simply can’t be saved.
4) The dying that can be saved that require resources that would save 10 others.
5) The suicidal.
6) The severely brain damaged.
7) The horribly disfigured.
8) The cardassian mercy policy of putting down those listed from 3 to 6.
9) The people looking for specific survivors.
10) The religious zealots demanding that all medical assistance be rejected by the people.
11) The people listening to the religious zealots. The children of these people.
D. Science: How bad is the planet, can it be saved and if so what will it take? The life on the planet has lost its vitality, it’s dying. The food chain doesn’t exist and the toxins are killing all life except for the most extreme extremophiles. The toxins need to be extracted and purified, new life seeded and tended, the planet basically terraformed.
E. Marines: Still combatants on the planet.
1) Klingons that wouldn’t leave. (they were found and rooted out by the cardassian soldiers)
2) Dug in Cardassian Soldiers, sneaky, terrorists, don’t know the Dominion war is over (as per Japanese). They launch a small pirate ship, mimic transponder of the actual small pirate ship the Endurance is using, dock and slip aboard the Endurance. Sabotage ensues. (they didn’t get that far)
3) Crazy civilians. With sticks. And knives. And a rock.
4) Collaborators the population wants to kill.
F. Pirates and slavers:
1) There’s not much to take, but there are pirates that have stashes here and they want those stashes. They don’t all have transporters and they are attempting to land and retrieve their goodies. There’s the typical gold press latinum, special liquors, art and jewelry, and there’s also special medicines, rare plants and animals, along with weapons and supplies the pirates need for their base(s).
2) The slavers have people stored here to pick up. They are in stasis and don’t show up on scans, the storage facilities are below ground and shielded form EM detection. They are here to pick up their inventory: 1,200 head of livestock. (not found, see following week’s adventure log)

View
Session 19: Triage At Sonebr
"...hmmm, that's a weird blip..."

What do you mean you’ve ‘acquired’ a case of black market Klingon prune juice?

If I haven’t chronicled the exploits of one or more of you adequately from last week please do post what I missed in the comments section here please.

With only 3 players in attendance due to some football festival that my team wasn’t taking part in, things played out in more of an individual and duo format, much of which hasn’t been inflicted upon the players yet. All players are encouraged to play their characters ‘offline’ in the comments section of this post below. They will be posted sequentially so events may become a bit disjointed for the casual reader but we will know. Yes, we will know.

PROLOGUE:
Sonebr IV is now in cardassian hands, and the Sonebr system out to its ort cloud is now cardassian space. While diplomats argue and borders are redrawn, uninhibited passage is guaranteed for any vessel en route from Taggrut to Sonebr. Meanwhile, 48,200+ cardassians remain on t he planet, starved. severely dehydrated, nearly dead or dying, along with Sonebr’s biosphere.

The Cardassian commanders at Sonebr formally request (directly since you have no liaison) that the Endurance lend a hand on Sonebr to help ease the population through this crisis whenever and wherever you see fit to help save as much of the population as possible. Computer census put puts them at 48,362 with some anomalous reading at areas of the city edge and in the nearby foothills. In general, a large percentage of this population is on the brink of death, mostly due to starvation, dehydration, and exposure. They lack food, water, shelter, and clothing, and have for some time now, and a good many are diseased and/or have serious injuries.

Pirates continue to come and go and the Klingons are very obviously in the area providing “protection for all ships”. This is keeping the Cardassian ships in tight around their vulnerable vessels and restricting their operations to this city while looting of other sites is obviously continuing. These would be the more brazen and/or desperate pirates by the way. Some of them you’ve seen before. The Breen and Ferengi ships are in the area as well.

CONLOGUE:
Things happening are broken up by position and start on the planet with Dr. Shaw (aka Wash) who is attempting to save lives. She is dealing with the worst of the worst in a group of 48,300+ people who are all in a condition very much like a Jewish WWII German prison war camp survivor when the allied forces found them. Less than 2% who are older than 8 years of age are male, the rest are females of all ages. As Wash works various people assist her. At some point she realizes one of her helpers is someone she knows named Mr. Jones who she briefly converses with, though no one is sure what the conversation is about.

Tactical: On board the ship, Tactical noted several ships in orbit, approaching, or simply in the area. These include 3 Breen cruisers, 3 separate Ferengi groups (all moving towards the planet), 25 Klingon attack craft, the Cardassian rescue flotilla, the Endurance herself (Yes, they noticed themselves), and roughly 20 small transport craft and 5 freighters, all unknown.

Additionally, Lt Starrbon discovered a ring of Cardassian defense satellites orbiting the planet that appeared dead or offline at least, 87 in all. Consulting with Lt. Grant from engineering, they went to work (after wresting 1 shuttlecraft from ops, the only one that could be spared and even that one would be sorely missed) checking out the ring. Lt. Grant, knowing that power sources would be useful on the planet, viewed the ring as a ready built reserve of power sources available for harvesting. Going into the first one (spacesuited and physically opening the cover and tinkering) he discovered that the main power connectors to the charging device and been severed with an energy beam, and also that it was booby-trapped. He managed to get a few feet away before the obvious chemical explosive charge went off.

Working on other means to harvest them, a scan revealed that the next one in line seemed to not have the same damage to it and so Jackson went out again, removed the panel, found no damage and just a simple on/off switch. He turned it on, it didn’t explode, but it was completely drained of power. Finding a small active panel, he set the system to begin charging and was looking for a way to reprogram it when a small data interface chip designed to plug into Cardassian technology was beamed directly in front of his faceplate, lightly startling the wearied war veteran. He plugged it in and Frae told him she had set the shuttle, with Ensign Ricky still inside, as a hostile target. The turret immediately locked onto the shuttle, and Ensign Ricky pooped a little. There was not enough power for a weapons discharge, as Frae was aware, and she reset the shuttle to friendly, thought the weapon was still trained on the shuttle, it’s last target. They subsequently activated 3 more defense satellites and progress (the GM assumes) continues.

Pirate transport capture:

Various small town surround the main city. While the city doesn’t have any buildings remaining, and not even many stand alone walls – really no shelter at all, these small towns do represent some opportunity for shelter for at least some of the residents. The residents are thirst-starved, food starved, naked, and without shelter in a mildly toxic environment. This area was occupied by the Klingons who kept the local atmosphere toxin free, and took that equipment with them when they left.

More recently, Starrbon made contact with each of the three Ferengi ships/groups inbound to Sonebr IV. The closest of them is former, now restored, Daimon Zort, Taar Meski, who is now 49% shareholder of Trakon Supplies (Grutos Prut owns 51%, new board of directors), wants to build out the mines on Sonebr and there isn’t a moment to lose.

The second of them is the Captain’s old friend, Daimon Girn of the Mretek. From the Taggrut incident. He’s doing well, really well. He has the missing key components, including the very large parts, needed to put the cities power systems and water purification plant back online. They are stored in the 5 terribly delicate Ferengi Cargo Liners with the overpowered engines and ludicrously heavy shields.

Finally, there is Daimon Ult of the Ferengi Salvage Confederation has all the inexpensive, well-loved and cared for, slightly used products that would be needed to put a world like Sonebr back on it’s feet in no time (3 months more or less). He has a cousin that specializes in low cost dome construction as well to give the citizens a nice-ish place to live. He can be here in a week and have a city level dome in place in roughly a month if people aren’t sentimental about existing structures.

Engineering: The Endurance crew and Cardassian military personnel are fitted with respirators, a simple and effective means of protecting against the atmosphere at the current levels of toxicity (which is steadily rising). What could those do for the weakened population if they were made available, and what would it take to make them?

To drive much of the larger projects that will be needed to save the population the planet will need a source of power. The Endurance’s Auxiliary Power systems are 2 high efficiency fusion power plants built right into her hull. The ship carries the pieces and parts to do a near full replacement including all critical components. If the ship is totally without power it gives the people onboard the chance to put power of some kind online and thereby survive. Rugged and durable and designed to function even when damaged, it’s an optimum solution to powering a small city fully. Tathon and Jackson started having the parts sent down.

Still, it’s hard to set up a fusion plant in a rubble field. Taking a que from the Cardassians who were using ship weapons to clear and flatten sections of the ruins to set up temporary shelters, Starrbon followed suit and did the same 2km away from the refugee population. Creating an area a half kilometer in radius, he then set about flattening a road to where the people were. Those on the ground and in space contacted the Endurance to shut the operation down as it approached a point 200m from the populace. The unfortunate part of this is the efforts of Starrbon and the Cardassians did kick more toxic particulates into the immediate atmosphere.

Additionally, Starrbon dropped a small engineering team into the nearest and least toxic (due to proximity) of the small towns. There the e-team pulled the shield generator from the shuttle (much pilot complaining was heard) and then the shuttle was released to return to shuttling materials to the planet. The engineering crew (2 ratings and an NCO) set to work to modify the shield generator to put a large but very light ‘shield dome’ over that community. Not designed to do much more than prevent additional toxins from entering, the town, it’s nearly ready and ready to power. With the addition of an atmospheric scrubber (like the kind the ship uses) all the toxins within it could be cleared in a couple of hours.

The same system scaled up could cover could be deployed in the area of the population to generally reduce the toxins in the open air to tolerable levels and eliminate the need for the breathing masks.

Medical:

Science:

Marines: There’s rebels in them there hills, maybe. There’s something there, the sensor’s say so.

View

I'm sorry, but we no longer support this web browser. Please upgrade your browser or install Chrome or Firefox to enjoy the full functionality of this site.