Bravo Fleet By-Laws

BY-LAW #1.1 – TASK FORCES

  1. Per Article IV, Section 2 of the Constitution, Bravo Fleet shall have the following Task Forces:
    1. Task Force 9 operating in the Gamma Quadrant.
    2. Task Force 38 operating in the Delta Quadrant.
    3. Task Force 47 operating in the Gavarian Corridor.
    4. Task Force 72 operating on the Breen border.
    5. Task Force 93 operating along the Romulan Neutral Zone.
    6. Task Force 99 operating as a special Task Force.
      1. Star Trek exists not only as a single time period series, but rather as a wide ranging franchise encompassing multiple time periods and realities. While the rest of the fleet operates within the modern time period about a decade after the conclusion of the Dominion War (presently 13 years after), there are other time periods represented throughout the various TV series and movies, which some members aspire to simulate in. Task Force 99 is designated as the location to represent each of these various divisions in time as separate sub-groups, acting in complete independence of each other, In Character, sharing no events in common with each other or the rest of the main fleet. Due to these special relationships, Task Force 99 shall be exempt from some of the rules that regulate the fleet as a whole.
      2. Task Force 99 is not subject to the rules or limitations regarding the number of sub-divisions, commonly known by the rest of the fleet as “Task Groups”, or the on the maximum number of simulations which may exist within the Task Force.
      3. In order to assist the TFCO and/or the Fleet to help highlight the differences between each of the individual time divisions within the Star Trek franchise, the TFCO may open and close any sub-division with approval of the Bravo Fleet Executive Officer.
      4. Task Group structures may be organized by genre, universe, game type, or other form of organization as deemed appropriate per subsection 2.
      5. Upon reaching 5 simulations which have reached “Active” status, the Task Force Commanding Officer may appoint a Command Adjunct for that period/genre to assist the TFCO with the advancement of canon and organization for the group.
      6. Task Force 99 may add simms at will. As ships within Task Force 99 do not impact the canon of the main Bravo Fleet timeline, they are not tracked in the main fleet registry.

BY-LAW #1.2 – MEMBER & STAFF DUTIES

SECTION 1 – PLAYERS

  1. All players shall post to any simm in which they are a member at least once per week unless they are on a leave of absence or the simm CO has made other arrangements.
  2. A player in BF is allowed to be an active member of no more than 6 simms across BF. Anyone who posts to the simm at least once every 3 weeks is considered an active member of that simm and should be reported in the CO’s monthly report. At the discretion of the CO, a player may control or ‘own’ secondary characters or NPCs on the simm but the player must designate which is his primary character for purposes of promotions, awards, and simm reports.
  3. All players have the responsibility to follow the chain of command; questions surrounding the interpretation of rules or any proposals to introduce new aspects to BF canon should be addressed from which ever level in the chain of command a player occupies to the next level and through that following level to the next level and so forth.
  4. All players have the responsibility of creating original characters which are not established Star Trek characters or relatives thereof, nor already created Bravo Fleet characters or relatives thereof without the permission of the creator of the Bravo Fleet character.
  5. All players will refrain from the unsolicited recruitment of other Bravo Fleet members to play on their BF simm or any simm outside of BF.
  6. All players will recognize the restraints of Star Trek and BF canon and will not create unusual and atypical classes of ships, types of weapons and alien creatures without the approval of the BFA.
  7. All players who wish to resign their character or position will do so by informing the next person in the chain of command, they will not announce their resignation by posting to a public forum such as the simm mailing list, the BF COs list, the BF Forums and so on.
  8. All players will try to resolve any disputes with other players in a respectful manner and will try to resolve them first with the other player and their with the next person in the chain of command before taking action with the committee known as the Judge Advocate General.
  9. All players will refrain from starting petitions or spamming mailing lists or other means of communication in order to advance their position on a particular issue. In order to make things manageable for those players who volunteer their time to help run the fleet, all concerns and proposals should be directed through the chain of command.

