Difference between pages "Command Policy" and "Policy:Security Office Supported Games"

From Bravo Fleet
(Difference between pages)
(Language clarification on flag stations and squadron strength)
 
(Added sections for battlezones and time-based JARs submissions)
 
Line 1: Line 1:
{{icons|bfo}}Last Update: 25 September 2023
+
Games officially by the Security Office shall be listed here, as per the [[Gaming Policy]].
  
==1 - Registry Definition==
+
== 1 - Star Trek Online ==
#The registry lists all starships, starbases, and other entities available to Bravo Fleet for use as Commands or Games.
+
 
#The registry’s purpose is to maintain consistency across Bravo Fleet and its ongoing canon. As such, entries will not be added to, removed, or altered from the registry without permission of the Intelligence Office.
+
# Bravo Fleet has officially supported in-game fleets for Star Trek Online (STO) on PC (both factions), on XBOX and on PlayStation (Federation Only), which provide members with various resources and perks.
#The registry represents the In Character starships and starbases available to the Fourth Fleet in {{Year}}, and the starships and starbases available to members in their personal writing or the RPGs they play and run. They are represented on BFMS by Games and Commands, which are attached to the dossiers of the members who own them, and house the character biographies of the crew and the Missions and Stories depicting their adventures.
+
# Members may also earn ribbons for STO gaming in factions or on platforms where Bravo Fleet does not maintain an official presence.
##Exceptions such as non-Starfleet ships or ships of a different era have been created for Fictions or Games, and may not be used as Primary Commands. These will be more often added, deleted, or altered.
+
 
##The use of registry entries in Games is governed by Section 4 of the Operations Policy.
+
=== 1.1 - STO In-Game Fleet Management ===
#Ships in the registry should only be used in lore by the members or Task Forces (in the case of TFHQ ships or Flagships only) to which they are assigned. If a story requires another ship, it should use a name not listed in the registry and would fall within the bounds of member canon.
+
 
#Stories may depict ships, including Starfleet ships, not in the registry. These must never be written as the 'main' vessel in a story, and their place in stories must be restricted to minor or supporting roles. The existence and use of these 'NPC' ships constitutes member canon.
+
# Bravo Fleet maintains fleets for the following factions/platforms:
##These ships must always have a name not found in the registry.
+
## PC - Federation - ''Bravo Fleet''
##NPC ships may not be written as assigned to a joint mission alongside a member's ship, and especially not under their command.
+
## PC - Klingon - ''House of yo’ loS''
##These ships should be playing roles like delivering supplies or personnel or being in need of rescue as a story's instigating event. They and their crews should not be recurring, significant dramatic actors in a manner that undermines the Squadron System (Section 3). Members who want to write multiple ships and crews must wait until attaining the fleet rank of Captain.
+
## PlayStation - Federation - ''Bravo Fleet''
#Events involving registry ships ''prior to'' 2399 may be referenced in circumstances such as character service records and backstory. This restriction changes at 2399 as this is when the current fleet canon went live; members should not be dictating fleet or member canon after this outside of their own characters and Command.
+
## XBOX - Federation - ''Alteran Royal Navy Bravo Fleet''
#Fleet canon about a ship is defined by the Intelligence Office or any member who holds that Command. Subsequent members who command a registry ship must adhere to that fleet canon and not retcon or change it without permission from the Intelligence Officer.
+
 
