Difference between pages "Negh'Var class" and "Introduction to Bravo Fleet Writing"

From Bravo Fleet
(Difference between pages)
 
 
Line 1: Line 1:
{{Specification
+
While Bravo Fleet offers many activities, our history as a role-play group means we retain a strong creative spirit. Members’ writing in various forms is at the forefront of driving the group’s canon as [[Starfleet|Starfleet’s]] [[Fourth Fleet]] in {{year}}. Bravo Fleet writing falls into two formats: [[Roleplaying Game Policy|roleplaying games]] (historically referred to as ‘sims’) and writing on members' [https://wiki.bravofleet.com/index.php/Command_Policy#2_-_Primary_Commands Commands].
| image = [[Image:Neghvarclass.png]]
 
| displayName = '''''Negh'Var'' Class'''
 
| name = Negh'Var
 
| affiliation = [[Klingon Empire]]
 
| operator = [[Klingon Defense Force]]
 
| status = Active
 
| role = Cruiser
 
| type = Warship
 
| precedingClass = Vor'cha
 
| succeedingClass = Bortasqu'
 
| dateEntered = 2372
 
| productionEnd =
 
| retired =
 
| expectedDuration = 100 years
 
| expectedRefit = 10 years
 
| timeResupply = 5 years
 
| crewComplement = 2,500
 
| emergencyCap = 10,000
 
| civilians =
 
| populationCap =
 
| flightCrew =
 
| passengers =
 
| length = 682.32 meters
 
| width = 470.09 meters
 
| diameter =
 
| height = 136.65 meters
 
| decks = 41
 
| propulsionSystem = Matter/Antimatter powered warp drive
 
| cruiseSpeed = Warp 8.9
 
| maxSpeed = Warp 9.6
 
| emergencySpeed = Warp 9.91 (for 12 hours)
 
| energyWeapons = *1x forward-mounted heavy disrupter cannon
 
*2x ventral "siege" disruptors
 
*18x disruptor cannons
 
| torpLaunchers = *2 forward
 
*2 aft
 
| torpPayload = 500 Klingon torpedoes
 
| shields = *Klingon deflector shields
 
*Klingon cloaking device
 
| dockingfacilities =
 
| shuttleBays = 1 main hangar deck
 
| shuttles = 10
 
| runabouts =
 
| fighters = 24
 
| aux =
 
| msd =
 
}}
 
  
The '''''Negh'Var''-class warship''' is a mightily impressive and intimidating vessel in the service of the [[Klingon Empire]]. Serving as the flagship class of the [[Klingon Defense Force]] in the latter half of the 24th century, the ''Negh'Var'' is a direct response to the [[Old Romulan Star Empire|Romulan Star Empire's]] flagship [[D'deridex Class|''D'deridex''-class]] warbird. Following its debut during the [[ma:Dominion_cold_war|cold war]] with the [[Dominion]], the ''Negh'Var'' continues to be a vital key within the Klingon fleets into the 25th century and has only recently been displaced as the Klingon flagship very recently by the [[Bortasqu' Class|''Bortasqu'''-class]].
+
== Roleplaying Games ==
+
RPGs. Group Writing. Sims. This form of collaborative writing is part of Bravo Fleet’s history, taking part most often on Starfleet ships in {{year}} - though games exist for different eras, factions, and even genres.
===Exploration and Science===
 
The ''Negh'Var'' is unique within Klingon shipbuilding in that its sensor suite was developed with a multi-faceted approach in mind. Although, much like the [[K't'inga Class|''K't'inga'']] and [[Vor'cha Class|''Vor'cha''-classes]], the sensor suite's primary purpose is tactical with an additional purpose of searching for resources, it was also built with exploration in mind. The Klingon Empire learned over the 24th century from their [[United Federation of Planets|Federation]] allies that exploration and scientific discovery can lead to untold and unimaginable advances in all areas of technological advancement. Learning from that, the ''Negh'Var'' is more than capable of the scientific duties on par with many Federation ships which allows it to conduct these studies while in deep space. Whereas most other Klingon ship classes would have to send preliminary data back to the nearest outpost so a dedicated science ship could be deployed, the ''Negh'Var'' itself would be carrying out these studies and sending comprehensive details back to the nearest outpost for analysis.
 
  
===Diplomacy===
+
It tends to take the language and form of a role-playing game, with members as ‘players’ writing (usually) one character and a Game Master writing the ship’s captain and dictating the main story beats. There can be all sorts of variations within this - the GM isn’t always the captain, players may write for many characters, or plots may be improvised by players rather than developed by the GM. Even writing in a less role-playing form, where members may share writing of characters and the planning of the story, counts as an RPG.
For a Klingon ship, the ''Negh'Var'' is leaps and bounds above all but the ''Bortasqu' '' in terms of diplomatic capability. The ''Negh'Var'' takes its cues directly from the ''Vor'cha'' with the increased ability to host dignitaries and spaces for diplomatic talks. It is equipped with full staterooms for Klingon administrators, massive quarters for diplomatic guests of the Klingon Empire, and sizable conference rooms. With the exception of the ''Bortasqu' '', the ''Negh'Var'' would be tasked with most diplomatic missions on behalf of the Klingon Empire and would likely fly the flag of the leader of a [[Great Houses|Great House]] in any diplomatic overtures, including with other Great Houses. However, much like the ''Vor'cha'', non-Klingons would find these accommodations lacking compared to counterparts such as the [[Odyssey Class|''Odyssey''-class]].
 
  
===Engineering===
+
The management of these games is overseen by the Bravo Fleet Operations Officer, who ensures they meet expected standards of quality and activity, usually agreed upon by both the Ops Officer and a prospective GM. These expectations exist because BF members can usually apply to join these games, so a GM is taking on a commitment to run an activity for the fleet.
Much like her predecessors the ''K't'inga'' and ''Vor'cha'', the ''Negh'Var'' was designed with the idea of a predator stalking its prey in the depths of space. Like the others, the primary hull was almost wing-like, with two nacelles on each side, connecting a long "neck" with a "head" command section. While the ''Negh'Var'' was meant to complement the ''Vor'cha'', not replace it, the ship is essentially an improved version of the ''Vor'cha'' in every way. The engine capabilities were increased, additional weapon mounts, the addition of siege weaponry built into the design, an advanced sensor suite for both combat and exploration, and even staterooms for diplomacy. Throughout the design process, the ''Negh'Var'' was one of the first ships in Klingon history to not be a simplistic engineering design but rather a more advanced one bringing many different efforts together at once.
 
  
===Tactical===
+
RPGs are run on the main Bravo Fleet website, using the Bravo Fleet Management System (BFMS). The BFMS also stores character biographies and crew rosters and supports the collaborative writing of members, which is easily seen and shared with the whole fleet. In Character, the 25th-century Starfleet ships are the Fourth Fleet’s Forward Operation Forces. They operate independently of [[Task Forces]], pursuing a wide range of missions under the command of the Fleet Operations Officer.
The ''Negh'Var'' was the most well-equipped ship in Klingon history at the time of its launch. With more weapons emplacements than any other Klingon ship previous, its seige technology, and torpedo payload the ''Negh'Var'' was, for a time, likely the most formidable warship in the Alpha or Beta Quadrants.
 
  
The ''Negh'Var'' is primarily unique from the previous cruisers in its lineage such as the ''K't'inga'' and ''Vor'cha''-classes by the two massive disruptor cannons on the underbelly of the ship. Tactically, these set the ''Negh'Var'' apart as being seige weapons against stationary targets be it planetary or starbases. The ''Negh'Var'' was the first Klingon ship to have such weaponry built into the design at inception, whereas previous classes would need to have such weaponry specially mounted for a specific mission profile.
+
== Command Writing ==
 +
{{For|article=[[BFMS Fiction Guide]]  on how to write on the website}}
 +
BF fiction is on the main site, where writing in the Bravo Fleet canon of all flavours can be found, from official Intelligence Office releases to the narratives driving Task Force story-arcs to the stories of individual members. This is the core of Bravo Fleet canon, lore development, and IC fleet activities. The majority of this fiction, and that discussed in this guide, focuses on stories about the Starfleet officers and starships of the Fourth Fleet in the 25th century - the [[Writing Primary Characters|Primary Characters]] of members, and their primary or squadron commands.
  
Additionally, the ''Negh'Var'' includes a hangar deck at the top of the ship in a pod-like structure which allows it to carry several ''Kivra''-class shuttles and multiple wings of ''To'Duj''-class fighters. Tactically, this allows the Negh'Var to serve as a command and control warship on the field of battle coordinating efforts not only as a massive deployment platform itself but also with any escort ships in its battlegroup.
+
Once you reach the rank of Midshipman, you can request your own Primary Command. This acts as an OOC platform and 'collection' for your writing, as well as the IC premise for your story - normally some sort of ship. For Midshipmen to Lieutenants, this is a ''California''-class utility cruiser, a minor ship best-suited to simple missions in Federation space. It might be based out of the Headquarters of your Task Force, going off into missions in that area of the galaxy, but your TF doesn't force you into any one region, base, or place. If you want some guidance on what might make a good story at that level, talk to your Task Force staff for help. Once you reach the rank of Lieutenant Commander, you get the freedom to choose from a selection of ship classes. At any point you have the liberty to write your starship’s adventures anywhere in Bravo Fleet canon, with your Task Force’s specific mission for inspiration and direction.
  
===Shipboard Life===
+
From the rank of Captain, you may be entitled to an additional Starfleet ship under the [https://wiki.bravofleet.com/index.php/Command_Policy#3_-_Squadrons Squadron system]. If at any point you wish to write a story about a non-Starfleet ship or a different era in Trek canon, this would require reaching the rank of Commander and successfully submitting a fiction proposal to the Intelligence Officer. Before considering one of these other stories, be sure to read the [[Fiction Proposal Guide]].
The ''Negh'Var'' at the time of its design and launch was, by and far, the most luxurious ship for a Klingon warrior to serve on according to Klingon societal norms. The ''Negh'Var'' is impressively large with a lot of accommodating space within, but it also regularly boasts a total complement including crew and troops of roughly 2,500 warriors. This translates to many lower-ranking troops finding their accommodations not much different than on a [[B'rel Class|''B'rel''-class]] Bird-of-Prey with cramped, spartan, bunk-like quarters. Larger, single rooms are reserved for officers and the most accommodating rooms are left for the ship's senior staff, guests, diplomats, and members of the Klingon High Council. However, there are several creature comforts that, by Klingon standards, would make the ''Negh'Var'' luxurious such as several dining halls, multiple holodecks, and a large Great Hall in the belly of the ship which is capable of accommodating hundreds of crew at once.
 
  
==Class History==
+
=== Fleet Canon and Member Canon ===
Shortly before the successful deployment of the ''Vor'cha''-class cruiser in 2367, the Romulan Star Empire emerged from its half a century of isolation in their mighty ''D'deridex''-class warbirds. The size and firepower of these newly discovered Romulan vessels worried the Klingon High Council enough that the ''Vor'cha'' may be insufficient. As a result, Chancellor [[ma:Gowron|Gowron]] ordered the development of a new warship in secret that could rival the ''D'deridex''-class and, in truth, also the once-enemy-turned-ally Federation's equally impressive [[Galaxy Class|''Galaxy''-class]] starships in combat.
+
Bravo Fleet canon is laid out by the [[Canon Policy]]. In brief, all members are required to abide by Star Trek canon and Bravo Fleet canon. But you are, as individual writers, encouraged to pay attention to Section 1.3 of the Canon Policy, titled 'Member Canon.'
  
Over the next few years the ''Negh'Var'' underwent development and construction at the highly secure fleet yards located at [[ma:Ty'Gokor|Ty'Gokor]]. Over its development, Chancellor Gowron became less suspicious of the Federation and increasingly sought out their assistance in its development.  
+
This consists of small details that are not specified by official or fleet canon, relevant to and developed by individual members. At its most obvious, it’s things like the creation of a strange nebula your starship surveyed somewhere in the Alpha Quadrant, or the lone Klingon captain who helped a ship. These are details that affect only your stories and your characters, and while you are welcome to discuss them, write about them, or even [[Submission Guide|add them to the Bravo Fleet wiki]], unless or until they are ratified by the Intel Office no other members are obligated to follow that canon or acknowledge its existence.
  
By 2371, the prototype, the IKS ''Negh'Var'', was ready for launch and was deployed as the flagship of the Klingon Empire. A year later, several other ''Negh'Var''-class ships were put into production with expectation being that the Klingon ship yards would be able to produce several of these vessels per year. The first real test for the class came a year later in 2372 when the IKS ''Negh'Var'' herself, now under the command of General [[ma:Martok|Martok]] served as the Klingon flagship during the [[ma:Klingon-Cardassian_War|Klingon Empire's invasion of Cardassia]]. This included the [[ma:First_Battle_of_Deep_Space_9|siege]] of [[ma:Deep_Space_9|Deep Space 9]], in which the ''Negh'Var's'' incredibly powerful seige disruptors were first seen in action by the Federation. The siege disruptors proved powerful enough to breach the station's shields sufficiently enough to begin mass transport of Klingon ground troops onto the station.
+
But those are easy examples. The Intel Office does not aspire to flesh out every single detail about the Trek universe, and nor does Star Trek canon itself provide all of the details. Some facts slip through the cracks: what’s the state of Tokyo in the 25th century? Who taught Basic Warp Design at Starfleet Academy in 2387? What is the current status of a very minor one-off alien race from TOS, almost a century and a half later?
  
By the time full hostilities broke out between the [[Dominion]] and the Federation-Klingon-Romulan Alliance, several ''Negh'Var''-class warships were in full service. Serving as command and control flagships during the Dominion War, the ''Negh'Var'' proved more than capable of holding their own against anything the Dominion was throwing at the Klingons. While the older, less advanced Klingon designs were falling in great numbers, the ''Negh'Var'' was able to break through Dominion lines in engagements. However, throughout the war, the Klingons were only able to produce five ''Negh'Var''-class ships before the war ended meaning that while impactful, they weren't able to end the war with any expediency on their own.
+
Some of these are questions which the Intel Office may answer as they arise. Others - like the Academy teacher - will most certainly not be defined by Bravo Fleet canon. Members are welcome to specify these details in their own stories, but with the understanding that nobody else is bound by them. Strong and interesting ideas that flesh out relevant parts of the universe may be adopted by the Intel Office into Fleet canon, but until then, they are Member Canon.
  
After the war, the ''Negh'Var'' continued to serve as the flagship of the Klingon Empire. The class was produced by all of the Great Houses in the effort put forth by the Klingon Defense Force to rebuild the Klingon fleet. The ''Negh'Var'' continued to serve in its capacity as a flagship and strike fear into enemies well into the waning years of the 24th century. In the beginning years of the 25th century, the ''Negh'Var'' is still a formidable capital ship in the Klingon fleet. Only in recent years has it begun to be supplanted by the much bigger ''Bortasqu' ''-class vessels. However, the deployment of the ''Bortasqu' '' has not slowed down the building efforts of the ''Negh'Var'' as a ship that appears to be a mainstay in most House fleets as well as the Klingon Defense Force overall.
+
Might this lead to contradictions? Very possibly. Is this a problem? Not usually. Often such details can be reconciled; it is possible, or even likely, that multiple officers taught Basic Warp Design at the Academy in 2387. It’s worth remembering that even Star Trek canon occasionally contradicts itself on these minor details, and Star Trek has survived it. If two entirely separate stories have different, minor details, it’s very easy to live and let live. If necessary, consult the Intel Office for guidance.
  
==In Play==
+
Remember that member canon doesn't mean "do what you want, and other people don't have to adhere to it." The point is that member canon should be details other people ''can'' ignore because it's a big galaxy. Don't contradict fleet canon, or Trek canon. Avoid, if possible, defining things that can't be worked around - do you really ''need'' to name the current head of Starfleet Tactical, even if fleet canon hasn't specified it? Our goal is to build a cohesive universe where everyone's playing in the same large sandpit, leaving room for one's own flair and stories - rather than to dictate every detail, ''or'' to have chaos wherever we go.
*
 
  
 +
== Common Issues ==
 +
As ever, the [[Canon Policy]] explains the do's and don't and ins and outs of Bravo Fleet storytelling and content creation. But there are a few mistakes/misunderstandings/knowledge gaps which come up fairly often:
  
{{clear}}
+
* You shouldn’t be writing about or including characters or ships from Star Trek canon! You can refer to them ''existing'', but for eg, we don’t know what the state of Sisko or DS9 are in the 25th century, so don’t make it a key part of your writing; don’t be an old friend, protégé, relative, etc, of ''any'' canon Trek character'','' that sort of thing.
 +
* The Command Registry is a list of all ships available in Bravo Fleet. It is meant to be a rarely-changed archive so that ships can build up a history, to help maintain a unified canon, instead of ships appearing and disappearing. This repository is not the play-thing for you to create your own task group. ''Do Not'' use ships in the registry for your writing if it’s not your own Command - there are many other names out there.
 +
** Non-registry Starfleet ships can feature in your stories - there's always a ship that needs rescuing, or delivers a guest, or maybe does even join your Command in an adventure. But there's a difference between a story where your characters work with a friendly or rival crew, and giving your captain command of their own task group of NPC ships, and the latter is against the rules - wait until you're eligible for a [[Command Policy|squadron]] for that.
 +
* The brass of Fourth Fleet Command are identified and established as characters – it’s [https://bravofleet.com/staff these fine folks]. If you need a staff-level character to appear in your writing (for briefings etc), either reach out to your Task Force Staff, or the Intel Office has established an NPC: Commodore [[Uzoma Ekwueme]]. He’ll show up, tell you what’s what, dress you down or pin a medal on you. Don’t kill him or make him evil.
 +
** This means, for most members, you shouldn't be inventing new admirals for your stories. That includes unnamed characters with the rank of admiral - that still counts as an admiral character.
 +
* This links to another rule: Your characters can hold ''up to'' the rank of captain ''or'' your OOC fleet rank, whichever one is higher. Like access to certain ship classes, starbases, or fiction concepts, writing flag officers is gated to OOC rank. With the TF staff characters, commanders of TFHQs, and Commodore Ekwueme, PCs and NPCs exist to facilitate your storytelling. Otherwise, allowing members to create and write flag officers, even as minor characters, usually results in one of the following:
 +
** Creating a new random Fourth Fleet admiral (see above!).
 +
** A member trying to bypass rank restrictions, in the same way that writing a lot about a non-registry ''Sovereign''-class starship that joins your avatar command on adventures would be.
 +
* Please pay ''close attention to our [https://wiki.bravofleet.com/index.php/Canon_Policy#Section_6_-_Content_and_Ratings Content Rules]''. In short: check if your Command needs to list its rating. And, to just directly quote this part from our policy:
 +
** Sexual violence should be addressed, if at all, with particular care. It should never be depicted directly in a scene, or be discussed by characters in any detail. Reference to sexual violence of any sort should never happen without the explicit OOC permission of every member involved in the story and, in RPGs, the GM. Stories may be removed at the Intelligence Officer's discretion, as per the above on appropriate content.
 +
*One final note that’s less about the rules and more about tone: Bravo Fleet has a frankly shameful history of failing to engage with the themes and tone of Star Trek. Starfleet is not a military (having weapons doesn’t make you military), Starfleet Marines have never, ''ever'' been canon, Section 31 (and equivalent depictions of Intelligence) is almost always written in a way which makes the reader want to die of embarrassment, and Star Trek is not a universe about the power of might making right. The Federation may be flawed but it is fundamentally a government founded on principles of respect, liberty, and the search for peace and knowledge. The Intel Office has worked hard to move away from depictions of Starfleet that would be more at-home in an unironic interpretation of the movie ''Starship Troopers.'' Work with us to tell stories that may be set against challenges in a difficult universe, in places which are dark and where doing the right thing is hard – but are at their core about a hopeful view of the future and humanity, even if it’s working ''towards'' that view.

Latest revision as of 13:26, 3 March 2024

While Bravo Fleet offers many activities, our history as a role-play group means we retain a strong creative spirit. Members’ writing in various forms is at the forefront of driving the group’s canon as Starfleet’s Fourth Fleet in 2401. Bravo Fleet writing falls into two formats: roleplaying games (historically referred to as ‘sims’) and writing on members' Commands.

Roleplaying Games

RPGs. Group Writing. Sims. This form of collaborative writing is part of Bravo Fleet’s history, taking part most often on Starfleet ships in 2401 - though games exist for different eras, factions, and even genres.

It tends to take the language and form of a role-playing game, with members as ‘players’ writing (usually) one character and a Game Master writing the ship’s captain and dictating the main story beats. There can be all sorts of variations within this - the GM isn’t always the captain, players may write for many characters, or plots may be improvised by players rather than developed by the GM. Even writing in a less role-playing form, where members may share writing of characters and the planning of the story, counts as an RPG.

The management of these games is overseen by the Bravo Fleet Operations Officer, who ensures they meet expected standards of quality and activity, usually agreed upon by both the Ops Officer and a prospective GM. These expectations exist because BF members can usually apply to join these games, so a GM is taking on a commitment to run an activity for the fleet.

RPGs are run on the main Bravo Fleet website, using the Bravo Fleet Management System (BFMS). The BFMS also stores character biographies and crew rosters and supports the collaborative writing of members, which is easily seen and shared with the whole fleet. In Character, the 25th-century Starfleet ships are the Fourth Fleet’s Forward Operation Forces. They operate independently of Task Forces, pursuing a wide range of missions under the command of the Fleet Operations Officer.

Command Writing

For the article, see BFMS Fiction Guide on how to write on the website.

BF fiction is on the main site, where writing in the Bravo Fleet canon of all flavours can be found, from official Intelligence Office releases to the narratives driving Task Force story-arcs to the stories of individual members. This is the core of Bravo Fleet canon, lore development, and IC fleet activities. The majority of this fiction, and that discussed in this guide, focuses on stories about the Starfleet officers and starships of the Fourth Fleet in the 25th century - the Primary Characters of members, and their primary or squadron commands.

Once you reach the rank of Midshipman, you can request your own Primary Command. This acts as an OOC platform and 'collection' for your writing, as well as the IC premise for your story - normally some sort of ship. For Midshipmen to Lieutenants, this is a California-class utility cruiser, a minor ship best-suited to simple missions in Federation space. It might be based out of the Headquarters of your Task Force, going off into missions in that area of the galaxy, but your TF doesn't force you into any one region, base, or place. If you want some guidance on what might make a good story at that level, talk to your Task Force staff for help. Once you reach the rank of Lieutenant Commander, you get the freedom to choose from a selection of ship classes. At any point you have the liberty to write your starship’s adventures anywhere in Bravo Fleet canon, with your Task Force’s specific mission for inspiration and direction.

From the rank of Captain, you may be entitled to an additional Starfleet ship under the Squadron system. If at any point you wish to write a story about a non-Starfleet ship or a different era in Trek canon, this would require reaching the rank of Commander and successfully submitting a fiction proposal to the Intelligence Officer. Before considering one of these other stories, be sure to read the Fiction Proposal Guide.

Fleet Canon and Member Canon

Bravo Fleet canon is laid out by the Canon Policy. In brief, all members are required to abide by Star Trek canon and Bravo Fleet canon. But you are, as individual writers, encouraged to pay attention to Section 1.3 of the Canon Policy, titled 'Member Canon.'

This consists of small details that are not specified by official or fleet canon, relevant to and developed by individual members. At its most obvious, it’s things like the creation of a strange nebula your starship surveyed somewhere in the Alpha Quadrant, or the lone Klingon captain who helped a ship. These are details that affect only your stories and your characters, and while you are welcome to discuss them, write about them, or even add them to the Bravo Fleet wiki, unless or until they are ratified by the Intel Office no other members are obligated to follow that canon or acknowledge its existence.

But those are easy examples. The Intel Office does not aspire to flesh out every single detail about the Trek universe, and nor does Star Trek canon itself provide all of the details. Some facts slip through the cracks: what’s the state of Tokyo in the 25th century? Who taught Basic Warp Design at Starfleet Academy in 2387? What is the current status of a very minor one-off alien race from TOS, almost a century and a half later?

Some of these are questions which the Intel Office may answer as they arise. Others - like the Academy teacher - will most certainly not be defined by Bravo Fleet canon. Members are welcome to specify these details in their own stories, but with the understanding that nobody else is bound by them. Strong and interesting ideas that flesh out relevant parts of the universe may be adopted by the Intel Office into Fleet canon, but until then, they are Member Canon.

Might this lead to contradictions? Very possibly. Is this a problem? Not usually. Often such details can be reconciled; it is possible, or even likely, that multiple officers taught Basic Warp Design at the Academy in 2387. It’s worth remembering that even Star Trek canon occasionally contradicts itself on these minor details, and Star Trek has survived it. If two entirely separate stories have different, minor details, it’s very easy to live and let live. If necessary, consult the Intel Office for guidance.

Remember that member canon doesn't mean "do what you want, and other people don't have to adhere to it." The point is that member canon should be details other people can ignore because it's a big galaxy. Don't contradict fleet canon, or Trek canon. Avoid, if possible, defining things that can't be worked around - do you really need to name the current head of Starfleet Tactical, even if fleet canon hasn't specified it? Our goal is to build a cohesive universe where everyone's playing in the same large sandpit, leaving room for one's own flair and stories - rather than to dictate every detail, or to have chaos wherever we go.

Common Issues

As ever, the Canon Policy explains the do's and don't and ins and outs of Bravo Fleet storytelling and content creation. But there are a few mistakes/misunderstandings/knowledge gaps which come up fairly often:

  • You shouldn’t be writing about or including characters or ships from Star Trek canon! You can refer to them existing, but for eg, we don’t know what the state of Sisko or DS9 are in the 25th century, so don’t make it a key part of your writing; don’t be an old friend, protégé, relative, etc, of any canon Trek character, that sort of thing.
  • The Command Registry is a list of all ships available in Bravo Fleet. It is meant to be a rarely-changed archive so that ships can build up a history, to help maintain a unified canon, instead of ships appearing and disappearing. This repository is not the play-thing for you to create your own task group. Do Not use ships in the registry for your writing if it’s not your own Command - there are many other names out there.
    • Non-registry Starfleet ships can feature in your stories - there's always a ship that needs rescuing, or delivers a guest, or maybe does even join your Command in an adventure. But there's a difference between a story where your characters work with a friendly or rival crew, and giving your captain command of their own task group of NPC ships, and the latter is against the rules - wait until you're eligible for a squadron for that.
  • The brass of Fourth Fleet Command are identified and established as characters – it’s these fine folks. If you need a staff-level character to appear in your writing (for briefings etc), either reach out to your Task Force Staff, or the Intel Office has established an NPC: Commodore Uzoma Ekwueme. He’ll show up, tell you what’s what, dress you down or pin a medal on you. Don’t kill him or make him evil.
    • This means, for most members, you shouldn't be inventing new admirals for your stories. That includes unnamed characters with the rank of admiral - that still counts as an admiral character.
  • This links to another rule: Your characters can hold up to the rank of captain or your OOC fleet rank, whichever one is higher. Like access to certain ship classes, starbases, or fiction concepts, writing flag officers is gated to OOC rank. With the TF staff characters, commanders of TFHQs, and Commodore Ekwueme, PCs and NPCs exist to facilitate your storytelling. Otherwise, allowing members to create and write flag officers, even as minor characters, usually results in one of the following:
    • Creating a new random Fourth Fleet admiral (see above!).
    • A member trying to bypass rank restrictions, in the same way that writing a lot about a non-registry Sovereign-class starship that joins your avatar command on adventures would be.
  • Please pay close attention to our Content Rules. In short: check if your Command needs to list its rating. And, to just directly quote this part from our policy:
    • Sexual violence should be addressed, if at all, with particular care. It should never be depicted directly in a scene, or be discussed by characters in any detail. Reference to sexual violence of any sort should never happen without the explicit OOC permission of every member involved in the story and, in RPGs, the GM. Stories may be removed at the Intelligence Officer's discretion, as per the above on appropriate content.
  • One final note that’s less about the rules and more about tone: Bravo Fleet has a frankly shameful history of failing to engage with the themes and tone of Star Trek. Starfleet is not a military (having weapons doesn’t make you military), Starfleet Marines have never, ever been canon, Section 31 (and equivalent depictions of Intelligence) is almost always written in a way which makes the reader want to die of embarrassment, and Star Trek is not a universe about the power of might making right. The Federation may be flawed but it is fundamentally a government founded on principles of respect, liberty, and the search for peace and knowledge. The Intel Office has worked hard to move away from depictions of Starfleet that would be more at-home in an unironic interpretation of the movie Starship Troopers. Work with us to tell stories that may be set against challenges in a difficult universe, in places which are dark and where doing the right thing is hard – but are at their core about a hopeful view of the future and humanity, even if it’s working towards that view.