From Bravo Fleet InfoBase

Under Article II of the Bravo Fleet Constitution, by-laws may be created to define detailed rules and regulations for the fleet.

Structural Bylaws (1)

By-law #1.1 - Task Forces

Per Article IV, Section 2 of the Constitution, Bravo Fleet shall have the following Task Forces:

By-law #1.2 - Member & Staff Duties

Section 1 - Players

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.
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.
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.
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.
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.
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.
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.
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.
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

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.
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.
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.
Simm COs shall have the final responsibility for recruiting members of their simm and shall do so within the restrictions set by Bravo Fleet.
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.
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.
No player shall command more than three simulations in the whole of Bravo Fleet including its affiliates.
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.
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. Affiliate COs will add players to the ban list in the event that a CO resigns a command in an Affiliate. 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.

Section 3 - Task Force Commanding Officers

TFCOs have the right to reject any applications for players or COs coming to his or her TF. Any rejected applications will be forwarded to the Bravo Fleet Chief of Staff to determine whether or not to wholly reject them, pass them to another Task Force, or to send them to the BF Academy.
TFCOs have the right to administer their Task Force as they see fit, including the right to chose their own TF staff, within the confines of the constitution and by-laws.
TFCOs have the right to vote on all matters that come before the Bravo Fleet Admiralty, in casting these votes a TFCO shall take into account not only his or her opinion on the matter but also the interests of his or her Task Force which he or she represents on the BFA.
TFCOs may create an operational plan for their Task Force which shall be approved by their staff and ratified by the Bravo Fleet Chief of Staff.
TFCOs have the responsibility to work closely with their TFXO (and, if applicable TF2XO) who should be treated as a TFCO-in-waiting and trained and educated as such.
TFCOs have the responsibility to maintain Bravo Fleet's website for their Task Force.
TFCOs have the responsibility to advertise for their Task Force, and to assist in the recruiting of new players for simms within the Task Force.
TFCOs have the responsibility to bring to the attention of the BFCoS any and all suggestions and ideas made by members of their Task Force that have been approved by the TFCO, for possibility of becoming BF canon.
TFCOs have the right to give initial approval for major changes to simms (including ships/starbases, technology, and specification alterations) while waiting for final approval from the Bravo Fleet Chief of Staff.
TFCOs have the responsibility to attend any Fleet Staff meetings when held, unless other arrangements are made.
TFCOs have the responsibility to encourage COs to participate in Bravo Fleet by setting a good example. This includes sending news articles, HoH submissions, IRC, MBs, and voting for BF.
TFCOs have the responsibility to participate on the Fleet Staff mailing list and in the Fleet Staff forums to the best of their ability.
TFCOs have the responsibility to keep the BFCoS and the Fleet CnC updated on any simm changes in their Task Force.
TFCOs have the responsibility to ensure that training is provided for all new Simm COs within their Task Force.
TFCOs have the responsibility to add COs they have removed or who have resigned to the CO probation list and note the circumstances of their depature. A TFCO also has the right to refer a CO who has resigned to JAG if he/she feels the circumstances of the departure merits a longer probation than the standard defined in the constitution.

Section 4 - Bravo Fleet Chief of Staff

The Bravo Fleet Chief of Staff shall maintain regular contact with and shall be easily accessible to the TFCOs within the Fleet to provide guidance or advice.
The Bravo Fleet Chief of Staff is responsible for keeping up-to-date on matters within the Task Forces.
1. The Bravo Fleet Chief of Staff has the right to take authoritative action in the task forces on an as needed basis in exceptional circumstances. In general, these circumstances are defaulted to major changes in task force canon, major changes to Bravo Fleet canon, or changes to the entirety of the task force with which the player base disagrees. In all these matters, however, the BFCO will have the final decision.
The Bravo Fleet Chief of Staff shall provide training and mentoring to the TFCOs under their command as required.
The Bravo Fleet Chief of Staff shall receive any requests brought to them by a TFCO whether these are request from the TFCO for changes in the Task Force or a request passed to the TFCO through the chain of command that the TFCO is unable to resolve. These requests shall be addressed in the following matters:
1. Approve
2. Reject with reason
3. Refer to the BFCO or BFXO for approval or rejection
4. Refer to the full BFA for further review
The Bravo Fleet Chief of Staff shall attend Fleet Staff meetings when held.
Encourage COs to participate in Bravo Fleet by setting a good example. This includes sending news articles, HoH submissions, IRC, MBs, and voting for BF.
Keep BFCO updated on any matters as required.

