Roleplaying Game Policy

From Bravo Fleet
This article is official Bravo Fleet Official Policy.

This policy is governed by the Operations Office, and any questions should be directed to the Bravo Fleet Operations Officer.

1.0 - Introduction

  1. A roleplaying game (RPG) is a standing group of two or more members writing together in a formalized manner using a registry item (such as a starship or station). These groups have more oversight than informal or ad hoc collaborative writing to ensure that the rights of all members are protected and to regulate how these groups are proposed and granted.
  2. Roleplaying Games fall under the Operations Office, and this policy is maintained by the Bravo Fleet Operations Officer.
  3. Roleplaying Games operate directly on the Bravo Fleet Management System, with out-of-character interactions provided via a fleet-owned stand-alone Discord server.

2.0 - Game Managers

  1. Every RPG is led by a game manager (GM), who has overall responsibility for both the story and administration of their game.
  2. GMs have the final say over recruiting and dismissing members from their game, within the bounds of the fleet’s non-discrimination policy.
  3. GMs have the responsibility to ensure that their games are a respectful space for all members, which includes moderating out-of-character discussions, and seeking appropriate interventions from fleet staff when necessary.

2.1 Game Manager Eligibility

  1. Game Managers must hold the fleet rank of Lieutenant Commander or higher, must have a primary command, and must have earned at least 20 Service Ribbons.
    1. The Bravo Fleet Operations Officer may grant an exception to this rule for a member of a game who has volunteered to run that game upon the resignation or removal of the previous GM.
  2. Game Managers must be active members of the fleet, i.e. not in the Reserves.
    1. Game Managers who enter the Reserves, whether voluntarily or through the automated AWOL system, will immediately lose their game.
  3. Game Managers agree to follow this policy, all other Bravo Fleet policies, the Bravo Fleet Charter, and the Bravo Fleet Magistrate Code as a condition of their appointment, which includes acknowledging:
    1. A game may be passed to another member following a GM’s resignation or removal, including its name, registry number, history, past or present missions, and any other assets; and,
    2. Decisions about player retention, recruitment, and removal must comply with Bravo Fleet’s non-discrimination policy.

2.2 Game Manager Appointment

  1. Game Managers are appointed by the Bravo Fleet Operations Officer, following the approval of an appropriate proposal or application as detailed in section 4 of this policy.
  2. In the event of a game manager’s resignation or removal, the Bravo Fleet Operations Officer may allow a member of a game to take over as Game Manager, but this is not an automatic process and that appointment may be contingent on meeting other criteria.

2.3 Game Manager Removal

  1. The Bravo Fleet Operations Officer may remove game managers in the following circumstances:
    1. Failure to participate in one’s own game for 60 days or more when not on LOA, as evidenced through replying to an in-progress joint post or publishing a post;
    2. Failure to respond to communications from the Operation Office related to the GM’s RPG within 72 hours when not on LOA;
    3. Failure to maintain active Bravo Fleet membership, as per section 2.1.2.a of this policy;
    4. Failure to comply with the Bravo Fleet Canon Policy and/or their game’s original proposal and/or activity plan (e.g. changing the name or class of their game without permission or moving to a different time period without permission.); or,
    5. Failure to comply with other sections of this policy.

2.4 Game Manager Cooling-Off Periods

  1. Game Managers who resign will not be eligible for an appointment as the GM to a new game for 60 days following their resignation.
  2. Game Managers who are removed will not be eligible for an appointment as the GM to a new game for 120 days following their removal.

2.5 Game Manager Leaves of Absence

  1. Game Managers who anticipate being out of contact for longer than 72 hours should inform the other members of their games and the Operations Office that they have taken a Leave of Absence (LOA).
  2. Leaves of Absence must include a set return date.
  3. Leaves of Absence 14 days or longer should clearly designate who is running the game during the GM’s absence, or if the game is going on hiatus.
  4. Leaves of Absence longer than 60 days are not permitted; GMs needing breaks of this long should instead resign and propose a new game when their schedules allow.
  5. GMs who do not return within 72 hours of their stated return date are subject to removal under section 2.3.b of this policy.

2.6 Assistant Game Managers

  1. Assistant Game Managers (AGMs) assist a GM in running a game.
  2. AGMs are appointed by and may be removed by a GM at will.
  3. AGMs need not hold senior in-character positions on their game.
  4. AGMs neither are automatically eligible to succeed their GM to take over a game nor have any particular standing or authority in the fleet beyond their role on their game.

3.0 Players

  1. Players are those members who write on an RPG.
  2. Any active member of Bravo Fleet may apply to any game.
    1. Members who enter the Reserves, whether voluntarily or through the automated AWOL system will immediately lose their positions on any games they are part of. Upon resuming active status, they may re-apply to the games they were on, but acceptance is not guaranteed.

