Sunday, November 30, 2008

Deadline Approacheth

I have re-edited the rule set, and as the deadline for completion is December 1st, I don't see it being updated again before the Relaunch, as coordinated with the Twelve Trek Days of Christmas. Exactly when that will kick off, and Fantasy Trek's announcement date as a part of that is to be announced. You can expect a pdf available for download, as well as files that will be automatically sent to new subscribers to the yahoo group. If anyone reading this is curious enough to have a whack, you should join the yahoo group. That's the first step to playing. You won't be under any obligation, and you can leave easily if you change your mind. Emails are not shared, you won't see any spam as a result of signing up. Basically there is nothing to lose and a free gaming experience to gain.

And on another note, I'm looking forward to getting back to actually playing this game again. There's lots going on, and lots to catch up on.


What is Fantasy Trek?
Not Just a Game. It's a Star Trek Experience
http://fantasytrek.blogspot.com

Thursday, November 20, 2008

Closer to Relaunch

And looking forward to getting back to playing.... even if I'm just playing by myself :) I think I've actually finished every item on the checklist... witness said checklist here:


pitch done
overview not necessary
all combat describe done
heavy refine done
light refine done
no combat done
general description done
planet classification done
random missions done
mix done
how they work together done
advancement done
experience points done
multipliers for experience done
description of classes done
variants library done
federation dread/heavy/light/frigate done
klingon dread/heavy/light/frigate done
romulan dread/heavy/light/frigate done
maps (disclaimer) done
quick start guide revise check
Command College/sample done
FAQ revise done

Not necessarily in that order, and nothing's official until December 1st. Soon I'll post the whole thing here, while I try to pretty-up a pdf... which I've never done before. Then post on the  blogsite for download, which I've never done before. Then start to create a java game. Which I've never done before.


What is Fantasy Trek?
Not Just a Game. It's a Star Trek Experience
http://fantasytrek.blogspot.com

Sunday, November 16, 2008

Working Towards Relaunch

If things get a bit choppier over the next week or so, I am putting a great deal of what used to be my free time into final work for what I am calling a Relaunch. In conjunction with the "Twelve Trek Days of Christmas" (exact dates to be announced), Fantasy Trek will actually have a working set of rules and resources, including a full ship library. There will be a downloadable PDF that includes everything you need.

I'll try to post weekly while I'm doing that, but you hordes of Fantasy Trek junkies may just have to put on a TOS command yellow uniform and plug in a TOS DVD. I'm working my way through season three. "For the World is Hollow and I Have Touched the Sky". Not bad, if you can ignore the costumes and stock asteroid footage from "The Paradise Syndrome", which I can. After TOS finishes, I've got seasons 1 and 2 of TNG on DVD. And of course, I saw the preview for the new Trek movie attached to "Quantom of Solace". Life is good.

Back to Fantasy Trek. Amongst everything else, I've added "Captain's Log" to the Command College. You are given a sentence, and you write a log entry of at least 100 words. That gives you one Command College point. Ten of those make one experience point. That was intended primarily to help non-combat players take part in Command College, but obviously any players are welcome.


What is Fantasy Trek?
Not Just a Game. It's a Star Trek Experience
http://fantasytrek.blogspot.com

Wednesday, November 12, 2008

Summary of Events Stardate 1108.13

