User:Beckett/Sandbox/Command Policy

From Bravo Fleet
< User:Beckett‎ | Sandbox
Revision as of 17:02, 16 December 2022 by Beckett (talk | contribs) (Created page with "= Section 1 - Registry Definition = # The registry lists all starships, starbases, and other entities available to Bravo Fleet for use as Commands or Games. # The registry’...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Section 1 - Registry Definition

  1. The registry lists all starships, starbases, and other entities available to Bravo Fleet for use as Commands or Games.
  2. 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.
  3. The registry represents the In Character starships and starbases available to the Fourth Fleet in 2401, 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. Events involving registry ships prior to 2399 may be referenced in circumstances such as character service records and backstory. 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. This restriction begins at 2399 as this is when the current fleet canon went live; members should not be dictating fleet or member canon for this period outside of their own characters and Command.
  • 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.

Section 5.2 - Primary Commands (Starships and Auxiliary Craft)

  • 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 2401.
  • Members can write on their Primary Command 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.
  • Members 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. This includes any member 'upgrading' from a Raven-class to a starship command at Lieutenant Commander.
  • Primary 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.
Ship classes by rank
Midshipman Lieutenant Commander Commander Captain
Raven Aquarius Akira Century
California Defiant Galaxy
Challenger Excelsior II Inquiry
Cheyenne Gagarin Manticore
Diligent Intrepid Obena
Grissom Luna Odyssey
New Orleans Nebula Prometheus
Norway Olympic Ross
Nova Pathfinder Sovereign
Parliament Rhode Island Typhon
Reliant Sutherland Vesta
Saber
Springfield
Steamrunner

Section 5.3 - Primary Commands (Starbases)

  • Starbases as an Primary Command work the same as starships, but are subject to different requirements. They represent starbases assigned In Character to the member’s Task Force in the Fourth Fleet in 2401.
  • When a member reaches the rank of Commander they may request a starbase from the registry for use as their Primary Command. This is instead of a starship, not in addition to.
  • 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.
  • Starbase classes available are restricted by rank.
Starbase classes by rank
Commander Captain Fleet Captain Attached ships (Available at Captain)
Jupiter Anchorage Canopus Aquarius
K-Type Copernicus Unity Defiant
Regula Presidium Diligent
Vision Watchtower Nova
Rhode Island
Saber