3.1 Player Applications

  1. Members may apply to join games through the BFMS.
  2. GMs should keep an accurate account of which positions are open for application on their Command’s listing.
  3. For the best chance of success, members should consult with a prospective GM before applying to see what sort of writing sample is requested, what positions are available, and what they are looking for in terms of a character biography.
  4. Games may have narrower requirements than the Canon Policy, which could include restrictions on certain species, abilities, or backgrounds for characters, but may not allow things that would otherwise be forbidden by that policy. That is to say, a game may be more restrictive than the canon policy but not less restrictive.

3.2 Player Removal

  1. GMs may remove any player at any time for any reason that does not violate the Non-Discrimination Policy. This could include lack of posting, quality of posting, and/or out-of-character interactions.
  2. GMs who remove a player should inform the Operations Office upon removing a player, so the fleet can be aware of any potential problems.

4.0 Game Proposals

  1. Any member eligible to run a game (as described in section 2.1 of this policy) may propose either a custom game or a pre-made game.
  2. Game Proposals should be submitted through the BFMS; members are encouraged to contact the Operations Office in advance to discuss their proposal. Members are encouraged to read the RPG Proposal Guide to assist them in their creation. This will be used/referred to as part of the Operations Officer's response to the proposal.
  3. Custom Game proposals should clearly articulate three distinct mission ideas, describe how the proposed game would fit in with the fleet’s other offerings, justify the use of the proposed registry item, and prove that the concept has been developed well enough to survive in action.
  4. Pre-Made Game proposals should identify which concept from the premade games bank is being selected, at least one mission beyond the one specified for that concept, and a detailed explanation of both why the potential GM is selecting the concept and how they see it working in practice.
  5. Proposals for games set in Bravo Fleet’s primary era must use an existing registry item if an item for that class already exists and is available.
    1. Proposals for games set outside of Bravo Fleet’s primary era may propose a brand-new registry item.
    2. The use, alteration, or creation of any registry item is at the discretion of the Bravo Fleet Intelligence Officer.
  6. Proposals will be reviewed first by the Bravo Fleet Operations Officer and then by the Bravo Fleet Intelligence Officer, either of whom may request revisions.
  7. Games proposed using the pre-made game concepts bank will be assigned a mentor from the Operations Office for the duration of their first mission (the mentorship period) during which that representative is empowered as a co-Game Manager.

5.0 Activity Classifications

  1. Games are listed as Active, Long-Form, Provisional, or Inactive. These classifications help members identify which games are a good fit for their play-style and time commitments.
    1. Active games:
      1. Have at least two players, including the GM;
      2. Have existed for at least two months; and,
      3. Have an activity plan which requires at least two posts per player per month.
    2. Long-Form games:
      1. Have at least two players, including the GM;
      2. Have existed for at least two months; and,
      3. Have an activity plan which requires less than two posts per player per month.
    3. Provisional games:
      1. Have less than two players, including the GM;
      2. Have existed for less than two months; or,
      3. Are a pre-made game still in its mentorship period.
    4. Inactive games:
      1. Are on hiatus; or
      2. Lack a GM.

6.0 Activity Plans

  1. Each GM must set an activity plan in consultation with the Operations Office, which should state how many posts a game is planning on writing per month, how many players it is hoping to retain, how many missions a game is planning per year, whether a game is long-form or active. and what the rough proportion of solo to joint posts will be expected. For example:
    1. “The USS Enterprise is an active game, which expects at least four posts per player per month, and is hoping to maintain a crew of between six and twelve players, for a range of between 24 and 48 posts per month. These will be a mix of joint and solo posts, spread over approximately six missions per year.”
    2. “The USS Voyager” is a long-form game, which expects at least one post per player per month on average, and is hoping to maintain a crew of between four and six players, for a range of between four and six posts per month. These will be predominantly joint posts, spread over approximately two missions per year. There may be breaks in our activity between missions, lasting no more than 60 days each without prior approval from the Operations Office.”
  2. RPGs that need to take temporary breaks from their activity plans should request a change in status to Inactive, with the agreement of the Operations Office, to go on Hiatus.
  3. RPGs that do not fulfill their activity plans are subject to closure.

7.0 Content Ratings

  1. Game Managers must abide by the content rating guidelines established in section 6 of the Canon Policy.
  2. Game Managers may not admit players who are younger than 16 for any RPG with a two in any category of their rating.
  3. If a game breaks any of the restrictions outlined in this section, Bravo Fleet Command reserves the right to remove the Game Manager and delete the content which caused the violation.