##Fleet canon established by prior commanders is limited to the names of captains and crewmembers and the dates of their assignments, and major points of the ship's activities, such as participation in a fleet-wide storyline or where and when the ship was commissioned. Members are not beholden to retain more minor details of a ship's mission history, design, or configuration. Any pre-2399 history of a command established by a member is member canon and thus may be rewritten or disregarded by any new commander.
+
# Members may join an in-game fleet with one or more in-game characters, also known as “alts” or “toons”, by requesting to do so in the Bravo Fleet Discord channel #sto-char-mgmt.
##The history of registry ships is maintained on their wiki article. Members are free to depict this history as they wish, either retaining original text or rewriting. There is no obligation to mention events or history prior to their command. The only requirement is to retain a list of previous commanders, ''with links to their BFMS Commands'', as seen [https://wiki.bravofleet.com/index.php/USS_Rhyndacus#Notable_Crew here].
+
## Characters that do not log in at least once every six months will be removed from the in-game fleets to ensure there are enough slots for all members.
#Ships are assigned to a member's dossier when they are created as Commands on BFMS. A member must create an application for the Command that the Intel Office processes. The IO does not create Commands for members. Commands exist to house Missions, Stories, and crew rosters; they show the ship on the member's dossier, and ensure the registry displays what ships are available or unavailable. ''All'' ships in use require a Command, including RPGs and squadron ships.
+
## Members who transfer to the Reserves voluntarily or through the AWOL process will have their characters removed from the in-game fleets.
##Once a ship has been relinquished, the BFMS Command will be labelled as 'Archive' and exist on the member's dossier for archival purposes only. Members may edit the Command page or the roster, but they may not add further Missions or Stories.
+
## Character in-game biographies for STO characters are not required, but are encouraged.  
#Members should not apply for Commands on BFMS until they are ready to acquire or change their Primary Command, or for a fiction/RPG proposal to be discussed with the Intelligence Officer/Operations Officer. Draft Commands or proposals self-identifying as WIPs will have their registry link removed or be deleted.
+
# In-Game rank is based off of the rank achieved in Bravo Fleet, though it is not exact due to limitations of the game engine on providing only a set amount of ranks:
#Members may change their assigned Commands once every six months or after they are promoted, whichever comes first. This applies to ''all'' of a member's Commands; if only one ship in a squadron of two is changed, six months must elapse or a promotion must be earned before ''either'' ship can be changed.
+
## All members will get promoted to a rank approximate to their BFMS ranking, with the following levels:
##If a member has not used their full squadron strength entitlement, they may request ships to fill it anytime. However, this resets the Command change cooldown. So long as a member ''can'' request additional ships, they may do so as often as they like, but they may not change those ships until six months have elapsed or a promotion has been earned.
+
### Cadet/Bekk - Cadet ranks
##Exceptions may be permitted at the discretion of the Intelligence Officer. This may apply in cases such as the release of new starship classes or other significant alterations to the command registry.
+
### Junior Officer - Midshipman to Lieutenant
==2 - Primary Commands==
+
### Senior Officer - Lieutenant Commander to Fleet Captain
#Primary Commands are attached to a member's dossiers as their character's starship or auxiliary craft. They are the vessels assigned In Character to a member’s Task Force in the Fourth Fleet in {{Year}}.
+
### Flag Officer - Commodore and Above
#Members can write on their Primary Commands on their own or with others. Writing with others on a Primary Command does not require a proposal or activity commitment being sent to the Intelligence Office. Members ''may not'' use their Primary Command as an RPG; ie, they may not openly recruit for crew or create a separate website, and collaboration should be limited to invitation-only. RPGs which any member of the Fleet may apply to join must be accepted by the Bravo Fleet Operations Officer, and thus Primary Commands are unsuitable for this purpose.
+
## As there is no automated connection to BFMS for ranks, the positions will be audited periodically to update listed ranks
#All Commands will be removed from a member's dossier upon transfer to the Reserves.
+
### If there is a character of yours and you do not see the assigned promotion list please mention in #sto-char-mgmt
#When a member reaches the rank of Midshipman they may request a ship on the registry for use as their Primary Command. Ship classes available are unlocked upon reaching certain ranks.
+
# Permissions for each in-game rank are assigned at the discretion of the Security Office, and all members have access to:
#Members below the rank of Captain may only have one Primary Command. Requesting a new eligible Primary Command will result in the current registry ship being removed from the member's dossier and returned to the pool of available ships.
+
## Purchase from provisioned fleet stores and fleet shipyards
{| class="wikitable" style="margin:auto"
+
## Visit fleet holdings
|+Ship classes by rank
+
## Invite non-members to fleet holdings
 +
## Use of the Fleet Bank, the degree of which is determined based on rank
 +
 
 +
=== 1.2 - STO Awards ===
 +
 
 +
# Bravo Fleet uses the following awards in Star Trek Online:
 +
## Campaign Ribbons
 +
## Joint Action Ribbons
 +
## Combat Action Ribbons
 +
 
 +
=== 1.2.1 - STO Campaign Ribbons ===
 +
 
 +
[[File:STO-Storyarcexample.png|thumb|right|An example of a Mission Journal screenshot, showing the Cardassian Struggle arc is completed.]]# Campaign Ribbons for STO gaming are earned by the following actions per character:
 +
## Reaching Level 65
 +
## Completing Story Arcs in groups as follows:
 +
### Completing the faction specific storyline arcs
 +
### From the end of the faction specific arc to New Romulus
 +
### Solonae Dyson Sphere and Delta Quadrant
 +
### Iconian War, Yesterday's War and Future Proof
 +
### New Frontiers and Gamma Quadrant
 +
### Age of Discovery, J'Ula's Discovery and Klingon Civil War
 +
### All of The Galaxy At Large arcs that have been removed from the main story
 +
## Completing at least three reputations to Level 6
 +
## Completing all the current Admiralty factions to Level 10
 +
## Completing the first individual Duty Officer branch to Level 4
 +
## Completing five Duty Officer branches to Level 4
 +
## Completing at least two Research and Development Branches to Level 20
 +
## Completing each of the primary Specializations (Command, Intel, Pilot, Temporal, Miracle Worker)
 +
## Completing all of the secondary Specializations on one character (Constable, Strategist, Commando)
 +
## Complete a Recruit Transponder (Delta, Temporal, Gamma, Klingon)
 +
# Campaign ribbons can be earned by the following actions once per account:
 +
## Progressively completing 50 levels in the Endeavour system (awarded at 50, 100, 150, et al)
 +
## Progressing and completing one STO Event, to completion of the prize at the end of the event
 +
### This is a repeatable action that can be completed for each event, but can only be used to claim one Campaign Ribbon per event, per account
 +
### This Campaign Ribbon excludes Event Campaigns
 +
## A bonus for specific performance in a gaming-related competition, per that competition's rules
 +
# A qualifying submission for this award should contain a screenshot showing the character's name, level and the activity completed as applicable, as well as the character's name in the gaming activity form's text box.
 +
 
 +
==== 1.2.2 - STO Joint Action Ribbons ====
 +
 
 +
# Joint Action Ribbons for STO gaming are earned by playing Star Trek Online in a group of Bravo Fleet members against environments and sometimes players too.
 +
# Activities include:
 +
## Task Force Operations or Special Task Forces
 +
## Patrols
 +
## Red Alerts
 +
## Daily missions
 +
## Story missions
 +
## Battlezones
 +
# A qualifying submission for this award should contain a screenshot with proof that a qualifying action has been completed.
 +
## Multiple actions of the same type should be submitted as a single submission whenever possible, as long as the same number of participants are in each instance.
 +
## When submitting multiple screenshots of different types of content, each content type (Normal TFOs, Advanced TFOs, Story Missions, etc.) must be submitted separately.
 +
## When submitting for battlezones, since this is a time-based submission, you must provide a screenshot of your start time in the battlezone and a screenshot of the end time. Rewards will be calculated at a rate of 4 Joint Action Ribbons per hour of game play, with one hour minimum being required for submission.  
 +
# Joint Action Ribbons are awarded based on the following formula, where the multipliers change by the table below:
 +
Number of Screenshots x Member Multiplier x Content Multiplier = Total Ribbons
 +
 
 +
{| class="wikitable" style="text-align:center;"
 +
|- style="font-weight:bold;"
 +
! colspan="2" | JAR Member Multipliers
 +
! colspan="2" | JAR Content Multipliers
 +
|- style="font-style:italic; border-color:inherit;"
 +
| Description
 +
| Value
 +
| Description
 +
| Value
 
|-
 
|-
!Midshipman!!Lieutenant Commander!!Commander!!
+
| 2 Members
 +
| 1x
 +
| TFO/STF (Normal), Patrol, Battlezone, or Red Alert
 +
| 1x
 
|-
 
|-
|[[California Class|California]]
+
| 3 Members
|[[Aquarius Class|Aquarius]]
+
| 2x
| colspan="2" |[[Akira Class|Akira]]
+
| TFO/STF (Advanced)
 +
| 2x
 
|-
 
|-
| ||[[Centaur II Class|Centaur II]]|| colspan="2" |[[Defiant Class|Defiant]]
+
| 4 Members
 +
| 3x
 +
| Story Mission
 +
| 2x
 
|-
 
|-
|
+
| 5 Members
|[[Challenger Class|Challenger]]
+
| 4x
|[[Duderstadt Class|Duderstadt]]
+
| TFO/STF (Elite)
|
+
| 3x
|-
+
|}
|
+
 
|[[Cheyenne Class|Cheyenne]]
+
==== 1.2.2 - STO Combat Action Ribbons ====
| colspan="2" |[[Echelon Class|Echelon]]
+
 
|-
+
# Combat Action Ribbons in STO are awarded for any action that pits a player against another player, with two or more BF members taking part.
| ||[[Edison Class|Edison]]|| colspan="2" |[[Excelsior II Class|Excelsior II]]
+
# Activities include:
|-
+
## PvP Task Force Operations menu option under the minimap.
|  ||[[Grissom Class|Grissom]]|| colspan="2" |[[Gagarin Class|Gagarin]]
+
## Competitive Reputation TFOs
|-
+
# A qualifying submission for this award should contain a screenshot with proof that a qualifying action has been completed, in this instance the final scoreboard at the end of the match.
|  ||[[New Orleans Class|New Orleans]]||[[Intrepid Class|Intrepid]]
+
# Combat Action Ribbons are awarded based on the following formula, where the multipliers change by the table below:
|
+
Number of Screenshots x Member Multiplier x Content Multiplier x Other Multiplier = Total Ribbons
|-
+
 
|  ||[[Norway Class|Norway]]|| colspan="2" |[[Inquiry Class|Inquiry]]
+
{| class="wikitable" style="text-align:center;"
|-
+
|- style="font-weight:bold;"
|  ||[[Nova Class|Nova]]|| colspan="2" |[[Luna Class|Luna]]
+
! colspan="2" | CAR Member Multipliers
|-
+
! colspan="2" | CAR Content Multipliers
|
+
! colspan="2" | CAR Other Multipliers
|[[Olympic Class|Olympic]]
+
|- style="font-style:italic; border-color:inherit;"
| colspan="2" |[[Manticore Class|Manticore]]
+
| Description
|-
+
| Value
|  ||[[Parliament Class|Parliament]]|| colspan="2" |[[Nebula Class|Nebula]]
+
| Description
|-
+
| Value
|
+
|Description
|[[Phoenix Class|Phoenix]]
+
|Value
| colspan="2" |[[Pathfinder Class|Pathfinder]]
 
|-
 
| ||[[Raven Class|Raven]]|| colspan="2" |[[Prometheus Class|Prometheus]]
 
 
|-
 
|-
| ||[[Rhode Island Class|Rhode Island]]|| colspan="2" |[[Sutherland Class|Sutherland]]
+
| 2 Members
|-
+
| 1x
|
+
| Competitive Reputation TFO
|[[Reliant Class|Reliant]]
+
| 1x
| colspan="2" |
+
| Participate
 +
| 1x
 
|-
 
|-
| ||[[Saber Class|Saber]]|| colspan="2" |
+
| 3 Members
 +
| 2x
 +
| PvP
 +
| 2x
 +
| Win
 +
| 2x
 
|-
 
|-
| ||[[Springfield Class|Springfield]]|| colspan="2" |
+
| 4 Members
 +
| 3x
 +
|  
 +
|  
 +
|  
 +
|  
 
|-
 
|-
|
+
| 5 Members
|[[Steamrunner Class|Steamrunner]]
+
| 4x
|
+
|
|
+
|  
 +
|  
 +
|  
 
|}
 
|}
==3 - Squadrons==
 
  
#The Squadron system allows members holding the dossier rank of Captain and above greater flexibility in their Command choices. Where Commanders and below may pick a single Primary Command from a list, Captains are entitled to a certain level of ‘Squadron Strength’ in their Command selection. This gives them options like choosing between a single, larger ship or multiple smaller ones.
+
== 2 - World of Warships ==
#If a member holds multiple Commands under the Squadrons system, these ships are all subject to the same usage requirements as outlined under Primary Commands above. They may not be used as RPGs, and IC are starships assigned to the member’s Task Force.
+
 
