Star Trek: A Call To Duty
Player's Handbook

Chat Edition v.990731

Welcome to Star Trek: A Call To Duty™, Paramount Digital Entertainment's official Star Trek™ Role-Playing-Game.  We are pleased you have decided to heed the call!

The purpose of this handbook is to provide you with the information you will need to participate in the Chat Version of Star Trek: A Call To Duty.   This handbook includes a brief game overview, detailed information about game operation and important game policies.  It is essential that you review this handbook before participating in the game.

Due to the evolution of Star Trek: A Call To Duty  the contents of this handbook will change periodically.   All handbook revisions will be made available for new players to download  and will be distributed to active players via email updates.  Questions about the handbook should be posted to the feedback newsgroup (startrek.rpg.actd.feedback) on Paramount's news server (news.startrek.com).

Game Overview

Role-playing is when a person assumes the identity of a character and acts out that character's thoughts and emotions.  In Star Trek: A Call To Duty role-playing means assuming the identity of a Starfleet officer, exploring strange, new worlds, seeking new life and new civilizations, and boldly going where no one has gone before.

The Chat Version of the game is composed of a series of missions that take place in chat rooms.  As a Starfleet officer, each character is assigned a specific position (Science Officer, Tactical Officer, etc.) on a starship.  The objective of the game is to work with other characters to successfully complete each mission.

During missions characters are presented with various events which require them to make decisions and take action.   The result of character actions are determined by a game host (Assistant Game Manager) and then communicated to the players.  The quality of character decisions and the timeliness of character actions determine the success of failure of a mission.

Star Trek: A Call To Duty is part of the Star Trek: Continuum™ web site on the World Wide Web.  The game and all of the information you will need in order to participate can be found in the Starfleet Academy section, under A Call To Duty.

Game Operation

This section of the handbook contains information on how to role-play, the steps required to begin participating in Star Trek: A Call To Duty, and information on game training and game play.  Questions about this section should be posted to the Feedback newsgroup (startrek.rpg.actd.feedback) located on Paramount's server (news.startrek.com).

Staff and Player Roles

Assistant Game Managers (AGMs)
AGMs are game hosts responsible for game operation.  Their responsibilities include providing game materials, managing the game environment, and maintaining game quality and player satisfaction.

Game Materials - Before each mission begins, an AGM will provide a player with mission orders, the objectives of the mission.  The AGM may also provide additional information to players whose characters will have important roles during the mission.

Game Environment - During each game session, an AGM will communicate information about events that are taking place.   When characters react to these events, the AGM will then communicate the result of character actions to the players.

Game Quality - During each game session, an AGM will prevent visitors from disrupting the mission.  The AGM will also monitor the game session for Terms of Use violations and take action to prevent future violations.

Player Satisfaction - At all times, an AGM will provide an open forum through which players may ask questions, make comments, and submit suggestions.  The AGM will respond to all such correspondence.

Commanding Officers (COs)
COs are players responsible for mission direction.  Their responsibilities include providing game materials and directing fellow players.

Game Materials - Before each game session begins, a CO will provide players with a mission briefing: instructions pertaining to the mission orders.   Mission briefings are not used with training missions.

Player Direction - During each game session, a CO will give direction to the players.  This direction will be in the form of orders from the CO's character to other characters.  It is up to each player to decide whether or not to obey the orders.

Executive Officers (XOs)
XOs are players responsible for mission direction during the absence of the CO.    Their responsibilities include providing game materials and directing fellow players.

Game Materials -  In the absence of a CO, before each game session begins, a XO will provide players with a mission briefing: instructions pertaining to the mission orders.  Mission briefings are not used with training missions.

Player Direction - In the absence of a CO, during each game session, a XO will give direction to the players.   This direction will be in the form of orders from the CO's character to other characters.  It is up to each player to decide whether or not to obey the orders.

Second Officers (2nd Officer)
Second Officers are players responsible for mission direction during the absence of the CO and XO.  Their responsibilities include providing game materials and directing fellow players.

Game Materials - In the absence of the CO and XO, before each game session begins, the Second Officer will provide players with a mission briefing: instructions pertaining to the mission orders.  Mission briefings are not used with training missions.

Player Direction - In the absence of the CO and XO, during each game session, the Second Officer will give direction to the players.  This direction will be in the form of orders from the CO's character to other characters.  It is up to each player to decide whether or not to obey the orders.

Non-Player Characters (NPCs)
NPCs are temporary characters, which are used by players to enhance the game.    NPCs may be used as protagonists or antagonists.  Protagonist NPCs are typically used as allies while antagonist NPCs are typically used as enemies.  To enhance the game, an AGM may request that one or more players assume NPC roles for the duration of a mission.

Communication Protocols

The purpose of communication protocols is to allow all players to participate in the game in an easy, streamlined fashion, which is simple to get used to and remember.  Rather than just 'text on a screen', these protocols allow players the ability to convey emotions, perform actions, and control every facet of their participation in a game.

The importance of the communication protocols lies in the fact that they establish a common 'language' with which to participate.  Since all players adhere to these protocols, it greatly simplifies the understanding of what is actually going on in the game, making the experience richer and more enjoyable.

Each communication protocol is explained below.

Face to Face Communication
This form of communication is used when speaking to another character in the immediate area.  To use Face to Face Communication precede your text with the last name or title of the character to which you are addressing, followed by a colon.  If you are speaking to everyone there is no need to reference a name or title.

Examples:
   Lt. Johnson:
        Captain: The Gorn are firing on the planet.

    Ens. Taylor:
        Captain: They have fired on the survey team's position.

    Capt. Harris:
        Taylor: Lock on to the survey team and beam them directly to sickbay.

    Ens. Taylor:
        Captain: Aye sir, establishing transporter lock.

    Capt. Harris:
        Johnson: Hail the Gorn ship.

    Lt. Johnson:
        Captain: Hailing frequencies open, sir.

