Roleplaying Game and Sandbox 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. Defining RPGs and Sandboxes: Roleplaying Games (RPGs) and Sandboxes are both opportunities for members to engage in our shared canon universe together through the use of a registry item (such as a starship or station) and some formal structure for their collaboration.
2. Purpose: Bravo Fleet RPGs are regulated by set rules and guidelines to ensure that the rights of all members are protected and that everyone involved can enjoy them. Less formal collaborative partnerships are permitted under the Command Policy.
3. Listings: All Bravo Fleet RPGs and Sandboxes are listed on the Bravo Fleet Management System.
4. Communication: All Bravo Fleet RPGs use Discord services for out-of-character interactions. Bravo Fleet will own these assets (e.g., the server, category or channels where they are located).
5. Scope of Policy: Roleplaying Games and Sandboxes fall under the Operations Office, and the Bravo Fleet Operations Officer maintains this policy.

2.0 Writing RPGs

1. Definition of a Writing RPG: A Writing RPG is a standing group of two or more members writing together on the BFMS in a formalized manner using a registry item to tell a set of stories through joint writing.
   1. Each Writing RPG is directed by a Game Manager (GM) who regulates the plot's focus and development through a series of missions.
   2. Players create characters they write for and interact with other players’ characters within missions.
2. Platform for Writing RPGs: Only the BFMS may be used for writing RPGs.
3. Activity Plans: Each Writing RPG has a set activity plan formally explaining its operation. Within the activity plan, the Written RPG will define:
   1. How many stories each player is expected to create and share on BFMS per month:
   2. How many missions it plans to achieve over one (1) year;
   3. How many players it hopes to maintain;
   4. And what additional expectations (if required) players must abide by (e.g. certain species allowed, how a plot and/or subplot can be developed).
      1. See Section 2.4 for an example of Activity Plan.

2.1 Writing RPG Game Managers

1. Every RPG is led by a game manager (GM).
2. GMs are responsible for the following:
   1. The development of the RPG’s missions.
   2. The recruitment and dismissal of players.
   3. The appointing of an Assistant Game Manager (AGM), if required.
   4. Providing all members that join as players a respectful space for them to enjoy, which includes moderating out-of-character discussions and seeking appropriate interventions from fleet staff when necessary.

2.1.1 Writing RPG 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.
3. Game Managers agree to follow this policy, all other Bravo Fleet policies, the Bravo Fleet Charter, and the Bravo Fleet Judicial Code as a condition of their appointment, which includes acknowledging:
   1. An RPG 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. All decisions about player recruitment, retention, and removal must be in compliance with the Bravo Fleet Charter and Bravo Fleet Judicial Code.

2.1.2 Writing RPG 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 2.2 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.1.3 Writing RPG Game Manager Removal

1. The Bravo Fleet Operations Officer may remove a GM in the following circumstances:
   1. Failure to participate in one’s own RPG for 60 days or more when not on LOA, by not replying to an in-progress joint post or publishing a post within that window;
   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 comply with the Bravo Fleet Canon Policy, with their RPG’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.) and/or guide and/or rules or;
   4. Failure to comply with other sections of this policy.
2. Failure to maintain active Bravo Fleet membership and being sent to the Reserves either voluntarily or through the AWOL system will result in automatic removal.

2.1.4 Writing RPG Game Manager Cooling Off Period

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

2.1.5 Writing RPG Game Manager Leaves of Absence

1. GMs will follow a similar model of declaring a Leave of Absence (LOA) to the Leave of Absence Policy.
2. GMs will declare their LOA in the GM Lounge and within the general channel for their RPG.
3. The GM can appoint a designated player (usually the Assistant Game Manager) to manage the RPG in the GM’s absence; the GM will inform the Operations Office of who this is, or the GM can propose to set the RPG on hiatus status with consent from the Bravo Fleet Operations Officer.
4. LOAs longer than 60 days are not permitted; GMs needing breaks of this long should instead resign.

2.1.6 Assistant Game Managers

1. Assistant Game Managers (AGMs) assist a GM in running a game if the GM wishes to appoint an AGM.
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 are neither 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.
5. There is only one AGM per RPG. No other senior management/leadership role is required in running an RPG.

2.2 Writing RPG Proposals

1. Any member eligible to run a Writing RPG (as described in section 2.1.1 of this policy) may propose either a custom game or a pre-made RPG.
2. Writing RPG 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.

2.3 Writing RPG Activity Classifications

1. Writing RPGs are listed as Active or Inactive.
   1. Active:
      1. Have at least two players, including the GM;
      2. Have an activity plan or guide and rules that determine how players can/must interact with the setting.
      3. Regular activity is published on the BFMS.
   2. Inactive RPGs:
      1. Are on hiatus;
      2. Lack a GM;
      3. No regular activity is published on the BFMS.

2.4 Writing RPG 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 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. 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.

2.5 Writing RPG Content Ratings

1. All Writing RPGs and Sandboxes must abide by the content rating guidelines established in the Content Policy.
2. GMs may not admit players younger than 16 for any RPG or Sandbox with a two in any rating category.
3. If a game breaks any of the restrictions outlined in this section, the Bravo Fleet Operations Officer reserves the right to remove the GM and will have the content which caused the violation deleted from the BFMS.

3.0 Tabletop Roleplaying Games

1. Definition of a Tabletop RPG: A Tabletop RPG (TTRPG) is a standing group of two or more members playing a tabletop roleplaying game (such as Star Trek: Adventures) set on a registry item. They engage regularly over a specific communication platform.
   1. TTPRGs are overseen by a Game Manager who directs the players through their mission.
   2. Players determine the actions of their characters based on their characterisation, and the actions succeed or fail according to a set formal system of rules and guidelines. Within the rules, players have the freedom to improvise; their choices shape the direction and outcome of the game.