##All ships must have their own Command on BFMS. This is solely to ensure the registry accurately reflects what ships are in use and dossiers show all of a member's ships. Members are free, however, to house Stories and Missions involving the ship and crew on any of their squadron BFMS Commands.
+
# Bravo Fleet has an officially supported presence on the North American PC server for World of Warships (WoWS), using the tag [4BF].
##Members with multiple ships should designate one as their Primary Command on BFMS. This is solely for display and organisational purposes, and has no other or IC significance. The Primary Command must be a Squadron Commands, and may not be an RPG or Fiction.
+
# Members may join the clan by searching for [4BF] or "4th Fleet - Bravo Fleet" and requesting to join in-game, or by requesting an invite on the Discord channel #worldofwarships-invites
##Members have some freedom on how to IC depict these multiple ships. They may be entirely unaffiliated, all falling directly under their Task Force’s IC chain of command, with the member using them to tell totally different stories.
+
# Members in the clan may contribute oil from crates to the fleet base.
##Members may use all/some of them to form an IC-only unit within their Task Force, referred to as a squadron. This typically takes its title from the squadron’s ‘lead ship’ or starbase (for example, a squadron led by the USS Endeavour would be called ‘Endeavour Squadron’). This ensures all squadrons have a unique IC name. Members may not call these IC units ‘task groups’, to avoid confusion with the OOC unit.
+
 
##Members may create an officer in command of this squadron, who may or may not also be the commanding officer of one of these starships/starbase, and who falls IC under the chain of command of the member’s Task Force. All Canon Policy rank restrictions remain.
+
=== 2.1 - World of Warships Fleet Management ===
#The Squadron Strength to which a member is entitled is dependent on their dossier rank.
+
 
{| class="wikitable"
+
# All members will join in as members, with the staff being determined based on the determination of the Security Office.
|+'''Squadron Strength by Dossier Rank'''
+
# As there are Clan Battles, any member wishing to organize one may do so at any time.
!Captain
+
 
!Fleet Captain
+
=== 2.2 - World of Warships Awards ===
!Commodore
+
 
!Rear Admiral
+
# Bravo Fleet uses the following awards in World of Warships:
!Vice Admiral
+
## Campaign Ribbons
!Admiral
+
## Joint Action Ribbons
!Fleet Admiral
+
## Combat Action Ribbons
|-
+
# Members may earn gaming ribbons for World of Warships if they are not in the in-game clan or on the NA server, but only on PC.
|3
+
## The console version of World of Warships is a different game altogether with unique balancing and differing ship tiers; therefore it is not supported at this time.
|4
+
 
|6
+
==== 2.2.1 - World of Warships Campaign Ribbons ====
|7
+
 
|8
+
# Campaign Ribbons for World of Warships gaming are earned by:
|9
+
## Purchasing with Ship XP/Free XP and silver a Tier VI-X ship, once per country tech tree per tier, through regular means or an Early Access event.
|10
+
### Ships purchased with Doubloons, coal, steel or real-world money may not be submitted for Campaign Ribbons.
|}
+
## Purchasing with XP and silver a super ship marked with a star in a country's tech tree, which will award three Campaign Ribbons per ship earned.
 +
