18-1987
8047
100
90
80
70
60
50
40
30
20
10
00
20-62
LV-426
20-69
1-987
23-1524
54-2023
7125
100
90
80
70
60
50
40
30
20
10
00
AA
-/+
AA
=
AB
=
AC
-/+
AA-AC
RND
26-318
04-557
LIBRARY COMPUTER ACCESS/RETRIEVAL SYSTEM
user authorization code accepted
23-09
screen top
03-111968
04-41969
05-1701D
06-071984
07-47148
08-091966

STAR TREK MC

LCARS Terminal • SERVER RULES

Table of Content

  1. Definitions
  2. Title 1 - Respect & Behavior
  3. Title 2 - Roleplay
  4. Title 3 - Promotions
  5. Title 4 - Faction Rules
  6. Title 5 - Staff & Punishments

DEFINITIONS

  1. Player = A catch-all term for all members of the server, regardless of position and tasks.
  2. Member A visitor, guest or member of the server not tasked with administrative tasks.
  3. Staff = A team member of the server tasked with administrative tasks.
  4. Gamemaster/GM = A player tasked with creating roleplay events and guiding roleplay.
  5. In-Character = Actions as the player’s character, from hereinafter known as “IC”.
  6. Out-of-character = Actions outside of the roleplay, from hereinafter known as “OOC”.

TITLE 1 - RESPECT & BEHAVIOR

  1. Every player or staff must be treated with respect and equally at all times.
  2. No player shall be deprived of possibilities, inclusion or other aspects due to their gender, religion, sexual identity or beliefs.
  3. Names on discord or other STMC platforms should be appropriate and must not be insulting, inappropriate or violate (1) 1 in any way. It is recommended to change their discord server name to their character name.
  4. Spam is not allowed. Spamming is defined by sending the same or similar message or content repeatedly in a short or regular time frame.
  5. Advertisement of other (Star Trek) projects, videos or other content not related to Star Trek MC is prohibited. If uncertain, contact a staff member before posting!
  6. Client modifications that provide an unfair advantage are prohibited.