SECTION 2 – SIMM CO’S

  1. A Simm CO shall be required to complete and pass command academy and develop a website for his or her simm before they can be declared ‘active’ Commanding Officers.
  2. Simm COs shall not permanently damage, destroy, change the class of or provide a change in the specifications of the class, as defined by Bravo Fleet, of their in character ship or starbase without the approval of their TFCO.
  3. Simm COs shall not destroy or otherwise do anything to effect any base, ship or other simm that currently exists in Bravo Fleet, including mothballs.
  4. Simm COs shall have the final responsibility for recruiting members of their simm and shall do so within the restrictions set by Bravo Fleet.
  5. Simm COs shall direct any applications to their simm or existing players on their simm which do not attain quality posting standards to an Academy established for training purposes under this constitution or remove them from their simm.
  6. No CO shall command more than one simulation in each part (defined below) of Bravo Fleet.
    1. Notwithstanding the above, a CO may command a non-Starfleet simulation in addition to their Starfleet command, or vice versa, in each part (defined below) of Bravo Fleet. The following condition(s) must be met:
      1. Twelve months of active command experience.
      2. Active growth and steady mission progression in current (Starfleet or non-Starfleet) simulation.
    2. Bravo Fleet main and each affiliate are defined as distinct “parts” of Bravo Fleet.
  7. No player shall command more than three simulations in the whole of Bravo Fleet including its affiliates.
  8. Simm COs shall file a monthly report to their TFCO, in the form prescribed by their TFCO, no later than the 4th of each month.
  9. A Simm CO that resigns from his or her position(s) shall be barred from taking a new command in BF for 90 days in order to allow for a “cooling off” period during which the player can re-evaluate his or her ability to command. Should a Simm CO resign in a public area, as is prohibited by the constitution, an additional 6 months shall be added to the cooling off period. If the CO in question has two commands at that time and retains his/her BF main command, the second existing command is not effected, however the restrictions would apply to any attempts to obtain a new command.
    1. Notwithstanding the above, a Simm CO may rescind his or her resignation within 24 hours and face no penalty.

BY-LAW #2.1 – PLAYABLE SPECIES

Bravo Fleet aims to create a fun environment for Star Trek fans to role play with as much freedom as possible. To that end, we must create some guidelines which, though meant to allow as much flexibility as possible, provide some security to our players as to what they can expect and what they will not encounter in our Star Trek game. They are as follows:

  1. For the purposes of clarity, the following terms are defined as follows:
    1. “omnipotent species” means a species or character who is actually or virtually immortal; for example members of the Q Continuum or the Organians.
    2. “crossover species” mean a direct copy of a species that exists in a non-Star Trek universe, for instance vampires from Buffy the Vampire Slayer or Jedi Knights from Star Wars.
  2. Bravo Fleet does not permit the playing of omnipotent species shown in Star Trek, other fiction or unique omnipotent creations.
  3. Bravo Fleet does not permit the playing of crossover species. While Bravo Fleet encourages creativity and its COs may allow species from Star Trek novels and non-canon works as well as player created species, direct crossovers are not permitted.
  4. Under the constitution, Bravo Fleet simulation COs “have the right to adminster their games as they see fit (within the rules)” and therefore, outside of the restictions above may allow any other Trek canon or player created species. However, Bravo Fleet encourages its COs to exercise caution in accepting characters of species which may not be plausible (unusual interspecies hybrids, overly powerful “superhero”-type characters, etc) and suggests conference with the CO’s TFCO or other BFA members for a second opinion.
  5. Notwithstanding this by-law, any characters of species imported from a non-Trek fictional universe, and barred from play in section 2 of this by-law, that are active on the date of this by-law taking effect are grandfathered in and may continue to be played on any simm whose CO permits them.
  6. Nothwithstanding this by-law or the constitution, any characters of an omnipotent nature, barred from play in section 1, or any established characters from the Star Trek universe, barred from play in III.1.4 of the Constitution, are allowed to be used from time-to-time as non-player characters (NPCs) for a particular story line.

BY-LAW #2.2 – FICTIONS

Section 1: Definition

  1. A fiction simulation is a TFCO-authorized writing group that is made with the express purpose of creating canon material for Bravo Fleet and their task forces, and tying in with the storyline of the task force and Bravo Fleet.
  2. There are two different non-simm fiction types that shall be primarily used within a task force:
    1. Permanent fiction simulations, made up of task force senior staff and guest writers. Membership on a permanent fiction simulation does not count towards a player’s total character count in Bravo Fleet.
    2. Non-permanent fiction simulations, made up of up to 3 non-staff members of the task force. Membership on a non-permanent fiction simulation counts towards a player’s total character count in Bravo Fleet.
      1. Any fiction simulation that wishes to add more than 3 members will be reclassified as a full simulation.
  3. Notwithstanding the above, a fiction simulation may be created by the Bravo Fleet Admiralty via a simple majority that is independent from any task force to write and contribute to Bravo Fleet canon directly.