# A qualifying submission for this award should contain a screenshot showing the country tech tree with the unlocked branch, with at least one of the branches showing either a checkmark or a silver currency value beside the one being submitted for in the country tree.
  
=== 3.1 - Starship Strength ===
+
==== 2.2.3 - World of Warships Joint Action Ribbons ====
  
# Ship classes are allocated a certain level of Strength depending on their size, power, modernity, and so forth.
+
# Joint Action Ribbons for World of Warships gaming are earned by groups of members by completing any PvE battles, including:
# Members may select any number of ships as their Commands under the Squadrons system, so long as the total Strength does not exceed their rank entitlement.
+
## Co-Op Battles
# Ship classes by rank (As above in 2 - Primary Commands) may not directly correlate with a starship's squadron strength. This is intentional, reflecting how some ships may be more or less popular when they are a member's only command, but valued differently when part of a larger squadron.
+
## Operations
 +
## Asymmetric Battles
 +
# A qualifying submission for this award should contain a screenshot with proof that a qualifying action has been completed, either with the scoreboard or combat summary, with the BFMS IDs and Handles of all of the members involved.
 +
## Multiple actions with the same group of members may be submitted together as a single submission, but there should be a different submission for each type of battle and if different numbers of players are involved.
 +
# Joint Action Ribbons counts for each gaming submission are calculated with the following formula, using the values in the table below:
 +
Number of Battles Submitted x Member Multiplier x Content Modifier x Win/Loss Modifier = Total Ribbons
  
{| class="wikitable" style="margin:auto"
+
{| class="wikitable" style="text-align:center;"
|+Ship classes by rank
+
|- style="font-weight:bold;"
|-
+
! colspan="2" | JAR Member Multipliers
!1!!2!! colspan="2" |3
+
! colspan="2" | JAR Content Multipliers
!4
+
! colspan="2" | JAR Win/Loss Multipliers
|-
+
|- style="font-style:italic;"
|Small Civilian Ship
+
| Description
|[[Alita Class|Alita]]
+
| Value
|
+
| Description
|[[Constitution III Class|Constitution III]]
+
| Value
|[[Odyssey Class|Odyssey]]
+
| Description
|-
+
| Value
|[[Aquarius Class|Aquarius]]|| colspan="2" |[[Akira Class|Akira]]||[[Galaxy Class|Galaxy]]
 
|
 
|-
 
|[[California Class|California]]|| colspan="2" |[[Duderstadt Class|Duderstadt]]||[[Obena Class|Obena]]
 
|
 
|-
 
|[[Centaur II Class|Centaur II]]
 
|[[Echelon Class|Echelon]]
 
|
 
|[[Ross Class|Ross]]
 
|
 
|-
 
|[[Challenger Class|Challenger]]
 
| colspan="2" |[[Excelsior II Class|Excelsior II]]
 
|[[Sagan Class|Sagan]]
 
|
 
|-
 
|[[Cheyenne Class|Cheyenne]]|| colspan="2" |[[Gagarin Class|Gagarin]]||[[Sovereign Class|Sovereign]]
 
|
 
|-
 
|[[Defiant Class|Defiant]]
 
| colspan="2" |[[Inquiry Class|Inquiry]]
 
|[[Vesta Class|Vesta]]
 
|
 
|-
 
|[[Edison Class|Edison]]|| colspan="2" |[[Luna Class|Luna]]||
 
|
 
|-
 
|[[Grissom Class|Grissom]]|| colspan="2" |[[Manticore Class|Manticore]]||
 
|
 
|-
 
|[[Intrepid Class|Intrepid]]
 
| colspan="2" |[[Nebula Class|Nebula]]
 
|
 
|
 
|-
 
|[[New Orleans Class|New Orleans]]|| colspan="2" |[[Pathfinder Class|Pathfinder]]||
 
|
 
|-
 
|[[Norway Class|Norway]]|| colspan="2" |[[Prometheus Class|Prometheus]]||
 
|
 
|-
 
|[[Nova Class|Nova]]||[[Sutherland Class|Sutherland]]
 
| ||
 
|
 
|-
 
|[[Olympic Class|Olympic]]||
 
|  ||
 
|
 
|-
 
|[[Parliament Class|Parliament]]|| colspan="2" | ||
 
|
 
|-
 
|[[Phoenix Class|Phoenix]]||
 
|  ||
 
|
 
|-
 
|[[Raven Class|Raven]]||
 
|-
 
|[[Rhode Island Class|Rhode Island]]
 
|
 
|-
 
|[[Reliant Class|Reliant]]
 
|
 
 
|-
 
|-
|[[Saber Class|Saber]]||
+
| 2 Members
 +
| 1x
 +
| Co-Op Battle
 +
| 1x
 +
| Defeated in submitted battle
 +
| 1x
 
|-
 
|-
|[[Springfield Class|Springfield]]||
+
| 3 Members
 +
| 2x
 +
| Operations and seasonal game modes
 +
| 2x
 +
| Win submitted battle
 +
| 2x
 
|-
 
|-
|[[Steamrunner Class|Steamrunner]]
+
| 4-5 Members (in supported modes)
|
+
| 3x
 +
|
 +
|
 +
|  
 +
|  
 
|}
 
|}
#For example, upon reaching the rank of Captain a member has a Squadron Strength entitlement of 3. If they already have a Commander-level ship, they are only using 2 of their Squadron Level. They may ‘upgrade’ as they did upon reaching the rank of Commander, returning their current ship to the registry and choosing a single new Command with a Strength of 3. If they keep their ship with its Strength of 2, they may choose to add to their dossier another ship with a Strength of 1.
 
##Members are under no obligation to use their total Squadron Strength. These Commands are a reflection of the hard work of members, however, and may be chosen for storytelling opportunities or simple prestige.
 
#‘Small Civilian Ship’ is a catch-all term for non-Starfleet civilian vessels members may wish to use for different kinds of storytelling. It refers to ships of, for example, the [[Kaplan F17 class]] or the [[Groumall class]], usually freighters, that are not affiliated IC with Starfleet and may be used for trading, prospecting, exploration, or other adventures. Acquiring a ship like this is subject to a successful Fiction Proposal, and so they are not listed as available on the registry but created as required by the Intelligence Office.
 
#The Intelligence Office may make adjustments to ship class Strengths to account for balance as the system and canon evolve. No member will have an asset removed because of a rebalance, but they would only be grandfathered in until they wanted to change their squadron, at which point the new strength values would be used.
 
  
=== 3.2 - Starbase Strength ===
+
==== 2.2.4 - World of Warships Combat Action Ribbons ====
  