(Moderator's Note: if you're wondering where I've been, well, that demonstrates the flexibility of playing Fantasy Trek. Real Life has taken over a bit. Work, election silliness, etc... but even so, the storyline keeps going. The schedule on Fantasy Trek is extremely flexible, and the boss very forgiving :)...)

Summary of Events
Stardate 1108.13

TNG Era:

Ambassador Endara Khan notes timely assistance of USS Exeter and USS Guadalcanal in securing more involved negotiations with Kazon Ogla First Maje Jabin regarding cooperation with Federation exploration of Delta Quadrant. Ambassador Khan described the negotiations as 'promising'.

USS Archer reports an increase in Klingon activity in their patrol area. A full strike wing, consisting of  two Negh'Var class dreadoughts, eight Vor'cha class heavy cruisers, sixteen K'Tinga class light cruisers, as well as various support craft was running uncloaked in the general direction of the Lambda Hydrae system, which lies in the neutral zone within the triangle zone. As soon as the strike wing detected the Archer, it cloaked and went to warp. The move is seen as hostile and potentially destabilizing. Captain Beckett reported that the Klingons showed no signs of hostility towards Federation interests. Furthermore, it is unknown if the strike wing belonged to one of the council members on unauthorized manuevers, or was a defense force movement.

TOS Era:

USS Xerxes forced to delay its transition through Klingon space in binary system near Beta Lankal as Klingon task force moved through the area. Its mission remains unchanged, despite imposition of so-called Organian Peace Treaty.


What Are Your Orders, Captain?

(Moderator's Note: There are no predetermined right or wrong answers. The most popular solution will give the players who chose it a "Command College Point". Ten of those equal an experience point. Think of it as a correspondence course while onboard ship. Answer via the 'comment' feature)

Resolution of #2 "Should I Stay Or Should I Go?"

Upon emerging from the chokepoint, the Agamemnon had firing solutions drawn up to target the three attack ships waiting for it. The Galaxy Class ship was able to disable all three ships in moments, and was preparing to warp out of the system when a fourth threat presented itself. A mobile shipyard had apparently been hidden behind a cloaking barrier generated by the three KaVort'cha's. Power level scans showed that it was twelve hours from producing and launching another KaVort'cha. Further, it was estimated that another ship could be produced every twenty-four hours.

Acknowledging that the Agamemnon could not destroy the shipyard by itself, Captain Decker quickly reasoned that they could either:

1) Attempt to board and disable the station with elite 'Hazard Team' forces,  or,

2) Warp out and hope to return with a task force capable of destroying the shipyard and securing the vital Archer system.

Captain Decker led her Hazard Team aboard the shipyard, and despite enormous personal risk, downloaded a classified database containing Klingon fleet movements in the area. Captain Decker's team used a timed explosive device to destroy the shipyard's warp core. The Agamemnon made it safely out of the area without sustaining any injuries. Offensive operations from the Klingon Empire were severely curtailed in the sector.


What is Fantasy Trek?
Not Just a Game. It's a Star Trek Experience
http://fantasytrek.blogspot.com

Sunday, November 9, 2008

Classified Personal Log Ambassador Endara Khan Stardate 1108.09

Classified Personal Log
Ambassador Endara Khan
Ocampa Homeworld
Stardate 1108.09
Access Code **************

An integral part of the diplomatic toolkit is empathy. One must find some way... any way to identify with the parties involved. In this case, the parties involved are the Kazon Ogla and the human species, or rather, the impression that the Kazon Ogla have gotten of humans.

When the USS Voyager found itself thrust into the Delta Quadrant, it also found itself thrust into a diplomatic/Prime Directive quagmire. The Kazon Ogla was exploiting the Ocampa, and would have taken control of the Caretaker array if nobody intervened. Captain Janeway was forced to make a split-second decision, and her decision was that the Caretaker was better destroyed than in Kazon hands. Carrying out that decision made her an enemy of the Kazon. Refusing to share even rudimentary technology with the Kazon only reinforced that standing. The impression that remained with the Kazon was that humans were presumptuous, interfering and aggressive people who asked for concessions but didn't share their technology. What I must do is make it clear to the Kazon why Captain Janeway felt compelled to act the way she did, and why they should deal with us anyway.

The first step, in my opinion, was to find out what their biggest problem with us was. That, as it turns out, was the refusal to share technology. That was regarded as a grave insult that became an obsession for the Kazon, who were locked in a constant struggle to survive. My next step was to offer them rudimentary replication technology that could improve their dire conditions without risking them developing transporter technology. The answer to that was a basic protein resequencer that has no technological connection to the transporter or the replicator.

