Shortly before twelve noon, local time, a fleet belonging to the rebel Klingon houses engaged with Marines from the 19th Marine Expeditionary Unit from Starbase 400 in the Arcanus system. Initial reports put the rebel fleet at somewhere around 30 ships of various types. Opposing them, alongside the planetary defense grid, was the 19th MEU, the three ships that brought them to Arcanus IV, and a detachment of the 181st Fighter Wing and its transport vessel.
Initially the Federation forces in orbit were forced to pull back to safety due quite simply to the number of vessels arrayed against them. Planetary defenses were almost as quickly overwhelmed and the Klingons began to deploy their troops to the planet’s surface. After a brief reorganization, the limited forces the Federation had in orbit took the fight to the enemy. Though heavily outnumbered, the three ships and their fighter support stubbornly held their ground against a numerically superior force and destroyed numerous enemy vessels. Including several Birds of Prey and a Negh’Vaar, before reinforcements of the 18 th MEU, also from Starbase 400, arrived. These reinforcements were then further reinforced by the unexpected arrival of a task force from Klingon Loyalist forces. This combined fleet was able to destroy the majority of the enemy fleet before the enemy disengaged and fled the area.
According to witnesses the fighting on the surface was desperate and quite literally hand to hand and face to face at times. The Marines were set up in defensive positions around their three landing zones, which had been selected because they were the most obvious locations for the enemy to land at as well.
Forward elements of the 19th MEU engaged the landing Klingons before they were forced to execute a withdrawal under heavy fire. This withdrawal pulled the Klingons into the guns of the entrenched Marine defenders at the landing zones. The fighting was quite literally hands and teeth before the Marines received reinforcements as well as fire support from the 18 th MEU and its vessels that had by this time arrived and engaged the rebels as well.
Casualties on both side are reportedly quite heavy. Klingon losses are unknown at this time, though quite a few were killed by the precision phaser fire from the ships in orbit. The USS Tirpitz, most of her Marines deployed to the surface leaving only about 500 onboard to crew the vessel, lost all life support during the fighting in orbit. There are reportedly less than twenty survivors. Figures on the ground forces report several hundred killed and possibly well over a thousand wounded, perhaps as many as two thousand between the 18th and 19th MEU’s. The detachment of the 181st Fighter Wing accompanying 19th MEU reported about 25 aircraft destroyed, about a dozen pilots killed and the rest of the fighters that accompanied 19th MEU damaged. Fighters arriving with 18th MEU reported no losses and only some aircraft damaged.
Klingon Loyalist forces have assumed defensive position in orbit as well as on the ground of Arcanus IV. The 18th and 19th MEU’s and their support elements are preparing to return to SB400 at the time this report was written.
We’ve seen a sea of change in the Delta Quadrant, with death, destruction and a new discovery. I don’t think I’ve ever seen anything quite like this, but that is the unfortunate reality in the area of the Delta Quadrant the Federation currently operate in.
Task Force 38 is the Fourth Fleet’s task force in the Delta Quadrant as part of the Delta Quadrant Initiative. With its focus area of operations being the Round Table (Sector 22 Delta), its main goal is first contact, exploration and providing diplomatic support.
Tragically, a surprise and ruthless Borg attack on Starbase 900 meant the orbital facility was destroyed with a massive loss of life. To further add to the Federation’s problems in the area, Rear Admiral Diego Macedo ordered Captain Peter Gardner of the USS Excelsior to destroy the Solaria Gateway and cut the Task Force off from the Beta Quadrant, although on the up side it prevents the Borg from easily reaching Federation space.
To further boost Task Force 38’s chances of survival against the Borg, Rear Admiral Macedo decided to step down as Task Force Commanding Officer and is now in a new role as a diplomat, hoping to forge alliances to combat a common enemy. In his place, Lieutenant General Jagged Anderson takes over as TFCO, with his former role being the Marine Expeditionary Brigade Commanding Officer. He is now in charge of protecting the survivors of the Borg attack and using that as a platform to rebuild the Federation’s personnel and infrastructure. Rear Admiral Solek remains as the Task Force Executive Officer.
To remember those who were tragically lost in the destruction of Starbase 900 and other conflicts with the Borg in the Delta Quadrant, a memorial named Hestia’s Hearth has been created in the same place as Starbase 900.
Now Lieutenant General Anderson faces a tough task, rebuild the Federation’s forces in the Delta Quadrant whilst attempting to make new allies. Despite what people think, the Borg aren’t the only threat the remaining forces in the area face, with the Vaadwaur also posing a serious threat, could they be the next ones to strike? Time will tell, but one thing I can tell is that despite everything, the determination to rebuild and carry on is stronger than ever.
Since the Canterra Sector was overrun by the Gorn, the way of life in that region of space has changed for its inhabitants in ways they could never imagine. What was once a peaceful and quiet region of space is now a hive of activity as Starfleet attempts to halt the Gorn’s advances…
Task Force 93 has a five point mandate, which is to provide incident response to the Gorn invasion in the Canterra Sector, monitor the Romulan Star Empire, protect the Raeyan Transit Corridor, rebuild Starfleet’s presence in the Raeyan Sector and seek peace in the Gavarian Corridor. More recently, there have been a number of issues in the Klingon Empire to deal with as well.
Speaking of the Klingons, rumours have been rife that their government system is currently unstable, although all attempts to confirm these rumours have been met with a firm denial. Despite this, there are a number of rogue elements that carried the Klingon Empire who are carrying out their own activities as they please, which does little to alleviate the concerns that a number people have about the stability of the Klingon Empire’s government.
Federation starships have encountered these rogue elements who are attempting to expand their territory into the Raeyan Transit Corridor, claiming that it is “Their rightful place of expansion”. At least one vessel to witness these events unfolding is the USS Centauri-B, with its Commanding Officer Captain Ch’qaoqihr who has shared his deep concerns about the pressure building up in the area and beyond and the uncertainty that it presents.
This means that Task Force 93 is now stretched to its limit, having to devote its resources to no less than three areas in order to try and maintain the region’s security as best as they possibly can. This devotion of resources could mean that Task Force 93 could ultimately have to draw in more reinforcements from other areas of the Fourth Fleet to stop the Gorn in their tracks, protect the vital Raeyan Transit Corridor and also prepare for the potential civil war in the Klingon Empire.
Despite all these issues however, Commodore Anin, Executive Officer of Task Force 93, informs us that at the present moment in time very little resources are diverted to monitoring the Klingon Empire, with most of the task force’s strength diverted towards the Canterra Incident in an attempt to find a diplomatic resolution to the Gorn’s invasion of the area.
The crackle of static announces the brightening of a still black screen. The sizzling sound of an electrical short followed by a quietly muttered curse follows. Suddenly the screen turned from black to a fuzzy, dusty grey. Then came a rag wiping the lens off followed by another curse as the screen turned to a close-up of a man’s shirt, so close you could almost tell the thread count.
“James, this recording light is on. I think it’s starting to work.” A woman’s excited voice comes from somewhere to the right.
“Yeah, but no way to tell if it can transmit, or if the microphone still works.” Came the reply, sounding quietly hopeful.
“I’m doing the best I can with scavenged parts, I’m not a miracle worker. There, if this thing’s gonna work at all, it’ll be now.”
“I know Sam. You’re the best in the station at what you do.” This James replied as he stepped back from the lens.
As he moved back the scene begins to take shape around him. Debris and rubble litter the area, his own clothing is dusty, torn, and in a few places, dots of dried blood can be seen on his shirt sleeves. He looks tired, haggard even, that things haven’t gone well for him is obvious.
“This is James Devlin, until the Gorn invasion I was a reporter here on Cestus for FNS. I don’t know if anyone can see this, hear me, or if this is even transmitting at all, but I have to try and get the word off planet. It’s been weeks since the Gorn invaded, I wish I could be more exact, but the days just run together.” He looks around, drawing a deep breath and letting it out slowly. “I… I’m not sure where to begin, so much has happened.
“The initial orbital bombardment was over quickly, only a few hours, but as you can see around me, it did extensive damage in the cities. Then came the Gorn themselves. They arrived by shuttle, transport ships, and transporter. They overran the capital in little more than a day. Patrols are everywhere, curfews are in effect, if you’re lucky enough to have somewhere to go at night anyway. Prison camps have been erected outside the city, Sam do we still have that footage we shot?”
“Nope. That was on the drone the lizards shot last week when they saw us filming.”
“Well we did have footage anyway. Civilians are kept in one camp and any Starfleet personnel the Gorn find are put in another. There are shelters, but they can’t be enough for everyone and I don’t want to guess at the treatment people are getting there. There are even rumors of people just disappearing, both from the streets and the camps, usually after a patrol has been through the area.” The man visibly shuddered at the idea that ran through his mind.
“I think we’re transmitting James.” Came Sam’s voice from off screen with a sense of urgency. “Liazards just moved into the area. Even money they’re tracking the transmission signal. We gotta move.”
“I.. uhm.. this is James Devlin signing off! Hopefully we can still report tomorrow or the next day.” James moved back in to the camera to shut it down.
“Yeah if they don’t catch…”
Akagi is a name that has travelled with the history of Bravo Fleet for a very long time now. Even with several different commanding officers and appearances in different Task Forces over that time, the Akagi has finally become a mainstay in Task Force 38 under the command of Captain Aurelia Prendergast. Karen, the commander of this sim, revealed that “this particular version of the Akagi began back in the spring of 2012, originally under the command of Captain Jeff Murdock. When Murdock stepped down in March 2014, the sim was taken over by myself and a new website was created for her.”
Karen was an ideal candidate to step up when Murdock stepped down having been aboard the sim since its early days. “Myself and the XO have been on board the Akagi since the very early days and we’ve seen many people come and go, including the ship’s first Captain,” she reveals. But despite the losses along the way, something must have been going right for the crew. “Several of the players currently on board have also been with the ship for a long time, some of them as far back as 2012. Whilst we’re not the fastest at churning out posts, we’ve stuck together and I feel that we’ve created some fantastic stories along the way. The old Captain has also returned as a regular crewmember.” Whether it’s the writing or the community, a cohesion exists among these players that has encouraged several of the crew to stay together for so long at a time when player turnover elsewhere is extremely high. One thing is sure, this all bodes well for the sims continued participation in TF38’s future.
But what exactly has been going on, in character, that has encouraged these people to remain and dedicate their time to writing their characters’ lives aboard the Akagi? “As I took over the sim in 2014, my character who was then the XO ended up becoming the commanding officer when the Akagi was thrown out of the transwarp network thanks to the dealings of the old Captain’s future self. This left the ship stranded 100 light years from known Federation Occupied space in the Delta Quadrant. The main premise of the current storyline has been to get the ship back to Federation occupied space. Along the way, the ship has encountered a previously unknown species from another dimension known as the Krentarii and taken shore leave on a planet where it turned out that the tourism industry held a sinister secret and used children as slaves. The ship and the crew helped to liberate the slaves and end the terrible situation and also helped to return a lot of the slave children to their rightful homes.” Slaves, transwarp networks, beings from another dimension – it all sounds very exciting in the Delta Quadrant and its clear these enticing stories are part of the reason for the sims success in the past. But what has the CO got in mind for the future? “In the current mission, the Akagi has encountered another of the portals connecting our space time to the Krentarii’s dimension in the mess hall of all places and at the same time, a fleeing ship has happened upon the ship chased by a Borg Sphere.” The dastardly Borg were always bound to make an appearance at some point, weren’t they? It wouldn’t be the Delta Quadrant without them.
For some, enticing and keeping players is a difficult task, but Karen has a solid plan of attack to address this. “I want to provide my crew with a welcoming place to write and to help guide them to write some good solid science fiction stories.” We’re in this for the stories we write, and Karen is clearly focused on achieving quality rather than quantity.
It wouldn’t be Star Trek, though, without time travel and it’s clear that Karen has one aim in mind when she thinks to the future; longevity. “I want to see the Akagi last for a very long time and to be known for its strong science fiction stories that holds the essence of Star Trek at its heart.”
Unlike many, the CO of this fine little ship is humble to the end. “I’m honoured that the Akagi has been chosen for this article and I’d just like to say that every single one of my crew is valued and that it’s been an honour to write with them for the past few years.” But like always, the Akagi is just one cog in the wheel of Bravo Fleet and for that cog to keep turning, new recruits are needed. “Whilst all of the senior officer posts are now taken however, we have junior officer posts available in all of the major departments and are happy to accept both civilians onto the crew as well as consider other roles that a new player might be interested in creating so long as their ideas are sound and consistent with Star Trek canon.”
Congratulations to this month’s Sim Spotlight.
(Starbase 400-Stardate 69945.3) Hello again, this is Joseph Cronkite reporting. Fleet Admiral Bremer has been arrested! Returning from a Federation/Cardassian conference, Bremer was arrested by Commander Cobb of the Starfleet JAG Corps for the murder of a Cardassian Legit and the destruction of his ship. Bremer denied the allegations, saying he’d spoken to the Legit at the conference but certainty never attacked or killed him. Bremer will be taken to Earth to appear before Starfleet Command and for a General Court Martial, and the Cardassians are demanding he be extradited to stand trial on Cardassia.
In other, more happier news, we’ve learned that Major General Hurd has been promoted to the position of Task Force 99 Commanding Officer within the Forth Fleet (Bravo Fleet). She has chosen Rear Admiral K’Temoc to be the new Task Force Executive Officer. Congratulations to them both.
Update: We have an update to this breaking story. We’ve been told that Commander Cobb will be taking Fleet Admiral Bremer to Earth today. We’re not sure if it’s for a Court Martial or to be extradited to the Cardassians. In a possibly unrelated story, we’ve also learned that newly promoted Rear Admiral K’Temoc has taken the Pegasus out for a patrol mission. Unnamed sources stated several key Officers and a unit of Marines lead by General Jackson were also aboard the Pegasus.
Update II: We’ve learned some addition information. Fleet Admiral Bremer has escaped custody and Commander Cobb is also missing. No one aboard the USS Kuznetsov is sure how either could have gotten off the ship while it was at warp enroute to Earth, but all ships in the sector as well those between Starbase 400 and Earth have been placed on alert.
We will continue to follow up on this story, and more, as details become available. Until then, I’m Joseph Cronkite for the Federation News Service.
February 2016 was a strong month for the fleet as a whole. Representing Task Force 99 with the Sim of the Month award is a recent addition to the fleet, the USS North Star. This Vesta-class starship is commanded by Captain Cyndi Song.
“WOW!” exclaimed Cyndi in an interview with BFNS. “What an honor! I’m stunned and extremely humbled by this. I never expected to gain this award being so new into the Fleet. Many, Many Thanks to everyone who nominated the North Star.”
Neither the North Star or its Captain have strong roots in Bravo Fleet as the sim was founded a couple years ago in a different fleet. After seeing firsthand how the dwindling simming community was causing that fleet to dry up, Cyndi began looking for other options. “I looked at several fleets before deciding on Bravo Fleet. I felt it was a good fit for my ship and my crew.”
The North Star currently sports an amazing roster backed by ten versatile players. “Some of us play more than one position,” says Cyndi, who also indicated that there’s always room for more.
Where is the North Star now? After dealing with an intense mission which started with a garbled distress call, the crew is currently enjoying some R and R at the infamous Starbase 400. They’ll be launching on their next adventure very soon.
Captain Song’s amazement with winning this award did not stop throughout the interview. She had this to say: “I’d like to say Thank You to EVERYONE who nominated the North Star for this award. It’s a great honor and one I am very proud and honored to have been awarded. To my crew, I’d like to say thank you for serving on this fine ship. Without you and your continued support and creative writing skills I’d not have the ship, crew or this award. Ya’ll are the best and I’m honored and proud to be your captain.”
Congratulations to the crew of the USS North Star! Keep up the great work!
In a rare move, the first Sim of the Month Award for Task Force 72 was awarded to a brand new sim in Bravo Fleet, the USS Argonaut. Overseeing eight other players is Commander Michael Cousland, played by Jason.
“It is an honor,” says Jason, “to be in Bravo Fleet and to earn this award in our first month here.”
Like the Argonaut itself, Jason too is a recent addition to Bravo Fleet, having signed up for service on another vessel before sitting in the Captain’s Chair. “I started to get that itch all us old CO’s get,” he explains. He’s commanded a couple sims before outside of Bravo Fleet, and it was the connections he made over the course of his simming career that helped to quickly launch the Argonaut. “You never know what you will find when you give people a chance.”
And with just a month of game time logged, gameplay continues to excel, breathing life into Task Force 72. As with 72’s other simulations, the Argonaut finds itself charged with the defense of the Alpha Quadrant and also challenged to explore strange new worlds. It’s current mission, “The Fate of Us” finds the Argonaut clearing an old Federation outpost that was last used as a hospital. Unfortunately, the Hospital was bombarded, leaving few survivors.
When FNS asked Jason if he had any advice for struggling or new COs, he replied, “The first thing keep your head up. Things will always happen in the simming world, sometimes those things can bring you down. Give everyone a chance in your sim, you will never know who will be great with a little help and training.”
Jason even declares that the Admiralty and even one’s own crew are excellent resources for help should it ever be needed. And of course, “Having fun is the most important thing of all and very important it is a game.”
Much more is in store for the intrepid crew. After all, the Argonaut is just getting started.
In an unexpected return, the Borg have struck with a vengeance. Four Borg cubes were spotted approaching Starbase 900. Instead of their typical assimilation patterns, the Borg mercilessly struck and destroyed Starbase 900.
Crewman Apprentice Jonas Gabriel, who was piloting a workbee tending to the nearby Norway-class USS sh’Pavress, didn’t expect to survive. “The sh’Pavress immediately broke its moorings in an attempt to retrieve as many survivors as possible,” he told the Federation News Service. “I watched as she wasn’t tractored, and instead took a cutting beam to the middle of the Engineering hull.” The sh’Pavress suffered what appeared to be a warp core breach moments later.
Other eyewitnesses confirmed the Borg sent in further reinforcements to the attack, including two more cubes and three spheres. One can assume they wanted to leave nothing to chance, absolutely destroying Task Force 38’s Command and Supply Hub in the process.
The surrounding radiation field amazingly shielded Gabriel from the attack and Borg sensors, allowing him to hide until he could be retrieved by a relief force that arrived from the Solaria Gateway. “I might be a crewman,” says Gabriel, “but I’ll definitely do my part to avenge those the Borg savagely murdered.”
Several Starfleet vessels responded to the crisis, including the Sovereign-class USS Helios. What’s curious is that the Helios arrived without her saucer section. Its fate, and those aboard it, remains unknown. Rear Admiral Diego Macedo had been reported aboard, and it is uncertain if he survived the battle.
Among the casualties are the USS Talyx, USS Claw, USS Magellan, USS Monitor, USS Khitomer, USS Hammond and USS Takei. A final casualty list has not yet been released as survivors are still being processed and accounted for.
Rumors are circulating regarding what could be the Admiral’s final order: destroying the Iconian Gateway that connects Task Force 38 elements to the remainder of the fleet. FNS reached out to Fourth Fleet Command to investigate the validity of this rumor, but our representatives were unavailable for comment.
Taking home the first Sim of the Month Award for Task Force 99 this month is none other than the Endeavour NX-06. Commanded by Captain Edward Pearson, the Endeavour is currently simming in the year 2156, two years after the final televised adventure of the NX-01 (not counting the series finale).
At press time, ten intrepid writers aboard the Endeavour bravely explore a frontier never explored on the small screen, the Earth-Romulan War.
It’s no surprise to learn that the man behind Captain Pearson, J.P. (or CaptainPorthos as he’s known on RSB) has a special place in his heart for Enterprise-Era Trek. “When Star Trek: Enterprise came along,” J.P. told BFNS, “this was my first opportunity to watch a Star Trek series on TV from start to finish, and I did that. The Enterprise-era means alot to me. In a way, it was MY Trek. It’s what I was able to grow up with.”
The Endeavour does not represent J.P.’s first attempt to explore more stories in the 2150s. He first tried with the Discovery, an independent sim that simply didn’t last. While J.P. moved on to creating more unique sims, the Imperiax in Task Force 93 and the USS Jericho in Task Force 9, J.P. could not forget about his first love. “I wanted to play in an era that I wasn’t able to do justice to before. Based on the story and background that I was using, Endeavour seemed like the perfect fit and thus the sim itself was born.”
Two years have since passed, and the Endeavour continues to stand strong, especially as it must deal with the early days of the Earth-Romulan War. Official canon states that the war will not end until 2160, so one can easily expect the war to deliver more ups and downs as the missions continue.
And despite the Discovery’s early failures, J.P. has found the Endeavour to bring a refreshing change. “I can’t deny that it is my favourite of the three ships,” he declares, though he quickly professed his love for his other ships. “I think it probably just boils down to my love for the Enterprise-era.” And by looking at his website, his love can’t be overlooked. Thanks to his incredible graphics and coding skills, the Endeavour’s website looks like it was lifted off of T’Pol’s bridge station!
Of course, an impressive website does not make a sim great. J.P. knows the secret, “Of course in the end, it just all falls down upon the shoulders of my players who have helped Endeavour get to where it is today. I have a loyal group of players there with whom I’ve had the privilege of writing with for some time and it’s just great when you can count on others to help you out.”
But what is next for the Endeavour? Aside from exploring the Romulan War, they’ll continue the ageless spirit of The Original Series, exploring new worlds and encountering alien life, even life in the form of probes left to their own devices.
When asked how he handles the challenge of running an Ent-Era simulation in today’s choppy simming waters, J.P. had this to say: “I let my players know that I’m in it for the long haul through thick and thin. If we only have four or six players, I’m still going to continue writing and playing, and telling stories. I think that it’s important for people to know that the time they’re investing isn’t going to be just thrown away the first moment you encounter troubled waters. In today’s simming world you need to be patient and persistent. You have to worry less about the downfalls around you, and more about what you’re doing to improve things. Eventually the pieces will fall into place and you’ll be rewarded in kind.”
Truer words can not be said. On behalf of Bravo Fleet, we here at BFNS salute the Endeavour NX-06 on their well-deserved award!
The beginning of 2016 saw Task Force 9 launch with a record start, scoring a three-digit post count. Emerging as the trend-setter of the Task Force is none other than the USS Nogura, a Sovereign-class starship under the command of Kai, known in-character as Captain Nathan Hunter.
With nine writers aboard the Nogura, Kai has fearlessly led the Nogura through the Bajoran wormhole and plunged the ship right into the Task Force Canon to deal directly with the devious Consortium. This unique plot required a different approach for the Nogura as she is something few other sims in Bravo Fleet are not: a transfer.
“There were a number of reasons why I chose to bring the Nogura to Bravo Fleet,” says Kai, who just a few months before was the Commanding Officer of Task Force 93, overseeing operations in the Beta Quadrant. He relinquished the role to focus on what he loves most, simming. Kai cites the fantastic Bravo Fleet Community among the reasons he ported the Nogura over. But above all, Kai says, “I had wanted to partake in TF9’s storyline for a while and when my crew seemed open to the possibility of transferring, I jumped at the chance to speak to greenfelt22 and Jelim_Mar and look into the chance of transferring.”
The transfer was solidified quickly, just in time for the sim’s first birthday in November 2015. “It was the best decision I have made.”
But Captain Hunter was not the in-character Captain when the Nogura arrived. That honor belonged to the now Lieutenant-Commander Azulas. After arriving in the Gamma Quadrant and stopping a rogue Klingon vessel, she was rewarded with a multi-level demotion to make room for Hunter’s arrival. And, the Nogura doesn’t get far before she’s confronted (more like ambushed) by four Starfleet vessels. Three words are transmitted, “Pity is Treason,” and suddenly the crew of the Nogura bears witness to betrayal, insurrection and more as they are officially hazed into the Task Force Canon.
And even as February treads along, the crew of the Nogura continue to write away, fighting to regain control of their starship. If they’re successful, more danger awaits. Kai has far worse things planned for the crew, including a deadly contagion, discover new threats and rogue Romulan agents, and even encounter the Jem’Hadar.
But all of this wouldn’t have been possible without a strong writing base. “I’d like to think that we have become an integral part of TF9. We have achieved some fantastic levels of activity, received two Sim of the Month Awards and one of our players has twice been Player of the Month. Nothing that we have achieved would be possible without my fantastic crew.” Kai goes on, “I have been a CO for many years and commanded many sims, but in that time, I don’t think I have had a crew quite like this. I love writing with them and for once in my life, I feel able to pass on a bit of the control to them (very hard for me as I am a control freak!) I hope each of them remains aboard for ages to come.”
Every Commanding Officer has experienced struggle trying to launch or keep a sim going. Kai’s final word is an excellent piece of advice for COs, no matter if they are green or seasoned veterans: “Without my crew, me and my command are nothing. More people, more CO’s should take notice of this. No sim can exist without the players and more should be done to reward them and keep them interested. If a CO can motivate and reward his or her crew, they can achieve anything as a group.”
Anyone needing to see this advice in action only needs to look at the Nogura and its writers. It’s safe to say the Nogura is here to stay. Congratulations on Sim of the Month!
The Hall of Honours team is proud to congratulate the following simulations on being awarded the Simulation of the Month award for December 2015. The Simulation of the Month (of a Task Force) is awarded to a simulation for its contribution to the Task Force canon, activity, quality, number of players and others. All simulations in a Task Force are automatically considered for this award however nominations are sought from fellow CO’s. It is awarded by the Hall of Honour on behalf of the TFCO, so it is important that you get your nominations in each month. Can we all please congratulate these fine simulations in our community on being named December 2015 Simulations of the Month. Your awards will shortly be confirmed to you all on the Bravo Fleet Wiki and we will look into doing some nice banners to allow you to show off your award.
Task Force 9 Simulation of the Month – No Nomination
Task Force 38 Simulation of the Month – USS Victory
This is well deserved as the sim has a number of players who has come to us with ideas as well as trying to help us get the Canon going. This sim deserves this because they are good at communicating with me and are wanting to help with the Canon
Task Force 72 Simulation of the Month – Deep Space 12
I am nominating Deep Space 12 for this award, I have really seen a big improvement in the simulation across a month when simulations are shutting down or slowing down for the holidays, I have seen Deep Space 12 keep on improving and they are really taking a big step in the lead of the Order of 12 storyline within Task Force 72 and I want to acknowledge that in some way to the whole crew of Deep Space 12
Task Force 93 Simulation of the Month – Deep Space 14, Themis Group
Deep Space 14 was nominated by one of the Task Force’s COs, and I agree wholeheartedly. This month, Deep Space 14 was both the most active simm in the Task Force, and it doubled the number of posts it made in the past two months – put together!
Task Force 99 Simulation of the Month – USS Carpathia, Alternate Division
TF99’s Sim of the Month award goes to the USS Carpathia for actively posting, having a well developed storyline, and for having a successful reboot of their fantastic story.