Non Face to Face Communication
This form of communication is used when speaking to another character out of the immediate area.  To use Non Face to Face Communication precede your text by enclosing the last name or title of the character, or area of the starship/station to which you are addressing with asterisks.

Examples:
   Ens. Taylor:
        *Doctor* Prepare for casualties!

    Lt. Curtis:
        *Taylor* You may energize when ready.

    Ens. Taylor:
        *Sickbay* Initiating transport.

When communicating with vessels or starbases you should precede the intended message with 'COM:'

Examples:
   Capt. Harris:
        COM: Gorn vessel: Why have you attacked our survey team?

    Capt. Y'rissa:
        COM: U.S.S. Griffon: You are trespassing in Gorn territory.  Leave now or face destruction!

Non Verbal Communication
This form of communication is used to express actions and emotions.  To use Non Verbal Communication enclose your actions and emotions in double colons.  Actions and emotions should be integrated with other forms of communication whenever possible.

Examples:
   Ens. Jackson:
        ::materializes in sickbay::

    Lt. Curtis:
        ::goes to Jackson and scans his injury with a medical tricorder::

    Ens. Jackson:
        ::holds arm in pain::

Alternate Location Communication
This form of communication is used when away from the starship/station.  To use Alternate Location Communication precede any other form of communication with the @ sign.

Examples:
   Ens. Baker:
        @ ::scans area with tricorder::  Grant: All clear as expected.

    Ens. Grant:
        @ ::opens the equipment case:: Baker: We should start with soil samples.

    Ens. Baker:
        @ ::joins Grant and removes some sample containers::

Private Communication
This form of communication is used when you have an out-of-character comment or question for another player or when the AGM needs to communicate vital information to you.    To use private communication just ask your question or make your comment in the OOC (Out-Of-Character) chat room that your AGM directed you to.

Note: When you're in either a Training Mission, Station Mission, or Starship Mission you will be required to not only have the appropriate Mission chat room open (e.g. #ACTDTrainingCenter, #ACTDStationMissions, or #ACTDShipMissions) but you will also be required to have the OOC chat room, specified by your AGM, open before the mission begins.

Getting Started

This section of the handbook contains information on getting started.  Questions about this section should be posted to the Feedback newsgroup.  If you would like to participate in future Chat missions, please send an email to James Young,  the Game Manager, at ACTDJames@startrek.com requesting admission.  He will send you information via email that will assist you in enlisting for training.  You must attend one training session a week, and complete three training sessions in a row in order to graduate.

Once your have completed training, you will fill out a form where you must supply your favored starships/stations and positions.  You will receive a Character Creation Form from Game Management that you will be required to fill out and send back. 

Character Creation Form
This form will require you to provide the details of your proposed character.    When sending the form back to the Game Manager, you must make sure it is in TEXT format, otherwise it will not be accepted.  This is done to speed up the administration of placing your character on a starship/station.

PLAYER INFORMATION
Real Name:
Email Address:

CHARACTER INFORMATION
First Name:
Middle Name:
Last Name:
Race:
Age:
Gender:
Height:
Weight:
Eye Color:
Hair Color:
Other Physical Characteristics:

Birthdate:
Birthplace:
Mother:
Father:
Siblings:
Spouse:
Children:

Note: Your character is subject to approval by the Game Manager.   It is recommended that you choose a to have a character with a standard Starfleet race (e.g. Human, Vulcan, Betazoid, etc.).  Other races such as Klingon and Ferengi are acceptable.  Half-Romulan are also accepted.   We will not approve any character that is a Borg (or was once a Borg), a Jem'Hadar, a Changeling, a Q, or a character that has bionic implants that allow the character any supernatural strength.   We cannot accept races that appear only in the Star Trek Novels.  All characters submitted become the property of Star Trek: A Call To Duty and Paramount Digital Entertainment.

Reviewing the Handbook
This handbook has been developed to provide you with the information you will need to participate in the game.  You are required to review the information in this handbook prior to participating.  Failure to review this handbook will prevent you from participating.

Game Training
This section of the Handbook contains information on game training.    Questions about this section should be posted to the Feedback newsgroup.

Overview
Before you may begin participating in the game you must first learn how to play.    This is accomplished through game training, where new players participate in training missions.  The purpose of these missions is to prepare you for the game and to make sure that you understand how to play.

Training is important because it ensures game quality and player satisfaction.  During the game the pace is fast and there is no time to stop and ask questions.  Without training new players would quickly become frustrated and the game might be impacted negatively.  For this reason, all players are required to complete game training.

Officer Training
The training process is composed of three steps, signing up, attending, and completing training missions.  Each of these steps are outlined below.

Signing Up For Training Missions
To sign up for training missions all you need to do is email the Game Manager, James Young, at ACTDJames@startrek.com.    You will be sent a reply with all of the necessary information and directions that you will need to read and follow in order to complete the signup process.