Section 5 - Bravo Fleet Operations Officer

The Operations Officer will be charged with the direct oversight of the activities of the various divisions of the Operations department. The OPS will appoint or remove, as needed, responsible Bravo Fleet Members to the positions above after conferring with the Bravo Fleet CO and Bravo Fleet XO.
The Operations Officer is charged with coordinating all Out of Character Operations of the Bravo Fleet Community through the efforts of the BF Operations Staff.
Members of the Bravo Fleet Operations Staff will submit monthly reports of progress to the Bravo Fleet Operations Officer. In turn, the Bravo Fleet Operations Officer will seek opinions, suggestions, and advice from  the Operations Staff and bring them before the full BFA as needed. Bravo Fleet Ops will make progress reports to the BFA at least once every three months.
All new BF Operations staff positions will be voted on by the BFA, and require a 50% majority in order to pass. The position will then be filled by the BF Operations Officer.

Section 6 - Bravo Fleet Executive Officer

The Bravo Fleet Executive Officer (BFXO) shall serve as the BFA vice-chair. Also, the BFXO shall act as chair for the BFA when the BFCO is unavailable for routine matters such as calling for a vote on an issue before the BFA.
The BFXO will act, on an "as needed" basis, as mediator upon any disputes on transfer requests within the fleet.
The BFXO will coordinate with the Bravo Fleet Chief of Staff on keeping the Bravo Fleet Management System and fleet mothballs lists up to date, in order to make ship requests and transfers smooth and coordinated. This will also maintain an accurate list of simm locations.

Section 7 - Bravo Fleet Commanding Officer

The Bravo Fleet Commanding Officer (BFCO) shall be the chief executive of Bravo Fleet and shall serve as chair of the BFA.
The BFCO shall have a deciding vote in the case of a tie for matters before the BFA even if he or she has already cast a vote.
The BFCO has the final say in all matters brought up the chain of command that do not require a decision of the BFA.
The BFCO shall nominate persons to occupy all BFA-level positions, subject to approval of the BFA. The BFCO, when nominating someone in a TF chain of command, is advised to consult with the TFCO to determine the suitability of a person prior to nominating him or her for the BFA.
The BFCO may delegate any of his or her powers, save those surrounding executive orders, to other members of the BFA.

By-law #1.3 - Operations Staff

The following positions shall be part of the BF Operations Staff:

The Academy Commandant shall be charged with the development and maintenance of training materials and courses for players, new simm COs and others as necessary.
The Infobase Coordinator will be responsible for maintaining standards and quality on the infobase, and for compiling and updating Bravo Fleet history and canon based on the activities undertaken in the stories of member simms. He will also may appoint Infobase Staffers to assist with those duties as needed.
The Recruitment Officer shall be charged with overseeing recruitment efforts throughout the fleet and helping to both guide and undergo those efforts when it is needed.
The Hall of Honor Admin shall be charged with overseeing the Hall of Honor and all applicable duties involved with that entity.
The Forum Admin is the head of Bravo Fleet’s forum, and acts accordingly as the head of Relay Station Bravo.
The FNS Chief Editor is the chief editor and guidance for the Fleet News System.
The Director of Research and Development will be responsible for oversight of the review process addressing Bravo Fleet's specifications and technology (both ship and personal). In addition, the Director and any staff members he chooses to retain shall also be made available to assist any members of the fleet with proposals regarding ship classes and other technology, and the the Director will be charged with forwarding any and all completed proposals to the BFA for review, comment, or implementation.
The Internet Officer is charged with all Bravo Fleet webmaster-related duties.
The Graphics Director which is charged with overseeing, managing, and policing the Bravo Fleet online graphics presence to ensure that it complies with the established regulations for graphics and their use. In addition, the Graphics Director shall manage the Bravo Fleet Graphics Team, either directly or through a Graphics Team Leader at their discretion.