We discovered the Kazon in a precarious state, reduced to piracy in order to acquire food and water. My first move was to see to their needs, and then to arrange to meet with First Maje Jabin. Our initial assistance was enough to assure that. My promise of twelve protein resequencers earned further meetings. Fortunately, Captain Farrell on the Exeter was able to contact the nearby USS Guadalcanal. The Guadalcanal was able to provide the resequencers.

I know that I am dancing on the edge of the Prime Directive, but I also know that we must find a way of dealing with the Kazon. The fact that the Kazon are aware of transporter and replicator technology (as a result of their dealings with Voyager) means that any cultural contamination through the protein resequencer will be minimal. Further discussions with them are another matter.

My ancestry is Mongolian, and in fact, I am a direct descendent of Genghis Khan. That has always been a point of immense personal pride. Despite his barbarous reputation and fierce temper, Genghis Khan helped to shape the world that led to the United Federation of Planets. And now, as I try to empathize with the Kazon Ogla, I see a parallel with young Temujin as he sought to unify the disparate Mongol tribes under one Khan. The Kazon were once united and strong, and I think that they could be again. And just as a united Mongol nation helped to unify and bring order and prosperity to an ancient world, so could a united Kazon bring some sense of order to the Delta Quadrant, with the Federation as strategic partners. That might sound like a recipe for disaster, but if the Kazon sects are allowed to drift further and further apart, their advanced starfaring technology would eventually end up for sale to the highest bidder. Stability for the quadrant would be much more assured with a strong, united Kazon people.



What is Fantasy Trek?
Not Just a Game. It's a Star Trek Experience
http://fantasytrek.blogspot.com

Tuesday, November 4, 2008

Summary of Events Stardate 1108.04

Summary of Events
Stardate 1108.04

TNG Era:

No further communications from USS Guadalcanal in its support mission of USS Exeter and Federation Ambassador Endara Khan. At last report it was supporting the diplomatic mission with the Kazon Ogla on the Ocampan homeworld.

USS Frank Houghton reports no further sightings or indication of the Klingon QeylIs Mindu' Assault Fleet. Frank Houghton and Starbase Lighthouse remain on yellow alert status.

Achilles Class USS Archer is on unspecified manuevers near Klingon border. Their orders are to monitor the fluid border area and report any major changes or deployments of Klingon forces. Rules of engagement emphasize their primarily non-combat, reconnaissance role, but authorizes any necessary defensive measures at the captain's discretion.

TOS Era:

USS Xerxes has failed to make contact following imposition of Organian Peace Treaty. Its mission was to establish contact with the Archer system, and to investigate the MZ-5
outpost. While the Klingons appear to be unaware of the specifics of the mission, their diplomatic mission warned that any Federation incursions into Klingon space would be dealt with 'quickly and ruthlessly'. Since the outbreak of hostilities, there has been no contact with the Archer system, which lies just beyond a narrow swath of Klingon territory.

What Are Your Orders, Captain?

(Moderator's Note: There are no predetermined right or wrong answers. The most popular solution will give the players who chose it a "Command College Point". Ten of those equal an experience point. Think of it as a correspondence course while onboard ship. Answer via the 'comment' feature)

Resolution of #1 "Chokepoint":

When the Klingons briefly withdrew from the Khitomer Accords, the Galaxy Class USS Agamemnon was caught in a dangerous situation while on a purely scientific mission in the Archer system. The Agamemnon was investigating a previously uncharted asteroid field, and was in the dense center of the field when it received a challenge from at least three cloaked Klingon vessels of unknown class. The 'challenge' promised to blanket the field with photon torpedoes (resulting in almost certain destruction of the starship) if the Captain didn't surrender immediately.

What complicated the situation was the fact that the Agamemnon was unable to scan with any reliability through or beyond the field, and the only passage out of the field was a narrow chokepoint that would take five minutes to navigate. That was the obvious exit point, and odds are the Klingons knew that.

Once the Agamemnon has cleared the field, it can warp out of the system and try to rejoin friendly forces. In the meantime, it needs to find out what's waiting for it beyond the chokepoint.

Executive Officer Commander Simon Ranier quickly assesses the situation and offers two possible choices:

1) Send an armed shuttle through the chokepoint with an advanced sensor program as the Agamemnon follows closely behind. This will get the ship out of the field quickly, but would put the ship in the middle of an undefined situation.

