XoooooX= Wormhole (2,1) oxoxoxoxox= Nebula MS= Major System (Kri'staK) (21,14) ms1= minor system 1 (10,7) ms2= minor system 2 (1010,) ms3= minor system 3 (12,17) ms4= minor system 4 (15,11) ms5= minor system 5 (17,22)
RCA1= Romulan Heavy Cruiser 1 (4,12) RCA2= Romulan Heavy Cruiser 2 (4,14) RCC3= Romulan Construction Ship (frigate class) (4,13)
Nebula properties: No shields No tractors No weapons lock outside of range 3 (from range 4+, need 1 in 6 roll to hit)
Post by General Kapact on May 16, 2009 1:33:42 GMT -5
Long Range Sensor Scan wa'Hom System Kri'staK Sector
Minor system 1 (wa'Hom) Orders: Remove all enemy craft. Establish outposts on at least two planets. Scan asteroid belt. Investigate debris field. Minimum of two Random Planetary Missions. XX=wa'Hom sun AA: Ab'Qaff Battle Group Dur: IKS DuranQo XXXXXXXXXXX=Asteroid Field xoxooxx=Debris Field
Post by General Kapact on May 24, 2009 12:11:32 GMT -5
USS Resolute Sovereign Class Admiral Allyna Nechayev
Nechayev watched the tIQ'leth slip through the ring of holoemitters and vanish as if it had cloaked. "Our turn," she muttered under her breath. "Have the Archer and the Pike drop back and pick up the rear." She watched as the Galaxy Class Pike and Achilles Class Archer pulled out of formation. "That takes care of the heavy cruisers. Light cruisers in ahead of them." The Intrepid Class Narendra and the Excelsior Class Entebbe moved next. "Now tuck the frigates in behind us." Three Norway Class ships dropped in behind them. "Abrahms, John Connor, Langdon, form up." She thought briefly that the Federation and the Empire somehow couldn't seem to stop shooting at each other, even if they were just simulations now. Oh well. "All ships go to red alert. Take us into the holofield."
Class H Desert Age: 4-10 billion years Diameter: 8,000-10,000 km Location: Hot Zone/Ecosphere/Cold Zone Surface: Hot and arid, little or no surface water Atmosphere: May contain heavy gases and metal vapors Life forms: Drought- and radiation-resistant plants, animal life Example: Rigel XII, Tau Cygna V
12) An inhabitant of the planet tries to take over your ship.
Stardate 0309.24 IKS DuranQo Planet wa'Hom One
Our mission to survey and establish an outpost on the first planet in the wa'Hom system has at last given us a chance to do battle on this mission. Scans of the atmosphere revealed heavy gases and trace metal vapors, but sufficient oxygen and nitrogen for us to survive. Knowing this, I expected to find some resilient species to provide a challenge for us. Orbital sensor scans, however, showed no sentient life on the planet, and in fact little vegetation. It turned out, however, that there was indeed hostile life on this world.
I led the first survey team, transporting with ten warriors to a large desert on the northern continent. We were starting to scan microscopic life that mixed with the surface sand when what appeared to be a sandstorm suddenly engulfed us. We attempted to move away from the storm, only to find that it followed us. After numerous attempts to evade the storm, I ordered the team transported back to the ship.
Once on board, we found that the storm had been caught in the transporter beam. It immediately pushed through the bulkheads on a molecular level, according to the science officer. From there it went straight to the the warp engine and computer core. Systems began to go crazy seconds later. The storm, whatever it was, was trying to take over the ship. Fortunately, our scans of the storm revealed much about the strange life that composed the sandstorm including its vulnerability to delta radiation. From that point, it was a simple matter of inoculating the crew to delta radiation, and then bathing every inch of the ship in the deadly substance. The sand-entity was removed as a threat. We then equipped enough torpedoes with sufficient delta radiation to cleanse the planet of the organism. We estimate that the planet will be habitable in a few days, at which time a permanent team will be assigned to fully survey the planet and construct an outpost.
Post by General Kapact on May 27, 2009 0:30:54 GMT -5
Would you like to do more than just read? How about shaping the story? Start your career in the Center Seat. Get started right now with the Quick Start Guide:
To get started, answer the following questions:
Pure Combat (Do you play for pure combat? You know that other events might decide the nature of that combat, but you just want to blow things up. And think about this: Do you like to micromanage combat, allocating power to personalize your attack/defence strategy, making combat a personal match of wits, or do you just like quick matches that can be over in minutes?)
Non-Combat (You don't care about the combat. You like to write and you want to explore.)
Mix (You appreciate both aspects of game play. You accept that the ship you love to write about may lose battles from time to time.)
Alignment: Federatinn Klingon Romulan Other (specify)
Command crew: (You can stick to the TOS crew configuration of science officer, helm, navigator, communications officer, etc, or you can use the TNG idea of Operations Officer combining some duties.You can also customize your bridge crew configuration. You're the Captain)
Note: unless you have something else in mind, all players in this stage of the game get a Heavy Cruiser to start. The 'something else in mind' I mentioned is if you decide you want a mission-specific ship like a scout or police ship, which is likely to be a frigate or destroyer. Just remember that you might be limiting yourself in a case like that. And don't be intimidated by the need to create a command crew. If you're a story-teller, you're used to this, but it isn't necessary to start. And if you're in it for pure combat, the command crew is recommended but not necessary.
That is really all you need to start. I will happily walk any new players through the first few missions. If you are concerned that you don't have enough time to contribute, don't be. This game is as casual as you want. Exploring takes as much or as little time as you want. Write once a day or once a week. A hundred words or a thousand. The most intense level of this game, heavy combat takes a commitment of no more than one email a day. And even in that case, if you miss a day, it's forgivable. Even the moderator has a RL and the occasional computer issue. The game is turn-based. Combat results will be posted online daily. And if it still doesn't make sense, think of it like your favorite role-playing/writing group gathering for some table-top, Dungeons and Dragons-style game playing.
Summary of Events:
Captain Reggie Farrell reports an agreement in principle between Kazon-Ogla First Maje Jabin, Kazon-Oglamar Eeluk and Federation Ambassador Endara Khan on non-aggression between Federation forces and Ogla and Oglamar forces. The agreement includes limited cultural and humanitarian exchange. Final details have yet to be announced.
Following reports of similar findings of two thousand year old human biomatter and Vulcan hull fragments in two locations in the Alpha Quadrant, the USS Guadalcanal has been ordered to transmit all data, including holographic data through the Durandal wormhole to Starfleet Command for study. The Guadalcanal has further been ordered to continue their survey of the Delta Quadrant and to ascertain the status of the Romulan Warbird Decius.
The USS Lily Sloane reports that its probe passed through the subspace rift in the Coramonde system, but vanished seconds later. The last transmission of the probe contained hundreds of repititions of a single word that linguists believe may belong to an ancient Vulcan dialect. The data has been transmitted to Starfleet Command and the Vulcan Science Academy for further analysis.
Starships USS Archer and USS Arizona report little change in the situation in the Triangle Zone that marks the convergence of Klingon, Romulan and Federation territory. They have attempted to appeal to passing Klingon ships to pull back, but so far have had no success. A Vulcan diplomatic team is preparing an approach to the Klingon Ambassador in an attempt to mediate a cease-fire before the fighting spreads.
An unsubstantiated transmission originating from Klingon space reports the destruction of two Klingon taskforces well within Klingon space. This might add credence to Klingon accusations of a group of Federation starships destroying a Klingon freighter in the Morska sector. The same transmission stated that two 'Federation Battlecruisers' had been destroyed in the combat. 'Federation Battlecruiser' is the Klingon designation for a Constitution Class Heavy Cruiser.
Starfleet Command has received a message packet, delivered by a Tellarite freighter, from Chalenger NX-07 detailing their journey thus far, and providing detailed starcharts and sensor readings. According to Captain Carpenter's logs, they have not had direct contact with any Romulan ships, either civilian or military.
Columbia NX-02 is continuing to track a suspected Romulan vessel that recently attacked a ship in the Denobulan system.
Yorktown NX-03 has been sent to investigate the disappearance of two Sloane Class light cruisers, which had in turn been investigating the disappearance of the EX-01 Roddenberry. The Sloane Class ships had been following an ion exhaust trail which may have been a clue to the disappearance of the Roddenberry.
"What Are Your Orders, Captain?"
(TNG Era) "Too Much Information" Resolution
The shuttlecraft Apollo followed a holo-presence probe through the planet's atmosphere, and maintained an altitude of 100 meters above the site of the downed USS Coramonde. As soon as the probe reached the surface, it began to transmit telemetry to the hovering shuttle. In the Agamemnon, the crew is forced to wait, as any data transmitted from the probe to the shuttle could conceivably contain contaminated material. Finally, several hours later, the computer on board the Apollo reports that the protected memory from the Coramonde has been downloaded and scanned for any alien or malicious data. It reveals bio and metallurgical scans of the biotech as it was drawn down to the surface. Stress readings from the impulse deck and hull reveal that the ship was being drawn down to the surface, and Captain Edward Hubble ordered maximum reverse impulse and warp power diverted to shields and the structural integrity field in an attempt to keep the ship intact as it came down. The power that brought it down was not revealed. Captain's logs stated that the ship had been pulled forward in time as it traveled through the rift, which was bathed in neutrinos. Finally, the bioscans confirmed the presence of human DNA in the biotech, while metallurgical scans revealed traces of Vulcan hull material quantum dated at two thousand years old. None of this adds to their knowledge of the biotech, but it does answer the question of time travel, and it goes a long way toward explaining the fate of the Coramonde.
While the holo-presence probe was inside the Coramonde, it confirmed that there was no life left on the Coramonde except for the biotech, which seemed to have absorbed the crew, in much the same way that it attempted to absorb Lt. Keller. With the protected memory removed from the Coramonde, Captain Decker chooses to destroy the downed ship in order to prevent it from falling into unauthorized hands, and to remove the threat from the biotech infecting the ship. After confirming that there is no other life on the planet, Captain Decker orders the Coramonde targeted with photon torpedoes and destroyed.
The Agamemnon breaks orbit from the unnamed planet, and Captain Decker orders the ship to return to the rift in the hope that they can safely return home. Once they arrive, she is relieved to discover that the rift is stable, and probes sent through show that it is safe to return. As the Agamemnon passes through, its scanners are unexpectedly inundated with line after line of signal code, repeating a single, indecipherable word that appears to be Vulcan in nature. As the science department struggles to shunt the data to auxiliary drives to stop the code from overwhelming the computer core, Captain Decker starts to wonder if this happened to the Coramonde at some point, and if the data will reveal the connection between the two thousand year old Vulcan hull material, the two thousand year old human DNA, and the dangerous biotech. Does the time travel phenomenon stretch back two thousand years, or were ancient Vulcans interacting with ancient humans. She doesn't doubt that the Vulcans can translate the code, but she also wonders if they would be happy to see or share information about what they were doing with human DNA two thousand years ago. She knows that she might hold the key to solving a mystery that spreads from the Alpha Quadrant to the Delta Quadrant, if only she handles it correctly...
Due to the probable sensitivity of the subject matter, Captain Decker records a small portion of the data and deletes the rest, which consists of nothing but repititions of the same indecipherable word. Then she proceeds directly to Starfleet Command to physically hand the recording to Starfleet Command. She also reports on the fate of the USS Coramonde.
(TOS Era) "Our Fleet's In Jeopardy"
More than a month ago, the USS Xerxes completed a dangerous journey across Klingon space to investigate a loss of contact with the Federation outpost at Archer IV. It discovered that the outpost was still safe, but desperately needed reinforcing. Section 31 has dispatched a fleet to cross Klingon space to do just that. The fleet consisted of the Heavy Cruisers USS Nelson USS Halsey USS Farragut USS Churchill and USS Eisenhower. In the Morska sector, the fleet encountered and destroyed a Klingon freighter. In the Mempa sector, the fleet was faced with a full-sized Klingon task force. It was victorious, and no distress signal was sent to alert more Klingons. Unfortunately, during the battle, the Nelson sustained massive damage, requiring the fleet to remain in the sector for two days. Then, on its first day of waiting, another Klingon taskforce happened upon the fleet. The Klingons were again destroyed before they could get a signal out, but during the battle, the damaged Nelson was destroyed, and the Halsey was crippled. Again, the fleet will have to wait two days before the Halsey can continue the mission.
Fleet Captain Tiberius is now faced with a diminished fleet and the real possibility of failing in his mission. Waiting in the Mempa sector for two more days seems to present the risk of losing yet another starship. They dare not leave the Halsey alone while they continue on, nor does it seem prudent to divide the fleet in order to guard the Halsey while it completes repairs. Also, requesting reinforcements would still require a two day wait since the closest starship is a day away from the neutral zone. Every possible alternative endangers the mission and the fleet.
Choose what you think should be the next course of action, and write a brief summary.
There are no predetermined right or wrong answers. Feel free to discuss the challenge with other players. Every player who submits an entry receives a "Command College Point". Ten of those equal an experience point. The most popular choice will determine the next step taken. If the next step involves combat, (to be determined by a 1d6 roll), I will post the results of that combat.
(From last week) "...how this got started..."
9) The Q entity (or other ultra-powerful being) causes mischief on the surface of the planet and in orbit.
Class M Age: 3-10 billion years Diameter: 10,000-15,000 km Location: Ecosphere Surface: Surface water abundant; if water covers more than 80%, planet is considered Class-O or Class-P Atmosphere: Nitrogen, oxygen, trace elements Life forms: Extensive vegetation, animal life, humanoids Example: Earth, Vulcan, Cardassia Prime
(Ent Era) Columbia NX-02 Captain Erika Hernandez
I'm not exactly sure how to explain all this, or to even adequately express what happened. All I can do is try to start with how this got started and go from there. While investigating the apparent disappearance of a planet in the Tau Ceti system, we were suddenly scrambling to gather sensor readings as the planet reappeared. There were no obvious phenomenon to explain what had happened, and fortunately we had maintained a good distance from the planet's position, so the ship was never in danger. We made contact with authorities on the planet, and found that from their point of view, as well as all of their artificial satellites, there had never been any change in their situation. They even showed us sensor records of the Columbia in orbit during the time that the planet had seemed to vanish. At that point, I decided to take a huttlepod down to investigate readings from the surface.
However, as our shuttle dropped through the atmosphere, we suddenly found that the planet and the ship, and the rest of the system for that matter seemed to have disappeared. Then there was bright flash inside of the cabin, and the rest of my team was replaced with Captain Jonathon Archer. Captain Jonathon Archer of the Enterprise, currently in a completely different sector of space, almost a hundred lightyears away. Whoever it was that appeared in the shuttlepod never tried to convince me that he was Captain Archer, but rather launched, without prelude, into a passionate reading of what the linguistic banks later identified as Klingon love poetry. Just for the record, I contacted Jon after it was all over, and he confirmed (with a bemused chuckle) that he had not somehow transported himself across space into my shuttlepod to recite Klingon poetry. In any case, whoever it was finished his poetry reading and vanished with a flourish and another flash of light. The crew returned at the same time. We then completed our investigation, but unfortunately could find no explanation for the strange incident.
(For Next Week: Expand the following into a log entry of at least 100 words. Members post answers to the yahoogroup or the 'comment' feature on the blogsite. Lurkers feel free to leave comments on the blogsite)
"...a concept we never considered..."
There's been more attention paid to the quadrant simple combat game this week, to add to Fantasy Trek's quick-play value. While Operation Reinforce is now being guided by the "What Are Your Orders, Captain?" feature, I decided to run a random sector assault with a Klingon CA, the DuranQo. The random 1d6 roll tells me what I'm facing, DEFSAT, frigate, light cruiser, heavy cruiser, dreadnought, or reusable shipyard for quick repairs. Once you find the shipyard you can always go back to it between combats. And of course, you only face each class once. I'm kind of enjoying the challenge of having to allocate points to offense and defense before I roll for the AI. It is definitely a challenge when you get an opponent even closely matched. In the round I'm playing now, I'm at full health, thanks to that shipyard, and I'm facing the dreadnought. If I get past that (which is a long-shot), it's a quick whack at the DEFSAT and all done. Quick update: The Dreadnought took out the DuranQo on the first volley. Oh well, that's one more ship in the Black Fleet. The only pain to the whole thing is the task of setting up the template. And that isn't much of a pain, unless you're on a palm pilot that just has an on-screen keyboard.
Fleet Action. Head-To-Head Bare Knuckles Naval Combat. Boarding Party Action. Solid Interactive Storytelling Like No Commercial Game Can Offer. How Much Star Trek Can You Handle? Fantasy Trek. Not Just a Game. It's a Star Trek Experience fantasytrek.blogspot.com The Only Rebel Underground Star Trek PBEMMMORPG
Post by General Kapact on Jun 15, 2009 14:50:03 GMT -5
Vorcha class Heavy Cruiser Captain Korvus
Stardate 0309.31 IKS DuranQo Planet Two wa'Hom System
The second planet in this minor system has all of the boring desert topography of the first planet with none of the redeeming hostile lifeforms. It is barely habitable, covered by desert everywhere, except for the polar regions, which are half liquid. Nonetheless, scans beneath the surface reveal large deposits of dilithium crystals. For that reason, I have recommended to General Kapact that this planet is worthy of an outpost. I have transported down an initial survey team to begin mining the planet, and a construction ship will arrive soon to manufacture a full mining outpost.
Post by General Kapact on Jun 15, 2009 14:54:09 GMT -5
Random Planetary Adventure #2 Kri'staK Sector wa'Hom System
Class Q Variable Age: 2-10 billion years Diameter: 4,000-15,000 km Location: Hot Zone/Ecosphere/Cold Zone Surface: Ranges from molten to water and/or carbon dioxideice, due to eccentric orbit or variable output of star Atmosphere: Ranges from tenuous to very dense Example: Genesis Planet
11) You meet a society that causes you to question whether or not to interfere with their development.
Stardate 0409.06 IKS Ab'Qaff wa'Hom system Planet Six
Just beyond the asteroid belt in this system, we discovered that the sixth planet in this system is dangerously unstable. While there is nothing in this system or the immediate vicinity that easily points to an explanation for this instability, my science officer theorizes that a rogue planet or other large body making regular passes through the system could account for gravitational anomalies sufficient to cause this. He even suggests that the asteroid field could have been a planet that suffered from a collision from such a body, and the resulting cataclysm could have destabilized the sixth planet. While scanning the sixth planet, we determined that it contains a tenuous atmosphere not suitable to us, so I am not going to establish an outpost. There is a microscopic species indigenous to the planet, but changes occurring on the planet will most likely destroy this life before it can evolve. I have decided to leave an outpost in orbit of the planet to monitor the system and the microscopic life on this planet.
A) Roll  A) Helm: Position/Movement[12,11 /Speed9]/[Course 180 ] A) Countermeasures/Reinforce shields/Cloak/Tractor/Repair: [ECM/ECCM2(1)+retained][Reinforce shields()+retained]CloakTractor[pts] Repair A) Tactical: Target[C Port] Target Bearing Target Range Fire weapons [FWDdisruptors(x)+FWDphotonsMISSED(x)FWDdisruptors(x)+FWDphotons(x)] A) Auxiliary Craft: Launch ECM Support shuttles a,b,c,d Shuttle[ , /Speed]/[Course] Target Target Bearing Target Range Fire weapons [(x)]/(Fighter[ , /Speed]/[Course] Target Target Bearing Target Range Fire weapons [phasers(x)+photons(x)]
B) Roll  B) Helm: Position/Movement[ 15,11 /Speed9 ]/[Course 180] B) Countermeasures/Reinforce shields/Cloak/Tractor/Repair: [ECM/ECCM6(3)+retained][Reinforce shields()+retained]CloakTractor[pts] Repair B) Tactical: Target[C Port] Target Bearing Target Range Fire weapons [FWDdisruptors(4x4)+FWDphotons(6x4)AFTdisruptors(x)+AFTphotons(x)] B) Auxiliary Craft: Shuttle[ , /Speed]/[Course] Target Target Bearing Target Range Fire weapons [(x)]/(Fighter[ , /Speed]/[Course] Target Target Bearing Target Range phasers(x)+photons(x)]
C) Roll  C) Helm: Position/Movement[20,13 /Speed4]/[Course090 ] C) Countermeasures/Reinforce shields/Cloak/Tractor/Repair: [ECM/ECCM8(4)+retained][Reinforce shields()+retained]CloakTractor[pts] Repair C) Tactical: Target Target Bearing Target Range Fire weapons [FWDphasers(x)+FWDphotons(x)AFTphasers(x)+AFTphotons(4x4)] C) Auxiliary Craft: Shuttle[ , /Speed]/[Course] Target Target Bearing Target Range Fire weapons [(x)]/(Fighter[ , /Speed]/[Course] Target Target Bearing Target Range Fire weapons [phasers(x)+photons(x)]
Results: Damage to A: Damage to B: Fwd shields 13/28 Damage to C: Port Shields 21/21, Port Armor 3/3, Port Hull 3/3, Impulse 1/2, Fire Control 1/2, Disruptors 2/2, Sensors 2/2, Tractors 1/2
With the L'ara disabled and incapable of withstanding another assault, the Ab'Qaff and the Temujin moved in and beamed boarding parties onto the damaged ship. Their combined marines outnumbered the Romulan crew by a margin of three to one. It was an unfortunate end for the Romulan crew. After the brutal fighting, a crew from the Ab'Qaff assumed command of the warbird. The Light Cruisers Hammer and Kapikus will remain on station, awaiting the arrival of a mobile shipyard to repair and recrew the captured ship while the rest of the Battle Group continues the mission of securing the system.
Post by General Kapact on Jun 15, 2009 15:15:02 GMT -5
Stardate 0409.21 IKS Ab'Qaff wa'Hom system Kri'staK Sector
I have received word that the mobile shipyard Lursor has completed its job of repairing, refiting and recrewing the captured Romulan warbird that I have christened the IKS Krayak. The Lursor will convert the two empty troop ships that supplied crews into a single refining station at the edge of wa'Hom's resource rich asteroid belt, and two auxiliary craft from the Lursor will serve as mining/freighter craft for the operation. I have advised the high council and recommended a regular convoy operation be initiated to bring wa'Hom's resources to the Empire.
Our investigation of the debris field at the edge of the system has revealed a bit of a curiosity. While we expected and encountered planetary debris and cometary fragments, indicating cataclysmic events already in evidence in the system, we also found starship hull material that appears to be Vulcan in origin. What makes that interesting is the fact that quantum dating indicates that the hull material is more than two thousand years old. It is generally accepted that Vulcans were traveling the stars that far back, as the Romulans originated from that world. But I have never heard of any of those ships being found, especially in this unexplored corner of the alpha quadrant. No doubt their scientists will be eager to study the debris. After we're finished with it.