Regulatory By-laws (2)

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:

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.
Bravo Fleet does not permit the playing of omnipotent species shown in Star Trek, other fiction or unique omnipotent creations.
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.
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.
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.
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

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.
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.
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

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.
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 Chief of Staff.
Task forces may not authorize more than four fiction simulations in their task force - one permanent fiction simulation and three non-permanent fiction simulations.
Any fiction simulation developing Bravo Fleet overall canon must be written with a 13+ rating and be approved by the Bravo Fleet Admiralty.
Any fiction simulation developing task force canon is subject to approval and restrictions as set by the relevant TFCO and task force staff.
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.
Fiction simulations that are writing for above a 13+ rating must have appropriate warnings placed on their website and posting group.
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 BFCoS.

By-law #2.3 - Ship & Station Command Requirements

Section 1 - Approved commanding classes and qualifications for command

The following classes of ships and starbases have been approve for the use as simming environments in BF:
1. Group A Commands: Akira, Ambassador, Atlantia, B'rel, Cheyenne, Condorde, Defiant, Diligent, D'Kora (Marauder), Dominion Attack Ship, D'renet, Excelsior, Excelsior Refit, Explorer, Galor, Hideki, Intrepid, Kelly, Khellian, K't'inga, K'Vort, Laehval, Nebula, New Orleans, Norway, Nova, Nova Refit, Olympic, Preax, Saber, Shrike, Steamrunner, Ventarix, Wildcat
2. Group B Commands: Ares, Excalibur, Galaxy, Insignia, Keldon, Luna, Valdore, Vor'cha, Jupiter Station, Regula (All types), Troy
3. Group C Commands: D'deridex, Dominion Cruiser, Negh'Var, Prometheus, Sentinel, Sovereign, Alexandria, Nor class (Federation or Cardassian), Ilium, Immense
4. Group D Commands: Dominion Battleship, Galaxy Refit, Premonition, Ronin, Scimitar, Mannheim Temporal Research, Ship Yard, Spacedock, Planetary bases and colonies, non-Federation starbases and settlements.
5. Civilian vessels, for the purpose of this by-law, are classified as a Group A simm, but the simm must be approved by the BFCoS before being created.
In order to encourage a level of realism that is consistent with both a real-world application of time served as a commanding officer and in order to cater to our players' desires, the following experience shall be required of players:
1. For Group A Commands, a minimum total of four months active player experience in BF or six months relevant active player experience outside of BF.
2. For Group B Commands, a minimum total of nine months command experience of an active simm.
3. For Group C Commands, a minimum total of twelve months command experience of an active simm.
4. For Group D Commands, a minimum total of eighteen months command experience of an active simm.
5. In order to qualify for a class change, a CO must also have nine months of active command experience served on their current class in addition to any other Command Group requirements.

Section 2 - Retired and mothballed ship and base classes

The following classes of ships will be classified as retired in the fleet:
1. Group A Retired - Akula refit, Centaur, Challenger, Constellation, Constitution Refit, Freedom, Miranda refit, Niagara, Oberth, Springfield, Syndey
  1. The ships listed in Group A retired ships may still be used a support vessels for starbases.
  2. Group A retired ships may still be accessed for active command on a case by case basis subject to the approval of the Bravo Fleet Commanding Officer.
2. Group B Retired - Angel, Apollo, Apollo Refit, Asimov, Charleston, Constitution Refit II, Denmark, Proteus
  1. Group B retired ships are no longer authorized for active use in Bravo Fleet and will be phased out due to mesh availability and/or copyright issues. If these issues are resolved, Group B ships can be again evaluated for fleet wide use.
3. Any retired ship currently in active service may continue as such indefinitely until the ship is declared inactive. At that point it shall be retired.

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

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.
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.
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
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
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
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.
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

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.
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.
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.
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
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.
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
2. Completed at least six months of consecutive active TGCO 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.
COs can be promoted to Rear Admiral, Major General or alien equivalent by the BFCoS upon recommendation by the TFCO when the following conditions are met:
1. Completed at least twenty-four months of active command experience
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, BFCoS, or BF OPS.
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
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.
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
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.
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
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 TGCO 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.
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.
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.
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.
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.