2) Launch a probe through the chokepoint in order to assess the situation before exposing the ship to attack. The problem with this is that the Agamemnon would have to wait five minutes to see what lies beyond the chokepoint.

Captain Decker decided against risking a shuttle to unknown forces, opting instead to launch a probe. After a nervous five minutes, her caution was rewarded when the probe revealed three KaVort'cha Class attack ships gathered at the entrance to the chokepoint. While Captain Decker took a risk in giving the Klingons time to attack, her decision saved an armed shuttle and crew, and was justified by the discovery that the Klingon force would have had to have redeployed in order to saturate the asteroid field with torpedoes. She also deduced that the Klingons would have expected her to use the shuttle to leave the field as quickly as possible. In taking the opposite approach, she was able to catch the Klingons off guard.

#2 "Should I Stay Or Should I Go?"

Upon emerging from the chokepoint, the Agamemnon had firing solutions drawn up to target the three attack ships waiting for it. The Galaxy Class ship was able to disable all three ships in moments, and was preparing to warp out of the system when a fourth threat presented itself. A mobile shipyard had apparently been hidden behind a cloaking barrier generated by the three KaVort'cha's. Power level scans showed that it was twelve hours from producing and launching another KaVort'cha. Further, it was estimated that another ship could be produced every twenty-four hours.

Acknowledging that the Agamemnon could not destroy the shipyard by itself, Captain Decker quickly reasoned that they could either:

1) Attempt to board and disable the station with elite 'Hazard Team' forces,  or,

2) Warp out and hope to return with a task force capable of destroying the shipyard and securing the vital Archer system.

When you consider these options, keep in mind that the three Kavort'cha's have only been disabled. If your Hazard Team takes too long or fails, the Agamemnon will be in serious trouble. And remember that the shipyard is mobile. If you leave the system unmonitored for too long, you could find that the shipyard has moved on. And of course, you always have the option of deciding on an alternate course of action.

Your mission is to choose (and briefly explain) what you think is the best course of action, or suggest an alternate course of action. What are your orders, Captain?


What is Fantasy Trek?
Not Just a Game. It's a Star Trek Experience
http://fantasytrek.blogspot.com

Saturday, November 1, 2008

Captain's Log USS Archer Stardate 1108.02

Captain's Log
USS Archer
Stardate 1108.02

I remember a movie, from Earth, mid-twentieth century, called "Run Silent, Run Deep", that dramatized submarine warfare in the second world war. I've been reminded of that kind of life, or what I imagine it was like, for the past week. We've been operating very quietly, in an area adjacent to, and sometimes across the Klingon border. The border changes these days, as wolf-packs of Klingon battle cruisers assert their dominance over an area, then become bored, and move along. There have been groups of three Vorcha' Class attack cruisers drifting in and out of our classified area. We might be able to take them. The Archer is an Achilles Class, built to fight the Borg and the Dominion. But our orders are to "monitor the situation", not try to destroy the entire renegade Klingon force. So we watch, and record, and if confronted with an untenable situation, we defend ourselves. But as Admiral Nechayev has reminded me more than once, every shot we fire has the potential to tip the scales and drop us into war. And we're trying to avoid that.

I will note that the captain and crew of the USS Blalock saved our lives in Gamma Hydra. Details are classified, but we would not be here putting up with troublesome Klingons without them. Thanks, team. 


What is Fantasy Trek?
Not Just a Game. It's a Star Trek Experience
http://fantasytrek.blogspot.com