# Starbases as Commands work the same as starships under the Squadron system, but are subject to different requirements. They represent starbases assigned In Character to the member’s Task Force in the Fourth Fleet in {{year}}.
+
# Combat Action Ribbons for World of Warships gaming are earned by groups of members by completing any PvP battles, including:
# Members do not have to choose between a starbase or starship under the Squadron system. They are only restricted by their rank’s total Squadron Strength.
+
## Random
# Registry Starbases are created by the Intelligence Office, and will have their own wiki article explaining the location and setting material relevant to that starbase that has been ratified by the Intelligence Office. This is Fleet Canon that cannot be altered without permission of the Intelligence Office, even by the member to whom the starbase registry is attached. As such, members should heavily consider their choice, as a Starbase Command is under more restrictions and requirements from the Intelligence Office.
+
## Brawl
## Members interested in creating a station command should consult directly with the Intelligence Office if one of the concepts on the wiki isn't suitable for their idea.
+
## Clan Battles
# Because stations impact shared canon more directly than starships, members will be unable to trade in a station for one year after acquiring it.
+
# A qualifying submission for this award should contain a screenshot with proof that a qualifying action has been completed, either with the scoreboard or combat summary, with the BFMS IDs and Handles of all of the members involved.
# These stations are settings in Fleet Canon and thus may feature in the writing of other members. This is restricted to simple visits for shore leave, resupply, or administrative duties like briefings. It cannot include stories which materially impact the station or its crew, and all rules in using another members’ BFMS characters apply.
+
## Multiple actions with the same group of members may be submitted together as a single submission, but there should be a different submission for each type of battle and if different numbers of players are involved.
## It is not necessary to request permission from the member who owns the station before featuring it in your story. Asking ahead of time may make aligning member canon easier.
+
# Combat Action Ribbons counts for each gaming submission are calculated with the following formula, using the values in the table below:
## When writing on another member’s starbase, only use locations aboard established on the station’s wiki article or refer to them in a generic sense. For example, do not create, name, and describe a whole new bar without the owner’s permission - but you may refer to your characters meeting in a bar.
+
Number of Battles Submitted x Member Multiplier x Content Modifier x Win/Loss Modifier = Total Ribbons
## Do not ask members for a joint post when visiting their starbase. The station owner may offer, but should not feel obligated to share their time in such a way or be put in the position of having to say ‘no.
 
## If you require a member of the station’s crew to interact with yours, such as a deck officer greeting a new arrival or a security officer breaking up a bar fight, you should either create a junior officer NPC in a generic crew role or, if appropriate, ask permission of the station owner to use a specific character.
 
  
{| class="wikitable" style="margin:auto"
+
{| class="wikitable" style="text-align:center;"
|+Starbase classes by Strength
+
|- style="font-weight:bold;"
|-
+
! colspan="2" | CAR Member Multipliers
!2!!3!!4
+
! colspan="2" | CAR Content Multipliers
|-
+
! colspan="2" | CAR Win/Loss Multipliers
|[[Jupiter Class|Jupiter]]||[[Anchorage Class|Anchorage]]||[[Canopus Class|Canopus]]
+
|- style="font-style:italic;"
 +
| Description
 +
| Value
 +
| Description
 +
| Value
 +
| Description
 +
| Value
 
|-
 
|-
|[[K Class|K-Type]]||[[Copernicus Class|Copernicus]]||[[Unity Class|Unity]]
+
| 2 Members
 +
| 1x
 +
| Random and Brawl
 +
| 1x
 +
| Defeated in submitted battle
 +
| 1x
 
|-
 
|-
|[[Regula Class|Regula]]||[[Narendra Class|Narendra]]||
+
| 3 Members
 +
| 2x
 +
| Clan battle and seasonal game modes with PvP
 +
| 2x
 +
| Win submitted battle
 +
| 2x
 
|-
 
|-
|[[Vision Class|Vision]]||[[Presidium Class|Presidium]]||
+
| 4+ Members (in supported modes)
|-
+
| 3x
| ||[[Watchtower Class|Watchtower]]||
+
|  
 +
|  
 +
|  
 +
|  
 
|}
 
|}
  
=== 3.3 - Attached Ships ===
+
== 3 - Star Trek Infinite ==
 +
 
 +
# Star Trek Infinite is a 4D strategy game by Paradox Interactive that, beginning in the mid 24th century, gets you to play as one of the major powers you see in Star Trek to become the dominant force in the Alpha and Beta Quadrants. It heavily borrows off the framework of Stellaris, but has unique elements to make this a Star Trek game through and through.
 +
# Bravo Fleet supports gameplay and allows players to earn achievements through gameplay.
 +
 
 +
=== 3.1 - Star Trek Infinite Awards ===
  
# Certain commands, like starbases, have an attached ship, which has its own registry entry but has an effective Strength of 0. Whether or not an attached ship is selected does not affect a member’s Squadron Strength.
+
# Bravo Fleet uses the following awards for Star Trek Infinite:
# Most attached ships are assigned to starbases. Upon requesting a starbase, the member should identify to the Intelligence Office an appropriate choice of ship from the registry. That ship will then be removed from the public pool. It will not be given a BFMS Command, but should be written about as part of the starbase’s Command.
+
## Campaign Ribbons
# The ''Odyssey''-class always has an ''Aquarius''-class ship attached. Unlike with starbases, the ''Aquarius''-class’s name is predetermined and cannot be changed. Details about an ''Odyssey’s'' ''Aquarius''-class will be listed on the ship’s wiki page.
+
## Combat Action Ribbons
# A strength 1 starship is attached to every station command in order to ensure that members have the ability to interact with fleet events set in other areas. This starship is assigned to the station directly to support it, as the ''Defiant'' was to DS9. This does not add to or subtract from the strength of a member's squadron, i.e. you could not use additional squadron strength to attach a strength 2 starship to your station.
+
# Members may earn ribbons for Star Trek Infinite through play with fellow Bravo Fleet members, or via achieving several in-game milestones.
# Members may choose to depict any of their other ships as attached to or operating out of the starbase.
 
  
=== 3.4 - Requesting Squadron Ships ===
+
==== 3.1.1 - Star Trek Infinite Campaign Ribbons ====
  
