Saturday, March 23, 2019

Investigation at Kortar

Tasked with further investigating the neural parasites, the crew of the Tiberius found themselves entering Klingon space (with the High Councils permission) to investigate the Kortar Station. A thriving station during the height of the Klingon Expanse, now only those Klingons who have fallen from the Empire serve on this remote, frontier station. The main question the crew was looking for is: why did the station suddenly go dark after recalling the Decius?

Upon arrival at Kortar, scans revealed a lifeless station with no ships in the vicinity. However, one escape pod was found inside a nearby asteroid field with 1 faint life-sign believed to be Klingon. The crew attempted to tractor beam the pod to the ship, but quickly learned of some interference the asteroid field was creating. The crew then thought about using the transporters, but the same interference would make the task equally as difficult. After a few minutes of discussion, they came up with an alternate plan: jump into the worker-bees and gently push the pod into the shuttle bay.

Once inside the bay and the pod was opened, the crew was shocked at what they saw: a mutilated Klingon in what appeared to be regressed form. The Klingon died almost immediately. Scans concluded that the Klingon mutilated himself and that the neural parasites DNA was trying to re-write the Klingon's DNA.

The crew then decided that they had to visit the station and find what they came looking for. A small away team beamed over to the command level in EV suits and attempted to restore the station's atmosphere. Once the team restored the atmosphere, the rest of the away team joined them on the command level and began searching for clues. While trying to access the operations consoles, Lt. Vos accidentally tripped a security protocol. This placed the entire Command level to go into lock-down mode, though Lt. Foxwell was able to override the lockout and resume collecting data.

Data revealed that the Commander was worried about what was happening on the station. The crew surmised that the Commander was the one that sent the distress signal and evacuated the stations atmosphere from sickbay. Logs also indicated a Romulan was seen on a Tellarite freighter bound for the Cordolan system, which the crew figured would be where they need to go to next.

Before the crew left the station, and to be thorough, the crew made the trip to the infirmary to collect more data. There, they found multiple dead Klingons along with a few dead parasites. One of each was transported to the Tiberius for additional studying. The crew also found an unsent audio message, which, when decrypted, revealed that the Kortar Project, whatever that was, was a complete failure and that Klingons were proving to be an incompatible species for integration and were de-evolving. This made Lt. Commander Torc (our Klingon security officer) breathe a breath of relief knowing there was a fighting chance to resist the parasite.

At this point, the crew returned to the ship with the data and to find they will indeed be heading to the Cordolan system to track down the freighter and the Romulan they saw on the security footage and figure out this mystery.

Check back in 2 weeks to see what the crew of the Tiberius finds in the Cordolan system.

Sunday, March 10, 2019

Rescuing the Alcubierre

After delivering supplies to Starbase 23 and making a few repairs to the Tiberius, the crew was off on her first official mission. Starfleet informed the crew the USS Alcubierre, an Oberth-Class ship, has not reported in as expected. Located in the Elicona sector, the crew was tasked to figure out what happened to the Alcubierre. The Alcubierre was testing a new warp core engine, one designed not to damage subspace at speeds in excess of Warp 5. Captain Ral & Starfleet surmised that something must have gone wrong with the Alcubierre and want to investigate this matter.

We set off on Stardate 51667.2 for the remote Elicona sector, the location of where the Alcubierre was testing the new warp engine. Upon arrival, the crew discovered subspace interference in the vicinity of the Alcubierre, rendering sensors, communications and transporters inoperable. So an away team was tasked to investigate the Alcubierre. First Officer Kingston tasked Lt. MacKenzie to lead the away team and report back what they find out.

The away team boarded the Hannibal (Type-8 Shuttlecraft) and headed over to the Alcubierre. While ENS Zaim prepared to dock the ship, he noticed the bay doors mysteriously opened and decided to park the Hannibal in the shuttle bay. However, the crew quickly discovered that no one was in the shuttle bay to welcome them, leaving them wonder how they were let aboard.