Section 2: Requirements

  1. All non-permanent fiction group managers shall be defined as a Simm CO in the Bravo Fleet Constitution, with all the rights under Article III, Sections 1 and 2 applicable except for the following:
    1. All fiction simulations must have written at least two posts every calendar month, involving all the writers of the fiction, unless arranged otherwise with their relevant TFCO.
    2. All writers on a fiction simulation may create more than one character on their fiction simulation, while membership on a non-permanent fiction simulation only counts as one active membership as defined by the Constitution.
    3. As per Article IV.1.5 of the Constitution, the minimum crew requirements do not apply to a fiction.
  2. In order to be approved as a fiction simulation, the following requirements must be met:
    1. The proposer must have served as an active simm commanding officer before.
    2. At least one post pre-written and at least three character bios completed
    3. A detailed outline on the direction that the fiction simulation is to go
    4. Approval from the Task Force Commanding Officer and the Bravo Fleet Executive Officer.
  3. Task forces may not authorize more than four fiction simulations in their task force – one permanent fiction simulation and three non-permanent fiction simulations.
  4. Any fiction simulation developing Bravo Fleet overall canon must be written with a 13+ rating and be approved by the Bravo Fleet Admiralty.
  5. Any fiction simulation developing task force canon is subject to approval and restrictions as set by the relevant TFCO and task force staff.
  6. Fiction simulations must all have publicly accessible archives, unless written permission has been obtained from the relevant TFCO and the written permission is publicly displayed on the fiction simulation’s website.
  7. Fiction simulations that are writing for above a 13+ rating must have appropriate warnings placed on their website and posting group.
  8. Non-permanent simulations are to be chartered for a period of one out of character calendar year, and must be renewed every year by the relevant TFCO and the Bravo Fleet Executive Officer.

BY-LAW #2.3 – SHIP & STATION COMMAND REQUIREMENTS

Section 1: Approved commanding classes and qualifications for command

  1. A command applicant shall be regarded as qualified for command if they have at least four verifiable months of active player experience on an active Bravo Fleet simm or an equivalent elsewhere.
  2. At the discretion of the Task Force Commanding Officer, a command applicant may apply for the following active classes within Bravo Fleet’s main canon timeline:
    1. Starfleet Ships: Akira, Ares, Argonaut, Ascension, Atlantia, Century, Concorde, Defiant, Diligent, Excalibur, Galaxy, Insignia, Intrepid, Kelvin, Luna, Nebula, Nova, Norway, Olympic, Onimaru, Prometheus, Rhode Island, Ronin, Saber, Sovereign, Steamrunner, Wallace
    2. Starfleet Bases: Aurora, Fleet Yards, Immense, Jupiter, Nor, Planetary Base, Presidium, Regulus, Spacedock
    3. Non-Starfleet Ships/Bases: B’rel, Ch’Haven, Civilian, D’deridex, D’Kora, D’renet, Galor, Hideki, Keldon, Khellian, K’Vort, Laehval, Negh’Var, Preax, Shrike, Valdore, Vor’cha
  3. Although not overly encouraged, at the discretion of the Task Force Commanding Officer, a command applicant may also apply for the following retired classes within Bravo Fleet’s main canon timeline:
    1. Retired Starships: Akula, Ambassador, Centaur, Challenger, Cheyenne, Constellation, Constitution, Excelsior, Explorer, Freedom, Miranda, New Orleans, Niagara, Oberth, Sentinel, Springfield, Sydney
    2. Retired Bases: K class, Regula
    3. Retired Non-Starfleet Ships/Bases: K’T’Inga, Ventarix

Section 2: Additional command regulations

  1. A commanding officer seeking to change ship classes must:
    1. meet the requirements set forth by the graded command groups.
    2. have at least six months active command service on their current class.
  2. A registry number shall not be granted with an appended suffix (such as NCC-1701-A)

BY-LAW #2.4 – PROMOTION GUIDELINES

Bravo Fleet enjoys celebrating player accomplishments, and one of the ways task force staff may express this is through IC promotions of their staff, though this is not the only way that the staff is able to celebrate accomplishments.

Section 1: Player Promotions

  1. A commanding officer, as outlined in Article III, Section 2 of the Bravo Fleet Constitution, is free to determine the starting rank for the players on their simm.
  2. COs are asked to take all factors in to make an accurate determination of whether the player’s character deserves the rank that is requested by the player. However, this determination is completely up to the CO.
  3. COs are free to promote their players in-character up to and including:
    1. Enlisted ranks: Master Chief Petty Officer, Sergeant Major or equivalent alien rank
    2. Officer ranks: Lieutenant Commander, Major, or equivalent alien rank
  4. Under extraordinary circumstances, the TFCO can authorize promotions above the ranks listed above for players, as follows:
    1. Enlisted ranks: up to Task Force Master Chief Petty Officer, Task Force Sergeant Major or equivalent alien rank
    2. Officer ranks: up to Captain, Colonel, or equivalent alien rank
  5. Under extraordinary circumstances, the BFCO can authorize promotions above the ranks listed above for players, as follows:
    1. Enlisted ranks: up to Bravo Fleet Master Chief Petty Officer, Bravo Fleet Sergeant Major or equivalent alien rank
    2. Officer ranks: up to Rear Admiral, Major General, or equivalent alien rank
  6. Though these ranks are attainable by a player, we do encourage COs to use means other than promotions to celebrate player accomplishments and good work, as in-character stories can be affected adversely by this.
    1. Alternatives can include player awards, assistance in creating and maintaining missions. COs are not limited to these options and there may be more that can be done with the player.
  7. Notwithstanding the above, a CO should never request that a player be promoted above the equivalent rank that they themselves hold, or equal to the CO’s rank if the CO holds a flag officer rank.