TITLE 2 - ROLEPLAY

  1. The life of your character is the highest good and must be protected at all costs. You should act in a way that does not put your character’s life in unnecessary danger of life or bodily injury. (Fear-RP)
    1. Roleplay actions must be life-oriented.
    2. If a player is put into such a situation, it must have a roleplay background and be absolutely necessary to accomplish the mission goal. Players that are in command of a mission must attempt to seek out a way that poses the least possible danger while still accomplishing the mission goal and escalate it accordingly.
  2. The usage of roleplay information gained through external sources that are not marked as roleplay access (rpa) is prohibited. (Meta-Gaming)
    1. Some roleplay relevant information found externally (i.e. on discord, other content) and is marked as rolepaly access (abbr. rpa) may be used in roleplay.
    2. Example: Watching a livestream of a fellow player, who is currently hiding from the player. The player sees the location of the hider on stream and uses it ingame to find the hider.
  3. Players are expected to roleplay as Starfleet Officers. As such, they must behave in a manner consistent with what is expected of a Starfleet Officer in Star Trek series and movies. Violations of this rule will be considered fail rp.
  4. Corrupt roleplay needs to be approved by Staff. If a player wishes to play a corrupt starfleet officer, they must seek permission from staff. The player will then receive an outline of what they can and cannot do. Corrupt roleplay may also be denied. This is a case-to-case decision.
  5. Players may not be in an external voice communication software during roleplay. They may not plan, coordinate or exchange roleplay actions through external communication sources. Everything related to IC matters and plans must be coordinated in the server while being IC.
    1. Staff are exempt to this rule, only when observing roleplay to ensure its quality, immersion or consistency. When they are taking part in roleplay, they must also not be in an external voice communication software.
  6. Roleplay situations must always be concluded. Players shall not leave the server prior to concluding a situation in roleplay. (Escape RP)
    1. If a player needs to leave due to a real life matter or emergency, they may disconnect prior to the conclusion of a situation. However, staff should be informed at the earliest possibility to avoid sanctions.
    2. Escaping roleplay situations by disconnecting to avoid IC consequences is prohibited.
    3. If the player’s game crashes and they rejoin right after, it is not considered escape rp. If the game crashes and cannot be restarted in time due to technical issues, staff should be informed to avoid sanctions.
    4. Purposely not rejoining after the character received IC consequences is also considered as escape roleplay.
  7. In-character (IC) insults are tolerated on a certain level. If characters cannot stand each other and an insult would be realistic in that situation, it is permitted. However, they must comply with title 1 paragraph 1. As such, insults should not be of the following nature, but is not limited to:
    1. Pertaining to OOC aspects of a player (e.g. roleplay abilities, disabilities in general, etc.)
    2. Racist, sexist, national socialistic or human demeaning in any other way.
  8. Bug exploitation is prohibited.
    1. If a player discovers a bug during roleplay, it must be reported to staff as soon as possible.
    2. The bug must not be exploited for personal benefit or other reasons.
  9. Trolling is prohibited. This includes, but is not limited to:
    1. Trapping other players (e.g. opening and closing doors in front of them, so they cannot pass or building traps for players)
    2. Making false statements to confuse players or roleplay parties that are not involved with the ongoing roleplay session (e.g. falsely relaying information that has not been provided by the gamemaster).
    10. Every player is limited to one account to roleplay with. This means, one player cannot play two characters on separate accounts. Selling a character, ingame possessions, ingame or out-of-game access or accounts for real money or other trade-ins is prohibited. Players must wear the respective department “armor” during their on-duty time in roleplay.
    1. If the player wishes to use the Star Trek MC uniform skin template (with their own head and respective department color) as their skin, they are exempt from wearing the armor.
     Only gamemasters are allowed to design the storyline of the roleplay session. No player shall intentionally deviate from the storyline by, for example, introducing a new major chunk of roleplay to the session that disrupts the original storyline.
    1. Example: A GM hosts a roleplay session about a computer virus disabling the whole ship. Suddenly, player P miraculously somehow scans a borg cube approaching.
  10. Fail-RP: Every player shall play their character according to their defined characteristics and abilities. The choices made by the character should reflect themselves and their background. Examples include, but are not limited to:
    1. A shy and introverted character would not suddenly be extroverted at a party and speak with many strangers or rush into unknown situations. For them to be able to do this, they would have to undergo a character’s journey and development.
    2. Behave realistically. Do not jump, run or fly around on the bridge or other locations during roleplay, when it is not necessitated by the situation.
    11. Random Deathmatch (RDM): The random killing, injuring or attacking of other players without a proper roleplay background is prohibited. Phasers or other weapons may only be used in accordance with in-character policies and with a roleplay background (e.g. hostile opponents are attacking Starfleet Officers). Power Gaming: Players may not force irreversible actions onto other players without their consent.
    1. For example: Cutting off extremities, giving a player a tattoo or performing impossible actions.
     The chat functions need to be utilized. When writing an out-of-character message, the local ooc (/ooc) or global (/gooc) channel needs to be used. All chat and roleplay functions are found in the tutorial / roleplay guide. English (also known as Starfleet Standard) must be spoken at all times on all STMC assets. Players may not choose canon names for their characters (i.e. James Kirk). Names must also not be similar to canon characters (i.e. “James Girk”, “Benjamin Cisko”, etc.
    1. Surnames (e.g. Kirk) are always blocked for characters. Given names (e.g. James) are generally allowed, but may be denied on a case-by-case basis.
     New Life Rule (NLR): If a player respawns after an unconsciousness, the details that led up to being unconscious should be blurred and not immediately accessible. Roleplay realistically! A player can remember the details, but remember that your character’s life and health is more important than catching the attacker. If the character is unconscious, the information and actions around them are unknown to the character after they wake up. No erotic roleplay! Players are limited to the available species on the server.

TITLE 3 - PROMOTIONS

  1. Promotions and the requirements are primarily handled through in-character policies.
  2. Department heads have the authority to promote subordinates to one rank below their own. Promotions have to be coordinated with the executive and commanding officer.
  3. Promotions may not be granted out of solidarity or personal relationships, but only due to performance, activity and competence.
  4. If a player feels treated unfairly, they may consult staff.
  5. Any promotions to ranks below Lieutenant Commander are handled by the department head. Promotions in that span must only be reported to, but not necessarily approved by command staff. However, command staff may deny the promotion with good reason.
  6. Promotions to or above Lieutenant Commander need to be approved by command staff.
  7. A player cannot be demoted below Crewman 3rd Class.
  8. Rank slots are limited to:
    1. 4 Commander
    2. 10 Lieutenant Commander
    3. 20 Lieutenants
    4. Infinite Lieutenant Jr. Gr.
    5. Infinite Ensigns
    6. There are no limited slots to enlisted ranks.
    7. Slots can be adjusted based on crew size & activity.

Title 4 - Faction Rules

  1. Faction leaders are the executive officer and commanding officer. They are also considered command staff.
    1. Usually a character that ranks Commander (XO) and Captain (CO).
    2. A player must not necessarily be a staff member to be a faction leader.
  2. The starfleet faction is divided into departments. Each department has their own department heads and responsibilities. The divisions are:
    1. Command: Contains command officers (XO and CO), strategic officers and helm officers.
    2. Tactical: Contains tactical officers.
    3. Security: Contains tactical officers.
    4. Engineering: Contains engineers officers.
    5. Operations: Contains engineers and operational officers.
    6. Medical: Contains medics.
    7. Science: Contains scientists.
  3. The department head needs to be a Lieutenant Commander or higher. The deputy department head needs to be a Lieutenant or Lieutenant Commander.
    4. Faction leaders are responsible for their subordinates and are expected to manage them accordingly (i.e. disciplinary action, promotions, meetings, etc.)..
    1. Staff may sanction or remove faction leaders, if the faction leader cannot control their personnel and are not acting appropriately as a faction leader.
  4. Department heads have similar responsibilities to their department as the faction leaders.
  5. Faction leaders and department heads must be approachable via discord for questions by their subordinates.

TITLE 5 - STAFF & PUNISHMENTS

  1. Staff contains community members, who are entrusted with moderating, developing and observing the community. They hold special permissions in order to enforce server rules.
  2. Community Members can become staff through special recruitment cycles or through appointment by the server administration.
  3. Staff Members must abide by internal rules and guidelines.
  4. Instructions, punishments and actions issued by staff must be obeyed. No argumentation should be made with a staff member in a public or private setting.
    1. If a player deems their punishment as unfair, unfounded or are unhappy with it, they need to submit a punishment appeal and/or file a staff complaint with the staff manager.
    2. Staff Members must clearly communicate what,why and how long punishment is issued. That communication is only made privately (in a support ticket) with the community member. Never in a public setting.
  5. Breaking any of these rules will result in a temporary ban. The player is then summoned to open a ticket on the discord. The support staff will explain the ban reasoning to the player and in return, the player then has the opportunity to produce a statement of their action. Afterwards, the ban duration is announced by the support staff.
    1. The duration of the ban starts after it was announced in the ticket, not at the day of the ban issuance.
    2. The punishment will not inflict on the player’s in-character career. Staff will inform the respective department heads that the player is not able to attend roleplay within their ban duration and no in-character disciplinary action may follow.
      Staff will not disclose details to the department head. However, server administration reserves the right to change the player’s in-character career, if deemed necessary based on the original offense.
  6. The server administration reserves the right to permanently exclude (ban) players from the project.
  7. Staff Members, who actively partake in roleplay or other activities on the server, are not exempt from these rules.
  8. Staff Members hold no special power in roleplay as their characters. They abide by the starfleet hierarchy based on their rank and position.
    1. If, however, a staff member fills a role for roleplay purposes (i.e. an Admiral), regular starfleet rules apply.
    2. If a staff member intervenes in the roleplay based on the offence, they must be obeyed.
    9. Every player has the right to file a complaint about a staff member with the staff manager.
    1. If the complaint is about the staff manager (or another manager), the complaint may directly be addressed to the server administration.
     Staff Members are appointed indefinitely.
    1. The server administration and staff manager have the right to dismiss a staff member from duty for good reason.
  9. Staff Members, who are in the support division, are expected to moderate the community channels. This includes managing messages and if necessary, issue time-outs, mutes or bans on the community discord.