From UFStarfleet LCARS
- 1 =^= Credits =^=
- 2 =^= Introduction =^=
- 3 =^= Administration =^=
- 4 Ships Departments (Roleplay)
- 4.1 =^= Command =^=
- 4.2 =^= Operations =^=
- 4.3 =^= Security =^=
- 4.4 =^= Medical =^=
- 4.5 =^= Science =^=
- 4.6 =^= Engineering =^=
- 4.7 =^= Other =^=
- 5 =^= Misc Information =^=
=^= Credits =^=
Originally written for [SS Tranquility]
- Written by: Ezra Sweet
- Audience: Potential & Current crew of USS Menelaus
- Created: 110604
- Last Revision: 120714 by Tedra Llewellyn
=^= Introduction =^=
This Document is intended to layout in one place, in a clear and simple manner, the operational procedures aboard USS Menelaus.
USS Menelaus is a 24/7 Role play vessel. All UFS people are expected and required to be aware of this and in character at all times.
USS Menelaus operates under the following UFS policies:
- Code of Conduct
- UF Starfleet General Orders
- Starfleet General Orders
- Group and SIM Rules
- Beta Antares Group and SIM Rules
If you have any questions, concerns or suggestions regarding the Menelaus Operating Procedures, please contact the ships Commanding Officer Ezra Sweet or the Exeutive Officer Tedra Llewellyn
=^= Administration =^=
Every Saturday 0900SLT - 1000SLT
Meetings are optional, however attendance is strongly encouraged.
The most senior officers of each branch is expected to give a short report at the end of this meeting (This is a role-play report to bring all up to speed with where we left off the last mission)
Every Saturday 1000SLT - 1200SLT
Missions are not optional. Crew are required to attend at the very least 2 Missions a month.
If you are unable to attend, every effort should be made to inform the ships CO or XO prior to the mission.
Recruitment is the responsibility of all ships members. If you are interested in joining the ship, please look to the Menelaus Forum where vacant posts are mentioned.
[Current Vacancies] or alternative the table below:
|USS Menelaus Command|
|Commanding Officer||Tedra de Arr (Tedra Llewellyn)|
|Executive Officer||tlhepa' (Tlhepa Gurbux)|
|USS Menelaus Crew Vacancies|
|Operations/Communications Officer||1 Vacancy|
|Engineering Officer||0 Vacancies|
|Security Officer||2 Vacancies|
|Science Officer||1 Vacancy|
|Medical Officer||2 Vacancies|
|Ship's Nursing Staff||1 Vacancy|
Inbound officers will not be given senior officer posts immediately. Each and every officer has to show that they deserve the post and can join as Ensign for a 2 week trial period. At Each mission within those 2 weeks the command and Department head are voting for the candidate. The officer needs two votes to continue serving on the ship if they have performed well and within the guidelines. After the 2 weeks, the CO, XO and Department Chief will discuss the officer’s performance and either approve or decline the application
- The first week is to see the officer in action.
- The second week we give help if needed in RP and all else.
- By the end we will judge if the officer can or cannot improve or be good to go and continue serving on the ship.
Final acceptance of a new recruit to join the ship is the right of the ships command staff alone.
- Senior Officers:
Senior Officers are appointed by Command on ship. Where ever possible, Senior Officers will be appointed from existing crew rather than brought into the ship to fill the role.
- Departmental Positions:
The filling of these positions is at the discretion of the Senior Officer to that department. This includes a vice head of department.
Leave of Absences And Terminations
Menelaus is founded on the belief held across UFS that Real Life (RL) comes before Second Life (SL)... always... without exception. As such, UFS LOA process has been designed to take this into account.
Menelaus abides by the UFS Leave of Absences And Terminations policy. As of Stardate 130324 the membership process has changed. As of above Date, new membership Registration lies directly within the database (http://tinyurl.com/ufs-membership-application)
- When you register your account in the database (if you havent done so, please do so) you will be a member for 1 year
- You can renew your membership for another year through the database (fill in the renewal form) or by sending an email to email@example.com after your database is locked when your membership expires
Basically this means that UFS no longer has LOA`s, retirements, civilians or other designations just members
When you register your membership with UFS, how active you are is really up to you. The CO can still do your assignments, promotions and transfers (off and onto the ship/station) but you are still a member as long as you have an active database account. For Transfers please IM the CO or XO and for LOA please use our LOA or Off Duty Form
Obviously you can still be classed as a civilian on your chapter and has really nothing to do with your UFS membership
Mission reports are important for us to track how you are progressing in role plays and also play an integral part of any promotion request. They can be broken down into 2 parts.
- Crew/Senior Officers (or Vice Department head in Senior Officers absence)
If you are the last person in your department to be present at the end of the mission, you do the report. Same goes if you are the last person of your department to leave before the mission is over.
In any other case, it's up to the Department. Department heads need to get their crew together and agree on some internal routine. Then they submit their report, to the First Officer within 48 hours of the end of the last Mission. A copy of the template can be obtained from your Department CO or XO
- First Officer (or Second officer in XO's absence)
The First officer completes their report, and then submits this report to the mission brief on the forum. The XO in turn then attaches the report from each department head into separate posts.
An example of the completed Forum log can be found [Here]
A list of report templates can be obtained from the Menelaus LCARS Database
These are as required for your Branch at HQ. You are welcome to send a copy to the Command on ship for further info on your monthly activities, though it is not required.
Ship Status Reports
Command will issue a Ships status report at least 48 hours before the next mission. This is an effort to ensure that all crew are fully aware of ships information prior to the next mission.
The Console on the left side of the Turbolift on Deck 1 distributes this information.
Personal logs are kept on the UFS Forum. These are fun ways to develop your character at a personal level and even continue the role play in ships downtime
Some good examples of crew logs are found here:
- Emilie Chardin: [Personal Log]
- Data Giant: [Personal Log]
- Reina Beaumont: [Personal Log]
Fleet Roll Call
Roll Call is a critical component of the administration of UF Starfleet. Roll Call serves the following purposes:
- Provides Command with an accurate listing of UFS Branches, Divisions, Starbases, Starships and Outposts
- Provides Command with a current roster of UFS Personnel
- Provides a guideline with which to reassign members from our group that have decided to leave or have become inactive to a correspondent status
- Eliminates the problematic and inaccurate practice of using Instant Messages and Notecards for Roll Call
Officers assigned to USS Menelaus are responsible for their own reporting on the UFS Fourm in their respective Branch Sections.
Click Roll Call for information about the process
Failure to report for Roll Call will result in ejection from their branch and reassignment to SS Abitus. This is automated
IMPORTANT NOTE: Officers reassigned due to roll call failure that subsequently reapply for Menelaus will only be accepted at the discreation of the ships CO.
Promotions aboard Menelaus comply fully with UFS Promotions guidelines.
It is the responsibility of your Commanding Officers to ensure that they are doing everything they can to help you meet the grade. Promotion requirements are set out by Department Chiefs, each rank requires more classes starting with the various intro courses within the UFS Academy. First off, TiG will be strictly enforced. That said, it is not, nor has it ever been the only thing we are considering when writing promotion recommendations. We consider a number of things, probably the most important of which is Loyalty and Dedication. Lt. Commander and Commander also require a Test, set out and monitored by the Commanding officer and/or XO.
Officers that serve a lengthy time aboard the Menelaus consecutively prove their loyalty to this command. Officers that go above and beyond to help make this command the best it can be prove their dedication. Participation also factors in, i.e. how vocal you are in the RP's and/or your attendance record. All this factors in at the end of the month.
Now we say this once and only once, so we suggest you heed this. IF YOU ASK ME ABOUT GETTING PROMOTED, YOU NEVER WILL BE. We are fully aware who is or isn't ready for a promotion. If you earned your rank you will surely get it as you were performing exemplary and in a dedicated manor. If you do not, it doesn't necessarily mean you aren't a good officer, rather that we feel you haven't really pushed yourself to be the best you can be. It also doesn't mean you wont get it the following month either. It all depends on you.
We would like to point out that at the end of the TiG period a meeting with the CO can be requested and there we can lay out a plan in order to get you your promotion. But it has to be done in a civilized manner. If you come to us yelling, screaming, cursing, kicking, etc, we can promise you it will be a very long time before you move up. We strictly do not give out pity promotions. We want each and every one of your promotions to mean something to you.
Should the promotion request be denied by UFS Promotion board, we will hold a meeting again with you to discuss their outcome.
From time to time, awards will be granted to officers serving aboard USS Menelaus. These are submitted, as required, by the CO at the end of each month. Department Heads are encouraged to bring to the attention of the CO any officers deserving of an award, which award and why.
A list of awards can be found at UFS Awards
From 2388 (2013) onwards we also will have Ships awards, whereas the CO/XO will be able to also give awards out to the crew or individual crew members.
|Service Time Ribbons|
|GM - Campaign Awards|
|USS Menelaus Honor Award|
|USS Menelaus Golden Award|
|USS Menelaus MVAM - Tactical Award|
|USS Menelaus Dedication Award|
|USS Menelaus Combat Service Award|
The Sandbox is free for all assigned officers to use, however any and all unauthorised projects being constructed in the Sandbox will be summarily returned. The purpose of the sandbox is for the betterment of the Menelaus, the Talisman and the Pathfinder Research Station, not your own personal projects.
Ships Departments (Roleplay)
This section underlines Roleplay aspects to each branch:
=^= Command =^=
Command is responsible for the USS Menelaus as well as the safety of the Crew. Command is required to receive and carry out the orders of UFS Command as well as maintain the general operational running of the ship, such as assignment of officers. All other departments report to Command on a regular basis to ensure that the correct decision is made on the most accurate and up to date information.
Chain of Command
The Chain of command can be quite complex, however detailed here is a concise explanation of its operation aboard Menelaus
- Commanding Officer
- Executive Officer
- Second Officer
- Chief Security Officer
- Chief Engineer
- Chief Operations Officer
- Chief Medical Officer
- Chief Science Officer
- Emergency Command Hologram (E.C.H.)
If you are aboard ship, then the person in Command is anyone online, highest up this list, and aboard ship at that moment. Taking over the command of the ship follows the CoC until the Second Officer, then after it is the higest ranking senior officer on obard. The only separation from this is if the commanding officer (at the time) leaves the bridge with someone specifically. Then that person is in command, regardless of who else is aboard and what rank or position they hold, they may however relinquish command to a more senior officer.
Said person can only be relieved by the ships Commanding officer or Executive Officer.
(For a Canonical Example of this please watch TNG: The Arsenal of Freedom)
Ship Status Reports
Command will issue a Ships status report at least 48 hours before the next mission. This is an effort to ensure that all crew are fully aware of ships information prior to the next mission.
The Console on the left side of the turbolift on Deck 1 distributes this information.
Menelaus is a ship of war; therefore her operation is more sensitive to the state of UFS Defense Conditions. All UFS officers, while aboard the ship, must adhere to the following:
DEFSTAT 5 Normal Operating procedure
DEFSTAT 4 Chief of Security prepares a series of Drills ready to be run should the DEFSTAT level be raised. All sidearm’s and rifles aboard are checked by security to ensure full functionality. Level 4 Diagnostics are run on, Defensive, Propulsion and Communication systems - this is repeated every 4 hours.
DEFSTAT 3 All personnel, regardless of branch, are issued sidearm’s (Phaser Type II only) by security. The Chief of Security proceeds to run a series of Security and Tactical readiness drills. Sensitive areas of the ship are placed under armed guard. Level 4 Diagnostics are run on key systems, Offensive, Defensive, Propulsion, Environmental, Life Support and Communication - this is repeated every 2 hours.
DEFSTAT 2 All shore leave is cancelled. The ship prepares it's self for orders to postpone all current missions from the Chief of UF Starfleet Operations and divert to join the fleet as required. The ship is at constant yellow alert and all transmission are on secure channels regardless of content. Level 3 Diagnostics are run on key systems, Offensive, Defensive, Propulsion, Environmental, Life Support and Communication - this is repeated every 2 hours. A four-shift system of six hours is immediatly implemented at the end of the current crew shift cycle; to keep crew fatigue down. This is maintained untill DEFSTAT is lowered or the Captain or Chief Medical Officer orders otherwise.
DEFSTAT 1 Ship aborts current mission and communication with the Chief of UF Starfleet Operations is made for further orders. All non UFS personnel are offloaded at the earliest available safe opportunity and the ship goes into lock down.
UFS current DEFSTAT Status can be viewed [here]
NOTE: The Issuing of Phaser Rifles is only authorised by the CO, XO, SO or Chief of Security.
=^= Operations =^=
Operations are responsible for resource allocation on the ship, be it personnel or ships systems. Operations also maintain the Communications and Helm functions. Operations officers are required to be familiar with the ships design, capabilities and the crew that are assigned. They are also expected to aid engineering from time to time as well as play a key role in any modifications to the ship conducted by engineering.
USS Menelaus runs a 3 shift rotation
- Alpha Shift: 0800 - 1630
- Beta Shift: 1600 - 0030
- Gamma Shift: 0000 - 0830
When UFS raises DEFSTAT to reach or exceed level 2, A four-shift system of six hours is implented to keep crew fatigue down.
- Alpha Shift: 0800 - 1400
- Beta Shift: 1400 - 2000
- Gamma Shift: 2000 - 0200
- Epsilon Shift:0200 - 0800
The Bridge of a starship is the nerve centre during any crisis situation. It is imperative that all officers assigned to the bridge know the roles inside and out as well as that standard practices aboard the bridge of a starship.
In accordance with academy classes Bridge Teamwork & Bridge Duty Stations the Menelaus follows standard practices.
Details on how these work uniquely can be found in the Menelaus Bridge Best Practises
Ship Alert conditions & Operational modes
- Condition Green
Standard Operating condition and peace time status of all UFS vessels. Crew Perform their regular routine duties; while off duty they may engage in personal hobbies, continued research, fraternise, and ebjoy the limited recreational facilities aboard. The Mandatory crew stations on the bridge at Green Alert are as follows:
- Commanding Officer
- Helm Officer
- Operations or Science Officer
- Security/Tactical Officer
Even at green alert, 40% of this ships weapons are on standby for quick power up, 1 shuttle is ready for launch in 5 minutes and the Operations manager, or Executive officer runs a level 4 Diagnostic of ships systems every 8 hours. Gamma Core is at full power, Beta runs at minimal power more and Alpha core is offline.
- Yellow Alert
The senior bridge officer (or the Captain and First officer at any time) can place the ship on Yellow Alert. This alert signifies the possibility of combat, hazardous flight conditions, or ships system malfunction. At Yellow alert, sleeping personnel wake, dress, and equip themselves. Off Duty personnel stand by in their quarters for assignment to their departments. Senior Bridge officers report for duty. All Crew members keep an eye out for anything out of the ordinary, reporting any strange readings, damage, or occurrence. Ships weapons arm, and the operations officer clear the decks of all low level system operations, such as holodecks or scientific surveys and so forth. The Operations officer or Executive officer runs a level 4 Diagnostic of the ships systems immediately. Beta and Alpha Cores are brought to hot standby mode. The ships Captain comes to the bridge if not their already.
Note: This alert condition is standard operating mode when UFS is at DEFSTAT 2
- Red Alert
Only the Captain or the senior officer in commmand can order red alert. In theory, a ship should go to Yellow alert first, which should bring the captain to the bridge to decide on red alert status. In Practice, crises don't always wait for turbolifts. On Red alert, all personnel head to battle stations. Security personnel fan out to transporter rooms and other strategic locations throughout the ship. Medical personnel report to sickbay and other duty stations. Engineers check and wait near critical systems. All ships cores are brought to full power. All shuttle crews report to shuttlebays, and all shuttles warm up. Weapons arm and load; shields come up. Active sensors begin sweeps at all ranges. The computer automatically runs a level 4 diagnostic check continuously.
Note: This alert condition is standard operating mode when UFS is at DEFSTAT 1
- Blue Alert
An alert condition that signifies exceptional situations are taking place, such as Docking and separation manoeuvres, landing protocols or environmental hazards. Except when initiating MVAM, Alpha and Beta cores are brought to hot standby. This condition simulates yellow alert, however the action required by the crew is generally varied, so the commanding officer will communicate with all crew the reason for the blue alert so that the correct actions can take place.
- Intruder Alert
This Operational mode is similar to Yellow Alert, but focuses on an internal breach of security. All non essential personnel are confined to quarters or duty stations for the duration of the emergency. Movement through the ship requires authorisation from an immediate superior officer and all turbolifts key to authorisation codes only. Armed Security teams patrol each deck, with teams stationed at sensitive areas of the ship. The Security Officer mounts a full internal scan of the ship, ready too seal bulkheads, flood the decks with anashtezine, or any other response required.
- Medical Alert
In the event of an outbreak, this operational mode confines all personnel to their current locations, while environmental controls isolate life support systems for each deck. This ensures that the contagion does not spread throughout the ship or facility. Priority power is routed to sickbay, and the Chief Medical Officer runs a full internal scan of the ship. If the infection involves the Gamma core, Alpha core is brought to hot standby in anticipation of taking over from Gamma core.
- Abandon ship
If the commanding officer considers the vessel lost, s/he may give the order to abandon ship. All shuttle crews ready their craft and prepare for immediate departure. If a habitable planet is in range, ships power transfers to all transporters. All personnel report to a designated mustering station in the event of the abandon ship order being given, with the key supplies on their evacuation roster. Lifeboats are enabled, and launched by either the bridge or by their occupant. A Microwarp buoy is launched containing a subspace transmitter and a copy of the ships logs. The operations officer or first officer oversees the evacuation of the ship while the rest of the bridge crew works to contain the emergency that caused this drastic measure.
- External Support Mode
State of reduced activity that exists when a ship is docked at a starbase or other support facility. The ship essentially remains at Condition Green operational modes. When docked at a UFS instalation the ships navigational computer is placed under the control of the station to which she is docked. Other systems are handed off to the facilities computer as required.
- Reduced Power Mode
An operational setting that is invoked during a major power systems failure aboard ship, such as critical fuel shortage or damage to the ships power generators. The responsibility of monitoring power usages falls to the Chief of Operations.
Systems that are taken offline are:
- Tractor beam systems
- Non essential and unsued work stations
- Power and life support to unsued quarters and rooms.
- Other unused Warp Cores
Systems that have reduced power to them are:
- Life and Environmental systems
- Propulsion systems
- Deck illumination systems
- All Non essential computer activity is suspended.
- Warp Core Operations is reduced
The Captain alone has to authorise any systems operation that falls outside of these parameters.
Under this operational mode, a call to Red alert will bring Weapons, Sheilds and Propulsion to full power so the ship can escape rather than engage in prolonged combat.
This mode is also activated if control of the ships power functions transfers to the less powerful Alpha core. Reduced Power mode can also be used to gain a tactical advantage against sensor readings at the expense of weapons.
All officers and crewman assigned to Menelaus are issued accommodation aboard ship for the duration of their assignment.
|Prim allowance personal things|
|Senior Officer/Dept. Chiefs||25|
|Junior Officer||15/20 depending on primstatus|
Standard Living Quarters typically include a small bathroom, living/working space, food replicator and a bedroom.
- Crew Quarters are located on Decks 3, 4 & 5 (right hand side of the ship)
- Senior Officers Quarters are located on Deck 2 (right hand side of the ship)
Non UFS Personnel assigned to the ship will be assigned any free quarters on deck 5 (excl VIP)
Many of the Menelaus's missions require crew to be away for extended periods of time far from the comforts of a Starbase or UFS Planet. As such, the ship is equipped to provide a home from home for the crew during off hours.
- Gym Facilities
Some Degree of physical fitness is required in Starfleet Officers, and like all ships, Menelaus provides facilities for crew to maintain that aboard. Located on Deck 4, the Gym provides excersies equipment and a martial arts mat.
- Target Range
The target range, located on Deck 5, provides of self healing polymer absorptive targets, and standart 2D targets
There is 2 medium sized Holodeck aboard, one located on deck 5 the other one deck 7 close to cybernetics. The crew can chose their Holodeck hours as they wish. If there are any questions, please refere to the XO for clarification.
- Crew Mess hall (Five Forward)
Located Aft of Deck 5, the crew mess hall looks out to the front of the vessel. This room affords comfortable resting space. Eating accommodation is provided by means of food replicators and a kitchen. Also a small Bar and a Greedy Greedy table are provided for some entertainment
Multi-Vector Assault Mode Process
Abandon ship procedure
Ships crew will follow the standard UFS policy for uniforms found here: Uniform Policy
Wearing attire not listed in the above policy is at the discretion of the ships Commanding Officers.
=^= Security =^=
Security is responsible for the security of UFS assets and personnel. Aboard Menelaus, Security officers primarily manage both internal security and external tactical operations. They do this primarily in a defensive manner and maintain crew proficiency with regular drills. Ships Security coordinates its efforts with the Ships Command.
Menelaus is equiped with two standard issue weapons for personnel
All Side arms are stored in the ships armoury as well as scattered about various decks in key locations.
The Chief of Security is responsible for the control and maintenance of phasers and rifles; as such a strict policy has been designed and can be found here
Menelaus Sidearm Control Regulations
Tactical Analysis Reporting
Upon contact with unknown species, security will be required to complete a tactical analysis of the species and vessels encountered. This will then be submitted to Menelaus Command & UFS HQ (Wiki) for archiving. Where appropriate these reports may also be sent directly to UFS Command, UFS Intelligence, UFS Security & UFS Marines for immediate briefing.
Contact with known species, which have made technological improvements that pose a threat to UFS assets will also require a report to amend existing information.
The Chief of Security will delegate this task as each report is required.
A copy of the reporting template can be found on the Menelaus LCARS Database
During an emergency, Security will place under guard, computer security control or total lockdown the following areas of the ship:
- Deck 1
- Alpha Engineering
- Beta Engineering
- Gamma Engineering
- Deck 6
- Brig (if occupied)
- Computer Core
- Torpedo Control Rooms
- Phaser Control Rooms
- Life Support Control
- Shuttle Bay & Airlocks
- Transporter Rooms
- Cargo Bays
- VIP Passengers
=^= Medical =^=
Medical is responsible for the wellbeing of all the crew, including any other souls aboard. They are required to treat any and all medical situations. While Menelaus may not be suited for large scale emergencies, she is fitted with the latest medical systems and equipment. Medical staff is required to keep the ships medical equipment well stocked and report any system problems to engineering immediately.
All officer serving aboard Menelaus are required to report for a complete a full physical at least once every quarter. Medical staff will contact you prior to your physical to arrange it, and while some leeway will be granted, medical staff can remove your from active duty should you not complete said physical
Also, any officer spending more that 2 weeks off ship on an away mission, is subject to a complete physical upon returning to the ship prior to resuming duties.
Ship Wide Quarantine Protocol
=^= Science =^=
Science is responsible for the cataloguing and research of things encountered during the ships missions. Their research is key to understanding the Life, Politics and Astronomical Phenomena’s that dictate the way UFS operates in the DQ. While Menelaus is not focused toward Science and as such is limited in its scientific abilities, its primary function will place it into the uncharted regions of space and so Science officers play a key role in providing preliminary data to UFS from which further Scientific mission can be charted.
The primary scientific data that Science officer aboard will capture is as follows:
The primary function of UFS, is to seek out new life and civilisations within the confines of UFS Policy and Regulations.
In Conjunction with Medical, Science Officers will document their findings for submission to UFS Science, Medical, Inteligence, Security and Command as required
A copy of the reporting template can be found on the Menelaus LCARS Database
The exploration of the Delta Quadrant is a massive undertaking.
Science teams will document their findings for submission to UFS Science, Intelligence, Security and Command as required
=^= Engineering =^=
Engineering is responsible for maintaining ships systems in order that the Menelaus remains at peak operational performance.
Maintenance is a routine duty of Engineering officers. There are several routine maintenance duties required at regular intervals.
The Transporter Systems requires several Maintenance checkups that are done weekly and monthly.
A Level 4 Diagnostics needs to be completed on the transporter system once a month, with decreasing intervals during heavy use of the transporters.
This Maintenance procedure includes a Scatter and Decontamination transport run followed by an overall cleaning from the Pads to the Controls. This needs to be done to clean dirt particles and anything else that might get into a transporter and remove it from the system. This is to prevent anything from getting into the transportee DNA/matter.
Maintenance should be carried out by officers who have completed the Transporter Certification
Warp Core Ejection
Emergency Core Shutdown
=^= Other =^=
Civilians are generally not found aboard Menelaus unless assigned by UFS Command to perform a function that pertains to the current mission.
Due to the primary function of Menelaus and likely hood her missions will be dangerous, we do not facilitate room for any crew member’s non serving family members.
Deck Layout REFIT
- Alpha Deck 1
- Briefing Room, Captain's Ready Room, XO Ready Room, Escape Pods, Main Airlock, Main Bridge.
- Alpha Deck 2
- Alpha Section Engineering, Senior Officer's Quarters, Supply Room, Transporter Room One, Cargo Transporter Room One.
- Alpha Deck 3
- Alpha Section Engineering, Senior Crew Quarters, Primary Computer Core Access, Primary Life Support, Waste Management,
- Alpha Deck 4
- Hydrophonics, Arboretheum, Sickbay, Operations Office, General Meeting Room, Crew Quarters, Gym/Dojo, Torpedo Control
- Alpha Deck 5
- Crew Quarters, Holodeck 2, Five Forward Messhall, VIP Quarters, Topedo Launch Control, Dockingexits 2x, Engineering Offices, Shooting Range, Auditorium
- Alpha Deck 6
- Captain's Yacht, Cargo bays 1 & 2, Impulse Engines, Main Engineering
- Beta/Gamma Deck 4
- Science Labs, Jeffrey Tube Access to deck Beta/Gamma 6
- Beta/Gamma Deck 5
- Beta Warpcore Upper Level, Main Shuttlebay upper level
- Beta/Gamma Deck 6
- Main Engineering, Main Shuttlebay
- Beta/Gamma 7
- Shuttle Storage & Maintenance, Cybernetics
- Beta/Gamma 8
- Astrometrics, Holodeck 1,
- Beta/Gamma 9
- unassigned / storage
- Beta/Gamma 10
- Security, Armory, Hazard Team, Intel Room, Brig, CSO Office
- More Deck listings to come
=^= Misc Information =^=
Role Play Rules (OOC information)
Rule Number 1: Except for Christmas holidays there won't be any weekend without a mission if we can help it, as long as the Sim and ship are there.
We currently have 5 seasoned GM on board of the USS Menelaus. They are all Senior Officers and in order to maintain a good standard for our missions these will be the primary GM.
We follow on our missions the general Chain of Command. If you are aboard ship, then the person in Command is anyone online, highest up this list, and aboard ship at that moment. Taking over the command of the ship follows the Chain of Command until the Second Officer, then after it is the highest ranking senior officer on board. The only separation from this is if the commanding officer (at the time) leaves the bridge with someone specifically. Then that person is in command, regardless of who else is aboard and what rank or position they hold, they may however relinquish command to a more senior officer.
Said person can only be relieved by the ship's Commanding officer, Executive Officer or Second Officer.
Also we want to encourage officers to become GM’s. For this reason, any officer who presents a mission idea that is cleared with the command officers will be offered the opportunity to GM the Mission but they will not be necessary CO. CO or acting CO will always be a seasoned GM. This does not mean the CO will lead the mission. His/her objective is to observe and help if needed. This will give the officer being GM the possibility to gain experience undisturbed but still with the confidence that there will be someone there if help is needed. The CO will not take over the mission except as last resort.
Most players on board are already established characters, so I won't go to the character creation. Here is a good guide to read about that though:
- No God-modding or perfect characters. (boring!)
- Do not control another person’s character without their express consent.
- Fights between characters should be kept to a minimum and no killing of crew members at all. However, if a fight or killing is unavoidably called for the players concerned must work the action out in PM and both parties should be amenable to the outcome.
- NO Metagaming - The writer of the character will usually know more than the character does. If the writer's character acts on knowledge they can't have that's metagaming.
- Please discuss any issues with either the CO/XO or the Gamemaster via IM. Gossiping about issues or spamming up the story is counterproductive and destructive.
- Try to answer when given an order, everybody can miss an order sometimes but with an aye, yes or repeat of the order, the GM knows that the order was received.
- There is real time (what you experience every day) and game time (time as it passes in the game). The Time is given by the GM and can vary from 1:1 time up to and including time jumps. The player goes ahead with each and acts accordingly.
- UFS conduct is always a given, as we do play in a Star Trek universe.
- And lastly…the GMs’ word is law during an RPG.
Role Plays Submissions
Role-play submission is very much encouraged. Any role-play idea's should be directed to the ships command officers
- Commanding Officer: Tedra de Arr Tedra Llewellyn
- First Officer: tlhepa' Tlhepa Gurbux
Ideas will be reviewed and a meeting arranged to discuss further the idea. Any idea, even in part, that goes forward will be credited accordingly on the Wiki, From 2388 (2013) forward there will also be a Form to be filled out, more soon
As a member of the crew on Menelaus, we would hope that you will help in the continuing growth of the ship. Be it through recruitment, contributions to the Menelaus Star, help with some building and scripting, maybe even an idea of your own. All crew should discuss ideas and ways they wish to help with their immediate CO on the ship. They in turn will then authorise it, or discuss it further with the relevant department. As with all things in UFS, you get out what you put in.