Section 2: CO Promotions

  1. Commanding officer ranks are more of an out of character formality than they are an in-character effect, as they can affect Bravo Fleet structures.
  2. COs can choose to let their rank affect their in-character rank, but are encouraged to make sure in-character requirements are completed before promoting themselves. Recommended guidelines are listed in each step of this section of the by-law.
  3. A Commanding Officer should start out as the rank of Lieutenant Commander, Major, or an alien equivalent while attending CO Academy and recruiting members for first time activity.
    1. Special circumstances, such as a CO whom has previously had a tenure as a command, may be exempt from the CO Academy requirements; however for purposes of recruiting and fairness, they will be asked to follow this rule.
    2. While the CO is awaiting players, the CO may use the IC rank of Commander.
  4. A CO can be promoted by the TFCO to Commander, Lt. Colonel or alien equivalent by the TFCO when the CO meets the following requirements:
    1. Completes the CO Academy
    2. Is declared an active simm per Bravo Fleet standards
  5. COs can be promoted to Captain, Colonel or alien equivalent by the TFCO when the following conditions are met:
    1. Completed at least six months of active command experience
    2. Has shown active growth in their simm and steady mission progression
    3. Has been active in task force discussions
    4. This rank can be applied to an IC setting at the place where it may convenience the storyline the best for the simm.
    5. Notwithstanding the above, a staff member can be automatically promoted to Captain or equivalent on their appointment to an Ops department head position.
  6. COs can be promoted to Commodore, Brigadier General or alien equivalent by the TFCO when the following conditions are met:
    1. Completed at least twelve months of active command experience or comparable staff service
    2. Completed at least six months of consecutive active TFXO or above experience
    3. Has shown active growth in their simm and steady mission progression
    4. Has been an active participant in task force discussions
    5. Has been active in the duties assigned to them by the TFCO
    6. Notwithstanding the above, a CO can be automatically promoted to Commodore or equivalent on their appointment to the position of TFXO
    7. Operations department heads can be promoted to this rank grade by the Operations Commanding Officer upon comparable Operations service to the above
  7. COs can be promoted to Rear Admiral, Major General or alien equivalent by the Bravo Fleet Executive Officer upon recommendation by the TFCO when the following conditions are met:
    1. Completed at least twenty-four months of active command experience or comparable staff service
    2. Completed at least six months of consecutive active TFXO or above experience
    3. Has shown active growth in their simm and steady mission progression
    4. Has been an active participant in task force discussions
    5. Notwithstanding the above, a CO can be automatically promoted to Rear Admiral or equivalent on their appointment to the position of TFCO, Bravo Fleet Executive Officer, or BF OPS.
    6. Operations department heads can be promoted to this rank grade by the Bravo Fleet Commanding Officer upon comparable Operations service to the above
  8. COs can be promoted to Vice Admiral, Lieutenant General or alien equivalent by the BFCO upon recommendation of the CO’s direct superior when the following conditions are met:
    1. Completed at least thirty months of active command experience or comparable staff service
    2. Completed at least nine months of consecutive active TFCO or above experience
    3. Has shown active growth in their simm and task force/division, and steady mission progression
    4. Has been an active participant in fleet discussions
    5. Notwithstanding the above, a CO can be automatically promoted to Vice Admiral or equivalent on their appointment to the position of BFXO.
    6. Operations department heads can be promoted to this rank grade by the Bravo Fleet Commanding Officer upon comparable Operations service to the above
  9. COs can be promoted to Admiral, General or alien equivalent by the BFCO when the following conditions are met:
    1. Completed at least thirty-six months of active command experience or comparable staff service
    2. Completed at least six months of consecutive active BFXO experience
    3. Has shown active growth in their simm and steady mission progression
    4. Has been an active chair of fleet discussions
    5. Notwithstanding the above, a CO can be automatically promoted to Admiral or equivalent on their appointment to the position of BFCO.
  10. COs can be promoted to Fleet Admiral, Marshal or alien equivalent by a 2/3rd vote of the BFA when the following conditions are met:
    1. Completed at least nine months of consecutive active BFCO experience
    2. Has shown active growth in their simm and steady mission progression
    3. Has been an active chair of fleet discussions
  11. Any CO holding a Flag level rank (Commodore grade or above) stepping down from or no longer holding a position within the Bravo Fleet command structure (defined herein as any Task Force or BFA position TFXO or above) shall be reduced in grade to the rank of Fleet Captain (or equivalent) and awarded the appropriate level Admiral Emeritus Award.
    1. The rank of Fleet Captain (or equivalent) shall not be attainable through any other means save those outlined above.
  12. No CO shall hold a rank above the theoretical maximum rank attainable in that position. Any CO holding a position within the Bravo Fleet command structure shall be granted either their highest earned rank or the rank maximum for that position as outlined above, whichever is lower.
    1. Any CO reduced in rank in this way shall be awarded the appropriate level Admiral Emeritus Award.
  13. For IC purposes, as there is little canon evidence of admiralty taking permanent, direct day to day command of a single starship, use of the rank of Commodore/Brigadier General/equivalent alien rank and above is discouraged in an IC simming environment where only one ship is routinely used.
  14. Notwithstanding points 2 and 13 above, a CO can elect to use any rank up to and including their OOC rank as their IC rank.
  15. Notwithstanding points 11 and 12, any CO who steps down from any position in the Bravo Fleet command structure after only three months or less of service in that position shall automatically be reduced to their pre-appointment rank.