Proceedural By-laws (3)

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:

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.
The class must have a baseline for specifications, as the submitter feels is appropriate for the class of ship
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 - 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.3 - Use of graphics

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.
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.
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.
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.4 - Leaves of Absence

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. They are defined as follows:
1. A Leave of Absence (LOA) is a brief leave from the fleet for a specified period of time agreed between the person taking the leave and their superior in the chain of command with a fixed return date.
2. An Extended Leave of Absence (ELOA) is a longer leave without a specified end date required due to extraordinary circumstances in the life of the player agreed between the person taking the leave and their superior in the chain of command without a fixed return date. Extraordinary circumstances could include personal illness, illness of a family member, natural disaster or military deployment.
  1. Notwithstanding the further contents of this By-Law, should a natural disaster strike an area of the planet known to be home to one or more Bravo Fleet Members, said members will automatically be granted an indefinite ELOA until their status can be ascertained by their superiors in the chain of command.
3. A player can be declared Absent Without Leave (AWOL), after being missing from a game without having been granted an LOA, an ELOA or without returning within the specified return date of an LOA or having been missing during an ELOA for more than six months or longer than anticipated.
Rights Granted to Players
1. To request a Leave of Absence or an Extended Leave of Absence from his/her game, a player must request said status by contacting his/her commanding officer.
  1. An end date must be specified for both an ELOA and LOA, and agreed upon by both the player and the leave-taker.
  2. Should a player not make contact within the bounds of the agreement, said player may be removed from the simm without penalty to the commanding officer.
Rights Granted to Commanding Officers
1. To request a Leave of Absence or an Extended Leave of Absence from his/her game, a commanding officer must request said status by contacting his/her Task Force Commanding Officer, through the chain of command.
  1. An end date must be specified for both an ELOA and LOA, and agreed upon by both the TFCO and the leave-taker.
  2. Commanding officers taking leaves must specify who is the Acting Commanding Officer in their stead, be this the XO or another player.
  3. The ELOA of a Commanding Officer carries several additional constraints, as described in the following subsections:
    1. If an appropriate Acting Commanding Officer cannot be found or the ELOA time is longer than an Acting Commanding Officer could cope with, the simm is to be closed, with the understanding that the Commanding Officer can apply to another simm at the end of his/her ELOA.
    2. If a CO does not return within the guidelines of his/her LOA, he or she may be removed from command. Should this happen, the TFCO will make all efforts to place a new commanding officer, first offering command to the ACO, and then other players. Should this not happen, the simm will be closed and the players will be offered positions elsewhere in the fleet.
    3. If a simm is closed under Section III.1.4.1 and a CO fails to return at the end of his/her ELOA period, the CO loses the right to return to command at his/her previous rank.
Rights Granted to Bravo Fleet Admiralty Members
1. All BFA members except the BFCO have the right to take leaves of absences up to 14 days by posting in the LOA section of the BFA forum and by contacting their direct superior in the chain of command, via email.
  1. Should a LOA last more than 14 days, it must be approved by the BFCO. The BFCO may grant an ELOA of up to one month.
  2. At no time shall the BFCO grant an ELOA that lasts longer than 1 month. Should a BFA member be faced with a scenario that will require extended leave time, said member must make a make a motion to the BFA to extend the ELOA, which shall include the reason for the request. The BFA may grant up to 2 ELOA extensions, in 2 week increments, for a total of a two month ELOA.
    1. LOA extensions will be passed by a simple majority of the BFA.
    2. Should the motion fail and the BFA member is not immediately able to return to active service, the member will forfeit his/her position on the BFA.
    3. Should the BFCO be the member taking a leave of absence, he or she must contact the BFXO as well as the BFA. He or she can choose to delegate his/her executive power to the BFXO during the leave of absence, should it be 14 days or less.
  3. The BFCO may grant himself/herself a single two-week extension on a LOA, creating an ELOA. In such a case, executive power automatically falls to the BFXO.
    1. If the BFCO continues to need LOA extensions, he/she must make a motion to extend the LOA to the BFA, which shall include a reason for the request.
      1. LOA extensions for the BFCO will be passed by a simple majority of the BFA.
      2. Should the measure fail, and the BFCO is not immediately able to return to duty, he/she will forfeit her position and the BFXO will immediately be promoted to fill the vacancy.
    2. If the BFCO is granted an ELOA, s/he shall be required to maintain verifiable communications via email, Instant Message, Private Message (IRC or Forums) or forum posting, on at least a bi-weekly basis with both the BFXO and the BFA. Failure to maintain such communication, or to return from the LOA by the agreed return date, may constitute the BFCO as being AWOL, and may be grounds for the BFA to seek relief in the form of impeachment from office.
  4. The following exemptions from requiring a vote to extend a leave of absence are hereby established:
    1. Deployment as a Member of the Armed Service of any government.
    2. Major medical/surgical procedure and/or long-term medical treatment.