Attending Training Missions
Begin by opening your favorite chat program.  Star Trek: A Call To Duty fully endorses Microsoft Chat due to its ease of use, although we do not require all users to participate using this chat program.  Log on to the chat server (chat.paramount.com) using your chat program and enter the training room (#ACTDTrainingCenter).   Once in #ACTDTrainingCenter, your Training AGM will tell you the name of the OOC (Out-Of-Character) Room.  You may enter the OOC room by either opening another instance of your chat program or by opening another room in the same instance of your chat program.  Whichever the case, you need to be in both rooms at the same time.   Once you have entered both rooms, rearranging the window sizes until you are comfortable with the layout.

At the beginning of the training mission, your AGM will assign a position to every player who is scheduled to participate for that session.  The positions that are assigned are non-negotiable.   Do not request a change of position assignment.  Refer to Appendix A for a complete description of each position.

Completing Training Missions
Once you have successfully completed three training missions in a row, you will receive instructions from your Training AGM as to how to proceed.  You will receive email with further instructions on how to proceed through your graduation and character placement process.

Game Play

This section of the handbook contains information on game play.  Questions about this section should be posted in the Feedback newsgroup.

Overview
Participation in the game takes place through starship or station missions.    Starship missions require a weekly commitment of one hour.  Station missions require only a monthly commitment of one hour.

Attending a Starship Mission
Begin by opening your favorite chat program.  Log on to the chat server (chat.paramount.com) using your chat program and enter the starship mission room (#ACTDShipMissions).   It is recommended that you arrive approximately fifteen (15) minutes prior to the ship start time.  Once in the starship mission room, your AGM will tell you the name of the OOC Room.  You may enter the OOC room by either opening another instance of your chat program or by opening another room in the same instance of your chat program.   Whichever the case, you need to be in both rooms at the same time.   Once you have entered both rooms, rearranging the window sizes until you are comfortable with the layout.

Mission Orders
Mission Orders are distributed via email by your AGM prior to the beginning of a new mission.

Mission Briefings
Mission Briefings are created by the Commanding Officer of each starship.    Mission Briefings contain information which pertain to each game session and are distributed via email as well as posted in the ship's mission thread.

Duty/Personal Logs
Duty logs and personal logs are key elements of the game.  They allow your character to grow and develop, as well as allowing your fellow players to get a better insight into your character's personality.  For the sake of space and easy reference, duty and personal logs should be in the same document, but made clearly distinguishable from one another.

All starship officers are required to write duty logs at the conclusion of each game session.  Failure to complete a duty log will result in you being marked 'ABSENT' for the week and will adversely affect your character's chances at promotion.  Duty logs explain the events that took place during the game session.  Keep the following things in mind when writing a duty log:

- Write from your character's perspective.
- Concentrate on your character's actions.
- Summarize interactions with other characters.

Starship officers may optionally write personal logs at the conclusion of each game session.  Personal logs explain your character's personal thoughts and observations.  Keep the following things in mind when writing a personal log:

- Write from your character's perspective.
- Reference your character's emotional state.
- Summarize interaction with other characters.

Logs should be distributed via email to the rest of the starship's crew.  Refer to Appendix D for a sample duty/personal log.

Do not refer to another character or another player's NPC in your logs in any way that deviates from what actually happened in the mission without permission first from the other player.  For instance, consider that your character may be a strict non-drinker or unsociable person.  If you received a log from another player detailing a wild party they attended with your character after the duty shift, that goes on to describe how your character ended up with a lampshade on his/her head, you'd be a little steamed, right?  Same goes for referring to another player's NPC, pet, friend, parent, etc.   If it's not your character, get permission first.

Game Policies

This section of the handbook contains the operating policies of Star Trek: A Call to Duty.  Questions about this section should be posted to the Feedback newsgroup.

Assignment/Reassignment

After graduating from Officer Training, players are assigned to a starship. Only after graduation will players be assigned, and the player will be contacted via email with further information. There are currently several starships running on different days of the week, so you will be asked to give a few choices since it is not possible to guarantee an assignment/position on any one particular day.

At any time thereafter, a player may request reassignment from a starship to another starship. Requests should be sent to your current AGM. These requests will be processed on a resource-availability basis, and granted whenever possible. Reassignment requests are granted at the sole discretion of Game Management.  Any request made for a Reassignment made to anyone other than your AGM will be ignored.

To request a change of position within the same starship, i.e. from Flight Control Officer to Operations Officer (if the OPS Officer position is open), all requests should be made directly to the Commanding Officer, who will then forward their recommendations to that particular starship's AGM for approval. The AGM will inform you via email of the status of your request.

Attendance/Leave of Absence

Attendance is vital to the overall experience of Star Trek: A Call to Duty. The more a player can attend, the richer the experience of the Game, and the deeper the player's understanding of the duties and nuances of participation.

Any player who is assigned to a starship is required to make a weekly commitment of one hour to attend and participate in the Game. If a player is not going to be able to attend a particular Game, he/she is responsible for notifying that Game's AGM at least twenty-four (24) hours prior to the mission. Four (4) consecutive absences will result in removal of your character from the starship. (See "General/Leave of Absence", below).

General/Leave of Absence

Any player not attending a Training/Starship mission in a thirty (30) day period will be assumed to have resigned from the Game. This will be checked automatically on a weekly basis. If a player is aware that he/she will be unable to participate for said period, there are procedures in place to allow a request for a Leave of Absence to be granted. In the case of players assigned to a starship, all requests must be made directly to the AGM responsible for that particular starship. Although a player may leave a starship for an extended period of time and still be guaranteed participation, there is no guarantee regarding availability of positions.

Promotions/Commendations/Demotions

Throughout the life of a player's character, there may arise occasions where promotions, commendations or demotions may become necessary or warranted due to actions the player has taken. Although these items are rare occurrences, the are necessary to maintain the realism aspect involved. It must be stated here that the purpose of playing the Game is not simply to be promoted: rather it is to have fun, and interact with people in a role-playing environment.

Promotions

From time to time, players may warrant promotions. There are many factors that a CO and/or AGM will consider when deciding if a player has earned this honor. Among them are:

- Leadership abilities
- Ability to work well in a team-oriented environment
- Overall creativity and appropriate application of a players actions/solutions in reference to problem-solving and participation
- Adherence to Game protocols and policies

Players should never request a promotion, and should regard those who are given this honor with the respect they deserve. Players will be notified in an official Starfleet Command communiqué of their promotion. All promotions will be automatically recorded in the player's Starfleet Service Record.

Commendations

When a player performs a particular act or solution that warrants recognition, they may be awarded a Commendation specifically for said act/solution. There are many different Commendations, including Bravery, Proficiency, Leadership, etc. Players will be notified in an official Starfleet Command communiqué of their Commendation, and their Starfleet Service Record will be automatically updated with this information.

Demotions

Demotions are rare, but for the sake of realism and continuity, any actions unbecoming of an officer in the Game may indeed result in a demotion of rank and/or position. Players will be notified in an official Starfleet Command communiqué of their demotion, and their Starfleet Service Record will be automatically updated with this information.

Conflict Resolution

If a player has a concern about or conflict with another player, an attempt must first be made to work things out directly with that player. Most conflicts can be solved in this manner, as many conflicts arise out of a simple lack of communication. If the conflict is not solved by direct player-to-player communication, the concerned player must then contact their respective AGM with the details of the problem. If a player is still not satisfied with the solution at this point, they can contact the Game Manager directly with all details, including the AGM's proposed solution, and all steps taken thus far.

Message Removal

If a player posts a message to a Game-related newsgroup, and then wishes to have the message removed, the player should contact their respective AGM directly Only the originator of the message can request its removal. Newsgroups will be checked regularly for erroneous or policy-violating postings.

Resignation/Reinstatement

Players may resign from the Game at any time, although players on a starship should consider giving some warning if they plan to resign. Players who resign from the Game can return at a later date with the same rank or position that the player previously held as long as the same character is used. If a new character is created he/she will start with a rank that is lower than the previous character's rank. Previous positions may already be taken so the reinstated Player will have to settle for a different position.

Terms of Use

If you have any disagreements with the Terms of Use below, you should not participate in Star Trek: A Call to Duty or use Star Trek: Continuum.

TRADEMARKS, COPYRIGHTS AND RESTRICTIONS

1. TM & COPYRIGHT © 1996 BY PARAMOUNT PICTURES CORPORATION. ALL RIGHTS RESERVED. STAR TREK and related marks are trademarks of Paramount Pictures Corporation. All material on this site, including, but not limited to images, illustrations, audio clips, and video clips (collectively the "Material") is protected by copyrights owned or controlled by Paramount Pictures Corporation. UNAUTHORIZED COPYING, REPRODUCTION, REPUBLISHING, UPLOADING, DOWNLOADING, POSTING, TRANSMITTING OR DUPLICATING OF ANY OF THE MATERIAL IS PROHIBITED.

2. Your use of this site constitutes your agreement to abide by these Terms of Use. Paramount Pictures Corporation, Paramount Digital Entertainment, Inc. and their parent, sister, and affiliated companies, as well as their agents and assignees, as applicable ("Paramount"), reserve the right, in their sole discretion, to modify, alter or otherwise update these Terms of Use at any time and you agree to be bound by such modifications, alterations or updates. You agree to review these Terms of Use on a periodic basis.

3. Paramount hereby grants you a personal, non-exclusive, non-assignable and non-transferable license to use and display, for home, noncommercial and personal use only, one copy of any Material and/or software that you may download from this site, including, but not limited to, any files, codes, audio or images incorporated in or generated by the software (collectively the "Downloaded Material") provided, however, that you must maintain all copyright and other notices contained in such Downloaded Material. You acknowledge and agree that you may not sublicense, assign or otherwise transfer this license or the Downloaded Material and that no title to the Downloaded Material has been or will be transferred to you from Paramount or anyone else. You also agree that you will not alter, disassemble, decompile, reverse engineer or otherwise modify the Downloaded Material.

SUBMISSIONS POLICY

4. Although we welcome your comments to our show and this site, Paramount does not accept unsolicited submissions for its shows, sites and other products. Therefore, please do not make any such submissions to Paramount through this site or otherwise. Paramount will not review any such submissions. Also, while we appreciate your comments, Paramount cannot make any guarantee that it will respond to your message.

Notwithstanding the foregoing, if you do send us a submission, whether requested or not (collectively the "Submissions"), such Submission shall immediately become Paramount's property. Paramount may use any such Submissions as it deems fit, but shall have no obligation to use any of them. You agree not to assert any proprietary right of any kind in the Submissions (including, but not limited to copyright or trademark) and you waive the right to receive any financial or other consideration in connection with such Submission including, but not limited to, credit. You agree that any Submissions may be used, edited, removed, modified, published, transmitted, and displayed by Paramount without any notice to you. In addition, you agree to waive any and all moral rights in such Submissions.

LINKED SITES

5. Paramount is not necessarily affiliated with sites which may be linked to this site and is not responsible for their content ("Linked Sites"). The Linked Sites are for your convenience only and you access them at your own risk.

DISCLAIMERS AND LIMITATIONS ON LIABILITY

6. Paramount is not responsible or liable for any infections or contamination of your system or delays, inaccuracies, errors, or omissions arising out of your use of this site or with respect to the Material contained on this site. This site and all Materials contained on it are distributed and transmitted "as is" without warranties of any kind, either express or implied, including, without limitation, warranties of title or implied warranties of merchantability or fitness for a particular purpose. The entire risk as to the quality, accuracy, adequacy, completeness contained on it, correctness, validity and quality of any material rests with you. Paramount is not responsible for any special, indirect, incidental, or consequential damages that may result from the use of, or the inability to use, the materials contained on this site whether the material is provided or otherwise supplied by Paramount or anyone else. Notwithstanding the foregoing, in no event shall Paramount's total liability to you for any and all claims, damages, losses, and causes of action (whether in contract or tort or otherwise) exceed the amount paid by you, if any, for accessing this site.

RULES FOR NEWSGROUPS AND CHATROOMS AND OTHER FORUMS

7. Paramount is not responsible for any material posted on the Newsgroups, Chat Rooms, or other forums conducted on this site ("Forums"). You shall not upload, transmit, distribute or otherwise publish through such Forums any content which:

(collectively "Non-Approved Material").

You agree to indemnify Paramount for any and all claims, damages, losses, and causes of action arising out of your publication or transmittal of Non-Approved Material or your failure to comply with these Terms of Use. While Paramount does not and cannot review every message posted by users in the Forums and is not responsible for the content of these messages, Paramount reserves the right to delete, move, or edit messages that it, in its sole discretion, deems abusive, defamatory, obscene, in violation of copyright or trademark laws, or otherwise unacceptable.

The views and/or opinions expressed by the experts and/or any other third party or guest on this site are their own and do not necessarily reflect the views of Paramount.

OTHER

8. This site is controlled and operated by Paramount from its offices in the State of California, United States of America. Paramount makes no representations that materials in this site are appropriate or available for use in other locations. Those who choose to access this site from other locations do so at their own risk and are responsible for compliance with any and all local laws, if and to the extent local laws are applicable. No software from this site may be downloaded, exported or re-exported into (or to a national or resident of) any countries that are subject to U.S. export restrictions.

9. This agreement shall be governed by, construed and enforced in accordance with the laws of the State of California, as it is applied to agreements entered into and to be performed entirely within such State. Any action you bring to enforce this agreement or any matters related to this site shall be brought in either the State or Federal Courts located in Los Angeles County, California. If any provision of this agreement is void or unenforceable in whole or in part, the remaining provisions of this Agreement shall not be affected thereby. This is the entire agreement between the parties relating to the matters contained herein and shall not be modified except in writing, signed by Paramount Pictures Corporation and/or Paramount Digital Entertainment.

Appendices

This section of the handbook contains several appendices, each containing reference materials related to the game. Questions about this section should be posted to the Feedback newsgroup.

Appendix A - Positions
The standard positions in Star Trek: A Call to Duty are as follows.

Commanding Officer - The primary responsibilities of the commanding officer are leadership and command of a crew or team in the direction of attaining a particular mission directive and the safety and well being of officers under his/her command.

Executive Officer - The primary responsibilities of the executive officer are acting as a conduit for relevant information to the commanding officer, ensuring the safety and security of the commanding officer, and advising the commanding officer in all instances.

Second Officer – The primary responsibilities of the Second Officer are acting as a conduit for relevant information to the commanding officer and the executive officer, advising both in all instances. In the absence of either the CO or XO, the Second Officer will ensure the safety and security and well being of officers under his/her command.

Flight Control Officer - The primary responsibilities of the flight control officer are course plotting, position verification, and supervision of manual and automatic flight operations. The flight control officer is also the primary bridge liaison to engineering.

Course Plotting - By using a combination of the navigational sensors, science sensors, and tactical sensors the flight control officer can calculate the course of the ship. Course can be input by desired destination, proximity to another vessel, relative bearing, absolute heading, or galactic coordinates.

Position Verification - The flight control officer must know the exact location of the ship in order to make course corrections. Ship location can be determined by time space beacons, subspace radio relays, other vessels, probes, sensors, or celestial objects.

Flight Operations (Manual/Automatic) - During manual and automatic flight operations the flight control officer must monitor navigational sensors, the navigational deflector, the structural integrity field, and the inertial dampening system.

Bridge Liaison (to Engineering) - Since the flight control officer monitors several critical systems aboard a starship, it is not surprising that flight control serves as liaison between the bridge and engineering. The flight control officer will often contact engineering to note performance problems or requirements related to flight control, if and when an engineering officer is not present on the bridge.

Operations Officer - The primary responsibilities of the operations officer are supervision of power allocation, coordination and scheduling of starship or unit resources, and assignment of away team personnel and equipment.

Power Allocation - During critical situations the operations officer is responsible for supervising power allocation. This may require rerouting power, taking key systems off-line, and coordinating activities with engineering.

Resource Coordination/Scheduling - At any given moment multiple requests for starship or station resources may be made. The operations officer must prioritize these requests and allocate the necessary resources. Starship and station resources include both equipment and personnel.

Personnel/Equipment Assignment - During away team missions the operations officer is responsible for notifying away team members and issuing equipment. The operations officer is also responsible for monitoring away team location, activities, and communication.

Communications - The operations officer has control of all communications systems. These systems include intraship communication, ship-to-ground communication, ship-to-ship communication, and long-range subspace communication.

Tactical Officer - The primary responsibilities of the tactical officer are control of starship or station shields, weapons, and communication, with the secondary duties of starship or station security.

Shields - During alert conditions the tactical officer is responsible for the activation and monitoring of starship shields. This includes making manual adjustments such as shield modulation and recalibration.

Weapons - The tactical officer has control of all starship or unit defensive systems. These systems include tactical analysis, targeting, and firing. All tactical maneuvers must be coordinated with the flight control officer.

Internal Security - Security of the starship/station and its personnel is paramount. For this reason, the tactical officer is responsible for internal security. This can range from security for visiting diplomats to counterinsurgency.

External Security - During away team missions personnel are vulnerable to attack. For this reason, the tactical officer is responsible for arranging security for officers away from the starship/station.

Science Officer - The primary responsibilities of the science officer are control of starship or unit sensor arrays, coordination of scientific endeavors, and interpretation of sensor data.

Sensor Arrays - The science officer has control of all sensor systems. These systems include navigational sensors, tactical sensors, long-range sensors, and sensor probes.

Scientific Endeavors - Since sensor systems are a shared resource the science officer is usually involved in a number of scientific projects. Departments such as stellar cartography often contact the science officer for advice and input.

Data Interpretation - Command decisions are made based on all available information; this includes scientific information. The science officer is responsible for the interpretation and dissemination of all scientific data collected by available sensor systems.

Engineer - The primary responsibilities of the engineer are monitoring, maintaining, and repairing starship/station systems.

Monitoring - Since most systems are critical, they must be monitored on a continuous basis. While much of this monitoring is automated, during critical situations officer interaction is required.

Maintaining - Keeping systems in prime condition is extremely important. For this reason, the engineer has control over diagnostic and maintenance equipment pertaining to each separate system.

Repairing - Damage to any system can lead to disaster. For this reason, the engineer has many resources with which to repair damaged systems. These include personnel, materials, and special equipment.

Medical Officer - The primary responsibilities of the medical officer are prevention, diagnosis, and treatment of medical problems experienced by starship or station personnel.

Prevention - Prevention of medical problems is accomplished through the use of routine physicals. All personnel are required to submit to physical examinations as required by the medical officer.

Diagnosis - Diagnosis of medical problems is accomplished through the use of advanced medical systems. These systems include medical tricorders, biobeds, sensor clusters, and extensive medical references.

Treatment - Treatment of medical problems is accomplished through the use of medical resources. These resources include medical equipment (e.g. hyposprays, neural stimulators, etc.) as well as holistic agents (e.g. medicines, physical therapy, etc.).

Counselor - The primary responsibilities of the counselor are diagnosis and treatment of psychological problems experienced by personnel. The counselor also advises command personnel.

Diagnosis - Diagnosis of psychological problems is accomplished through the use of in depth counseling sessions. All personnel are required to submit to psychological evaluations as required by the counselor.

Treatment - Treatment of psychological problems is accomplished through the use of psychological resources. These resources include different types of therapy and continued psychological counseling.

Advising - Since counselors are trained in psychological analysis it is not surprising that they often involved in command decisions. These decisions usually deal with diplomacy, negotiation, or first contact.

Appendix B - Ranks

The standard ranks in Star Trek: A Call to Duty are as follows:

Ensign (abbreviated Ens.)
Lieutenant Junior Grade (abbreviated LtJG.)
Lieutenant (abbreviated Lt.)
Lieutenant Commander (abbreviated LtCmdr.)
Commander (abbreviated Cmdr.)
Captain (abbreviated Capt.)

Appendix C - Sample Mission
Although missions can and will take on many different forms and styles, most will have a similar layout as far as the actual game looks. Included below is a sample mission, in which the AGM's messages to various players are indicated in bold italic lettering, with square brackets [] around them, although only the players that the AGM was communicating with would see the actual message. The positions in the following mission will be played by fictitious characters, and are:

Flight Control Officer

FCO Ensign_Bryant
Operations Officer OPS Ensign_Taylor
Tactical Officer TAC Lieutenant_Johnson
Asst. Tactical Officer Asst. TAC Ensign_Jackson
Science Officer SCI Lieutenant_Smith
Asst. Science Officer Asst. SCI Lieutenant_Baker
Asst. Science Officer Asst. SCI Ensign_Grant
Engineer ENG Lieutenant_Ryan
Medical Officer MED Lieutenant_Curtis
Counselor Counselor Ensign_Trent

Captain_Harris:
    ::sits in the Captain's chair reading over a status report::

SCI Lieutenant_Smith:
    ::on the bridge recalibrating the long range sensors::

FCO Ensign_Bryant:
    ::on the bridge at the Conn.::

MED Lieutenant_Curtis:
    ::in sickbay reviewing officer physicals::

Counselor Ensign_Trent:
    ::returning to the bridge from a counseling session::

TAC Lieutenant_Johnson:
    ::on the bridge at tactical::

ENG Lieutenant_Ryan:
    ::in engineering running diagnostics on the impulse systems::

OPS Ensign_Taylor:
    ::on the bridge at operations::

[FCO Ensign_Bryant: The ship is entering the Delpha system]

FCO Ensign_Bryant:
    Captain: We have entered the Delpha system.

TAC Lieutenant_Johnson:
    ::begins scanning for other starships in the system::

Captain_Harris:
    Bryant: Place us in a standard orbit around the third planet.

OPS Ensign_Taylor:
    Captain: Shall I alert the survey team?

FCO Ensign_Bryant:
    ::moves the starship into a standard orbit::

Captain_Harris:
    Taylor: Have them report to transporter room two.

FCO Ensign_Bryant:
    Captain: Orbit achieved sir.

Captain_Harris:
    Smith: Begin planetary scans.

[ENG Lieutenant_Ryan: Power surge in the EPS grid]

ENG Lieutenant_Ryan:
    ::notices a surge of power in the EPS grid::

Counselor Ensign_Trent:
    ::moves to science one to observe::

MED Lieutenant_Curtis:
    ::notes that the Captain is overdue for a physical::

OPS Ensign_Taylor:
    *Survey Team* Report to transporter room two.

SCI Lieutenant_Smith:
    Captain: Aye sir. ::initiates scans::

TAC Lieutenant_Johnson:
    ::continues tactical scans of the system::

Asst. SCI Lieutenant_Baker:
    Grant: Is the equipment ready?

Asst. SCI Ensign_Grant:
    Baker: Aye sir. ::picks up the equipment case::

Asst. SCI Lieutenant_Baker:
    *Taylor* On the way. ::exits the lab with Grant::

Asst. TAC Ensign_Jackson:
    ::follows Baker and Grant::

MED Lieutenant_Curtis:
    ::completes the review and begins an inventory of medical equipment::

ENG Lieutenant_Ryan:
    *Captain* I am detecting a surge in the EPS grid.

FCO Ensign_Bryant:
    ::monitors the inertial dampening field::

Captain_Harris:
    *Ryan* Is it serious?

ENG Lieutenant_Ryan:
    *Captain* No but I would like to inspect the plasma conduit on deck eight.

Captain_Harris:
    *Ryan* Proceed with the inspection.

[SCI Lieutenant_Smith: Scans indicate the planet is class M]

SCI Lieutenant_Smith:
    Captain: Scans are complete. The planet is class M as reported.

Counselor Ensign_Trent:
    Captain: If these readings are accurate this planet suits our needs.

ENG Lieutenant_Ryan
    *Taylor* I need to shut down plasma conduit H23.

Asst. SCI Lieutenant_Baker:
    ::enters the transporter room::

Asst. SCI Ensign_Grant:
    ::enters and steps onto the transporter pad::

SCI Lieutenant_Smith:
    Captain: I agree with the counselor.

Asst. TAC Ensign_Jackson:
    ::sets phaser for stun and joins Grant::

ENG Lieutenant_Ryan:
    ::heads to the turbolift:: Deck eight.

Captain_Harris:
    Smith: Any lifesigns?

OPS Ensign_Taylor:
    *Ryan* Noted, I will reroute power to the effected systems.

[SCI Lieutenant_Smith: No lifesigns, except for dense plant life]

SCI Lieutenant_Smith:
    Captain: Only dense vegetation sir.

OPS Ensign_Taylor:
    ::pulls up the power distribution and reroutes the flow::

Asst. SCI Lieutenant_Baker:
    ::sets the transporter and steps on the pad::

MED Lieutenant_Curtis:
    *Captain* When you have time I need to speak with you.

Captain_Harris:
    *Doctor* Noted, I will join you in a moment.

Asst. SCI Lieutenant_Baker:
    @ ::materializes on the surface::

ENG Lieutenant_Ryan:
    ::arrives on deck eight and heads to the conduit::

Asst. SCI Ensign_Grant:
    @::materializes on the surface:

Counselor Ensign_Trent:
    ::returns to his station::

Asst. TAC Ensign_Jackson:
    @::materializes on the surface::

OPS Ensign_Taylor:
    Captain: The survey team is on the planet.

Captain_Harris:
    Taylor: Noted, keep a transporter lock on them at all times.

Asst. TAC Ensign_Jackson:
    @::pulls phaser and takes up a defensive position::

[Counselor Ensign_Trent: You sense something strange, a presence you have not encountered before]

Counselor Ensign_Trent:
    ::senses a an unfamiliar presence::

ENG Lieutenant_Ryan:
    ::makes a minor repair to the conduit::

[Asst. SCI Lieutenant_Baker: Tricorder readings confirm that the area is clear]

Asst. SCI Lieutenant_Baker:
    @::scans the area with a tricorder:: All clear as expected.

Captain_Harris:
    *Doctor* I am on the way. ::heads to the turbolift::

[SCI Lieutenant_Smith: Sensors detect an anomaly off the port side of the ship]

SCI Lieutenant_Smith:
    ::notices an odd reading to port::

ENG Lieutenant_Ryan:
    ::heads back to engineering::

Asst. SCI Ensign_Grant:
    @::opens the equipment case:: We should start with soil samples.

Asst. SCI Lieutenant_Baker:
    @::joins Grant and removes some sample containers::

SCI Lieutenant_Smith:
    Captain: I am detecting an anomaly to port.

Captain_Harris:
    ::stops and turns to Smith::

Asst. TAC Ensign_Jackson:
    @::scouts the clearing perimeter::

Asst. SCI Ensign_Grant:
    @::starts taking soil samples::

ENG Lieutenant_Ryan:
    ::brings the conduit back online::

[TAC Lieutenant_Johnson: A Gorn vessel appears off the port bow]

TAC Lieutenant_Johnson:
    Captain: A Gorn vessel just appeared off of the port bow!

Counselor Ensign_Trent:
    ::looks at the view screen::

Captain_Harris:
    Johnson: Yellow alert.

FCO Ensign_Bryant:
    ::plots possible evasive maneuvers::

TAC Lieutenant_Johnson:
    Captain: Aye, initiating yellow alert.

Captain_Harris:
    *Doctor* I am going to be delayed. We have company.

MED Lieutenant_Curtis:
    *Captain* Understood.

ENG Lieutenant_Ryan:
    ::notes yellow alert::

[TAC Lieutenant_Johnson: The Gorn ship begins firing disruptors towards the planet]

TAC Lieutenant_Johnson:
    Captain: The Gorn are firing on the planet.

[OPS Ensign_Taylor: Analysis shows that the Gorn vessel is firing on the Away Team's position]

OPS Ensign_Taylor:
    Captain: They have fired on the survey team's position.

[Asst. TAC Ensign_Jackson: A disruptor blast hits the ground only 20 feet away from you, and your arm is broken by the ensuing shockwave]

Asst. TAC Ensign_Jackson:
    @::the blast throws me six feet::

SCI Lieutenant_Smith:
    ::begins scanning the area for other anomalies::

Asst. SCI Lieutenant_Baker:
    @*Captain* We are under attack.

Asst. SCI Ensign_Grant:
    @::runs to Jackson::

Captain_Harris:
    Taylor: Lock on to the survey team and beam them directly to sickbay.

Counselor Ensign_Trent:
    Captain: I recommend caution given recent relations with the Gorn.

OPS Ensign_Taylor:
    Captain: Aye sir, establishing transporter lock.

Captain_Harris:
    Bryant: Take us out of orbit.

OPS Ensign_Taylor:
    *Doctor* Prepare for casualties!

MED Lieutenant_Curtis:
    *Taylor* You may energize when ready.

FCO Ensign_Bryant:
    Captain: Aye sir. ::moves the ship out of orbit::

Captain_Harris:
    Counselor: Agreed.

OPS Ensign_Taylor:
    *Sickbay* Initiating transport.

Asst. SCI Ensign_Grant:
    ::materializes in sickbay::

Asst. SCI Lieutenant_Baker:
    ::materializes in sickbay::

Asst. TAC Ensign_Jackson:
    ::materializes in sickbay::

Captain_Harris:
    Johnson: Red alert! Raise the shields.

TAC Lieutenant_Johnson:
    ::activates red alert and raises the shields::

OPS Ensign_Taylor:
    ::takes non-essential systems off-line::

Captain_Harris:
    Johnson: Hail the Gorn ship.

TAC Lieutenant_Johnson:
    Captain: Hailing frequencies open sir.

ENG Lieutenant_Ryan:
    ::monitors all defensive systems::

Asst. SCI Lieutenant_Baker:
    Doctor: Jackson is injured.

MED Lieutenant_Curtis:
    ::goes to Jackson and scans his injury with a medical tricorder::

Asst. TAC Ensign_Jackson:
    ::holds arm in pain::

TAC Lieutenant_Johnson:
    ::targets the Gorn vessel::

Asst. TAC Ensign_Jackson:
    Doctor: How bad is it?

MED Lieutenant_Curtis:
    Jackson: It is just a broken arm. You will be fine.

Captain_Harris:
    COM: Gorn vessel: This is the U.S.S. Griffon. Why have you attacked our survey team?

Asst. SCI Lieutenant_Baker:
    ::looks relieved::

OPS Ensign_Taylor:
    ::listens to the conversation between the Captain and the Gorn::

MED Lieutenant_Curtis:
    Jackson: This will reduce the pain. ::administers a hypospray::

Captain Y'rissa:
    COM: U.S.S. Griffon: You are trespassing in Gorn territory. Leave now or face destruction!

[SCI Lieutenant_Smith: Other than the Gorn vessel, no other readings or disturbances on sensors]

SCI Lieutenant_Smith:
    Captain: I am not detecting any other anomalies in the area.

ENG Lieutenant_Ryan:
    ::places damage control teams on stand by::

Counselor Ensign_Trent:
    Captain: I believe they are acting alone.

MED Lieutenant_Curtis:
    ::mends the break in Jackson's arm::

FCO Ensign_Bryant:
    ::looks at the Captain::

Captain_Harris:
    COM: Gorn vessel: This is an obvious misunderstanding.

Captain_Y'rissa:
    COM: U.S.S. Griffon: On your part Federation!

OPS Ensign_Taylor:
    ::mutters under his breath:: Gorn scum!

MED Lieutenant_Curtis:
    ::scans Baker and Grant for injuries::

Captain_Harris:
    COM: Gorn vessel: We will withdraw if you are prepared to discuss the situation.

Captain_Y'rissa:
    COM: U.S.S. Griffon: There is nothing to discuss.

[TAC Lieutenant_Johnson: The Gorn vessel closes the comm. channel]

TAC Lieutenant_Johnson:
    Captain: They have cut communications.

Counselor Ensign_Trent:
    Captain: He will not back down.

SCI Lieutenant_Smith:
    Captain: I believe they are looking for a fight sir.

[TAC Lieutenant_Johnson: The Gorn vessel begins to disappear]

Captain_Harris:
    Smith: I concur and I am not going to give them one.

TAC Lieutenant_Johnson:
    Captain: The Gorn vessel has disappeared sir.

Captain_Harris:
    *Doctor* How are the members of the survey team?

MED Lieutenant_Curtis:
    *Captain* They are fine and may return to duty.

Captain_Harris:
    Bryant: Plot a course out of this system.

FCO Ensign_Bryant:
    Captain: Course laid in and ready.

Captain_Harris:
    Bryant: Engage at warp eight.

FCO Ensign_Bryant:
    Captain: Aye sir. ::engages the warp drive::

TAC Lieutenant_Johnson:
    Captain: Should I contact Starfleet Command sir?

Captain_Harris:
    Johnson: Yes and coordinate with Smith. I want to send them our sensor data.

SCI Lieutenant_Smith:
    ::nods to the Captain:

FCO Ensign_Bryant:
    Captain: Two minutes until we exit the system.

Captain_Harris:
    Johnson: Stand down red alert.

TAC Lieutenant_Johnson:
    Captain: Aye sir. ::deactivates red alert::

Appendix D - Sample Duty Log

Computer, open Assistant Tactical Officer's Duty Log.

<Computer> Duty Log for Ensign Jackson open.

Stardate 9707.27. In accordance with our orders to locate Class M planets for possible colonization we entered the Delpha System at 1900 hours. Long range sensors indicated that the third planet was Class M and a candidate for colonization. Shortly after entering orbit, a survey team was assembled.

Pursuant to starship protocol I was ordered to accompany the survey team to the planet's surface. The team was composed of myself and two officers from Geological Sciences, Ensign Baker and Ensign Grant. After the scientific equipment was secured, we beamed down to begin the survey.

Once we materialized I immediately took up a defensive position. I quickly verified that we were alone and then began scouting the area. Baker and Grant got to work, collecting their samples. That's when it happened. One minute I was examining an outcropping of rocks and the next I was in sickbay with a broken arm.

I was informed that we had been attacked by a Klingon Bird of Prey and that I had been injured in the resulting explosion. Thanks to Doctor Curtis my broken arm was taken care of without delay. The Captain, in order to avoid an incident with the Klingons, ordered the ship out of the system.

It appears that placing a colony in Delpha System would be a mistake.

Computer, close Duty Log.

<Computer> Duty Log closed.

Copyright Information

TM & Copyright © 1999 by Paramount Pictures Corporation.  All Rights Reserved.  Star Trek and all related marks are trademarks of Paramount Pictures Corporation. 

Last Update: 9907.31

Back to Main Console