Star Trek

USS Repulse

Rules

1. Posting Content

The USS Repulse uses novel-style, third person prose to relate to the reader the content of given character's contributions to the overall story. To this end, there are several inclusions and exclusions to posts that we ask players to make.

1.1: Because a given post may take place in multiple locations throughout the duration of the piece, we ask that players include location denotations to make it easy for other players to figure out where certain events take place at a glance to make for faster reference to established content in follow-up posts. This shall be done in the following manner;

[Actual Location, General Location, Celestial Location (if applicable)]

I.E.; [Starfleet Command, San Francisco, Earth] for posts taking place on a planet.

I.E.; [Captain's Ready Room, USS Repulse] for posts taking place on board a vessel.

1.2: Because of the nature of this simulation, certain symbology will not be used to denote items like telepathy, intercommunication traffic, and so forth. For portions of a post that utilize telepathy, the use of italics or single quotation symbols, i.e. '...', are acceptable. Any traffic using inter-connectivity equipment such as ship to ship, ship to personnel or person to person will be done with simple quotations i.e. "..." after denoting in the material that such a method is being used.

1.3: Because of the standard of quality the simulation aspires to, players are asked to attempt, whenever possible, to adhere to the proper grammar and punctuation standards which appear in all written forms of communication. This means, in brief, please put the capital letters in their proper place i.e. the front of the sentences. Place comas in places they need to be for a natural pause etc. and not every other few words. And ensure that all sentences end with either a period (.), a question mark (?), or an exclamation point (!) where appropriate. The ONLY exception, of course, is placing a coma (,) at the end of a spoken sentence i.e. a bit of dialogue rather than a period.

2. Posting Rates

The USS Repulse command staff understands and appreciates the fact that most players have obligations that extend beyond the simulation. And while we do make allowances for it as best we can, this is a game that is dependent on participation. With that said, we ask that players devote at least 2 posts per calendar month to the simulation, whether they be solo posts or joint post. The use of the personal log system in an attempt to make this quota is strongly discouraged as it adds nothing to the overall story we are trying to create.

3. Non-Player Characters (NPCs)

3.1: NPCs used in this simulation are created within the contents of a post written by our players. As such, the manifest shall be populated only by those NPCs that have been named (or shall be named in a post or joint post in progress) by a canon simulation post. This means that populating the manifest with random names simply to make the department look fuller than it is will not be authorized. Should a department be populated by 'ghost' NPCs, the Commanding Officer reserves the right to remove these NPCs should they not be named in a post within one (1) week of their creation.

3.2: NPCs shall be divided into two classifications. The first classification shall be termed 'unlinked' NPCs. The Second shall be termed PCNPCs. They are defined and governed as follows;

3.2.A: 'Unlinked' NPCs: These are NPCs that do not belong to anyone in the department specifically and are free to be used by anyone from any department. Unless otherwise specified by the Commanding Officer, NPCs of this nature can be treated in any way the storyline sees fit to use them, up to and including serious injuries and death.

3.2.B: Player Controlled NPCs: PCNPCs are non-player characters linked to a specific person's account. As such, they will be treated, for all intents and purposes, as an alternate player character for the purpose of using them in a post. This means that these NPCs will be under the sole control of their owner in terms of what will and will not happen to them. The Commanding Officer alone has the right to involve such characters in plots that would cause serious bodily harm or death to these characters though it will only occur after having spoken to the originator of that character and only serve in the best interests of the ongoing story.

4. Player Removal Guidelines

While it is the goal of the simulation to provide a place where all players feel welcome and wanted, there must be a policy in place to remove players that join the simulation but contribute very little to the overall game. The following shall be the process for removing inactive players;

4.1: Inactive players are defined as those players who fail to report their status to the Command Staff and/or fail to post to the simulation in a span of time that stretches beyond two calendar weeks from their last post.

4.1.A: A player on a leave of absence (LOA) is exempt from this policy for the duration of their stated LOA. If a player asks for a LOA for, as an example, three weeks, the time during the LOA would not be counted against the individual. However, at the end of the expressed length of LOA, should the individual fail to alert the command staff that a continuation of the LOA is required, two weeks after the end of said LOA, the player will be considered inactive.

4.1.B: Once a player has been labeled inactive, they shall receive via private message or email written notification of their status as an inactive player. Any person so labeled will be given one week from the initial correspondence to either provide a mission post of acceptable length or request a LOA for a defined period of time. Should a player fail to respond, they will be removed from their position and placed on the inactive roster of the simulation.

4.2: Players removed from their positions in this manner may return to the simulation, however their characters will not be allowed to return to their former positions should they hold Department Head or Assistant Department Head roles. Any Department Head removed in this manner shall be mandated to assume the assistant role regardless of a vacancy in the department as a condition for their reinstatement given their record of inactivity. Should the player show renewed activity in one month's time, they can be considered for resumption of the position of department head should it be vacant.

4.3: Those players who are called away from the simulation due to military deployments, medical issues that would prevent activity because of the nature of the illness or injury, and other circumstances beyond their control expressly explained to the Commanding Officer may be exempt from removal. These players, however, will be asked to step down from department head roles for the duration to allow other players a chance to assume the roles. Once the player returns to full duty under this clause, they will be allowed to return to their duties as a department head should they feel that they can reasonably return to a position of responsibility. This is at the player's option, though they may resume duties as the Assistant should they not feel they can return to their former roles.

4.4: Shore Leave will not be counted as part of this removal rule. It is not the policy of the Commanding Officer to enforce mandatory fun on anyone. Should a player choose to take this time as personal leave time away from the simulation for the duration and return after the active mission begins, this is perfectly acceptable. However, should a player fail to post after the start of the mission, they will still be subject to this policy.