BY-LAW #2.5 – EXTERNAL RESOURCES

Bravo Fleet may, from time to time, maintain and operate external resources (such as discussion forums, chat rooms, user-editted databases, etc) to supplement the fun environment it creates for its players. The administration of such resources shall be handled by specific administrative teams and one’s position within BF shall not guarantee a position within the external resources’ administration teams. Conversely, punishment – such as loss of moderation privileges and banning – within these external resources shall not necessarily reflect on a person’s standing in BF.

BY-LAW #2.6 – ATTACHED STARSHIPS

There is very little canon evidence to suggest that starbases ever have more than one starship permanently assigned to them. In order to encourage a level of realism that is more consistent with this, yet still allowing some flexibility, this by-law clarifies the restrictions surrounding attached starships.

  1. A base (Starbase or Planetary Base) commanding officer may choose any combination of attached vessels from the list below, provided the total value of these vessels does not exceed the points assigned to their Command Group (see By-law 3.2).
    1. Active Ship Classes:
      1. Six points: Akira, Argonaut, Luna
      2. Four points: Ares, Atlantia, Intrepid, Steamrunner
      3. Three points: Defiant, Diligent, Norway, Nova, Olympic, Rhode Island, Saber
      4. Two points: Wallace
    2. Mothballed Ship Classes:
      1. Five points: Ambassador, Excelsior, Explorer
      2. Four points: Akula, Cheyenne, New Orleans, Niagara, Freedom
      3. Three points: Springfield, Constellation, Constitution, Challenger, Centaur, Miranda
      4. Two points: Oberth, Sydney
    3. Alien Ship Classes (only attached to alien bases of the same species):
      1. Six points: Galor, Khellian, K’Vort
      2. Five points: Laehval, Shrike
      3. Three points: K’Tinga, Ventarix
      4. Two points: B’rel, Hideki, D’renet, Preax
  2. The command group of a base defines the number of allowed points:
    1. 5 points allowed for Group A Command and Group A Retired Command.
    2. 8 points allowed for Group B Command and Group C Command.
  3. All attached ships must be approved by the Bravo Fleet Executive Officer.
    1. Commanding officers may suggest a vessel name, class and registry choice for their proposed attached vessel(s).
    2. Once a commanding officer has made their selection, they may forward the selection to their Task Force Commanding Officer, who will forward it to the Bravo Fleet Executive Officer.
    3. Commanding officers are not required to make their selection immediately after acquiring a base.
  4. Any base commanding officer with attached starships exceeding the allowed total, or with classes not on the approved list at the time this by-law is implemented, may have their choices grandfathered, although they are encouraged to comply with this by-law.

BY-LAW #2.7 – BRAVO FLEET SIMULATION RATING GUIDELINES