# Members must use BFMS to request any Commands under the Squadron system, in the same manner as Command requests at the ranks of Lieutenant Commander or Commander.
+
# Campaign Ribbons are earned by completing the following tasks in either single player or multiplayer:
# BFMS requests for new Commands under the Squadron system must use the ‘Lore Office Proposal’ window to clearly communicate their allocation of their Squadron Level. This must include what ships, if any, are being returned to the registry.
+
## First Diplomatic Victory
## If a new Captain requests a Command with a Strength of 3 with no further detail, the Intelligence Office will assume they are returning their current ship to the registry, just as with previous upgrades, and process accordingly.
+
## First time completing the mission trees for each faction in a single round of play
## If a Member wishes to retain their current Command and add another, they may request the new ship under BFMS and say so in the Proposal window. A simple message, such as ‘I am keeping the USS Lollipop (Strength 2), and adding this one (Strength 1) for a total Squadron Strength of 3’ will suffice.
+
## Completing any one of the developer curated Achievements for the game
## If a Member wishes to return any of their ships to the registry, they must say so. Any requests for additional Commands that does not include a registry return and would bring a member over their Squadron Strength will be deleted. A simple message, such as ‘I am returning the USS Lollipop (Strength 2) and adding this one (Strength 3) for a total Squadron Strength of 3’ will suffice.
+
## One Campaign Ribbon is earned by each member in a multiplayer group by organizing a play group with a full four people at the same time, with a bonus second Campaign Ribbon to the organizer
# If the Intelligence Office receives competing requests for the same starship, requests for a primary command from Lieutenant Commanders or Commanders will be prioritised, or upgrades to a single Strength 3 starship for new Captains. After that, ships will be allocated on a first-come, first-served basis.
+
# A qualifying submission for this award should contain a screenshot of the applicable screen showing the completion of this task with the Victory screen showing all players, as well as a screenshot of the Save file.
  
== 4 - Flag Stations ==
+
==== 3.1.2 - Star Trek Infinite Combat Action Ribbons ====
  
# From the rank of Commodore, members are entitled to select a Starbase Command ''in addition to'' any Squadron Commands. These Flag Stations do not count against a member's Squadron Level, with an effective Strength of 0. They are subject to all the same Intelligence Office restrictions in development, modification, and usage as Squadron Starbases (see section 3.2 above).
+
# Combat Action Ribbons may be earned by playing with each other through a standard session, at any difficulty.
# Flag Stations exist to flesh out the Fourth Fleet’s infrastructure, and flag officers who have them are expected to adhere to the highest standards of Fleet Canon. The Intelligence Office may place additional requirements on Flag Stations regarding location, class, or mission profile, to ensure appropriate variety and for the best development of Fleet Canon.
+
# A qualifying submission for this award must include a screenshot of the Victory screen for the game at the time that the session ends, either as a completed game or a partially completed game, clearly showing all the empires involved, plus the BFMS ID of each participant and which empire they were playing.
# Changing Flag Stations is subject to the same requirements as any other Starbase Command: Members may change their Flag Station either upon promotion or once a year.
+
## If a partially completed game is submitted, please also include a screenshot of the save file.
# Upon promotion, members may wish to ‘upgrade’ their station class. Any member may create or select a different starbase in a different location, either selecting one in the registry or developing one with the Intelligence Officer. Replacing an existing starbase with one of a different class is permitted only at the discretion of the Intelligence Officer.
+
# Combat Action Ribbons will be calculated based on the following formula:
## If appropriate, the Intelligence Officer may agree to establish a new starbase in the same region for the member to change to. For example, a member might transition from a small ''Vision''-class to a larger ''Narendra''-class elsewhere in the same sector, perhaps reflecting the region’s growing IC importance. The original ''Vision''-class would remain in the area and be available for other members to select.
+
One Submitted Game x Member Multiplier x ((Victory Score - 500) / 500) x Win/Loss Modifier = Total Ribbons
## As always, changing a starbase or the major points of its surrounding area is subject to the Intelligence Office’s approval. Discuss your choice with the Intelligence Officer upon selecting a starbase if you expect to change your station class upon promotion but would like to keep the same or similar location.
 
# Flag Stations, like Squadron Starbases, may have an attached ship. This follows all the same rules as laid out in section 3.3 above.
 
# Flag Station classes are restricted by rank.
 
  
{| class="wikitable" style="margin:auto"
+
{| class="wikitable" style="text-align:center;"
|-
+
|- style="font-weight:bold;"
!Commodore!!Rear Admiral!!Vice Admiral
+
! colspan="2" | CAR Member Multipliers
!Admiral
+
! colspan="2" | CAR Win/Loss Multipliers
|-
+
|- style="font-style:italic;"
|[[Jupiter Class|Jupiter]]||[[Anchorage Class|Anchorage]]||[[Canopus Class|Canopus]]
+
| Description
|[[Spacedock Class|Spacedock]]
+
| Value
|-
+
| Description
|[[K Class|K-Type]]||[[Copernicus Class|Copernicus]]||[[Unity Class|Unity]]
+
| Value
|[[Aurora Class|Aurora]]
 
 
|-
 
|-
|[[Regula Class|Regula]]||[[Narendra Class|Narendra]]||
+
| 2 Members
|
+
| 1x
 +
| Defeated in submitted battle
 +
| 1x
 
|-
 
|-
|[[Vision Class|Vision]]||[[Presidium Class|Presidium]]||
+
| 3 Members
|
+
| 2x
 +
| Win submitted battle
 +
| 2x
 
|-
 
|-
| ||[[Watchtower Class|Watchtower]]||
+
| 4 Members
 +
| 3x
 +
|  
 
|
 
|
 
|}
 
|}
==5 - Fictions==
 
#Stories about alternative settings such as non-Starfleet ships or historic eras are called 'Fictions'. Like primary or squadron commands and RPGs, they have their own BFMS Command page and are held to the same standards in content and canon compliancy.
 
#Fictions may only be written by one individual member. Stories with multiple writers count as role-playing games, which fall under the purview of the Operations Department.
 
#A member who has reached the rank of Commander may submit a fiction proposal to the Intelligence Office. This is not necessary for fiction based on their Primary Command.
 
#The proposal should explain the premise of the story, a loose estimation of expected length, and what it contributes to Bravo Fleet canon, present or historic. It should include a broad activity commitment, such as '1 Story posted per month.' This is not a binding agreement, but helps the Intelligence Office identify inactive Fictions.
 
#Starfleet ships in the year {{year}}  are not an appropriate setting for Fictions. Members should use their Primary or Squadron Commands for these.
 
# Fictions do not draw from ships in the Bravo Fleet Registry, and so should discuss their ship, station, or concept needs with the Intelligence Office so an appropriate entry can be created.
 
#Fictions not set in {{Year}} should ''not'' draw from ships in the Bravo Fleet Registry. Members are subject to the same rank-based restrictions of classes (for example, a Commander writing a fiction set in 2375 still cannot request a Sovereign-class), but of course can request era-appropriate ship classes not listed in the registry.
 
