Star Trek: Tirpitz


Defending the Alpha Centauri Sector

While we were en route back to Starbase 39-sierra, we picked up a distress call from the U.S.S. Monmouth.  The Monmouth was reporting that it had come under attack by a Romulan task force, and was taking heavy damage.  We adjusted course to lend aid to the Monmouth, while forwarding the message along to Starfleet to appraise them of the situation.  

Rescuing the USS Monmouth

When we arrived in the system, we found that we weren’t the only ship to have responded to the distress call.  We made contact with the USS Sojourner, a science ship that had already detected six assorted Romulan ships harassing the Monmouth.  We quickly joined the battle, attempting to event he odds somewhat.  Of course, we were still outnumbered by a two to one margin.  The Tirpitz attempted to provide cover for the Monmouth, bringing our weapons to bear on any of the Romulan ships that attempted to set up an attack run on the sections of the Monmouth where its shields had failed.  The Sojourner’s assistance proved to be invaluable as it worked to weaken the enemy ship’s defenses.  With its assistance, we  were able to make quick work of two Romulan Birds of Prey. 

Starting our attack run

Which is not to say that this was an easy battle.  Working together, our three ships did a lot of damage to the Romulan attackers.  But we took a fair amount of damage ourselves.  One particularly nasty barrage from a D’deridex class warbird dropped our port shields and caused a hull breach on deck three of the Tirpitz.  We engaged in some evasive maneuvers, hoping to both buy Amy time to get our shields back online and to try to prevent the warbird from catching us in a tractor beam with our defenseless side exposed to further attacks.  The Sojourner focused its fire on our attacker, buying us some time by drawing the warbird’s attention away.  It gave us enough time to get our shields back on-line, and to line up for a strafing run on the Romulan ship. 

Working with the Sojourner

After our combined forces managed to destroy four of the attacking ships, the remaining enemy combatants retreated back towards Romulan space.  We had all suffered damage in the battle.  The Monmouth had taken the worst of it, due to being the victim of the Romulan’s surprise attack.  We contacted Starfleet command with our situation.  We were assigned to escort the Monmouth back to starbase for repairs, while the Sojourner was to return to their previous assignment.  We thanked the Sojourner’s commander and crew for their help in the battle before we set a course to leave the system. 

Out of Character

I don’t usually use the names of the other players I may end up grouped with when doing missions.  In this case, at least for one of the ships, I felt I needed to make an exception.  The USS Sojourner belongs to a fleet mate and fellow blogger.  This past weekend, we found ourselves in the same enemy contact instance, and shortly there after he had written up an after action report of our time together.  I liked his take on how things went, but it also got me thinking.  The fleet I’ve joined, the Federation News Network, has a fairly high concentration of bloggers in it.  So when we end up working together on the same mission or fleet action, there may be several different blog posts that get created from it.  I can only hope that my take on what happened was different enough from my fleet mate’s that it feels like a different perspective on a shared event, like the logs from two different ship captains in the same battle would be. 

A side effect of this encounter is that it may be possible to figure out how far ahead of my blog posts I’m playing.  

This shared encounter also pointed out a different problem with the game.  In the past, I’ve mentioned that the game can in several places force players onto teams together, but that it can’t force them to interact with each other.  So you’ll end up with groups of people who all have a common goal, but no communication between those people to actually achieve those goals.  You end up circling in space for a few minutes until one person decides on a direction to go, at which point the rest will just follow the leader.  The new problem I encountered with this mission is that the game doesn’t do much to alert you to the presence of other players that are friends or members of the same fleet.  You’ll receive notices of when a friend logs on or off, but I didn’t see anything that let me know that the captain of the Sojourner and I had any connection.  I’ll honestly admit that I didn’t know we were in the same fleet until I saw his blog post on the event.  Now part of that is probably my fault.  I’m terrible with names, and as a new member of the fleet, I’m still getting to know the different people in it.  But still, it would be nice if the game had some kind of message that let you know if and when a fleet mate has joined your random instance.  So if my fleet mate sees this, I’m sorry I wasn’t very talkative.  I didn’t notice it was you until after the fact. 

A Romulan Scimitar

As for the mission itself, it’s a fairly standard sector defense mission.  And it gives the player a pretty good idea of what to expect from Romulan space battles.  Romulan ships seem to use the same kind of slow-moving torpedoes that are used by species 8472 in their mission appearances so far, and they pack quite a punch.  I don’t know if I got hit by one or two, but I do remember going from full shields to none and taking a bit of hull damage because I wasn’t on the look out for them.  Between this sector defense and the previous mission, it’s looking like the use of tractor beams by the warbirds is a fairly common tactic.  The Romulan encounters seem to be pretty much the same in class and numbers as with Klingon encounters, with one big difference.  Scimitars. 

A Scimitar ready to fire its primary weapon

The Scimitar class warbird made its first appearance in Star Trek:  Nemesis.  And there are several of them running around in the enemy encounters.  They’re big and scary looking, but not all that much of a threat if you know what to look for.  They have one massive forward facing attack that is deadly.  But it’s preceded by a long animation, and a graphics display similar to the one used by the doomsday machine during the mission where it’s featured.  As long as you can stay behind a Scimitar, you should be fine.  I’ve even seen a group face two
Scimitars at the same time without any major losses to speak of.

Advertisements

3 Comments so far
Leave a comment

I went back to his post after reading this, and it is pretty cool to compare the two accounts.

And yes, I agree they should make the names of your fleetmates or people on your friends list a different color or something, so you can tell immediately.

Comment by mmogamerchick

Hey thanks for the shout-out. Great take on the story. I love the detail you provide in your posts. And ditto on the wish for a notification system.

Comment by rowan

[…] This post was mentioned on Twitter by Rom REEVES. Rom REEVES said: Defending the Alpha Centauri Sector « Star Trek: Tirpitz http://bit.ly/dg0Lhy […]

Pingback by Tweets that mention Defending the Alpha Centauri Sector « Star Trek: Tirpitz -- Topsy.com




Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s



%d bloggers like this: