Difference between pages "Guide:Starbase Bravo Rules" and "Starbase Bravo Mission Briefings"

Revision as of 09:36, 10 August 2023

This article is an Out of Character article relevant to Starbase Bravo.

Missions aboard Starbase Bravo always have been, and continue to be, member-led. Typically, SBB's quarterly missions offer opt-in suggestions or background events that players can participate in over months at a time. No one member's stories, or mission scenarios, cause enough disaster or chaos to interfere with every other player's ability to write about any subplot or personal story of their choice.

In addition to the overarching missions of 2401, Q2 introduced Mission Briefings. Each briefing is a unique story concept developed by the Academy department in partnership with the Intelligence and Operations departments. Mission Briefings identify scenarios, antagonists, locations and mission objectives that should be included and accomplished within each mission. Groups of players can claim each of the Mission Briefings and they will have dedicated Starbase Bravo missions created for posting their relevant stories. Each mission's outcome will be decided by the members telling the stories themselves, given considerations and options usually provided by the Academy department.

2401 Q2 Mission Briefings

Gomthree Has Something to Say

Gomthree, the offspring of Gomtuu, is one of the more wondrous neighbours of Starbase Bravo. With a migratory route that takes it between the Paulson Nebula and the Mellstoxx System, attempts at communication have been authorised. A science team is currently exploring telepathic communication with Gomthree, an attempt that has yielded some... unexpected results.

Briefing: You must assemble a team to complete a science mission to attempt communication with Gomthree during its migratory route. (One of your team members should include a Starfleet officer from a telepathic species.) However, even though Gomthree appears to be a creature of habit, and thus far has used the same route to travel, this time it has not. It has deviated from its normal course and your orders have changed to find out why, and whether Gomthree is in danger.

Conscientious Objection

After the horror of Frontier Day in 2401, there’s a lot of cleaning up to do. Rather than breaking out the mops and buckets, a crack team of medical, science, engineering or security officers have been tasked with implementing the transporter treatment developed by Starfleet Command to remove the Borg DNA from all the younger officers aboard Starbase Bravo. But some aren’t so willing to step onto the pad...

Briefing: You must assemble a team of officers assigned to the Borg DNA removal team, with specialities in a combination of medical, science, engineering, and security. Given the nature of the threat and with the recent events fresh in everyone’s minds, this is a high-stress assignment, and all four departments are working closely together to ensure the mission is completed quickly. However, much to your team’s surprise, there are some young officers that are refusing treatment...

Liberated Pursuit

Since the preparations for Frontier Day, a pack of six Tosk have been seen passing through the Promenade. The Operations department and Diplomatic Affairs have no records of them booking transport to, nor registering quarters aboard, the starbase. The Tosks' interactions with the starbase crew has been secretive and respectful in their search for food, information and passage on transport back to the Gamma Quadrant. However, without intergalactic currency or identification credentials, they have been frustrated by their limited success.

After Frontier Day, a starship of more than a dozen of the Tosk's militarized Hunters arrived at Starbase Bravo. Their search of the Promenade was similarly respectful, if frustrated, when they could not locate any of the Tosk. The Hunters remained in public areas and followed all of Starfleet's security protocols for the first couple of days until they caught sight of their first Tosk. Since then, the Hunters have drawn their concealed energy crossbows and begun firing them right through the crowded promenade to hunt the Tosk pack!

Briefing: You must assemble a cross-functional first response team to protect the promenade from becoming collateral damage between the Hunters and the Tosk. The team may include security, medical or maintenance department officers as first responders to the Hunters openly attacking the Tosk on the promenade. Also consider assigning deck officers, diplomatic officers, intelligence officers or social sciences officers to negotiate with the Hunters and/or the Tosk into safely parting Starbase Bravo for good!

First Contact In Practice

Operating out of a starship bridge simulator aboard Starbase Bravo, a team of Starfleet Academy cadets have been assigned a week-long simulation of a first contact scenario. Day one begins with encountering a warp-capable starship crewed by an unfamiliar insectoid species whose name translates to Loxypha in Federation Standard. As the cadets commence formal negotiations with the Loxypha, the commissioned officer observing the simulation notices that the holographic Loxypha aren't behaving the way they were programmed to behave!