Each TTRPG will have an agreed-upon set of rules either from published materials or from a custom system, which must be clearly identified on that TTRPG's BFMS page.

1. Each TTRPG will display on BFMS how members can join and how they can engage with the RPG.
2. Each TTRPG should set a schedule convenient for the GM and the players.

3.1 TTRPG Game Managers

3.1.2 TTRPG Game Manager Eligibility

1. Game Managers must hold the fleet rank of Lieutenant Commander or higher, and must have a primary command.
   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.
3. Game Managers agree to follow this policy, all other Bravo Fleet policies, the Bravo Fleet Charter, and the Bravo Fleet Judicial Code as a condition of their appointment, which includes acknowledging:
   1. An RPG 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. All decisions about player recruitment, retention, and removal must be in compliance with the Bravo Fleet Charter and Bravo Fleet Judicial Code.

3.1.3 TTRPG Game Manager Appointment & Removal

1. The appointment, removal, and LOA policies for TTRPG GMs are the same as those for Writing RPG GMs listed in sections 2.1.2, 2.1.3, 2.1.4, and 2.1.5 of this policy.

3.2 TTRPG Proposals

1. TTPRGs are proposed through the BFMS and the proposal should state what materials will be used to set the rules and setting, how often players will meet to play the game and what platform of communication players will use to interact with one another. Otherwise, the process for proposing a TTRPG is the same as the process for proposing a custom Writing RPG, as outlined in section 2.2 of this policy.

3.3 TTRPG Activity Standards

1. TTRPGs are expected to have at least one session every two months, and more frequent meetings are encouraged.

3.4 TTRPG Content Ratings

1. TTRPGs must select a rating under the Content Policy to set the expectations for the type of content members may expect during a play session, and they must stick to these ratings even for verbal and other non-written content.
2. Ahead of play, GMs must engage with members on the game's content rating, as outlined in the Content Policy. This includes not only agreement on the TTRPG's rating level but also discussion and consensus on the depiction of restricted topics or other topics that members or the GM may wish to exclude. This engagement should be a reciprocal opportunity for members, including the GM, to establish boundaries and thus engage in the game without fear of experiencing or causing discomfort. TTRPGs are held to this standard due to the immediate nature of the format, where a topic may arise mid-play, giving a member less opportunity to discuss any discomfort.

4.0 Writing Sandboxes

1. Definition of a Writing Sandbox: A Writing Sandbox is an open setting for members to write together on the BFMS in low-stakes, informal collaborative ways, where pick-up and ad-hoc joint writing is the central focus area. Members are able to join sandboxes with minimal prerequisites that vary from sandbox to sandbox. Sandboxes are assigned to either Operations or another department. Writing Sandboxes use a registry item.
   1. Writing Sandboxes are managed and developed by a Bravo Fleet Department, with its head having overall oversight in a similar capacity as a Game Manager.
2. Each sandbox has a set guide and rules that formally explain its operation.
   1. Guides must include how players can join and what and how to write in the sandbox.
   2. Rules must include Citizenship Guidelines, Content Guidelines (including content rating), Player Retention and Removal

4.1 Writing Sandbox Management

1. Unlike other RPGs, Writing Sandboxes are managed by a specific department. As such, it will become an addition to that department’s responsibilities in overseeing it. The Department Head will take the lead on this or delegate that task to a staff member.
   1. The Department Head may appoint staff members to aid in the management of the Sandbox at their discretion
2. With the Operations and Intelligence Offices, the department with oversight of the sandbox will review the maintenance and canon development for that specific sandbox if and when it is required.

4.2 Writing Sandbox Content Ratings

1. All writing sandboxes must abide by a 111 rating.

4.3 Writing Sandbox Creation

1. Writing Sandboxes are created as necessary to meet the needs of the organization.

5.0 Players

1. Players are those members who engage in an RPG or a Sandbox.
2. Only active members may apply to join an RPG or a Sandbox.
3. Members who enter the Reserves voluntarily or through the automated AWOL system will immediately lose their positions on any RPG and Sandbox they are part of. Upon resuming active status, they may re-apply to the games they were on, but acceptance is not guaranteed.

5.1 Player Applications

1. Members may apply to join RPGs and Sandboxes through the BFMS.
2. GMs/DHs should keep an accurate account of which positions are open for application on BFMS.
3. Members should consult the prospective GM before applying to understand how players engage and interact with the RPG for the best chance of success. Members should also read the RPG's activity plan or Sandboxe's guide and rules.
4. Some RPGs and Sandboxes may have narrower requirements, including restrictions on specific species, abilities, or backgrounds for characters, but may not allow things that the Intelligence Policy’s canon definitions would otherwise forbid. That is to say, a game may be more restrictive than the Intelligence Policy’s canon definitions but not less restrictive.
   1. Any restrictions based on criteria other than the content of the application, such as rank, having a certain quantity of activity ribbons, or earning a particular set of Bravo Fleet Academy Badges, must be approved by the Operations Officer.

5.2 Player Removal

1. GMs may remove any player at any time for any reason that does not violate Article II, Section 1 of the Bravo Fleet Charter.
   1. Reasons for removal could include the lack of involvement, quality of writing/engagement, and/or out-of-character interactions.
   2. RPGs and Sandboxes may include in their rules or expectations within their activity plans (but not limited to) what may warrant a player being removed from their specific RPG or Sandbox.
2. When a player is removed, this matter should be raised to the Operations Office via the GM-Lounge on the main Bravo Fleet Discord Server upon removing a player so the fleet can be aware of any potential problems.