NOTICE: With the exception of the provisions for the 18+ rating category, these ratings are merely guidelines. They are intended to protect under aged players of our fleet from any obscenities which may be contained in an individual simulation and to protect the fleet from any liability that may be associated with such content. Variance from these guidelines in individual posts may be necessary from time to time for the enrichment of the game, but should not be of such magnitude as to cause extreme shock or offense to the average adult reader, except for those in the 18+ rating category. Any complaint about the content of a sim should be approached by the Admiralty in the least restrictive of senses possible under these guidelines, so as to inspire creativity in future postings, instead of creating an air of censorship.

  1. 13+ (General Audiences):
    1. Sim may only include occasional use of mildly offensive language (cursing).
    2. Sim may contain violence, but must not contain graphic description of violence or injuries.
    3. Sim may only contain references to sexual conduct, and may not contain any descriptions of sexual intercourse or erotic situations.
  2. 16+ (Mature Audiences):
    1. Sim may contain frequent use of offensive language (cursing).
    2. Sim may contain graphic description of violence, but may not contain description of extreme violence, injuries, acts of mutilation or of sadism to such level they may cause shock or offense to the average adult reader.
    3. Sim may contain reference to specific sexual acts, but may not contain descriptions of the acts being performed. No descriptions of the aroused state of any sex organs or body parts or of penetration, masturbation, rape or any other form of non-consensual sexual acts.
  3. 18+ (Adult Audiences Only: Age Restricted, Non-Public Simulation):
    1. Sim may contain extreme use of graphic language (cursing).**
    2. Sim may contain extremely graphical descriptions of violence, injury and torture.**
    3. Sim may contain extremely graphical descriptions of sexual acts, intercourse and other forms of sexual activity.**
  4. Additional Information:
    1. All new simulations starting within the fleet shall be granted the rating of 13+. The Commanding Officer (CO) of the simulation may request a rating change to 16+ to the Task Force Commanding Officer (TFCO). If the TFCO approves the request, the TFCO should send it up to the Bravo Fleet Executive Officer (BFXO) with a cc to the Bravo Fleet Commanding Officer (BFCO) for approval verification.
    2. No simulation may be approved for a rating of 18+ unless the CO has achieved a minimum of 6 months of command experience in Bravo Fleet. All CO’s wishing to have their ship ratings raised to 18+ shall submit a request via email to their TFCO, stating the reasons they feel they need their simulations raised to the restricted age group. If the TFCO approves the request, the TFCO should send it up to the Bravo Fleet Executive Officer (BFXO) with a cc to the Bravo Fleet Commanding Officer (BFCO) for approval verification.++
    3. No simulation rated 18+ shall be permitted to be officially listed as a flagship for any member of Bravo Fleet with a flag rank (Commodore or higher). Any simulation run by a flag officer shall be listed in the general section of the Task Force, and shall not list the flag officer as being the CO of the simulation.
    4. No simulation listed as a Fiction Sim shall be allowed the rating of 18+, as these simulations are designed for the purpose of creating canon for the Task Forces and/or fleet.

+ Neither Bravo Fleet, nor the Fleet Admiralty endorse the use or discussion of graphic sexual or violent content. Due to the nature of the content, any simulation wishing to portray either shall be restricted from public access to anyone not a member of the simulation, and only people who have been verified to be aged 18 or older shall be permitted to join said simulations. Any simulation found to be in violation of these provisions, shall be subject to termination by the Fleet Admiralty and members involved may be subject to personal action via JAG or real world legal authorities.

++ The Bravo Fleet Commanding Officer and the Bravo Fleet Executive Officer retain the right and power to reverse any rating approvals which have not followed the proper protocols for approval, or that may be deemed to have insufficient cause for the restricted age rating.

BY-LAW #3.1 – ADOPTION OF MATTERS INTO BF CANON

Further to various articles of the Constitution, a player wishing to propose an addition to Bravo Fleet canon, be it in the form of technology, species or history, naming of ships or any other potential additions, shall do so in the means of a formal written proposal which shall explain the mertis to Bravo Fleet of adopting the proposal to its canon, an explanation of how the proposal has been developed and thought out and any other information that the player believes may be relevant to the proposal. Such a proposal shall be reviewed by each individual above the player in the chain of command at which time it shall be approved, passed higher on the chain of command if a decision cannot be made, or rejected with written reason.

In addition, the adoption of new starship or starbase classes into Bravo Fleet must meet the following requirements:

  1. The class must have a 3D mesh for rendering of graphics, in any format, with appropriate permission from the 3D artist to use the mesh.
  2. The class must have a baseline for specifications, as the submitter feels is appropriate for the class of ship
  3. The class must have at least one rendered graphic with a size comparison to one of the following classes of starships for scaling purposes: Intrepid, Galaxy, Sovereign

BY-LAW #3.2 – PROVISIONAL SHIP CLASSES

There may at times exist ship classes which may be desired for play in Bravo Fleet that cannot meet the conditions that are required for all ship classes playable inthe fleet. For example, the desired class may have images available, and permission from the person who made the images to use them, but a mesh may not be available. For these kinds of conditions, if there is enough interest from COs who may wish to still try to use the ship class, the BFXO or BFCO may upon request consider allowing the class for conditional use as Provisional Ship Classes. Should the artist of any of the images used for any provisional ship class decide to rescind their permission for us to use their images. the class will be immediately dropped from consideration for play under this provision.

Due to of the special nature and circumstances surrounding the inclusion of provisional classes, no provisional class shall be allowed in anything less thang Group B ship clearance as described in By-Law #2.3, Section 1.