Quick investigation of the control panel revealed most of the ships systems were down, though life support appeared operational on auxiliary power. The door leading to the corridor was only partially opened, leading the crew to find a way to access the rest of the ship. After the emergency hand actuator broke, the crew used brute force to open the doors. But while inspecting the console (and before power went out to it), a mysterious note appeared to Lt. Vos that said "Meet me in stellar cartography".

Once the crew made their way into the corridor, they came across the bodies of some dead Starfleet officers. Before they had time to inspect the bodies, a disruptor blast was heard and 4 Romulans were spotted and battled ensued. The crew dispatched 3 of the Romulans in short-order, with the remaining one fleeing.

At this point, the crew decided to head to stellar cartography to invest the mysterious message Lt. Vos received. There, they discovered the lone survivor of the Alcubierre, Ens Jim LaSalle. Jim filled in the crew on what had happened and requested their help to regain control of the computer system in stellar cartography to help track the location of the signal that called the Romulan ship away. The crew was successful in helping Ens LaSalle, and they discovered the location of the signal came from the Klingon station Kortar.

At this point, the crew decided they needed to head to main engineering to deal with the remaining Romulans and to regain control of the ship (and more importantly, to remove the subspace interference). Before leaving stellar cartography, however, Lt. Vos put an encryption in place to prevent (or at least slow down) the Romulans from regaining access to stellar cartography. This seemed to have worked as almost immediately it was found attempts to regain access were being made.

Since the ship was still disabled, Ens. LaSalle lead the crew through the jeffries tubes and turboshaft to a location just outside of main engineering. There, 2 Romulans were on guard duty, but hadn't noticed the crew sneak up on them. This allowed Lt. Vos to neutralize one of the Romulans, while Lt. Torc took out the other one, aided by Ens Zaim (a Betazoid) who was able to successfully confuse the two Romulans.

Shortly thereafter, the other 4 Romulans in main engineering were discovered, and another phaser battle ensued. Lt. MacKenzie bravely rushed into main engineering and quickly neutralized 2 of the Romulans. The third Romulan was also quickly neutralized (by Ens Zaim I believe), but the 4th, Sub-commander D'Nal, seemed to be resistant to the phaser fire. This allowed Sub-commander D'Nal to get off a blast of his disruptor onto Lt. MacKenzie, causing her to become injured. However, the next attack on D'Nal dropped him to a knee and took him out of combat (though he was not dead nor knocked out).

Lt. Commander Velesa quickly rushed to Lt. MacKenzie and stabilized her injury while the rest of the crew neutralized the Romulans. A mind-meld by Lt. Vos to D'Nal revealed a strange result: 2 minds were being read! Lt. Commander Velesa did a quick medical scan to reveal D'Nal was infected by the same neural parasite that the USS Enterprise discovered just a few years prior. The crew quickly dispensed with the parasite.

The crew then quickly restored all of the ships systems, allowing a security force to transport over to the Alcubierre to take care of the rest of the Romulans.

The away team made their report to 1st Officer Kingston, who promptly reported their findings to Captain Ral and Starfleet. Starfleet ordered the crew to track down the signal on the Klingon Station Kortar and to investigate the situation.

Tune in next time to see what the Tiberius discovers at the Kortar station.

Saturday, February 23, 2019

Session 1 - The Shakedown

Feb. 23 - After a few weeks of prep, the crew finally departed the shipyard of Mars and set course for Starbase 23 to both break-in the USS Tiberius and to deliver some supplies to the Starbase. While en route, the ship performed her systems test, and most things went smoothly.

The Captain wanted to see how his most junior helmsman would perform and ordered Ens. Zaim to steer the ship out of dry dock and on to Starbase 23. Much to the Captains delight, Ens. Zaim performed superbly.

Once the ship was off, the Captain made his rounds to each department to offer a few words of inspiration and to meet the crew. The crew of the Tiberius fell into their roles pretty quickly as system tests proceeded.

The mission for the crew was a fairly simple one: take some scans of the Paulson Nebula to test out the new sensors, then deliver some needed supplies to Starbase 23.