LOA/ELOA Procedures
1. Any CO, TGCO, TFCO, the BFCoS, the BFXO or the BFCO who receives an LOA notification or request from a player, CO, BFA member the BFXO or the BFCO, shall immediately send notification of receipt of the LOA request via the same medium as it was received on, as well as by email if the original medium was not such. The receipt should include acknowledgement of the LOA, as well as the understood return date. Failure to send such receipt may hinder the ability to seek relief against the player for failing to return from E/LOA. It is suggested that the return receipt also be CC'd to the acknowledging party's immediate superior for the purpose of independent verification.
  1. TGCO’s must forward any received LOA’s to the Task Force Senior Staff, and then by the Task Force Senior Staff to the Task Force Commanding Officer, as established in Section III.1
2. Any player, CO, BFA member, the BFXO or the BFCO who wishes to claim unfair removal from their position or demotion based on an LOA status, must provide the return receipt of confirmation from their superior that the LOA request was actually received, and that the date the player actually returned was on or prior to the agreed return date.
  1. In the event that such a claim is raised by a player, the Task Force Commanding Officer will render a decision on the matter. Should the player be a Task Force Staff Member, the Bravo Fleet Chief of Staff will render a decision on the matter. Should the claim be the result of a BFA vote, the decision may not be appealed.
3. In addition to the other protocols perscribed for the LOA of a BFA member, the following conditions are imposed to ensure the offices' duties are carried out in the absence of their official holder.
  1. Should a TFCO take a leave of absence, his/her power will be vested in the TFXO of his/her Task Force.
  2. Should the Bravo Fleet Chief of Staff take a leave of absence, his/her power will be vested in the BFXO.
  3. Should the BFXO take a leave of absence, his/her power will be vested in the Bravo Fleet Chief of Staff.
  4. Should a situation exist that necessitates a LOA or ELOA for the BFCoS and the BFXO, the BFCO has the right to appoint other BFA members as acting BFCoS or the Acting BFXO, without consultation of the BFA.
    1. Should the BFCO resign while there is an acting BFXO appointed via the preceeding section, the standard rules of succession by position (non-acting) and rank come into effect.

By-law #3.5 - Accepting New COs

No TFCO shall accept a new Simm CO unless he or she meets the following requirements
1. at least six months verifiable experience on an active Bravo Fleet Simm (the simm must be verified to be active for at least six months while the player is aboard)
2. the candidate must receive a favourable review from his or her ship’s Commanding Officer, or the CO's designate.
Upon reviewing the application, six 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.
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.
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.
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, Executive Officer OR Chief of Staff 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.
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.6 - 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:

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.
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.
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 Infobase.
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)

Affiliate By-laws (4)

By-law #4.1 - Futility's End affiliate