If there is a class you wish to have added under this provision, you should first consult with the TFCO of the Task Force you’d like to play the class in, and request the TFCO to refer the class to the BFXO and BFCO for possible inclusion under the conditions of this By-Law.

BY-LAW #3.3 – CHANGES TO SHIP SPECIFICATIONS

To provide a common simming environment for Bravo Fleet’s members, per III.2.4, a CO may not deviate from the official specifications of his ship’s class as defined by BF without approval. In order to make such changes, such as installation of new equipment, addition of technologies, increasing beyond the maximum number of crew in general or for a particular crew subset, or altering the types of support craft aboard the ship, a CO must submit a request in writing (email) to his TFCO. All deviations from the standard for the simm’s class should be listed on a seperate page as part of the simms website so that new and visiting players can avoid creating splits or other misunderstandings.

BY-LAW #3.4 – USE OF GRAPHICS

  1. In the case of created material for Bravo Fleet wide use (such as TF Logos and TF banners), the providing artist(s) agree to grant Bravo Fleet the royalty-free, (unless otherwise specified by Bravo Fleet) perpetual, irrevocable right and license to use, reproduce, and distribute such material to its sub-entities, in whole or in part, without any compensation or notice to the artist(s) whatsoever.
    1. In order for the above point to exercised, the artist in question must be advised of this by-law at the time any work for Bravo Fleet wide use is commissioned.
  2. Bravo Fleet and its Members, Simms, and Task Forces will not remove credits from images unless directly allowed to substitute them for an entry on a credits page by the original author of that work.
  3. Images that are made for a specific Bravo Fleet Simm and/or Task Force shall only be used by that Simm and/or Task Force alone unless the artist specifies otherwise.
  4. Members, Simms, and Task Forces of Bravo Fleet agree that the original artist may request the cessation of use of any artwork created for that Member, Simm, or Task Force. However, the aforementioned parties shall be allowed a time period of no less then two weeks to find replacement works to substitute for the images in question. If that time elapses and no replacement has been found, the Member, Simm, or Task Force will still have to cease use of said materials.

BY-LAW #3.5 – LEAVES OF ABSENCE

  1. This by-law establishes three statuses other than active that may be applied to players and administrators that are not currently performing their assigned game or fleet roles:
    1. LOA. A Leave of Absence (LOA) is a brief leave from the fleet for a specified period of time, with a fixed return date.
    2. ELOA. An Extended Leave of Absence (ELOA) is any leave over two weeks, or a leave that does not have a specified end date due to extraordinary circumstances in the life of the player. Extraordinary circumstances could include personal illness, illness of a family member, natural disaster or military deployment.
      1. Both LOAs and ELOAs must be agreed between the person taking the leave and their superior in the chain of command.
      2. Should a natural disaster strike an area of the planet known to be home to one or more Bravo Fleet Members, said members can automatically be granted an ELOA until their status can be ascertained.
    3. AWOL. A player can be declared Absent Without Leave (AWOL) for absences without an approved LOA or ELOA, by not returning within the specified return date of an LOA, or if an ELOA has continued, without any contact from the player, for significantly longer than anticipated.
      1. If any player is declared AWOL, after one week they may be removed from their positions and subsequent appropriate actions taken.
    4. Receipt of an LOA request should be acknowledged via the same medium it was sent.
      1. TGCOs receiving leave requests from COs should also notify their Task Force Senior Staff.
    5. Any player who wishes to claim unfair removal from their position while on leave must provide, to their immediate superior, the acknowledgement of their leave notification/request to show that the LOA request was received and that the date the player returned was on or prior to the agreed date. The complaint can then be processed through the CoC as necessary.
  2. Commanding Officers
    1. Commanding officers taking leave must also specify an Acting Commanding Officer in their stead.
      1. If an appropriate Acting Commanding Officer cannot be found or the ELOA time is longer than an Acting Commanding Officer will be able to cope with, the simm may be closed.
  3. Bravo Fleet Admiralty Members
    1. All BFA members have the right to take leaves of absences for up to 14 days.
      1. Any period greater than 14 days (ELOA) must be approved by the BFCO in advance. If approval is not given and the BFA member cannot return within the original 14 days, they may be required to forfeit their BFA position.
      2. LOAs must be posted in the LOA section of the BFA forum.
    2. Should a TFCO take a leave of absence, their power and duties will be vested in their Task Force XO. This does not include, however, the right to vote on BFA matters.
    3. Should a Department Head take a leave of absence, their power and duties will be vested in their Command Adjutant. This does not include, however, the right to vote on BFA matters.
  4. Bravo Fleet Commanding Officer
    1. The BFCO, when taking an LOA, must contact the Bravo Fleet Senior Staff and the BFA in advance.
    2. LOAs longer than 14 days (ELOA) must be approved by the BFXO. If approval is not given and the BFCO cannot return within the original 14 days, he or she may be required to forfeit their BFA position.
      1. If the BFCO is granted an ELOA, he or she shall be required to give updates of their status to the BFA on a weekly basis. Failure to maintain such communication may constitute the BFCO as being AWOL.
      2. Should the BFCO take an LOA, their power/duties, except those of Executive Order, will be vested in the Bravo Fleet Executive Officer
      3. Should the BFCO resign while there is an acting BFXO appointed via this bylaw, the standard rules of succession by position (non-acting) and rank come into effect.
    3. Should one or more BF Senior Staff member(s) take an LOA, the BFCO has the right to delegate their duties to other BFA members as necessary, without consulting the BFA.

