Difference between pages "USS Temeraire" and "Guide: Writing on the BFMS"

From Bravo Fleet
(Difference between pages)
 
m (Category)
 
Line 1: Line 1:
{{Starship
+
This guide will help you learn to use the integrated fiction writing system on the BFMS, i.e. Bravo Fleet's main website. These instructions are for those members with commands, which anyone with the rank of Ensign or above can request. For those without commands, consider writing on [[Guide:Starbase Bravo|Starbase Bravo]]. For more information on the non-mechanical aspects of fiction writing, check out the Lore Office's [[Introduction to Bravo Fleet Writing]].
| name = Temeraire
 
| prefix = USS
 
| image = [[Image:Temeraire.jpg|350px]]
 
| registry = NCC-89893
 
| class = Inquiry
 
| affiliation = [[Starfleet]]
 
| status = Active
 
| commission = 2399
 
| decommission =
 
| destroyed =
 
| taskforce = [[Task Force 47]]
 
| quadrant = [[Alpha Quadrant]]
 
| role = Heavy Cruiser
 
| co = [[bfms_char:43643|Captain Tharia sh'Elas]]
 
| xo = [[bfms_char:49898|Commander Vasoch Gor]]
 
| dedication =
 
}}
 
{{quote|Our greatest glory is not in never falling, but in rising every time we fall. |'''Confucius - ''Ship's Dedication Quote'''''}}
 
The '''USS ''Temeraire''''' is an [[Inquiry Class|''Inquiry'' Class]] starship assigned to the [[Fourth Fleet]] under the command of [[bfms_char:43643|Captain Tharia sh'Elas]]. After an inquiry into the disastrous testing of the MARS stealth system aboard the Inquiry-class starship Thesis, Starfleet Command relieved [[bfms_char:43418|Captain Italia Ruas]] of her command, opting to merge the crew with that of their aging counterpart, the [[USS Santa Fe]]. Whilst undergoing an overhaul, the ship has all traces of the controversial system removed, and is recommissioned with a new name and a new commanding officer. Redesignated as the USS Temeraire, pronounced ''Tem-uh-rare'', the ship’s technological advancements and experienced personnel make her a perfect candidate for a new mission.
 
  
==Design and Layout==
+
The basics of the fiction system are that a command is the ship or station where a mission is set (the 'command' for ''Star Trek: The Next Generation'' would be the ''Enterprise''-D), missions are like episodes (the first mission for ''TNG'' would be "Encounter at Farpoint"), and stories are like scenes (the first story in "Encounter at Farpoint" would be the ''Enterprise'' encountering Q for the first time).
Designed in response to Starfleet's change in emphasis following events of the 2380's, the Inquiry-class is designated as a heavy cruiser. As one of the fastest, most well-armed starships of her size, the Inquiry-class is a design that is quickly becoming commonplace throughout the Federation thanks to the standardisation of the class. Such standardisation has enabled a second 'block' of starships to be commissioned, making use of new technological advancements and upgrades. Temeraire is the fifth of the Block-II vessels to be constructed.
 
  
A high degree of automation means that, despite having mission capability on par with the Sovereign, Temeraire has less than half the crew complement. Happily, this ensures a comfortable standard of accommodation throughout the ship, and a variety of recreation facilities.
+
== Steps to Create a Mission and Story ==
 +
The steps for those members with their own commands differ slightly from the above instructions.
  
===Bridge, Deck One===
+
#Create a Mission:
Modelled on the successful layout of its older, larger cousin the Sovereign-class, the bridge of the Temeraire has a slightly altered colour scheme and a much changed console layout across the bridge. Making the most of a variety of technological advancements, such as holoprojectors, holographic communications, in-built weapons lockers and three dimensional computer displays in places, the Inquiry-class bridge module is one of the most advanced in the fleet. Perhaps one of its most charming features is the emblem of the United Federation of Planets emblazoned on the carpeting as a constant reminder of all the ship stands for.
+
##Navigate either to your command or to the Writing Controls panel of your dashboard. From your command click 'Add Mission.' From the Writing Controls panel, click 'Create Mission.'
<div class="thumb tleft">
+
##Give your mission a title.
[[file:TemeraireBridge.png|302px]]
+
##Select your command
<div class="thumbcaption">Bridge module, USS <i>Temeraire</i>.</div>
+
##If this is part of a fleet-wide or unit-wide plot, select the appropriate parent mission. Otherwise, you can ignore this field.
</div>
+
##Do not check 'Fleet-wide mission' or 'Unit-Wide Mission.'
In a move away from more recent styles, and harking back to the traditional layouts of yesteryear, the Temeraire has a single center command seat for the commanding officer. Directly head of them, down a few steps and between the commanding officer and the holographic viewscreen, two angled consoles serve as duty stations for Operations (port) and Flight Operations (starboard). Next, and facing into the heart of the bridge to allow maximum participation with the rest of the bridge crew are duty stations for science (port) and tactical operations (starboard). Directly behind the commanding officer, and in a further break from tradition, a combined duty station serves as positioning for the two most senior advisors and assistants to the ship's commander; the Strategic Operations Officer (port) and Executive Officer (starboard). Around the outside of the bridge, there are countless other additional stations. Behind the main science station on the port bulkhead, additional science and medical consoles are available for mission operations, as well as access to life support and environmental controls. Adjacent to them on the starboard bulkhead, mission operations and security stations ensure the continued safety of the ship and crew on a day to day, mission by mission basis. On the aft bulkhead, engineering is the focus. With a large, entirely interactive and customizable master systems display (MSD) and other engineering controls, the representative from engineering has full access to the ship's systems.
+
##Select the start date as today's date.
 
+
##Select 'In Progress'  as the mission status.
Around the command center, four doors provide access to and from the bridge. On the forward port bulkhead, access is available to the observation lounge, whilst the starboard door grants access to the commanding officer's private ready room (available for use by any officer in command of the ship). At the aft of the bridge, both doors provide access to turbo lifts which enable the crew to access the command center from the rest of the bridge. The starboard turbo lift grants express, overridden access to key locations such as engineering, shuttlebay 1, sickbay, tactical astrometrics and transporter rooms 1 and 2.
+
##Upload a mission image if you choose to do so.
 
+
##In the mission summary, provide a short summary of what you will be writing/what kind of writing will go in this mission. Think of this as the TV Guide summary, so you don't need to know the ending or give it away here. Something like "The ''Arcturus'' encounters a powerful anomaly in the Delta Quadrant."
==Notable Crew==
+
##In the mission description, you can provide either the same information as the previous step or provide a more detailed mission summary. You can always come back to expand on this later.
As one of the newer cruiser generation, the Temeraire is home to around 350 personnel from no less than 73 different species and member states of the Federation and beyond. Some of the ship’s more notable crew include:
+
##Scroll up and hit 'Publish.'
 
+
##Now that you've created your mission, go back to your Dashboard and click 'Create Story'
'''Commanding Officer:''' Captain Tharia sh'Elas ''(Andorian Female)''<br>
+
#Create a Story:
'''Executive Officer:''' Commander Vasoch Gor ''(Tellarite Male)''<br>
+
##Click on Create a Story on the Writing Control panel or from your Command.
'''Strategic Operations Officer:''' Lieutenant Commander T'Prynn ''(Vulcan Female)''<br>
+
##Select the appropriate command. You will only be able to select commands where all of these things are true: a.) There is an in-progress mission, b.) You have a story character added, c.) The manifest of that command has your story character displayed.
'''Chief Medical Officer:''' Lieutenant Commander Zinn ''(Deltan Male)''<br>
+
##Select the mission; if there is only one active mission on the command, it will be selected automatically.
'''Chief Flight Operations Officer:''' Lieutenant Dante Rawlings ''(Terran Male)''<br>
+
##Give your story a title by clicking on 'Add a Story Title"
'''Chief Science Officer:''' Lieutenant Akaria Okan ''(Risian Female)''<br>
+
##Give your story a date. This does not have to be precise. 'Mid-2399,' or 'April 5, 2399' are both options. You could also use a stardate, if you wished.
'''Chief Tactical Operations Officer:''' Lieutenant Noli Auru ''(Bajoran Female)''<br>
+
##Select the characters in your story. '''The characters you use must be set to story mode and assigned to your command.'''
'''Chief Operations Officer:''' Lieutenant Linn Mora ''(Bolian Male)''<br>
+
##Add the story content (i.e. the story itself) to the Story Content box.
'''Chief Engineering Officer:''' Lieutenant Prida Rala ''(Bajoran-Cardassian Hybrid Female)''<br>
+
###It is neither necessary nor appropriate to "sign" your posts with character names, as awards are given by word count.
'''Counsellor:''' Lieutenant J.G. Vittoria Chiera ''(Betazoid Female)''<br>
+
##Hit publish.
 
+
##Fiction ribbons will be assigned automatically after your story is published.
==Deck Layout==
+
#Create a Story with multiple authors:
{| class="wikitable"
+
##Follow the same steps above, up to step 7.
|- style="font-weight:bold;"
+
##Make sure that every author has at least one character linked on the story.
! Deck
+
##Instead of hitting publish, hit "Save" if you are leaving room for other authors to add more content.
! Description
+
##Your fellow authors will get an email and be able to see that the story is waiting for an update on the control panel.
|-
+
##Each author should add their content, and then hit save.
| 1
+
###If a post is accidentally posted before you are finished with it, you must inform the OCS '''''immediately''''' so that duplicate ribbons can be deleted.
| Bridge, Captain's Ready Room, Observation/Conference Lounge
+
##Once all of the authors are satisfied with the story, the last person should hit "Publish."
|-
+
###It is neither necessary nor appropriate to "sign" your posts with character names.
| 2
+
##Joint-writing ribbons will be assigned automatically after your story is published.
| CO's Quarters, XO's Quarters and Office, Enlisted Affairs Office, Emergency Batteries, Weapons Locker
+
[[File:Writing1.png|center|thumb|Click on the Writing Panel to access the writing controls.|alt=]]
|-
+
[[File:WritingControlsPanel.png|center|thumb|The buttons here will take you to the individual screens necessary to write on the BFMS and to do a wide range of other things.]]
| 3
+
[[File:Writing2.png|center|thumb|The create mission screen.]]
| Mess Hall, Senior Officer Quarters, Aft Viewing Lounge, Communications Array, Officers' Quarters, Gymnasium
+
[[File:SelectCommand.png|center|thumb|Before you can create a story, you must select a command. ]]
|-
+
[[File:Writing3.png|center|thumb|The story screen.]]
| 4
+
[[Category:Guides]]
| Officer Quarters, Crew Quarters, VIP Quarters, Transporter Rooms 1 & 2, Emergency Batteries, Chief Operations Officer's Office
 
|-
 
| 5
 
| Security Offices, Brig, Armoury 1, Security Training Facilities, CIO's Office, Aft Tactical Sensors, Crew Quarters, Holodecks 1 & 2, Cargo Bay 1
 
|-
 
| 6
 
| Main Computer Core (Level 1), Main Computer Core Control, Flight Control Room 1, Science Labs, Arboretum, Diplomatic Facilities, Civilian Quarters, Crew Quarters, Holodecks 3 & 4, Main Shuttlebay (Upper Level)
 
|-
 
| 7
 
| Main Computer Core (Level 2), Main Shuttlebay Flight Deck, Tactical Astrometrics/Stellar Cartography, Main Science Lab, CSO's Office, Counsellor's Office, Hydroponics Bay, Ship's Library, Civilian Quarters, School, Officer's Mess, Main Sickbay and Medical Facility, CMO's Office
 
|-
 
| 8
 
| Main Computer Core (Level 3), Impulse Assembly, Weapons Locker, Engineering Lab, Shuttlebay Elevators, Upper Shuttle Maintenance & Storage, Forward Tactical Sensors
 
|-
 
| 9
 
| Main Computer Core (Level 4), Impulse Engines, Warp Core Subsystems, Lower Shuttle Maintenance & Storage, Dorsal Docking Port, Emergency Transporters, Crew Quarters
 
|-
 
| 10
 
| Impulse Assembly, Deuterium Injectors, Shuttle Repair & Machine Shop, Engineering Support Area, Industrial Replicators, Armoury 2, Crew Quarters, Holodecks 5 & 6, Primary Environmental Control, Cargo Bays 2-5
 
|-
 
| 11
 
| Auxiliary Deflector Controls, Shuttle Elevator Assembly, Airlock, Crew Quarters, Transporter Rooms 3 & 4, Airlocks, RCS Thrusters, Secondary Stores, Secondary shuttlebay (upper)
 
|-
 
| 12
 
| Auxiliary Deflector Array, Primary SIF/IDF/Shield Generators, Systems Support Compartment, Maintenance Bay 1, Secondary shuttle bay (lower)
 
|-
 
| 13
 
| Torpedo Turrets Access, Torpedo Storage, Main Sensor Array, Deuterium Tanks, Science Labs, Crew Mess Hall (Aft), Maintenance Bay 2, Shuttle Storage
 
|-
 
| 14
 
| Deuterium Tanks, Flight Control Room 2, Turbolift Maintenance, Crew quarters
 
|-
 
| 15
 
| Captain's Yacht Access, Secondary Computer Core (Level 1), Weapons Locker, Transporter Room 5, Cargo Bays 6 & 7, Tertiary Stores
 
|-
 
| 16
 
| Secondary Computer Core (Level 2), Reserve Antimatter Storage, Main Navigational Deflector, Deflector Control, Main Engineering, Chief Engineer's Office, Weapons Locker, Warp Nacelle Access, Cargo Bays 8 & 9, Emergency Transporters, Auxiliary Sickbay, Secondary Computer Core (Level 3), Aft Sensor Array, Deflector Assembly, Secondary Plasma Vent, Emergency Transporters
 
|-
 
| 17
 
| Deflector Assembly, Auxiliary SIF/IDF/Shield Generators, Multi-purpose Chamber (Upper), Crew Quarters, Auxiliary Bridge, Lateral Sensors, Secondary Communications Array, Emergency Batteries, Complementary Deflector Assembly, Multi-purpose Chamber (Lower), Primary Stores, Forward Torpedo Launchers (2), Torpedo Magazine, Probe Storage, Primary Communications Array, Tractor Beam Assembly, Turbolift Maintenance. Primary Waste Reclamation
 
|-
 
| 18
 
| Antimatter Storage Pods, Forward Tractor Beam Emitter, Secondary SIF/IDF/Shield Generators, Cargo Bay 10 (Upper), Secondary Stores Antimatter Generator, Torpedo Magazine, Maintenance Bay 3, Cargo Bay 10 (Lower), Secondary Waste Reclamation, Secondary Environmental Control, Tractor Beam Assembly, Antimatter Generator, Antimatter Injectors, Secondary Sensor Array, Sensor Analysis Suite, Aft Tractor Beam Emitter, Aft Torpedo Launchers (2), Torpedo Magazine, Warp Core Jettison Hatch
 
|}
 
 
 
==History of the USS Temeraire==
 
 
 
===USS ''Temeraire'' In play===
 
*Temeraire was formally known as Thesis, with her name changed as part of her new look following an inquiry that saw her previous commander removed from command.
 
*Previously cordial relations have turned sour as the Thesis crew resent those from the [[USS Santa Fe|Santa Fe]] who have transferred in and took their jobs, replacing respected crew mates (including the captain).
 
*Temeraire is one of the first vessels, in-character, to be assigned to [[Task Force 47]] and will add strength to the new diplomatic and exploration focused pathfinder group.
 
[[Category:Task Force 47]]
 
{{DEFAULTSORT:Temeraire}}
 

Revision as of 14:03, 28 April 2022

This guide will help you learn to use the integrated fiction writing system on the BFMS, i.e. Bravo Fleet's main website. These instructions are for those members with commands, which anyone with the rank of Ensign or above can request. For those without commands, consider writing on Starbase Bravo. For more information on the non-mechanical aspects of fiction writing, check out the Lore Office's Introduction to Bravo Fleet Writing.

The basics of the fiction system are that a command is the ship or station where a mission is set (the 'command' for Star Trek: The Next Generation would be the Enterprise-D), missions are like episodes (the first mission for TNG would be "Encounter at Farpoint"), and stories are like scenes (the first story in "Encounter at Farpoint" would be the Enterprise encountering Q for the first time).

Steps to Create a Mission and Story

The steps for those members with their own commands differ slightly from the above instructions.

  1. Create a Mission:
    1. Navigate either to your command or to the Writing Controls panel of your dashboard. From your command click 'Add Mission.' From the Writing Controls panel, click 'Create Mission.'
    2. Give your mission a title.
    3. Select your command
    4. If this is part of a fleet-wide or unit-wide plot, select the appropriate parent mission. Otherwise, you can ignore this field.
    5. Do not check 'Fleet-wide mission' or 'Unit-Wide Mission.'
    6. Select the start date as today's date.
    7. Select 'In Progress' as the mission status.
    8. Upload a mission image if you choose to do so.
    9. In the mission summary, provide a short summary of what you will be writing/what kind of writing will go in this mission. Think of this as the TV Guide summary, so you don't need to know the ending or give it away here. Something like "The Arcturus encounters a powerful anomaly in the Delta Quadrant."
    10. In the mission description, you can provide either the same information as the previous step or provide a more detailed mission summary. You can always come back to expand on this later.
    11. Scroll up and hit 'Publish.'
    12. Now that you've created your mission, go back to your Dashboard and click 'Create Story'
  2. Create a Story:
    1. Click on Create a Story on the Writing Control panel or from your Command.
    2. Select the appropriate command. You will only be able to select commands where all of these things are true: a.) There is an in-progress mission, b.) You have a story character added, c.) The manifest of that command has your story character displayed.
    3. Select the mission; if there is only one active mission on the command, it will be selected automatically.
    4. Give your story a title by clicking on 'Add a Story Title"
    5. Give your story a date. This does not have to be precise. 'Mid-2399,' or 'April 5, 2399' are both options. You could also use a stardate, if you wished.
    6. Select the characters in your story. The characters you use must be set to story mode and assigned to your command.
    7. Add the story content (i.e. the story itself) to the Story Content box.
      1. It is neither necessary nor appropriate to "sign" your posts with character names, as awards are given by word count.
    8. Hit publish.
    9. Fiction ribbons will be assigned automatically after your story is published.
  3. Create a Story with multiple authors:
    1. Follow the same steps above, up to step 7.
    2. Make sure that every author has at least one character linked on the story.
    3. Instead of hitting publish, hit "Save" if you are leaving room for other authors to add more content.
    4. Your fellow authors will get an email and be able to see that the story is waiting for an update on the control panel.
    5. Each author should add their content, and then hit save.
      1. If a post is accidentally posted before you are finished with it, you must inform the OCS immediately so that duplicate ribbons can be deleted.
    6. Once all of the authors are satisfied with the story, the last person should hit "Publish."
      1. It is neither necessary nor appropriate to "sign" your posts with character names.
    7. Joint-writing ribbons will be assigned automatically after your story is published.
Click on the Writing Panel to access the writing controls.
The buttons here will take you to the individual screens necessary to write on the BFMS and to do a wide range of other things.
The create mission screen.
Before you can create a story, you must select a command.
The story screen.