Upon scanning the Nebula, the bridge crew (the PCs on night-watch), heard a distinct giggle sound. The crew immediately sprung into action, running scans of the bridge, running diagnostics on the sensors, etc. Scans found nothing. The Captain, who went to the science lab to look at the data as they came in, said they found a problem and ordered the scans again. This time, the giggle was louder and accompanied by a voice saying: "Stop, that tickles". A flash of light and suddenly, Q was standing on the bridge.

Q was looking for a safe-haven from Captain Picard, saw this shiny new ship, and thought that would be a good place to hide and have some fun. Q decided to first send the Tiberius into the heart of Romulan space where 3 Warbirds discovered the Tiberus and started closing in on them. Then Q took the ship into the heart of a ship-to-ship battle with the Dominion before finally tossing the crew into the middle of uncharted space in the Gamma Quadrant. Faced with Q continuing to threaten them, a deal was brokered where Q could visit the ship if he promised not to harm the ship. In return, Q made Lt. MacKenzie (who was in charge of the bridge) promise not to tell the Captain (a promise technically kept as Science Officer Vos (Vulcan) told the Captain everything).

Once the ship was clear from danger, they continued to set course toward Starbase 23. Reports were coming in that the Starbase was attacked by the Romulans, but no further word was given as Q once again appeared and sent the ship back into Romulan space. Q was upset that the Captain knew of his presence on the ship and threatened to return in the future.

Once Q put the Tiberius back into Federation space, the rest of the journey to Starbase 23 was uneventful. But now the crew must figure out how to deal with future encounters with the entity known as Q.

Thursday, February 14, 2019

Session 0 - Pre-gaming

Session 0 - The group came together quickly and started interacting on Discord (via text and some voice chat) to introduce their characters (and themselves). After some time, the group came up with a ship type and class. So without further ado, let me introduce you to the NOVA Class USS Tiberius!



We are a new vessel and a fairly new crew set to launch in the middle of 2374. I decided to make the crew junior level staff, with the promise of promotions during our campaign. So let's meet the crew!

Command (XO): Lt. Robyn MacKenzie (Human Female)
Science Officer: Lt. Vos (Vulcan Male)
Engineer Officer: Lt. Darwin Foxwell (Human Male)
Security Officer: Simil Troc (Klingon Male)
Medical Officer: Lt. Jr Adoken Lator (Bolian Male)
Helm Officer: Ensign Aanrul Zaim (Betazoid Male)

I will be playing the ship's captain, Captain Malko Ral, a joined Trill. Malko is the 5th host of the Ral symbiont. 2 of previous host have backgrounds in science, while 3 of his hosts (including Malko) are engineers.
Captain Malko Ral

As of this post, we are 9 days from launch! I'm putting the final touches on our introductory mission before we launch into the full campaign. I'm calling the first mission "Shakedown" as it will be the Tiberius' maiden voyage (and therefor a shakedown cruise). The mission will provide the crew a chance to break in the Tiberius while delivering supplies to Starbase 23.

Lots of prep work has been done so far to get this campaign started. This is my first time (ever) as a GM, so I've been a little nervous about what is needed. Thankfully, I have a great crew who has helped (either directly or indirectly) to make sure we are ready for our maiden voyage (which should mostly feature role-playing).

I still have to write the conclusion to our 1st mission, which will likely prove more adventurous then a boring supply run should be. Hopefully the crew will rise to the occasion (and have fun while doing so).

We meet to play every other Saturday afternoon at 4 PM ET to play starting February 23rd. Notes of our sessions will be made on this blog (mainly for our crew to review).

UPDATE: We are 3 days from launch. Feeling more and more confident about GMing. The first mission has been written. I hope it goes well and that it's not too much. Prep work is basically done and I'm excited to take this journey!

Tiberius' Conclusion

 After some delays due to various real life stuff, the crew of the USS Tiberius finally met this past Saturday to conclude our story. When w...