BY-LAW #3.6 – ACCEPTING NEW COS

  1. No TFCO shall accept a new Simm CO unless he or she meets the following requirements:
    1. the candidate must have at least four verifiable months of active player experience on an active Bravo Fleet simm or an equivalent elsewhere.
    2. the candidate must receive a favourable review from his or her ship’s Commanding Officer, or the CO’s designate.
  2. Upon reviewing the application, four or more months experience and the recommendation a TFCO will then make a judgment on the quality of the candidate. Character Biography rewrites, additional writing samples or additional reviews by other ship members may be requested. A failure to comply with requests for additional biography or writing samples will be immediately considered a rejection of the position by the candidate. A failure of ships crew to reply to requests for reviews will not be held against the candidate, but may impact their application process.
  3. All new COs will have a six month trial/probationary period. If a simm has not met the requirments to go active during this time, the CO may be removed.
  4. Upon receipt of a new command a player is asked to limit character expansion for at least the first six months they are a CO. This will mean that if a player has two characters and requests their third be a CO, then for six months they are to refrain from creating any new characters in Bravo Fleet or any of it’s affiliates until their six month trial period is over and their ship has gone active.
  5. All COs must agree to the following:
    1. By accepting the offer of a Command in Bravo Fleet, you acknowledge that you are applying for a command in Bravo Fleet, for the ship that you have listed. If for whatever reason you resign your command, your Task Force CO and/or Bravo Fleet can, at its option and with out any additional notice to you, re-use the name and registry number of the ship you commanded in Bravo Fleet, even if you decide to join another fleet with the ship or become an independent simm with the ship. By submitting this application, you acknowledge that you understand and agree to this. This rule can only be adjusted, in writing (via an email acknowledgement, not just by instant messanging), by the Task Force CO AND the Bravo Fleet CO.
    2. By accepting an offer of a Command from the TFCO, you acknowledge that if you resign from your command for what ever reason, or leave Bravo Fleet for another fleet or to go independent, the Task Force CO and/or the Bravo Fleet Commanding Officer or Executive Officer may contact your crew one time about the situation to make sure that they have been given the option of staying in Bravo Fleet, and to give them that option if it has not been given previously.
    3. By accepting an offer of command, COs recognize that Bravo Fleet is a large organization whose administration can be complex and, as such, though Bravo Fleet will consider the preferences of COs with regard to ship class, name, Task Force assignment, and other administrative issues, COs may not always get their first choice.
  6. Notwithstanding any provisions restricting the command of certain types of vessels, a TFCO may award command of a simm to the XO or another crew member when a CO resigns or is removed. Such a CO will be required to complete any requirements laid out in this section, if they are not already completed, immediately after his/her assuming the role of CO.

BY-LAW #3.7 – ACCEPTING OUTSIDE SIMM TRANSFERS

A simm requesting a transfer into Bravo Fleet from outside of Bravo Fleet and its affiliates may not be accepted unless it meets the following requirements:

  1. An independent or other simm wishing to come into Bravo Fleet will be treated as a general transfer as if it were already in the fleet. COs wishing to bring their ships into Bravo Fleet should contact a TFCO about coming in,who will then handle it accordingly to the way a transfer is. Questionnaires, interviews and e-mail exchanges are subject to the applicant so that a TFCO may better get to know the simm CO who they may be accepting.
  2. Simm crew and general activity required to obtain a place in Bravo Fleet will be at the discretion of the TFCO who is applied to.
  3. The simm must follow all Bravo Fleet rules and guidelines laid out by the Bravo Fleet Constitution and its By-laws. Circumnavigation of these rules will result in a disqualification in becoming a Bravo Fleet member simm.
    1. The simm must be willing to change any ship specifications which do not meet with already pre-approved specifications of the BFA. Bravo Fleet ‘canon’ specs can be found on the Bravo Fleet Wiki.
  4. The simm must be willing to meet with any other requests which the TFCO may present to at the time of application, including reduction in rank(s)