|
|
| Line 1: |
Line 1: |
| {{icons|bfo}}Last Update: 24 September 2023 | | {{Starship |
| | | name = Atascadero |
| | | prefix = USS |
| | | image = [[File:Solvang.png]] |
| | | registry = NCC-87080 |
| | | class = California |
| | | type = Utility Cruiser |
| | | affiliation = [[Starfleet]] |
| | | commission =2386 |
| | | decommission = |
| | | destroyed = |
| | | taskforce = Task Force 86 |
| | | taskgroup = Task Group 25 |
| | | role = Support |
| | * Diplomatic Support |
| | * Engineering Support |
| | * Scientific Support |
| | * Logistical Support |
| | * Medical Support |
| | | co = [[bfms char:76992|Captain Jonathan Jackson]] |
| | | xo = |
| | | dedication = |
| | }} |
| | {{quote|Let us never negotiate out of fear. But let us never fear to negotiate.|John F. Kennedy}} |
| | '''USS ''Atascadero''''' '''(NCC-87080)''' is a [[California Class|''California''-class]] multi-mission light starship currently assigned to [[Fourth Fleet]]'s [[Task Force 86]], operating in and around [[The Triangle]] region. Produced at the [[Avalon Fleet Yards]] and launched in 2386, the ''Atascadero'' incorporated the latest Starfleet technologies available at the time. While classified as a Multi-Mission Support vessel and capable of a wide spectrum of missions, the ''Atascadero'' specializes in low-level diplomatic and administrative missions that, while often unglamorous, are essential to Starfleet's long-term goals in the region. |
|
| |
|
| =1 - Registry Definition= | | == DESIGN AND LAYOUT == |
| #The registry lists all starships, starbases, and other entities available to Bravo Fleet for use as Commands or Games.
| | Externally similar to her ''California''-class sisters, the ''Atascadero'' has a large, circular primary hull, two large nacelles suspended below the primary hull, and a small secondary hull mounted between the nacelles. A "clean sheet" design intended from the beginning to fulfil second-line support duties, the ''California''-class has largely replaced the older ''Miranda'', ''Constellation,'' and ''Excelsior''-class ships which had been modified for these missions when their usefulness as front-line units had diminished. Unlike the sleek lines of larger explorers and cruisers which are optimized for speed and tactical situations, the ''California''-class is a pragmatic and utilitarian design which has an ungainly appearance, but has proved its value to Starfleet many times over since its introduction in 2368. |
| #The registry’s purpose is to maintain consistency across Bravo Fleet and its ongoing canon. As such, entries will not be added to, removed, or altered from the registry without permission of the Intelligence Office.
| |
| #The registry represents the In Character starships and starbases available to the Fourth Fleet in {{Year}}, and the starships and starbases available for Games and Commands.
| |
| ##Exceptions such as non-Starfleet ships or ships of a different era have been created for Fictions or Games, and may not be used as Primary Commands. These will be more often added, deleted, or altered.
| |
| ##The use of registry entries in Games is governed by Section 4 of the Operations Policy.
| |
| #Ships in the registry should only be used in lore by the members or Task Forces (in the case of TFHQ ships or Flagships only) to which they are assigned. If a story requires another ship, it should use a name not listed in the registry and would fall within the bounds of member canon.
| |
| #Stories may depict ships, including Starfleet ships, not in the registry. These must never be written as the 'main' vessel in a story, and their place in stories must be restricted to minor or supporting roles. The existence and use of these 'NPC' ships constitutes member canon.
| |
| ##These ships must always have a name not found in the registry.
| |
| ##NPC ships may not be written as assigned to a joint mission alongside a member's ship, and especially not under their command.
| |
| ##These ships should be playing roles like delivering supplies or personnel or being in need of rescue as a story's instigating event. They and their crews should not be recurring, significant dramatic actors in a manner that undermines the Squadron System (Section 3). Members who want to write multiple ships and crews must wait until attaining the fleet rank of Captain.
| |
| #Events involving registry ships ''prior to'' 2399 may be referenced in circumstances such as character service records and backstory. This restriction changes at 2399 as this is when the current fleet canon went live; members should not be dictating fleet or member canon after this outside of their own characters and Command.
| |
| #Fleet canon about a ship is defined by the Intelligence Office or any member who holds that Command. Subsequent members who command a registry ship must adhere to that fleet canon and not retcon or change it without permission from the Intelligence Officer.
| |
| ##Fleet canon established by prior commanders is limited to the names of captains and crewmembers and the dates of their assignments, and major points of the ship's activities, such as participation in a fleet-wide storyline or where and when the ship was commissioned. Members are not beholden to retain more minor details of a ship's mission history, design, or configuration. Any pre-2399 history of a command established by a member is member canon and thus may be rewritten or disregarded by any new commander.
| |
| ##The history of registry ships is maintained on their wiki article. Members are free to depict this history as they wish, either retaining original text or rewriting. There is no obligation to mention events or history prior to their command. The only requirement is to retain a list of previous commanders, ''with links to their BFMS Commands'', as seen [https://wiki.bravofleet.com/index.php/USS_Rhyndacus#Notable_Crew here].
| |
| #Ships are assigned to a member's dossier when they are created as Commands on BFMS. A member must create an application for the Command that the Intel Office processes. The IO does not create Commands for members. Commands exist to house Missions, Stories, and crew rosters; they show the ship on the member's dossier, and ensure the registry displays what ships are available or unavailable. ''All'' ships in use require a Command, including RPGs and squadron ships.
| |
| ##Once a ship has been relinquished, the BFMS Command will be labelled as 'Archive' and exist on the member's dossier for archival purposes only. Members may edit the Command page or the roster, but they may not add further Missions or Stories.
| |
| #Members should not apply for Commands on BFMS until they are ready to acquire or change their Primary Command, or for a fiction/RPG proposal to be discussed with the Intelligence Officer/Operations Officer. Draft Commands or proposals self-identifying as WIPs will have their registry link removed or be deleted.
| |
| #Members may change their assigned Commands once every six months or after they are promoted, whichever comes first. This applies to ''all'' of a member's Commands; if only one ship in a squadron of two is changed, six months must elapse or a promotion must be earned before ''either'' ship can be changed.
| |
| ##If a member has not used their full squadron strength entitlement, they may request ships to fill it anytime. However, this resets the Command change cooldown. So long as a member ''can'' request additional ships, they may do so as often as they like, but they may not change those ships until six months have elapsed or a promotion has been earned.
| |
| ##Exceptions may be permitted at the discretion of the Intelligence Officer. This may apply in cases such as the release of new starship classes or other significant alterations to the command registry.
| |
| =2 - Primary Commands=
| |
| #Primary Commands are attached to a member's dossiers as their character's starship or auxiliary craft. They are the vessels assigned In Character to a member’s Task Force in the Fourth Fleet in {{Year}}.
| |
| #Members can write on their Primary Commands on their own or with others. Writing with others on a Primary Command does not require a proposal or activity commitment being sent to the Intelligence Office. Members ''may not'' use their Primary Command as an RPG; ie, they may not openly recruit for crew or create a separate website, and collaboration should be limited to invitation-only. RPGs which any member of the Fleet may apply to join must be accepted by the Bravo Fleet Operations Officer, and thus Primary Commands are unsuitable for this purpose.
| |
| #All Commands will be removed from a member's dossier upon transfer to the Reserves.
| |
| #When a member reaches the rank of Midshipman they may request a ship on the registry for use as their Primary Command. Ship classes available are unlocked upon reaching certain ranks.
| |
| #Members below the rank of Captain may only have one Primary Command. Requesting a new eligible Primary Command will result in the current registry ship being removed from the member's dossier and returned to the pool of available ships.
| |
| {| class="wikitable" style="margin:auto"
| |
| |+Ship classes by rank
| |
| |-
| |
| !Midshipman!!Lieutenant Commander!!Commander!!
| |
| |-
| |
| |[[California Class|California]]
| |
| |[[Aquarius Class|Aquarius]]
| |
| | colspan="2" |[[Akira Class|Akira]]
| |
| |-
| |
| | ||[[Centaur II Class|Centaur II]]|| colspan="2" |[[Defiant Class|Defiant]]
| |
| |-
| |
| |
| |
| |[[Challenger Class|Challenger]]
| |
| |[[Duderstadt Class|Duderstadt]]
| |
| |
| |
| |-
| |
| |
| |
| |[[Cheyenne Class|Cheyenne]]
| |
| | colspan="2" |[[Echelon Class|Echelon]]
| |
| |-
| |
| | ||[[Edison Class|Edison]]|| colspan="2" |[[Excelsior II Class|Excelsior II]]
| |
| |-
| |
| | ||[[Grissom Class|Grissom]]|| colspan="2" |[[Gagarin Class|Gagarin]]
| |
| |-
| |
| | ||[[New Orleans Class|New Orleans]]||[[Intrepid Class|Intrepid]]
| |
| |
| |
| |-
| |
| | ||[[Norway Class|Norway]]|| colspan="2" |[[Inquiry Class|Inquiry]]
| |
| |-
| |
| | ||[[Nova Class|Nova]]|| colspan="2" |[[Luna Class|Luna]]
| |
| |-
| |
| |
| |
| |[[Olympic Class|Olympic]]
| |
| | colspan="2" |[[Manticore Class|Manticore]]
| |
| |-
| |
| | ||[[Parliament Class|Parliament]]|| colspan="2" |[[Nebula Class|Nebula]]
| |
| |-
| |
| |
| |
| |[[Phoenix Class|Phoenix]]
| |
| | colspan="2" |[[Pathfinder Class|Pathfinder]]
| |
| |-
| |
| | ||[[Raven Class|Raven]]|| colspan="2" |[[Prometheus Class|Prometheus]]
| |
| |-
| |
| | ||[[Rhode Island Class|Rhode Island]]|| colspan="2" |[[Sutherland Class|Sutherland]]
| |
| |-
| |
| |
| |
| |[[Reliant Class|Reliant]]
| |
| | colspan="2" |
| |
| |-
| |
| | ||[[Saber Class|Saber]]|| colspan="2" |
| |
| |-
| |
| | ||[[Springfield Class|Springfield]]|| colspan="2" |
| |
| |-
| |
| |
| |
| |[[Steamrunner Class|Steamrunner]]
| |
| |
| |
| |
| |
| |}
| |
| =3 - Squadrons=
| |
|
| |
|
| #The Squadron system allows members holding the dossier rank of Captain and above greater flexibility in their Command choices. Where Commanders and below may pick a single Primary Command from a list, Captains are entitled to a certain level of ‘Squadron Strength’ in their Command selection. This gives them options like choosing between a single, larger ship or multiple smaller ones.
| | The ''Atascadero'' was laid down in 2381 at the Avalon Fleet Yards as part of the fourth batch of the class ordered by Starfleet and was expected to be completed by the end of 2384. However, with the impending [[ma:Romulan_sun#The_Romulan_supernova|Romulan Supernova]], all of Starfleet's resources were diverted to constructing the largest evacuation fleet in history, delaying production on lower-priority projects. The [[ma:Attack_on_Mars|attack on the Utopia Planitia Shipyard]] caused further delays in starship production and the ''Atascadero'' was finally launched in December 2386, almost two years behind the initial schedule. |
| #If a member holds multiple Commands under the Squadrons system, these ships are all subject to the same usage requirements as outlined under Primary Commands above. They may not be used as RPGs, and IC are starships assigned to the member’s Task Force.
| |
| ##All ships must have their own Command on BFMS. This is solely to ensure the registry accurately reflects what ships are in use and dossiers show all of a member's ships. Members are free, however, to house Stories and Missions involving the ship and crew on any of their squadron BFMS Commands. | |
| ##Members with multiple ships should designate one as their Primary Command on BFMS. This is solely for display and organisational purposes, and has no other or IC significance. The Primary Command must be a Squadron Commands, and may not be an RPG or Fiction.
| |
| ##Members have some freedom on how to IC depict these multiple ships. They may be entirely unaffiliated, all falling directly under their Task Force’s IC chain of command, with the member using them to tell totally different stories.
| |
| ##Members may use all/some of them to form an IC-only unit within their Task Force, referred to as a squadron. This typically takes its title from the squadron’s ‘lead ship’ or starbase (for example, a squadron led by the USS Endeavour would be called ‘Endeavour Squadron’). This ensures all squadrons have a unique IC name. Members may not call these IC units ‘task groups’, to avoid confusion with the OOC unit.
| |
| ##Members may create an officer in command of this squadron, who may or may not also be the commanding officer of one of these starships/starbase, and who falls IC under the chain of command of the member’s Task Force. All Canon Policy rank restrictions remain.
| |
| #The Squadron Strength to which a member is entitled is dependent on their dossier rank.
| |
| {| class="wikitable"
| |
| |+'''Squadron Strength by Dossier Rank'''
| |
| !Captain
| |
| !Fleet Captain
| |
| !Commodore
| |
| !Rear Admiral
| |
| !Vice Admiral
| |
| !Admiral
| |
| !Fleet Admiral
| |
| |-
| |
| |3
| |
| |4
| |
| |6
| |
| |7
| |
| |8
| |
| |9
| |
| |10
| |
| |}
| |
|
| |
|
| == 3.1 - Starship Strength ==
| | One advantage of the delayed production schedule was allowing the most up-to-date subsystems to be included in the ship. Some of these advanced subsystems include an Advanced Environmental System, specifically in the VIP quarters, which allows the ship to accommodate nearly any form of sentient life. Also included was an Advanced Communications Suite, which allows the ship to send encrypted and secured holographic communications through the subspace network. Finally, numerous small incremental improvements have been incorporated into all Starfleet ships, differentiating the newest ships of the class from those built nearly 20 years prior. |
|
| |
|
| # Ship classes are allocated a certain level of Strength depending on their size, power, modernity, and so forth.
| | === VIP FACILITIES === |
| # Members may select any number of ships as their Commands under the Squadrons system, so long as the total Strength does not exceed their rank entitlement.
| | As one of the ''California''-class ships designated primarily for diplomatic and administrative support missions, the ''Atascadero'' includes three large VIP suites for visiting dignitaries, diplomats, and high-ranked Federation officials. The suites include not only an expansive VIP cabin, but also an anteroom and a half-dozen smaller adjoining cabins suitable for attendants, aides, or relatives of the VIP. These adjoining cabins are smaller but just as finely appointed as the larger VIP cabin. Each suite is a self-contained habitat, including dedicated environmental and communications systems, as well as the ability to quarantine from the rest of the ship if necessary out of medical or security concerns. |
| # Ship classes by rank (As above in 2 - Primary Commands) may not directly correlate with a starship's squadron strength. This is intentional, reflecting how some ships may be more or less popular when they are a member's only command, but valued differently when part of a larger squadron.
| |
|
| |
|
| {| class="wikitable" style="margin:auto"
| | Also included among the VIP facilities is a holodeck reserved exclusively as a meeting space for VIP's. This holodeck can produce any environment that is appropriate for any species in order to provide an environment which would be conducive to peaceful and productive negotiations. As with the VIP suites, this holodeck has dedicated environmental and communications systems, as well as enhanced security features which allow confidential negotiations to take place without fear of eavesdropping. |
| |+Ship classes by rank
| |
| |-
| |
| !1!!2!! colspan="2" |3
| |
| !4
| |
| |-
| |
| |Small Civilian Ship
| |
| |[[Alita Class|Alita]]
| |
| |
| |
| |[[Constitution III Class|Constitution III]]
| |
| |[[Odyssey Class|Odyssey]]
| |
| |-
| |
| |[[Aquarius Class|Aquarius]]|| colspan="2" |[[Akira Class|Akira]]||[[Galaxy Class|Galaxy]]
| |
| |
| |
| |-
| |
| |[[California Class|California]]|| colspan="2" |[[Duderstadt Class|Duderstadt]]||[[Obena Class|Obena]]
| |
| |
| |
| |-
| |
| |[[Centaur II Class|Centaur II]]
| |
| |[[Echelon Class|Echelon]]
| |
| |
| |
| |[[Ross Class|Ross]]
| |
| |
| |
| |-
| |
| |[[Challenger Class|Challenger]]
| |
| | colspan="2" |[[Excelsior II Class|Excelsior II]]
| |
| |[[Sagan Class|Sagan]]
| |
| |
| |
| |-
| |
| |[[Cheyenne Class|Cheyenne]]|| colspan="2" |[[Gagarin Class|Gagarin]]||[[Sovereign Class|Sovereign]]
| |
| |
| |
| |-
| |
| |[[Defiant Class|Defiant]]
| |
| | colspan="2" |[[Inquiry Class|Inquiry]]
| |
| |[[Vesta Class|Vesta]]
| |
| |
| |
| |-
| |
| |[[Edison Class|Edison]]|| colspan="2" |[[Luna Class|Luna]]||
| |
| |
| |
| |-
| |
| |[[Grissom Class|Grissom]]|| colspan="2" |[[Manticore Class|Manticore]]||
| |
| |
| |
| |-
| |
| |[[Intrepid Class|Intrepid]]
| |
| | colspan="2" |[[Nebula Class|Nebula]]
| |
| |
| |
| |
| |
| |-
| |
| |[[New Orleans Class|New Orleans]]|| colspan="2" |[[Pathfinder Class|Pathfinder]]||
| |
| |
| |
| |-
| |
| |[[Norway Class|Norway]]|| colspan="2" |[[Prometheus Class|Prometheus]]||
| |
| |
| |
| |-
| |
| |[[Nova Class|Nova]]||[[Sutherland Class|Sutherland]]
| |
| | ||
| |
| |
| |
| |-
| |
| |[[Olympic Class|Olympic]]||
| |
| | ||
| |
| |
| |
| |-
| |
| |[[Parliament Class|Parliament]]|| colspan="2" | ||
| |
| |
| |
| |-
| |
| |[[Phoenix Class|Phoenix]]||
| |
| | ||
| |
| |
| |
| |-
| |
| |[[Raven Class|Raven]]||
| |
| |-
| |
| |[[Rhode Island Class|Rhode Island]]
| |
| |
| |
| |-
| |
| |[[Reliant Class|Reliant]]
| |
| |
| |
| |-
| |
| |[[Saber Class|Saber]]||
| |
| |-
| |
| |[[Springfield Class|Springfield]]||
| |
| |-
| |
| |[[Steamrunner Class|Steamrunner]]
| |
| |
| |
| |}
| |
| #For example, upon reaching the rank of Captain a member has a Squadron Strength entitlement of 3. If they already have a Commander-level ship, they are only using 2 of their Squadron Level. They may ‘upgrade’ as they did upon reaching the rank of Commander, returning their current ship to the registry and choosing a single new Command with a Strength of 3. If they keep their ship with its Strength of 2, they may choose to add to their dossier another ship with a Strength of 1.
| |
| ##Members are under no obligation to use their total Squadron Strength. These Commands are a reflection of the hard work of members, however, and may be chosen for storytelling opportunities or simple prestige.
| |
| #‘Small Civilian Ship’ is a catch-all term for non-Starfleet civilian vessels members may wish to use for different kinds of storytelling. It refers to ships of, for example, the [[Kaplan F17 class]] or the [[Groumall class]], usually freighters, that are not affiliated IC with Starfleet and may be used for trading, prospecting, exploration, or other adventures. Acquiring a ship like this is subject to a successful Fiction Proposal, and so they are not listed as available on the registry but created as required by the Intelligence Office.
| |
| #The Intelligence Office may make adjustments to ship class Strengths to account for balance as the system and canon evolve. No member will have an asset removed because of a rebalance, but they would only be grandfathered in until they wanted to change their squadron, at which point the new strength values would be used.
| |
|
| |
|
| == 3.2 - Starbase Strength == | | === DIPLOMATIC STAFF === |
| | While all Starfleet Captains are authorized to negotiate on behalf of the Federation, as the ''Atascadero'' often serves as a diplomatic transport and meeting place, Starfleet has seen fit to assign officers to the ship who specialize in diplomacy. |
|
| |
|
| # Starbases as Commands work the same as starships under the Squadron system, but are subject to different requirements. They represent starbases assigned In Character to the member’s Task Force in the Fourth Fleet in {{year}}.
| | - Diplomatic Attache: <!--Please do not delete the Notable crew section. It is used by the Intel Office for command history tracking.--> |
| # Members do not have to choose between a starbase or starship under the Squadron system. They are only restricted by their rank’s total Squadron Strength.
| |
| # Registry Starbases are created by the Intelligence Office, and will have their own wiki article explaining the location and setting material relevant to that starbase that has been ratified by the Intelligence Office. This is Fleet Canon that cannot be altered without permission of the Intelligence Office, even by the member to whom the starbase registry is attached. As such, members should heavily consider their choice, as a Starbase Command is under more restrictions and requirements from the Intelligence Office.
| |
| ## Members interested in creating a station command should consult directly with the Intelligence Office if one of the concepts on the wiki isn't suitable for their idea.
| |
| # Because stations impact shared canon more directly than starships, members will be unable to trade in a station for one year after acquiring it.
| |
|
| |
|
| {| class="wikitable" style="margin:auto"
| | ===Notable Crew=== |
| |+Starbase classes by Strength
| | ====Commanding Officers==== |
| |-
| | *[https://bravofleet.com/command/100548 2401 - Present] : [[bfms char:76992|Captain Jonathan Jackson]] |
| !2!!3!!4
| |
| |-
| |
| |[[Jupiter Class|Jupiter]]||[[Anchorage Class|Anchorage]]||[[Canopus Class|Canopus]]
| |
| |-
| |
| |[[K Class|K-Type]]||[[Copernicus Class|Copernicus]]||[[Unity Class|Unity]]
| |
| |-
| |
| |[[Regula Class|Regula]]||[[Narendra Class|Narendra]]||
| |
| |-
| |
| |[[Vision Class|Vision]]||[[Presidium Class|Presidium]]||
| |
| |-
| |
| | ||[[Watchtower Class|Watchtower]]||
| |
| |}
| |
|
| |
|
| == 3.3 - Attached Ships ==
| | {{clear}} |
| | |
| # Certain commands, like starbases, have an attached ship, which has its own registry entry but has an effective Strength of 0. Whether or not an attached ship is selected does not affect a member’s Squadron Strength.
| |
| # Most attached ships are assigned to starbases. Upon requesting a starbase, the member should identify to the Intelligence Office an appropriate choice of ship from the registry. That ship will then be removed from the public pool. It will not be given a BFMS Command, but should be written about as part of the starbase’s Command.
| |
| # The ''Odyssey''-class always has an ''Aquarius''-class ship attached. Unlike with starbases, the ''Aquarius''-class’s name is predetermined and cannot be changed. Details about an ''Odyssey’s'' ''Aquarius''-class will be listed on the ship’s wiki page.
| |
| # A strength 1 starship is attached to every station command in order to ensure that members have the ability to interact with fleet events set in other areas. This starship is assigned to the station directly to support it, as the ''Defiant'' was to DS9. This does not add to or subtract from the strength of a member's squadron, i.e. you could not use additional squadron strength to attach a strength 2 starship to your station.
| |
| # Members may choose to depict any of their other ships as attached to or operating out of the starbase.
| |
| | |
| == 3.4 - Requesting Squadron Ships ==
| |
| | |
| # Members must use BFMS to request any Commands under the Squadron system, in the same manner as Command requests at the ranks of Lieutenant Commander or Commander.
| |
| # BFMS requests for new Commands under the Squadron system must use the ‘Lore Office Proposal’ window to clearly communicate their allocation of their Squadron Level. This must include what ships, if any, are being returned to the registry.
| |
| ## If a new Captain requests a Command with a Strength of 3 with no further detail, the Intelligence Office will assume they are returning their current ship to the registry, just as with previous upgrades, and process accordingly.
| |
| ## If a Member wishes to retain their current Command and add another, they may request the new ship under BFMS and say so in the Proposal window. A simple message, such as ‘I am keeping the USS Lollipop (Strength 2), and adding this one (Strength 1) for a total Squadron Strength of 3’ will suffice.
| |
| ## If a Member wishes to return any of their ships to the registry, they must say so. Any requests for additional Commands that does not include a registry return and would bring a member over their Squadron Strength will be deleted. A simple message, such as ‘I am returning the USS Lollipop (Strength 2) and adding this one (Strength 3) for a total Squadron Strength of 3’ will suffice.
| |
| # If the Intelligence Office receives competing requests for the same starship, requests for a primary command from Lieutenant Commanders or Commanders will be prioritised, or upgrades to a single Strength 3 starship for new Captains. After that, ships will be allocated on a first-come, first-served basis.
| |
| =4 - Fictions=
| |
| #Stories about alternative settings such as non-Starfleet ships or historic eras are called 'Fictions'. Like primary or squadron commands and RPGs, they have their own BFMS Command page and are held to the same standards in content and canon compliancy.
| |
| #Fictions may only be written by one individual member. Stories with multiple writers count as role-playing games, which fall under the purview of the Operations Department.
| |
| #A member who has reached the rank of Commander may submit a fiction proposal to the Intelligence Office. This is not necessary for fiction based on their Primary Command.
| |
| #The proposal should explain the premise of the story, a loose estimation of expected length, and what it contributes to Bravo Fleet canon, present or historic. It should include a broad activity commitment, such as '1 Story posted per month.' This is not a binding agreement, but helps the Intelligence Office identify inactive Fictions.
| |
| #Starfleet ships in the year {{year}} are not an appropriate setting for Fictions. Members should use their Primary or Squadron Commands for these.
| |
| # Fictions do not draw from ships in the Bravo Fleet Registry, and so should discuss their ship, station, or concept needs with the Intelligence Office so an appropriate entry can be created.
| |
| #Fictions not set in {{Year}} should ''not'' draw from ships in the Bravo Fleet Registry. Members are subject to the same rank-based restrictions of classes (for example, a Commander writing a fiction set in 2375 still cannot request a Sovereign-class), but of course can request era-appropriate ship classes not listed in the registry.
| |
| # A new fiction will have its own Command on BFMS, assigned to the member. This Command is for use solely within the bounds of the accepted fiction proposal, and must not be used as a Primary Command.
| |
| # Bravo Fleet fiction supports and enriches Bravo Fleet Canon, present and historic. Proposals from non-Trek settings will be rejected. Proposals from alternate universes of Star Trek will need to demonstrate their relevance to Bravo Fleet Canon content, themes, or characters to be accepted.
| |