Futility's End (FE) is an affiliate of Bravo Fleet, the storyline is set in 2405 following an apocalyptic war with the Borg.
1. The goal of Futility's End is to provide a mature writing environment that takes what is best about Trek, acknowledges the success of harsher, grittier television shows such as The Shield and Battlestar Galactica and combines the two to create a radical new spin on the canon whilst retaining the quality of the shows. We further aim to add to parts of Trek's galaxy that were never properly explored onscreen.
2. In addition to providing a simming environment for our players, Futility's End allows for writing of fiction as part of Futility's End canon and to keep the Futility's End story moving.
Futility's End is moderated by an entity known as Futility's End Quad.
1. The current Futility's End CO is Captain Trevor Hall who can be reached via email at fe[at]bravofleet[dot]org, he shall represent FE on the Bravo Fleet Admiralty.
2. The line of succession for Futlity's End is through the Futlity's End Quad, the FECO will nominate one (1) member of the quad as the defacto FEXO (This person will be marked as the FEXO on this page - this person will be next in line for succession. If this person is unable, or unwilling to take over Futility's End then the Quad will make the decision on who will be the next Futility's End CO.
3. If the Futility's End CO is unavailable, contact can be made with Futility's End by emailing quad[at]fehq[dot]net at least one member of the Quad will be available to respond to the Bravo Fleet Admiralty.
Futility's End is not subject to the Bravo Fleet Judge Advocate General.
Futility's End Quad is responsible for creating and enforcing rules within Futility's End as they and/or the FECO see fit. The up to date bylaws can be found at Futility's End Community.
1. Per Article II.3.2 of the Bravo Fleet constitution, members of FE "have the same rights and responsibilities as BF players" in general, however certain BF player rights are not applicable in FE. Specifically:
  1. Notwithstanding BF Constitution III.1.1 and III.1.14, FE and its players are not subject to JAG
  2. Notwithstanding BF Constitution III.1.2, some BF by-laws are specific to BF core and therefore are not applied at all to members of FE
  3. Notwithstanding BF Constitution III.1.3, FE has a separate chain of command from Bravo Fleet
  4. Notwithstanding BF Constitution III.1.6, FE does not require its players to post once per week
  5. Notwithstanding BF Constitution III.1.10, FE has canon distinct from Bravo Fleet and operates in a parallel universe splitting from BF due to a Borg invasion that did not occur in BF canon, therefore BF canon changes to not apply to the FE universe.
2. This by-law is deemed to have taken effect at the same time as the new constitution in June 2006.

By-law #4.2 - Naval Experimental Division affiliate

NXD is an affiliate of Bravo Fleet, the storyline is set in the time of the NX class and the epic voyage of Captain Jonathan Archer and the Enterprise NX-01. NXD is set in the year 2160.
1. The purpose of NXD is to provide players a place to simm in an environment that follows that of Star Trek Enterprise.
2. In addition to providing a simming environment for our players, NXD allows for writing of fiction as part of Star Trek Enterprise.
3. Any ship will be open for use except the Enterprise NX-01 and Columbia NX-02.
The NXD Affiliate is currently commanded by Lucas Martin Robinson who can be contacted at "nxd(at)bravofleet(dot)org", he shall represent NXD on the Bravo Fleet Admiralty.
1. As a matter of NXD canon and to place emphasis on Starfleet as a whole as it pertains to NXD the following is enacted;
  1. Affiliate CO Hereby referred to as the Commanding Officer of the NXD (NXDCO).
  2. Affiliate XO Hereby referred to as the Executive Officer of NXD (NXDXO).
  3. Affiliate CoS Hereby referred to as NXD Chief of Staff (NXDCoS).
2. NXD is moderated by a group known as Starfleet Command (SFC) consisting of Lucas Robinson as NXDCO, the NXDXO, chosen by the NXDCO, and the NXDCoS, chosen by both the NXDCO and NXDXO. The remaining members of SFC will include a Recruitment officer, News and History officer, a Training officer and a General Advisor. The SFC will be filled by agreement of the NXDCO, NXDXO and NXDCoS. Once the SFC is up and running, it will assemble once a month to discuss the status of NXD and vote on important topics.
3. NXD will also include the Corps of Captains (COC) which will participative in all SFC meetings as a part of the SFC. To be a member of the Corps of Captains a person must command a simm in NXD. The rank of the simm commander will not affect their status or value in the Corps of Captains.
4. SFC will vote on any issue that is brought to the table. Issues that do not pertain to staff will require only a majority vote. Votes relating to the staff, including replacement of NXDCO, NXDXO and NXDCoS, will require a unanimous vote of all but the person being voted against. However, replacement of a departing officer will only require a 2/3rds vote. To be clear, this means, an officer who departs will be replaced by a candidate that receives a vote of support from at least two thirds of the SFC including the COC.
All members of NXD shall be required to follow all parts of the current Bravo Fleet Constitution that are not time line specific, with the following exceptions:
1. Article III, Section 1, Point 1 (NXD members are not subject to BF JAG. See Point 5.)
2. Article III, Section 2, Point (NXD simm Co’s must have a total crew count of 5 to launch including themselves however the Co must abide by the rest of this point.)
3. Article V, Section 2 (Amend for NXD – NXD shall substitute its own group in place of the Bravo Fleet Judge Advocate General.)
4. The Affiliate: NXD will substitute for the Bravo Fleet Judge Advocate General (JAG) its own Corps of Captains (COC). Player issues that require the presence of the Judge Advocate General will instead be reviewed by the COC appeals of the decision of the COC will follow the chain of command starting with the NXDCoS then to the NXDXO and ending with the NXDCO.
  1. Any member of a simm may file a complaint or request for formal charges to the COC. They may file against any officer up to a simm XO. Charges against a simm CO or higher must be formally sent to the NXDCO, NXDXO and NXDCoS.
  2. Once a decision has been made by the Corps of Captains it can be appealed following the above listed chain.
The Affiliate Task Force Commanding Officer shall be required to follow all requirements under Article III, Section 4 of the Bravo Fleet Constitution with the following exceptions:
1. The Bravo Fleet Commanding Officer may invoke an Executive Order for urgent issues to the Affiliate when needed, overriding the Affiliate CO until such time as the Senior Staff of the Affiliate determine if the Affiliate should continue to fall under the Order.
2. The Task Force CO shall submit a "State of NXD" report to the Bravo Fleet Commanding Officer & Executive Officer on a quarterly basis. (See Paragraph 7, Point 7 of this document.)
The Affiliate known as NXD is exempt from the following with only the listed exception(s).
1. Under Article VII, of the Bravo Fleet Constitution, By-law #2 of the Bravo Fleet Constitution unless voted otherwise by SFC with the COC.
2. Under Article VII, of the Bravo Fleet Constitution, By-law #15 of the Bravo Fleet Constitution.
The Affiliate may add or remove items to this by-law only after a proposal and a vote by the Starfleet Command with the Corps of Captains. Once the vote has taken place an amendment will be presented to the BFA for adjustment to existing bylaws.
An Executive Order may be imposed by the NXD CO. The Executive Order will supersede any vote by the SFC with COC that does not pertain to personal. This order will stand for 90 days at which time the SFC alone will vote to keep the Executive Order or drop it. Executive Orders and all voted topics will go into the NXD constitution. The NXD constitution will answer all questions with regards to the operations of NXD that By Law 21 does not answer.
This by-law was proposed to the BFA on May 1st, 2009; it was enacted on May 1, 2009.

By-law #4.3 - New Explorative Operations affiliate

New Explorative Operations (NEO) is an affiliate of Bravo Fleet, the storyline is set around 2294 set around the movie Star Trek VI: The Undiscovered Country, better known as The Motion Picture (TMP) era.
1. The goal of New Explorative Operations is to provide a mature writing environment that takes what is best about Trek, acknowledges the success of darker themes in Star Trek, other television shows, and the real world. We further aim to add to parts of Trek's galaxy that were never properly explored onscreen; we also strive to achieve filling in the gaps of the era that were never spoken of.
2. In addition to providing a simming environment for our players, New Explorative Operations allows for writing of fiction as part of New Explorative Operations canon and to keep the New Explorative Operations story moving.
New Explorative Operations is moderated by an entity known as New Explorative Operations’ Command Staff. The command staff is typically made up of the Fleet Commanding Officer, Fleet Executive Officer, Fleet Chief of Staff and any Task Group Commanding Officers as well as any Fleet Advisors. The number of command staff members varies depending on the makeup of the fleet at the time.
1. The current New Explorative Operations Fleet Commanding Officer is Captain Valentine Robinson who can be reached via email at neo[at]bravofleet[dot]org, he shall represent NEO on the Bravo Fleet Admiralty.
2. The line of succession for New Explorative Operations is through the normal chain of command following the FXO, then the FCoS and so forth. However, a departing FCO also has the right to name a successor other then their FXO which supersedes the normal chain of command for the line of succession. If this person is unable, or unwilling to take over New Explorative Operations then the NEO Command Staff will make the decision on who will be the next New Explorative Operations Fleet Commanding Officer.
3. If the New Explorative Operations CO is unavailable, contact can be made with New Explorative Operations by emailing either the FXO or FCoS and at least one member of the command staff will be available to respond to the Bravo Fleet Admiralty.
New Explorative Operations is not subject to the Bravo Fleet Judge Advocate General.
New Explorative Operations Command Staff is the primary group responsible for creating enforcing rules within New Explorative Operations. The NEO Bylaws can be found here.
1. Per Article II.3.2 of the Bravo Fleet constitution, members of NEO "have the same rights and responsibilities as BF players" in general, however certain BF player rights are not applicable in NEO. Specifically:
  1. Notwithstanding BF Constitution III.1.2, some BF by-laws are specific to BF core and therefore are not applied at all to members of NEO
  2. Notwithstanding BF Constitution III.1.1 and III.1.14, NEO and its players are not directly subject to BF JAG.
  3. Notwithstanding BF Constitution III.1.10, NEO has canon distinct from Bravo Fleet and operates in a parallel universe. Therefore BF canon changes to not apply to the NEO universe and vice versa.
  4. Notwithstanding BF Constitution III.1.3, NEO has a separate chain of command from Bravo Fleet
This by-law is deemed to have taken effect at the same time as the new constitution in June 2006.

By-law #4.4 - Expedition Fleet affiliate

Expedition Fleet (EF) is an affiliate of Bravo Fleet, the storyline is set in the 2250's (current year +242) around the time of the 11th Star Trek film.
1. The goal of Expedition Fleet is to provide a mature writing environment that takes what is best about Star Trek and combines it with those concepts, themes, and designs from the newest Star Trek movie.
2. In addition to providing a simming environment for our players, Expedition Fleet allows for writing of fiction as part of Expedition Fleet canon and to keep the Expedition Fleet story moving.
Expedition Fleet is moderated by an entity known as the Expedition Fleet Cadre.
1. The current Expedition Fleet CO is Captain Bryan Cash who can be reached via email at ef[at]bravofleet[dot]org, he shall represent EF on the Bravo Fleet Admiralty.
2. The line of succession for Expedition Fleet is through the Cadre, the EFCO will nominate one (1) member of the Cadre as the de facto EFXO (This person will be marked as the EFXO on this page - this person will be next in line for succession. If this person is unable, or unwilling to take over Expedition Fleet then the Cadre will make the decision on who will be the next Expedition Fleet CO.
3. If the Expedition Fleet CO is unavailable, contact can be made with Expedition Fleet by emailing cadre[at]expeditionfleet[dot]org. At least one member of the Cadre will be available to respond to the Bravo Fleet Admiralty.
4. Expedition Fleet is not subject to the Bravo Fleet Judge Advocate General.
The Expedition Fleet Cadre is responsible for creating and enforcing rules within Expedition Fleet as they and/or the EFCO see fit. The up to date bylaws can be found at Expedition Fleet Community.
1. Per Article II.3.2 of the Bravo Fleet constitution, members of EF "have the same rights and responsibilities as BF players" in general, however certain BF player rights are not applicable in EF. Specifically:
  1. Notwithstanding BF Constitution III.1.1 and III.1.14, EF and its players are not subject to JAG
  2. Notwithstanding BF Constitution III.1.2, some BF by-laws are specific to BF core and therefore are not applied at all to members of EF
  3. Notwithstanding BF Constitution III.1.3, EF has a separate chain of command from Bravo Fleet
  4. Notwithstanding BF Constitution III.1.6, EF does not require its players to post once per week
  5. Notwithstanding BF Constitution III.1.10, EF has canon distinct from Bravo Fleet and operates in a parallel universe splitting from BF due to events that did not take place in the standard timeline, therefore BF canon changes to not apply to the EF universe.
This by-law is deemed to have taken effect on April 2nd, 2009.

Sister Fleet By-laws (5)

None at this time.

BF Bylaws