Rules


1. Prime Directive

Be respectful of each other, and have fun!


2. The Command Staff

2.1 The USS Arcadia’s Command Staff consists of the Commanding Officer (CO) and the Executive Officer (XO).

2.2 The Command Staff functions as a collegiate body and strives for consensus. For the proper functioning of the sim, however, final decisions on all sim-related matters rest with the CO, except where these Rules and the rules/regulations of Obsidian Fleet (OF) state otherwise.

2.3 In the absence of the CO, the XO assumes all rights and responsibilities of the CO until the latter’s return or in the event of vacancy until the vacancy is filled.


3. Characters

3.1 Primary Characters (PCs) are the players’ main characters. Each player may have only one PC on the Arcadia at any given time. Every PC must have a full biography.

3.2 Protected Non-Primary Characters (PNPCs) are secondary characters associated with a player and are linked to that player in the Nova system.

3.3 Non-Primary Characters (NPCs) are secondary characters not associated with any players.

3.4 The creation of PNPCs and NPCs is subject to the following requirement:

3.4.1 The CO and the XO may create characters in any department, provided the Department Chief is given prior notice.

3.4.2 A Department Chief may create characters within his/her own department. He/she may also create characters in another department with the approval of that department’s Chief. In both cases the CO and the XO should be given prior notice.

3.4.3 Any other players may create characters in any department with the approval of the Department Chief, provided that the CO and the XO are given prior notice. If the Department Chief’s position is vacant at the time of the characters’ creation, the approval of the CO is required.


4. Stories and Posts

4.1 The Command Staff should make all reasonable effort to involve the entire crew in the crafting of mission storylines. Changes to mission storylines after the mission has begun require the approval of the CO.

4.2 All proposed subplots and changes to existing subplots require the approval of the CO. Approval will always be granted except in cases of a) violations of the Sim Rules and/or b) potential conflicts with the mission storyline and/or with other subplots.

4.3 Players are expected to respond to JP tags within three (3) days. If a player is unable to respond to a JP tag within three (3) days, he/she should inform his/her JP partners.

4.4 No player may write for another player’s PC and PNPCs without that player’s express consent except in the following cases:

4.4.1 In Joint Posts (JPs) and Single Post (SP) critical to mission progression the CO and XO may write for a player’s characters if the said player a) has resigned, b) has been removed, c) is on leave, d) is unable to complete his/her post in a timely fashion, or e) has not completed his/her post in a timely fashion, provided that any such writing is kept to the minimum necessary for mission progression.

4.4.2 If a player resigns or is removed at any point during a mission, the CO and XO may write for his/her character in order to maintain story continuity, provided that such writing is kept to the minimum necessary.

4.5 No player may alter another player’s writing without that player’s express consent except in the following cases:

4.5.1 The CO and the XO may correct any spelling and grammatical errors.

4.5.2 The CO and the XO may make cosmetic modifications in order to ensure a consistent posting style, e.g. signature format, italics for ship names, etc.

4.6 Under no circumstances may a player alter, permanently injure, or kill another player’s PC and PNPCs without that player’s express consent.

4.7 Any posts may be used outside of the sim and its website for recruitment purposes, provided that the authors are clearly acknowledged.


5. Activity Requirement and Leaves

5.1 As a minimum measure of participation, players are required to log into the website at least once a week.

5.2 There are three types of leaves: a) Leave of Absence (LOA) for up to fourteen (14) days, b) Extended Leave of Absence (ELOA) for up to thirty (30) days, and c) Prolonged Leave of Absence (PLOA) for more than thirty (30) days.

5.3 Requests for LOAs and ELOAs are automatically approved, provided that the CO, the XO, and any other concerned players, e.g. JP partners, are informed of the leave and its duration.

5.4 PLOAs are reserved for players who are on active military duty. Requests for PLOAs are automatically approved, provided that the CO, the XO, and any other concerned players, e.g. JP partners, are informed of the leave and its duration.

5.5 Requests for LOA, ELOA, and PLOA extensions are approved at the sole discretion of the CO. While such approval is usually given, it is not guaranteed. If the extension is approved, the player should inform other concerned players, e.g. JP partners, of the extension and its duration.

5.6 A player is considered absent without leave (AWOL) if there is no communication from the said player for one (1) week or more since the last time the Command Staff reached out to him/her.


6. Ranks and Promotions

6.1 The determination of a PC’s initial rank upon acceptance is at the sole discretion of the CO.

6.2 The ranks of created PNPCs and NPCs require the approval of the CO.

6.3 Promotions for PCs, PNPCs, and NPCs are at the sole discretion of the CO.


7. Demotions and Removal

7.1 At the discretion of the CO, a player may be demoted in rank/position or removed from the sim for a) abuse of the leave system, b) prolonged or repeated AWOLs, c) prolonged or repeated lack of participation, d) any other serious or repeated violations of these Rules, or e) endangering the safe, civil, and productive simming environment of the Arcadia.

7.2 A player who has been demoted or removed may appeal to the OF’s Office of Mediation and Arbitration.