# A new fiction will have its own Command on BFMS, assigned to the member. This Command is for use solely within the bounds of the accepted fiction proposal, and must not be used as a Primary Command.
 
# Bravo Fleet fiction supports and enriches Bravo Fleet Canon, present and historic. Proposals from non-Trek settings will be rejected. Proposals from alternate universes of Star Trek will need to demonstrate their relevance to Bravo Fleet Canon content, themes, or characters to be accepted.
 

Revision as of 23:59, 5 March 2024

Games officially by the Security Office shall be listed here, as per the Gaming Policy.

1 - Star Trek Online

  1. Bravo Fleet has officially supported in-game fleets for Star Trek Online (STO) on PC (both factions), on XBOX and on PlayStation (Federation Only), which provide members with various resources and perks.
  2. Members may also earn ribbons for STO gaming in factions or on platforms where Bravo Fleet does not maintain an official presence.

1.1 - STO In-Game Fleet Management

  1. Bravo Fleet maintains fleets for the following factions/platforms:
    1. PC - Federation - Bravo Fleet
    2. PC - Klingon - House of yo’ loS
    3. PlayStation - Federation - Bravo Fleet
    4. XBOX - Federation - Alteran Royal Navy Bravo Fleet
  1. Members may join an in-game fleet with one or more in-game characters, also known as “alts” or “toons”, by requesting to do so in the Bravo Fleet Discord channel #sto-char-mgmt.
    1. Characters that do not log in at least once every six months will be removed from the in-game fleets to ensure there are enough slots for all members.
    2. Members who transfer to the Reserves voluntarily or through the AWOL process will have their characters removed from the in-game fleets.
    3. Character in-game biographies for STO characters are not required, but are encouraged.
  2. In-Game rank is based off of the rank achieved in Bravo Fleet, though it is not exact due to limitations of the game engine on providing only a set amount of ranks:
    1. All members will get promoted to a rank approximate to their BFMS ranking, with the following levels:
      1. Cadet/Bekk - Cadet ranks
      2. Junior Officer - Midshipman to Lieutenant
      3. Senior Officer - Lieutenant Commander to Fleet Captain
      4. Flag Officer - Commodore and Above
    2. As there is no automated connection to BFMS for ranks, the positions will be audited periodically to update listed ranks
      1. If there is a character of yours and you do not see the assigned promotion list please mention in #sto-char-mgmt
  3. Permissions for each in-game rank are assigned at the discretion of the Security Office, and all members have access to:
    1. Purchase from provisioned fleet stores and fleet shipyards
    2. Visit fleet holdings
    3. Invite non-members to fleet holdings
    4. Use of the Fleet Bank, the degree of which is determined based on rank

1.2 - STO Awards

  1. Bravo Fleet uses the following awards in Star Trek Online:
    1. Campaign Ribbons
    2. Joint Action Ribbons
    3. Combat Action Ribbons

1.2.1 - STO Campaign Ribbons

An example of a Mission Journal screenshot, showing the Cardassian Struggle arc is completed.

# Campaign Ribbons for STO gaming are earned by the following actions per character:

    1. Reaching Level 65
    2. Completing Story Arcs in groups as follows:
      1. Completing the faction specific storyline arcs
      2. From the end of the faction specific arc to New Romulus
      3. Solonae Dyson Sphere and Delta Quadrant
      4. Iconian War, Yesterday's War and Future Proof
      5. New Frontiers and Gamma Quadrant
      6. Age of Discovery, J'Ula's Discovery and Klingon Civil War
      7. All of The Galaxy At Large arcs that have been removed from the main story
    3. Completing at least three reputations to Level 6
    4. Completing all the current Admiralty factions to Level 10
    5. Completing the first individual Duty Officer branch to Level 4
    6. Completing five Duty Officer branches to Level 4
    7. Completing at least two Research and Development Branches to Level 20
    8. Completing each of the primary Specializations (Command, Intel, Pilot, Temporal, Miracle Worker)
    9. Completing all of the secondary Specializations on one character (Constable, Strategist, Commando)
    10. Complete a Recruit Transponder (Delta, Temporal, Gamma, Klingon)
  1. Campaign ribbons can be earned by the following actions once per account:
    1. Progressively completing 50 levels in the Endeavour system (awarded at 50, 100, 150, et al)
    2. Progressing and completing one STO Event, to completion of the prize at the end of the event
      1. This is a repeatable action that can be completed for each event, but can only be used to claim one Campaign Ribbon per event, per account
      2. This Campaign Ribbon excludes Event Campaigns
    3. A bonus for specific performance in a gaming-related competition, per that competition's rules
  2. A qualifying submission for this award should contain a screenshot showing the character's name, level and the activity completed as applicable, as well as the character's name in the gaming activity form's text box.

1.2.2 - STO Joint Action Ribbons

  1. Joint Action Ribbons for STO gaming are earned by playing Star Trek Online in a group of Bravo Fleet members against environments and sometimes players too.
  2. Activities include:
    1. Task Force Operations or Special Task Forces
    2. Patrols
    3. Red Alerts
    4. Daily missions
    5. Story missions
    6. Battlezones
  3. A qualifying submission for this award should contain a screenshot with proof that a qualifying action has been completed.
    1. Multiple actions of the same type should be submitted as a single submission whenever possible, as long as the same number of participants are in each instance.
    2. When submitting multiple screenshots of different types of content, each content type (Normal TFOs, Advanced TFOs, Story Missions, etc.) must be submitted separately.
    3. When submitting for battlezones, since this is a time-based submission, you must provide a screenshot of your start time in the battlezone and a screenshot of the end time. Rewards will be calculated at a rate of 4 Joint Action Ribbons per hour of game play, with one hour minimum being required for submission.
  4. Joint Action Ribbons are awarded based on the following formula, where the multipliers change by the table below:
Number of Screenshots x Member Multiplier x Content Multiplier = Total Ribbons
JAR Member Multipliers JAR Content Multipliers
Description Value Description Value
2 Members 1x TFO/STF (Normal), Patrol, Battlezone, or Red Alert 1x
3 Members 2x TFO/STF (Advanced) 2x
4 Members 3x Story Mission 2x
5 Members 4x TFO/STF (Elite) 3x

1.2.2 - STO Combat Action Ribbons

  1. Combat Action Ribbons in STO are awarded for any action that pits a player against another player, with two or more BF members taking part.
  2. Activities include:
    1. PvP Task Force Operations menu option under the minimap.
    2. Competitive Reputation TFOs
  3. A qualifying submission for this award should contain a screenshot with proof that a qualifying action has been completed, in this instance the final scoreboard at the end of the match.
  4. Combat Action Ribbons are awarded based on the following formula, where the multipliers change by the table below:
Number of Screenshots x Member Multiplier x Content Multiplier x Other Multiplier = Total Ribbons
CAR Member Multipliers CAR Content Multipliers CAR Other Multipliers
Description Value Description Value Description Value
2 Members 1x Competitive Reputation TFO 1x Participate 1x
3 Members 2x PvP 2x Win 2x
4 Members 3x
5 Members 4x

2 - World of Warships

  1. Bravo Fleet has an officially supported presence on the North American PC server for World of Warships (WoWS), using the tag [4BF].
  2. Members may join the clan by searching for [4BF] or "4th Fleet - Bravo Fleet" and requesting to join in-game, or by requesting an invite on the Discord channel #worldofwarships-invites
  3. Members in the clan may contribute oil from crates to the fleet base.

2.1 - World of Warships Fleet Management

  1. All members will join in as members, with the staff being determined based on the determination of the Security Office.
  2. As there are Clan Battles, any member wishing to organize one may do so at any time.

2.2 - World of Warships Awards

  1. Bravo Fleet uses the following awards in World of Warships:
    1. Campaign Ribbons
    2. Joint Action Ribbons
    3. Combat Action Ribbons
  2. Members may earn gaming ribbons for World of Warships if they are not in the in-game clan or on the NA server, but only on PC.
    1. The console version of World of Warships is a different game altogether with unique balancing and differing ship tiers; therefore it is not supported at this time.

2.2.1 - World of Warships Campaign Ribbons

  1. Campaign Ribbons for World of Warships gaming are earned by:
    1. Purchasing with Ship XP/Free XP and silver a Tier VI-X ship, once per country tech tree per tier, through regular means or an Early Access event.
      1. Ships purchased with Doubloons, coal, steel or real-world money may not be submitted for Campaign Ribbons.
    2. Purchasing with XP and silver a super ship marked with a star in a country's tech tree, which will award three Campaign Ribbons per ship earned.
  2. A qualifying submission for this award should contain a screenshot showing the country tech tree with the unlocked branch, with at least one of the branches showing either a checkmark or a silver currency value beside the one being submitted for in the country tree.

2.2.3 - World of Warships Joint Action Ribbons

  1. Joint Action Ribbons for World of Warships gaming are earned by groups of members by completing any PvE battles, including:
    1. Co-Op Battles
    2. Operations
    3. Asymmetric Battles
  2. A qualifying submission for this award should contain a screenshot with proof that a qualifying action has been completed, either with the scoreboard or combat summary, with the BFMS IDs and Handles of all of the members involved.
    1. Multiple actions with the same group of members may be submitted together as a single submission, but there should be a different submission for each type of battle and if different numbers of players are involved.
  3. Joint Action Ribbons counts for each gaming submission are calculated with the following formula, using the values in the table below:
Number of Battles Submitted x Member Multiplier x Content Modifier x Win/Loss Modifier = Total Ribbons
JAR Member Multipliers JAR Content Multipliers JAR Win/Loss Multipliers
Description Value Description Value Description Value
2 Members 1x Co-Op Battle 1x Defeated in submitted battle 1x
3 Members 2x Operations and seasonal game modes 2x Win submitted battle 2x
4-5 Members (in supported modes) 3x

2.2.4 - World of Warships Combat Action Ribbons

  1. Combat Action Ribbons for World of Warships gaming are earned by groups of members by completing any PvP battles, including:
    1. Random
    2. Brawl
    3. Clan Battles
  2. A qualifying submission for this award should contain a screenshot with proof that a qualifying action has been completed, either with the scoreboard or combat summary, with the BFMS IDs and Handles of all of the members involved.
    1. Multiple actions with the same group of members may be submitted together as a single submission, but there should be a different submission for each type of battle and if different numbers of players are involved.
  3. Combat Action Ribbons counts for each gaming submission are calculated with the following formula, using the values in the table below:
Number of Battles Submitted x Member Multiplier x Content Modifier x Win/Loss Modifier = Total Ribbons
CAR Member Multipliers CAR Content Multipliers CAR Win/Loss Multipliers
Description Value Description Value Description Value
2 Members 1x Random and Brawl 1x Defeated in submitted battle 1x
3 Members 2x Clan battle and seasonal game modes with PvP 2x Win submitted battle 2x
4+ Members (in supported modes) 3x

3 - Star Trek Infinite

  1. Star Trek Infinite is a 4D strategy game by Paradox Interactive that, beginning in the mid 24th century, gets you to play as one of the major powers you see in Star Trek to become the dominant force in the Alpha and Beta Quadrants. It heavily borrows off the framework of Stellaris, but has unique elements to make this a Star Trek game through and through.
  2. Bravo Fleet supports gameplay and allows players to earn achievements through gameplay.

3.1 - Star Trek Infinite Awards

  1. Bravo Fleet uses the following awards for Star Trek Infinite:
    1. Campaign Ribbons
    2. Combat Action Ribbons
  2. Members may earn ribbons for Star Trek Infinite through play with fellow Bravo Fleet members, or via achieving several in-game milestones.

3.1.1 - Star Trek Infinite Campaign Ribbons

  1. Campaign Ribbons are earned by completing the following tasks in either single player or multiplayer:
    1. First Diplomatic Victory
    2. First time completing the mission trees for each faction in a single round of play
    3. Completing any one of the developer curated Achievements for the game
    4. One Campaign Ribbon is earned by each member in a multiplayer group by organizing a play group with a full four people at the same time, with a bonus second Campaign Ribbon to the organizer
  2. A qualifying submission for this award should contain a screenshot of the applicable screen showing the completion of this task with the Victory screen showing all players, as well as a screenshot of the Save file.

3.1.2 - Star Trek Infinite Combat Action Ribbons

  1. Combat Action Ribbons may be earned by playing with each other through a standard session, at any difficulty.
  2. A qualifying submission for this award must include a screenshot of the Victory screen for the game at the time that the session ends, either as a completed game or a partially completed game, clearly showing all the empires involved, plus the BFMS ID of each participant and which empire they were playing.
    1. If a partially completed game is submitted, please also include a screenshot of the save file.
  3. Combat Action Ribbons will be calculated based on the following formula:
One Submitted Game x Member Multiplier x ((Victory Score - 500) / 500) x Win/Loss Modifier = Total Ribbons
CAR Member Multipliers CAR Win/Loss Multipliers
Description Value Description Value
2 Members 1x Defeated in submitted battle 1x
3 Members 2x Win submitted battle 2x
4 Members 3x