Briefing: You must assemble a crew of cadets from the Mellstoxx III Starfleet Academy to participate in the simulation as a bridge crew, engaging in a mission of first contact. These cadets may be members of Cadet Squadron Bravo or a combination of cadets from different years and classes. Between one and three commissioned officers can also be assigned to oversee the simulation. With an appropriate specialty, one of the officers may be evaluating the cadets' performance in the simulation, and the others will be acting as observers, invigilators or mentors to the cadets. However, remember that the cadets are in command of the simulation starship. The commissioned officer (or, if no commissioned officers participate, the cadet commanding officer) will investigate why the simulation has gone off-script and must decide if they will tell the cadets about the malfunction or allow them to continue first contact.

@@ Line 1: / Line 1: @@
-The purpose of this guide is to set community expectations for participation in Starbase Bravo. For information on how to join and how to post, consult the [[Guide:Starbase Bravo|Starbase Bravo guide]].
+''This article is an Out of Character article relevant to [https://bravofleet.com/command/34941/ Starbase Bravo].''
-== Citizenship Guidelines ==
+Missions aboard [[Starbase Bravo]] always have been, and continue to be, member-led.  Typically, SBB's quarterly missions offer opt-in suggestions or background events that players can participate in over months at a time.  No one member's stories, or mission scenarios, cause enough disaster or chaos to interfere with every other player's ability to write about any subplot or personal story of their choice.
-# We will not always agree on everything, but when we do disagree it’s important that those disagreements are handled respectfully. It’s also essential that when a moderator (generally, a voting member of the BFC) asks for a discussion to stop, it stops.
+In addition to the overarching missions of 2401, Q2 introduced Mission Briefings.  Each briefing is a unique story concept developed by the Academy department in partnership with the Intelligence and Operations departments.  Mission Briefings identify scenarios, antagonists, locations and mission objectives that should be included and accomplished within each mission.  Groups of players can claim each of the Mission Briefings and they will have dedicated Starbase Bravo missions created for posting their relevant stories.  Each mission's outcome will be decided by the members telling the stories themselves, given considerations and options usually provided by the Academy department.
-# Bravo Fleet’s Non-Discrimination and Harassment policy applies to every interaction you have as a member of this organization, whether it occurs directly on the fleet's server or not, so please be courteous and respectful in your interactions with your fellow authors.
-# Membership on the Bravo Fleet Discord server is required to participate in Starbase Bravo.
-# Unsolicited negative/"critical" feedback of others' writing is not appropriate.
-== Content Guidelines ==
+== 2401 Q2 Mission Briefings ==
-Content written for Starbase Bravo must comply with the lore policy, which allows for a broad range of stories and interactions.
-# Content written for Starbase Bravo must comply with the [[Loremaster Policy|lore policy]], which allows for a broad range of stories and interactions. Consult the [[Bravo Fleet Timeline]] or the [[Starbase Bravo|Starbase Bravo in-character article]]. for more information on our specific canon setting.
+=== Gomthree Has Something to Say ===
-# The Intelligence Officer has the final say on what content is appropriate for any Bravo Fleet story, so if you have a question about this policy, you may wish to consult with them before posting.
+[[Gomthree]], the offspring of [[ma:Gomtuu|Gomtuu]], is one of the more wondrous neighbours of Starbase Bravo. With a migratory route that takes it between the [[Paulson Nebula]] and the [[Mellstoxx system|Mellstoxx System]], attempts at communication have been authorised. A science team is currently exploring telepathic communication with Gomthree, an attempt that has yielded some... unexpected results.
-# Proofreading is encouraged as a courtesy to your fellow authors, and posts that are unintelligible or gibberish may be removed by the Intelligence Officer. With that being said, it's never appropriate to mock someone for spelling or grammar "mistakes."
-# Posts are encouraged to be in third-person prose, from a past perspective.
-# Do not use other people's characters without permission. Ask for a joint post instead, especially given that the point of this sandbox is to encourage interaction! With that being said, if you wish to hold a senior role on the station, it's expected that you should be reasonably open to joint post requests.
-## It's rude to start a joint post without first asking if the player owning the character wishes to write with you.
-## Try to respond to a tag within 48 hours, or at least reach out to the other author(s) to discuss your situation. Repeatedly agreeing to joint posts and then leaving other authors hanging could result in a warning, as described later in the retention section, but we understand that life happens so just communicate!
-## Department Head characters are more like special guest stars or recurring characters than active participants in most plots, and these positions are held by senior fleet staff. If you ask in advance, and have a compelling story reason for doing so, they may allow you to use their characters for very minor interactions—just ask!
-## It is okay to ''reference'' other characters, though, especially the station's senior staff, as long as you aren't implying actions not consistent with their biographies.
-# Do not alter the environment of the station without permission from staff, which would include any event that would impact characters outside of the post you are writing. Examples include station-wide illnesses, major security threats, severe accidents, or anything that would likely result in the station's senior-most staff needing to be informed about it. This ensures that anyone can join at any time without needing to take into account the actions of every writer—and keeps our sandbox intact for everyone to enjoy.
-=== Explicit Content Rating ===
+''Briefing'': You must assemble a team to complete a science mission to attempt communication with Gomthree during its migratory route.  (One of your team members should include a Starfleet officer from a telepathic species.) However, even though Gomthree appears to be a creature of habit, and thus far has used the same route to travel, this time it has not. It has deviated from its normal course and your orders have changed to find out why, and whether Gomthree is in danger.
-Starbase Bravo is rated 111 on the [https://rpgrating.com/create RPG Ratings Scale,] which is intended to be suited to members as young as 13, the minimum age to be a part of Bravo Fleet. This means that references to violence, cursing, and sex should be no more graphic than they are on shows such as ''Star Trek: The Next Generation'' and ''Star Trek: Discovery''. '''When writing with others, always ask before writing content that includes swearing, sex, or violence. Posts that do not follow these guidelines may be deleted at the Intelligence Officer's discretion.'''
-# '''Language: Infrequent, mild swearing is permitted.'''
+=== Conscientious Objection ===
-## Mores differ on how much swearing is appropriate, and different regions treat different expletives differently (c.f. The word ‘cunt’ in American English vs most of the Commonwealth countries’ regional Englishes.) so this policy will be enforced with grace, but, unfortunately, is an instance where American English will serve as the standard, as that is the dialect most prominent in Star Trek.
+After the horror of [[ma:Frontier_Day|Frontier Day]] in 2401, there’s a lot of cleaning up to do. Rather than breaking out the mops and buckets, a crack team of medical, science, engineering or security officers have been tasked with implementing the transporter treatment developed by Starfleet Command to remove the [[ma:Assimilation#DNA_modifications|Borg DNA]] from all the younger officers aboard Starbase Bravo. But some aren’t so willing to step onto the pad...
-## Picard brought us the first instances of “fuck” in Star Trek, which is the limit of how crass one should be on SBB, but it should be extremely infrequent.
-### Generally speaking, fuck should be used to express exasperation not to describe sexual behavior. “Fuck!” versus “He fucked him.” Use your common sense, here.
-## Keep in mind that Starfleet officers, while explicitly not part of any military, are disciplined professionals. Regular swearing on duty is not something that would happen, and it’s likely something that could have (mild) in-character consequences.
-# '''Sex: Mild sexual innuendo and references permitted.'''
-## This is not Game of Thrones but we’re also not the Brady Bunch. If are referencing sex, consider why you are doing so and what it’s adding to a particular scene.
-## References to specific sexual acts should generally be avoided (and, again, think about why you would make them at all) but you don’t have to pretend a couple is celibate either. Fade to black when Star Trek would.
-### “You were great last night.” ← OK. It references sex (maybe), but doesn’t get too specific.
-### “He [blanked] my [blank] in the Jefferies tube.” ← Pushing it, as it’s a reference, not a description.
-### “The two of them [adverb] [sex act verb] each other, starting with their [adjective] [body part, pl.], and working down to the [body part]...” ← Just no.
-## This restriction is not meant to be regressive or prudish in nature, but to make sure that our content is appropriate for all members. Sex and love are great–and our characters are sentient beings who are likely having it. We don’t have to ignore that, but we also don’t need to read the play-by-play of your cybering.
-## Sexual violence is never appropriate content for this sandbox.
-# '''Violence: Mild violence is permitted'''
-## One of the great things about energy weapons is that they don’t tend to leave gruesome wounds. Either it stuns, kills, or vaporizes a being entirely. As this is what we deal with most, leaving the description to ‘a dead body’ is sufficient, as there wouldn’t be maiming and that sort of thing. There’s just no need to go into a lot of blood and gore to get the point across, because that’s not a normal feature of the genre.
-### That being said, why would there be a dead body on Starbase Bravo at all?
-## Phaser fire fights are to be expected when the story calls for them, keeping the above in mind.
-### Probably unlikely to occur off of the holodeck or in training scenarios in the heart of the Federation, though.
-## There shouldn’t be references to or uses of modern day firearms, on the holodeck or not.
-## Self-harm, sexual violence, and domestic violence are not appropriate content for this sandbox.
-== Player Retention and Removal ==
+''Briefing'': You must assemble a team of officers assigned to the Borg DNA removal team, with specialities in a combination of medical, science, engineering, and security. Given the nature of the threat and with the recent events fresh in everyone’s minds, this is a high-stress assignment, and all four departments are working closely together to ensure the mission is completed quickly. However, much to your team’s surprise, there are some young officers that are refusing treatment...
-Membership on Starbase Bravo is open to all, but it is a privilege not a right and can be revoked in certain circumstances.
-# Members who AWOL out (i.e. are inactive for sixty days or more) will have their characters removed from the sandbox. While this will not prevent someone from re-applying when they rejoin or force them to re-earn the tier they last had when they return to active status, it does open any restricted positions back up for grabs. This is to keep people from hoarding important roles.
+=== Liberated Pursuit ===
-# Members who break the rules listed here or other fleet policies may be removed from Starbase Bravo through the collective judgement of the Intelligence Officer and Operations Officer.
+Since the preparations for Frontier Day, a pack of six [[ma:Tosk_(species)|Tosk]] have been seen passing through the Promenade.  The Operations department and Diplomatic Affairs have no records of them booking transport to, nor registering quarters aboard, the starbase.  The Tosks' interactions with the starbase crew has been secretive and respectful in their search for food, information and passage on transport back to the Gamma Quadrant.  However, without intergalactic currency or identification credentials, they have been frustrated by their limited success.
-## Content or Citizenship Offenses not rising to the level of a magistrate complaint will be handled administratively based on the number of offenses. Members may appeal to the Bravo Fleet Executive Officer if they feel their conduct has been unfairly judged.
-### Initial Offense: Warning
+After Frontier Day, a starship of more than a dozen of the Tosk's militarized [[ma:Hunter|Hunters]] arrived at Starbase Bravo.  Their search of the Promenade was similarly respectful, if frustrated, when they could not locate any of the Tosk.  The Hunters remained in public areas and followed all of Starfleet's security protocols for the first couple of days until they caught sight of their first Tosk.  Since then, the Hunters have drawn their concealed energy crossbows and begun firing them right through the crowded promenade to hunt the Tosk pack!
-### Second Offense: Removal and 30 day probation on re-applying
-### Third Offense, following reinstatement: Removal and 60 day probation on re-applying.
+''Briefing'': You must assemble a cross-functional first response team to protect the promenade from becoming collateral damage between the Hunters and the Tosk.  The team may include security, medical or maintenance department officers as first responders to the Hunters openly attacking the Tosk on the promenade.  Also consider assigning deck officers, diplomatic officers, intelligence officers or social sciences officers to negotiate with the Hunters and/or the Tosk into safely parting Starbase Bravo for good!
-## Content or Citizenship Offenses rising to the level of a magistrate complaint will be referred to the Magistrate, with the member suspended from Starbase Bravo pending the conclusion of any proceedings.
+=== First Contact In Practice ===
+Operating out of a starship bridge simulator aboard Starbase Bravo, a team of [[Starfleet Academy]] cadets have been assigned a week-long simulation of a [[ma:First_contact|first contact]] scenario.  Day one begins with encountering a warp-capable starship crewed by an unfamiliar insectoid species whose name translates to Loxypha in Federation Standard.  As the cadets commence formal negotiations with the Loxypha, the commissioned officer observing the simulation notices that the holographic Loxypha aren't behaving the way they were programmed to behave!
+''Briefing'':  You must assemble a crew of cadets from the [[Starfleet Academy—Mellstoxx III|Mellstoxx III Starfleet Academy]] to participate in the simulation as a bridge crew, engaging in a mission of first contact.  These cadets may be members of Cadet Squadron Bravo or a combination of cadets from different years and classes.  Between one and three commissioned officers can also be assigned to oversee the simulation.  With an appropriate specialty, one of the officers may be evaluating the cadets' performance in the simulation, and the others will be acting as observers, invigilators or mentors to the cadets.  However, remember that the cadets are in command of the simulation starship.  The commissioned officer (or, if no commissioned officers participate, the cadet commanding officer) will investigate why the simulation has gone off-script and must decide if they will tell the cadets about the malfunction or allow them to continue first contact.