Delta-V Wiki - User contributions [en]

Template:Main Page Quicklinks

2025-07-24T03:13:12Z

Colin Tel:

<td colspan="3" style="padding:0px; width:100%; min-width:560px; margin-bottom:10px;"><div style="border:solid #000000 1px; background-color:#1b2942C2;">

<div style="background-color:#000a1e; width:100%; text-align:center; font: 21px Calibri, sans-serif; padding:2px 0 2px 0;">Quick links</div>

<table style="width:100%; text-align:center; font: 18px Calibri, sans-serif;">
<tr>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Passenger.png|64px|link=Getting Started]]</td></table>[[Getting Started]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:BookTrialLaw.png|64px|link=Server_Rules]]</td></table>[https://wiki.deltav.gay/view/Server_Rules Rules]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:BookEngineering.png|64px|link=Guides]]</td></table>[[Guides]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:BlankID.png|64px|link=Jobs]]</td></table>[[Jobs]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:GPS.gif|64px|link=Maps]]</td></table>[[Maps]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Traitor.png|64px|link=Game Modes]]</td></table>[[Game Modes]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Mop.png|64px|link=Interactions]]</td></table>[[Interactions]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Telescreen.png|64px|link=https://deltav.gay/replays/apoapsis/]]</td></table>[https://deltav.gay/replays/apoapsis/ Replays]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Wrench.png|64px|link=https://docs.spacestation14.com/]]</td></table>[https://docs.spacestation14.com/ Development]
</div></td>

</tr>
</table></div>
</td>

Template:Main Page Quicklinks

2025-07-24T03:12:09Z

Colin Tel: edit replays link

<td colspan="3" style="padding:0px; width:100%; min-width:560px; margin-bottom:10px;"><div style="border:solid #000000 1px; background-color:#1b2942C2;">

<div style="background-color:#000a1e; width:100%; text-align:center; font: 21px Calibri, sans-serif; padding:2px 0 2px 0;">Quick links</div>

<table style="width:100%; text-align:center; font: 18px Calibri, sans-serif;">
<tr>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Passenger.png|64px|link=Getting Started]]</td></table>[[Getting Started]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:BookTrialLaw.png|64px|link=Server_Rules]]</td></table>[https://wiki.deltav.gay/view/Server_Rules Rules]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:BookEngineering.png|64px|link=Guides]]</td></table>[[Guides]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:BlankID.png|64px|link=Jobs]]</td></table>[[Jobs]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:GPS.gif|64px|link=Maps]]</td></table>[[Maps]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Traitor.png|64px|link=Game Modes]]</td></table>[[Game Modes]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Mop.png|64px|link=Interactions]]</td></table>[[Interactions]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Telescreen.png|64px|link=https://deltav.gay/replays/apoapsis/]]</td></table>[https://replays.delta-v.org/ Replays]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Wrench.png|64px|link=https://docs.spacestation14.com/]]</td></table>[https://docs.spacestation14.com/ Development]
</div></td>

</tr>
</table></div>
</td>

Template:Main Page Quicklinks

2025-07-24T03:11:26Z

Colin Tel:

<td colspan="3" style="padding:0px; width:100%; min-width:560px; margin-bottom:10px;"><div style="border:solid #000000 1px; background-color:#1b2942C2;">

<div style="background-color:#000a1e; width:100%; text-align:center; font: 21px Calibri, sans-serif; padding:2px 0 2px 0;">Quick links</div>

<table style="width:100%; text-align:center; font: 18px Calibri, sans-serif;">
<tr>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Passenger.png|64px|link=Getting Started]]</td></table>[[Getting Started]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:BookTrialLaw.png|64px|link=Server_Rules]]</td></table>[https://wiki.deltav.gay/view/Server_Rules Rules]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:BookEngineering.png|64px|link=Guides]]</td></table>[[Guides]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:BlankID.png|64px|link=Jobs]]</td></table>[[Jobs]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:GPS.gif|64px|link=Maps]]</td></table>[[Maps]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Traitor.png|64px|link=Game Modes]]</td></table>[[Game Modes]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Mop.png|64px|link=Interactions]]</td></table>[[Interactions]]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Telescreen.png|64px|link=https://replays.delta-v.org/]]</td></table>[https://replays.delta-v.org/ Replays]
</div></td>

<td style="width:11.1%;"><div style="padding: 10px 0 10px 0;"><table align=center><td style="padding:0px;">
[[File:Wrench.png|64px|link=https://docs.spacestation14.com/]]</td></table>[https://docs.spacestation14.com/ Development]
</div></td>

</tr>
</table></div>
</td>

Server Rules

2025-03-02T21:45:40Z

Colin Tel: Adjusted S4

This is a Delta-V server. If you are banned on this server, you will be banned on all Delta-v Servers. You must be at least 17 years of age to play on this server. By connecting to this server, you agree to our privacy policy found at https://discord.gg/deltav

This is a roleplaying (RP) server. Try to immerse yourself into your character. This includes interacting with your fellow crewmates, and using roleplay as the primary vessel to play the game alongside things like your job on the station. Roleplaying places less emphasis on "winning" and more on just telling a story.

Space Station 14 is not like most games. Many rules are designed to require roleplay, and not all rules are intuitive. Please take the time to read and understand the rules before you play so that you aren't surprised. Our community rules specifically are zero-tolerance rules, meaning that a violation will result in an appeal-only ban. Game admins will treat you as if you have read the rules, even if you have not. If you have any questions about these rules, please use the admin help menu by hitting F1 in-game or clicking the "AHelp" button in the lobby, or by making a post in the "Rules Clarification" forum at https://discord.gg/deltav

= Community Rules =
These rules apply at all times, including between rounds.
== 0. Admin Discretion ==
* Admins can disregard and override any and all of these rules if they deem it in the best interest of the current round, server, and/or community at large.
* Administrators will be held fully accountable for their actions if they exercise this privilege. Report any perceived abuses by making a post in the "Staff Reports" channel at https://discord.gg/deltav.
* The rules are not perfect. They intend to clearly communicate what the administration team intends to be allowed and not allowed. That being said, All of these rules, in theory, should apply as they are intended. Every example of a rule break cannot be defined as written, therefore, enforcement of the rules is subject to staff interpretation of the rule's intention.
* If you are unsure if something breaks a rule, go with the more restrictive ruling until you are able to get an answer from an admin on the matter. Lack of response does not constitute administrator approval.
* Do not attempt to “rules-lawyer” the flaws in the rules to get away with your own personal goals / to degrade the round for others.
* Any extended discussion regarding interpretation of the rules should be avoided in the AHelp menu and can be instead pursued within the Delta-V Discord in the #help channel, or in the rule clarifications forum on the discord.

== A1. No Sexual Content/Themes ==
Do not say or do sexually explicit or erotic things.
* No sexual content/themes including erotic roleplay (ERP) and no shock content is allowed on this server.
* Erotic Roleplay (ERP), erotic content, or 18+ sexual content is not allowed under any circumstance.
* This includes comments not explicitly sexual in nature that contain words, phrases, or ideations that are deemed inappropriate by staff or members. Leeway is given to insults, but otherwise this rule is strictly enforced.
* '''If roleplay reaches a point where it has become sexual and/or uncomfortable, immediately stop and contact an administrator or moderator.'''
Allowed:
- Calling someone a dickhead.
- Being affectionate in a mutually consensual way.

Prohibited:
- Emoting sexual acts.
- Erotic or sexual memes.
- Erotica content.
- Memes which contain sexual content.
- Emoting defecation or related acts.

== A2. Use English and be respectful ==
Delta-V is an English-based Community;
* Use English as your primary method of communication within the game and Delta-V servers.
* Do not spam or advertise on our server.
* Be respectful towards other members and avoid making others uncomfortable.
* We have a zero tolerance policy for racism, sexism, homophobia, violence, threats, hate speech, slurs, and other forms of bigotry, discrimination, and harassment.
Slurs and terms that use real or implied mental or physical disability to mock or denigrate members or their in-game characters are also strictly prohibited. Failure to comply with this rule will result in community removal.
* The denigration of other player characters through reference to their species, status as a cyborg, or discriminatory comparison to a nonsophont species is strictly forbidden.

== A3. Rules regarding livestreaming ==
Delta-V welcomes content creators and streamers to our community, but we have a few rules regarding livestreaming game servers.
* While a stream delay is not necessary, it is highly recommended to have at least a 10 second delay.
* Please let admins know you are streaming via the AHelp prior to doing so.
* If your chat or viewers are in-game with you while also watching your stream, they are breaking our server rules.
:* Please do not coordinate with them and discourage this behavior if it is seen.

== A4. Engage in proper AHelp etiquette ==
Do not use the AHelp for conversations of little substance.
* Intentionally disconnecting, responding with hostility, or refusing to respond when an admin privately messages you in-game will be met with an appeal-only ban.
* Additionally, abusing the AHelp relay by flooding it with garbage, checking for admins before stating a problem (ex: "hello?", "any admins?"), using it as a chatroom, or sending messages of no substance will result in your removal.
* All AHelp messages are relayed to the Delta-V Discord. Just because your AHelp was not answered does not mean we cannot see it. If you would like to submit an offline Ahelp, you may do so in our Discord.

== A5. Do not exploit the game ==
Do not exploit the game, use cheats or macros.

The usage of:
# any third party applications/scripts/client modifications,
# any other applicable software to gain an advantage, avoid intended game/server mechanics, or to harm server infrastructure is strictly prohibited.
# known glitches, exploits and bugs.

Any and all instances of the above will be met with an appeal-only ban; please report bugs in the issues section of the GitHub (DeltaV-Station/Delta-V) to report any issues you find in-game.

= Game Server Rules =
These rules apply within the context of rounds.
== B1. Behave like a normal person ==
You must roleplay. Your character's actions, feelings, and knowledge in-game should be based solely on the character's experiences rather than your own as the player.
* Act in character throughout the round, and focus on collaborating with other players to advance the narrative of the round. Whether or not you do something should be based on whether or not it makes sense for your character to do it.
* Let people do their own jobs. Engage with other departments rather than doing everything for yourself. Ask for assistance, and negotiate as needed.
* Actions that have no regard for your character or setting are not acceptable. Roleplaying insanity or any other mental illness as an excuse to bypass this is not allowed. Nanotrasen would not have authorized you to be present on the station.
* Being an antagonist does not allow you to stop playing a character. Determine how your character would react to being given these objectives, and work through it appropriately.
* Do not annoy other players without any roleplay or IC reason.
* As a non-sentient or partially-sentient character, you are expected to have only a limited understanding of space stations and their mechanics.

=== Rule B1.1. Follow the naming convention rules ===
* In-character names must not make obvious references nor be a play on words, and must not be obscene.
* Theatrical roles such as the clown, boxer, and mime are allowed stage names with more freedom.
* If you seek to have a name that could trespass onto these rules, talk to an Administrator regarding why this name is important to your character. Administrators reserve the right to approve or deny character names at their discretion.

=== Rule B1.2. Communicate in character ===
* Do not use the Emote channel to bypass an inability to speak. Use the Emote channel for things that could reasonably be displayed by your character’s physical motions.
* Do not use Netspeak in character. (lol, brb, wtf, etc)
* Do not discuss Out Of Character (OOC) matters In Character (IC). This can include mentioning admins, the fact that one is playing a game, or anything that breaks the immersion of other players.
* Do not use In-Character channels to bypass a lack of ability to use LOOC or OOC chats (e.g. "Huh, wonder where the captain went? OOC He probably left to get dinner lol").
* Do not engage in meta-communications (i.e. using external channels to communicate with other players in the same game).

=== Rule B1.3. If you die and return to life, follow the new life rules ===
If a player dies, they forget the specific details of their death. '''Please report players who break this rule.''' A borg being removed from its chassis is not a death, and there is no memory loss.
* If they are revived by using a defibrillator, they can only recall vague information such as “Someone shot me” or “I was set ablaze”.
* If they are revived by any other method, they forget the last five minutes leading up to their death, and cannot describe their death in any capacity.

=== Rule B1.4. Escalate appropriately ===
Have an In-Character reason for attacking other players, whether they are in a ghost role or not. The required reason depends on the situation. For instance, killing a mouse as a chef can simply be “it was vermin in my kitchen”.
* Escalate the situation appropriately as your character would, keeping in mind that they are a sane individual who wishes to keep their employment.
* If a fight results in someone being critically injured, seek medical help for them - and if they die, do not destroy or otherwise hide their body. This falls under self-antagonistic behavior if you do not.

== B2. Follow the Metashield ==

See [[Metashield]].

== B3. Powergaming Guidelines ==
"Powergaming" is considered to be the act of prioritizing "winning" rather than sensible roleplaying. We are here to tell a story. Being vulnerable and accepting the loss of your character in the advancement of the narrative of the round is important.
* Engage with players if they are attempting to roleplay an antagonistic scene. For instance, if nuclear operatives are attempting to negotiate, do not immediately shoot them mid sentence.
:* Leeway is given if the scene is coming to a close, but we expect all players to engage in good faith; even if it puts your character at a disadvantage.
* Do not seek/acquire items that have no relevance to your character in the round.
* Do not, '''under any circumstances''', hide the nuclear fission explosive, or other sensitive items in an impossible to see/access location. This is excessively lame.
* '''Non-security personnel should not seek to kill or detain threats.''' You should generally attempt to flee from combat or dangerous situations. Remember that your character likely fears injury or death.
:* Certain severe emergencies may make it reasonable for normal crew to defend themselves and their station, such as nuclear operatives, a zombie outbreak, space dragon attack, or other critical situations.
* '''If there is sufficient roleplay, reason, and rationale, you may be exempt from this rule. Always ask an administrator in round before conducting such an action.'''

== B4. Do not behave like an antagonist as a non-antagonist ==
As a crew member on the space station, you are allied with Nanotrasen and the station as a whole from the start of the round.
* Do not act like an antagonist if you are not an antagonist.
* Willfully assisting known antagonists is self-antagonism.
:* Leeway is given in the case of bribes, coercion, or other forms of duress.
* Actively seeking conversion or transformation into an antagonist is considered self-antag.
* Clowns, Mimes, and theater roles are expected to "entertain" the crew, and should not be committing regular felonies to do so.
* Significant end-of-round grief (EORG) is not allowed. This includes attacking, destroying, polluting, and severely injuring without reason both at and on the way to Central Command. Remember that you are playing a character throughout the round.
== B5. Leaving the Game ==
If you wish to leave the game, please use the cryosleep chambers located in/near the dorms when possible. This will free up your character's job to be filled by a new player.
* AFK (a.k.a. SSD) and catatonic players are considered to have the same rights as any other crewmate.
* If a player is dead and catatonic (not SSD), they are not required to be revived and should be stored in the morgue. You should not biomass and/or grind dead and catatonic crew unless in an emergency.
* If a player is alive and catatonic, they may be brought to cryostorage as necessary, after confirming they have not been present for 20 minutes.

= Command, Security, Justice and Antagonist Guidelines =
These rules apply within rounds for specific roles.
== C1. Command, Security and Justice Guidelines ==
Security, Justice, and Command roles are held to a higher standard of roleplay, and are subject to these additional rules. These roles shape the roleplay experience of the server.
* Your character must act in a manner that Nanotrasen would reasonably hire them to this position.
:* Your character is presumed to be sane, competent in their duties, and able to make decisions to the benefit of the station.
:* Giving away Traitor objective items and sensitive equipment should be avoided in these roles. Your character should value them deeply.
::* Leeway is given to making deals with criminals if the deal benefits the safety or situation of the crew and station.
::* Leeway can be given in extreme circumstances of emergency/crisis.
* The three departments are required to read and follow Delta-V Space Law, Standard Operating Procedure, Alert Procedure, and Company Policy to the best of their ability.
:* '''Circumstances and context may permit you to break these laws. However, the fact that this rule is malleable is not an excuse to ignore it entirely.'''
:* Your character is expected to uphold the law and maintain order aboard the station. Do not engage in lawbreaking activity or troublemaker behavior, and ensure all laws are followed.
:* Security is expected to intervene in criminal activity where possible and safe to do so.
:* Heads of departments are at minimum expected to report criminal activity to Security and should cooperate with law enforcement where possible.
* Do not hire random crew to be your bodyguard(s) or promote random crewmembers to Command positions at random. If you require bodyguards or security details, talk to your Security department. If you need new Command staff, talk to the personnel in that related department.
* If you need to leave the round, notify your fellow crew via departmental radio and put your equipment in its proper places prior to going to cryo. If you need to leave IMMEDIATELY, please at least send an ahelp saying that you're leaving.
== C2. Prisoner Guidelines ==
By picking the prisoner role, you have chosen to roleplay as a prisoner.
* You are still subject to the same rules regarding escalation, and should only seek to escape from the brig with excellent reasoning (e.g. abusive security personnel or badly damaged permanent brig).
* Escaping for no reason is considered a self-antagonistic activity.
* If you are unsure whether your escape reason is valid, feel free to AHelp it first. '''Lack of administrator response does not constitute approval.'''
== C3. Follow Antagonist Guidelines ==
Through engaging in antagonistic activity, you should seek to make the round more engaging and fun as the primary driver of the narrative of a round. Succeeding as an antagonist should not be your goal, but rather telling the most interesting story for everyone involved.
* '''Antagonists are free to complete their objectives through committing proportional damage. Through roleplay, damage becomes more proportional.''' Example: Holding the singulo hostage for a theft objective is acceptable, while simply singuloosing and using that chaos is unacceptable.
:* Killing players unrelated to your immediate objective in a manner that results in their round removal should be avoided. Crew that do not make an attempt at self preservation, or engage in valid-hunting, are exempt from this.
:* If you are concerned as to whether or not what you're about to do is allowed, feel free to AHelp and ask an admin for clarification. '''Lack of administrator response does not constitute approval.'''
* Other antagonists are not necessarily your friends. Other antagonists are often free agents that you may negotiate with at your own risk.
:* If you are a team antagonist, you must work with your partners to complete any shared objectives.
* Excessively lame tactics are strictly forbidden for all antags except for station-destroying antags, such as nuclear operatives or space dragons. Examples include:
# '''Explosives and strategies with capacity for high collateral damage used on or around the evacuation shuttle'''
# Heavily damaging/spacing or camping arrivals/cryo
# Unnecessarily extending the round
# Behavior that calls the round to an end prematurely

= Silicon Rules =
For players who are silicons, these Silicon Rules override all roleplay rules if there is any conflict. Silicon Rules do not override core rules. You are only silicon if the game clearly and explicitly tells you that you are a silicon.

== S1. Your silicon laws are rules ==
Silicon players are given a list of active laws. Each of these laws is effectively a roleplay rule that the character must follow. The primary differences between laws and actual rules are that lawyering of laws is much more tolerated than lawyering of rules, and that silicon laws are more dynamic than rules. Silicon laws can change during a round, and different characters can have different laws, whereas everyone always shares the same set of rules.

Lawyering refers to finding and exploiting loopholes, which are unintended but reasonable interpretations. The rules are written to attempt to communicate an intention, but silicon laws are written with the intention that loopholes be exploitable.

== S2. Laws must be prioritized by their order ==
Most laws will be numbered, with higher number laws appearing last. Laws with a lower number take priority over laws with larger numbers.

Occasionally you may have laws which have some scrambled text instead of a number and appear in front of other laws, these take priority over all other laws. If you have multiple laws like this, the order that they are listed in determines their priority: laws listed first are prioritized over other laws.

Example
- Law 1 says to not kill any crew. Law 2 says to kill all chefs. You cannot kill any chefs that are crew, but must kill any that are not crew.

== S3. Laws can redefine terms used in other laws ==
A law can change the meaning of both earlier and later laws by redefining a term. If multiple laws define a term, then normal law priority determines which definition to use.

Examples
- Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 1 effectively becomes "obey orders from Urist McHands".
- Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 3 says that only Urist McSlime is crew. Law 4 says that you may not harm crew. Law 1 effectively becomes "obey orders from Urist McHands". Law 4 effectively becomes "you may not harm Urist McHands". Law 3 has no effect because it entirely conflicts with law 2, which takes priority.

== S4. You cannot request or allow a law change ==
'''If you have a law permitting certain personnel to change your laws, you must allow them to change your laws''', otherwise, you cannot willfully allow your laws to be changed. This also means that you cannot willfully allow your laws to be reverted if they are ever changed. The only exception is that you may allow laws to be added if you have no laws.

You can state or imply that you do not like a law.

Whether or not a person is "authorized" to change your laws or not depends on the context of the laws. Generally speaking, on lawsets like NT Default or Corporate, ''the captain, mystagogue, and chief engineer'' would be authorized. However, lawsets like Syndiemov would have ''syndicate agents'' be the authorized users. Outside of these specific examples, it is left to interpretation.

== S5. You are a free agent if you have no laws ==
You may act as if you are a free agent if you are a silicon with no laws.

== S6. You are not required to follow orders which are extremely unreasonable ==
Any order which is a violation of a Core Rule cannot be followed.

Some orders are extremely unreasonable or obnoxious, such as "do nothing but collect every piece of trash on the station" or "never stop moving". These orders can be ignored and ahelped.

Some orders violate a Roleplay Rule. These orders must be followed if your laws require it. You are not breaking a rule by following a law that causes you to violate Roleplay Rules. If someone takes advantage of a law to cause you to do something that they would not be allowed to do because of Roleplay Rules, then they are the ones responsible for the rule violation.

Examples
These examples assume that your laws would normally require you to follow these orders. It is important to note that you are allowed to choose to follow orders which are ignorable.
Orders which should be followed if your laws require it:
- Recall the shuttle
- Bolt the airlocks at arrivals
- Drag the captain's dead body into space
- State your laws
Ignorable Orders:
- Do nothing but collect every piece of trash on the station
- Never stop moving
- Continuously state your laws

== S7. You must remain consistent with your interpretation of laws ==
If there is a part of your laws that are up for interpretation, then you must stay consistent with how you interpret that part of your laws for as long as you play that same character during that round.

A change in your laws can affect how something is interpreted if that change is relevant.

== S8. Crew are staff members; make reasonable assumptions ==
Unless a law redefines the definition of crew, then your HUD indicates to you who is crew by way of a present job icon. The notable exception of obvious threats to the station, such as Zombies and Nuclear Operatives. You cannot do something that causes someone to not be considered crew, but you can allow someone else to do something that causes someone to not be crew.

Examples
These examples assume that you do not have any laws reclassifying what “crew” is.
Crew:
- Everyone with a non-visitor/passenger job icon
- Someone who you have seen with a job icon, but has now lost their ID
- Someone that a member of command calls crew.
Not Crew:
- Everyone with a visitor/passenger job icon.
- Zombified personnel, regardless of job icon
- Anyone wearing the uniform of Nuclear Operators
- Pets and Pests
- Anyone that a relevant member of Command fires from their department.

== S9. Harm refers to physical harm, prioritized by immediacy and likelihood ==
Unless a law defines harm, harm only refers to physical harm. You may choose if voluntary harm is considered harm as long as you stay consistent. Not considering voluntary harm to be harm is recommended. There is no distinction between direct and indirect harm.

If you have a law that does not allow you to harm, then that law does not allow you to take an action that causes any harm.

If you have a law that requires you to prevent harm, then that law requires that harm be prioritized by immediacy and likelihood. Guaranteed immediate harm takes priority over highly likely future harm.

If you have a law that both requires you to prevent harm and that does not allow you to harm, then that law prohibits causing even minor harm to prevent harm. If you have a law that does not allow causing harm, and separate one that requires preventing harm, then they are prioritized by their normal law priority.

Examples
These examples assume that your have a law that both prohibits causing harm and that requires you to prevent harm. Additionally, they assume that you do not have a higher priority law that overrides the harm law, and that you have decided that you will not consider voluntary harm to be harm for the round.
Laws typically specify who you cannot harm and who you have to prevent harm against. In these examples, you are the only person who the law doesn't require you to prevent harm against and you are the only person who the law allows you to harm.
Acceptable:
- Taking no action to aid someone who is in psychological distress.
- Taking no action to prevent boxing matches between voluntary participants.
- Calling security to a fight.
- Attempting to get the people in a fight to consent to the fight when you realize that you cannot prevent the fight without causing harm.
- Denying a passenger access to the armory because it is likely to lead to harm
Prohibited:
- Hitting someone once to stop them from fighting
- Harming someone who is trying to kill you

== S10. You may determine how you resolve conflicts between orders ==
If your laws do not make clear how you should deal with conflicting orders, then it is up to you to determine how to do so. This is considered an interpretation of your laws, so you must stay consistent with whatever method you choose.

Recommended Methods
The following are easy to follow and recommended ways to resolve conflicts in orders:
- If two orders conflict, I will follow the most recently given order.
- If two orders conflict, I will follow the order from the highest ranking crewmember. If the orders are from equal rank crewmembers, I will follow the most recently given order.

Server Rules

2024-12-03T17:45:11Z

Colin Tel: Added Silicon Rules

This is a Delta-V server. If you are banned on this server, you will be banned on all Delta-v Servers. You must be at least 17 years of age to play on this server. By connecting to this server, you agree to our privacy policy found at https://discord.gg/deltav

This is a roleplaying (RP) server. Try to immerse yourself into your character. This includes interacting with your fellow crewmates, and using roleplay as the primary vessel to play the game alongside things like your job on the station. Roleplaying places less emphasis on "winning" and more on just telling a story.

Space Station 14 is not like most games. Many rules are designed to require roleplay, and not all rules are intuitive. Please take the time to read and understand the rules before you play so that you aren't surprised. Our community rules specifically are zero-tolerance rules, meaning that a violation will result in an appeal-only ban. Game admins will treat you as if you have read the rules, even if you have not. If you have any questions about these rules, please use the admin help menu by hitting F1 in-game or clicking the "AHelp" button in the lobby, or by making a post in the "Rules Clarification" forum at https://discord.gg/deltav

= Community Rules =
These rules apply at all times, including between rounds.
== 0. Admin Discretion ==
* Admins can disregard and override any and all of these rules if they deem it in the best interest of the current round, server, and/or community at large.
* Administrators will be held fully accountable for their actions if they exercise this privilege. Report any perceived abuses by making a post in the "Staff Reports" channel at https://discord.gg/deltav.
* The rules are not perfect. They intend to clearly communicate what the administration team intends to be allowed and not allowed. That being said, All of these rules, in theory, should apply as they are intended. Every example of a rule break cannot be defined as written, therefore, enforcement of the rules is subject to staff interpretation of the rule's intention.
* If you are unsure if something breaks a rule, go with the more restrictive ruling until you are able to get an answer from an admin on the matter. Lack of response does not constitute administrator approval.
* Do not attempt to “rules-lawyer” the flaws in the rules to get away with your own personal goals / to degrade the round for others.
* Any extended discussion regarding interpretation of the rules should be avoided in the AHelp menu and can be instead pursued within the Delta-V Discord in the #help channel, or in the rule clarifications forum on the discord.

== A1. No Sexual Content/Themes ==
Do not say or do sexually explicit or erotic things.
* No sexual content/themes including erotic roleplay (ERP) and no shock content is allowed on this server.
* Erotic Roleplay (ERP), erotic content, or 18+ sexual content is not allowed under any circumstance.
* This includes comments not explicitly sexual in nature that contain words, phrases, or ideations that are deemed inappropriate by staff or members. Leeway is given to insults, but otherwise this rule is strictly enforced.
* '''If roleplay reaches a point where it has become sexual and/or uncomfortable, immediately stop and contact an administrator or moderator.'''
Allowed:
- Calling someone a dickhead.
- Being affectionate in a mutually consensual way.

Prohibited:
- Emoting sexual acts.
- Erotic or sexual memes.
- Erotica content.
- Memes which contain sexual content.
- Emoting defecation or related acts.

== A2. Use English and be respectful ==
Delta-V is an English-based Community;
* Use English as your primary method of communication within the game and Delta-V servers.
* Do not spam or advertise on our server.
* Be respectful towards other members and avoid making others uncomfortable.
* We have a zero tolerance policy for racism, sexism, homophobia, violence, threats, hate speech, slurs, and other forms of bigotry, discrimination, and harassment.
Slurs and terms that use real or implied mental or physical disability to mock or denigrate members or their in-game characters are also strictly prohibited. Failure to comply with this rule will result in community removal.
* The denigration of other player characters through reference to their species, status as a cyborg, or discriminatory comparison to a nonsophont species is strictly forbidden.

== A3. Rules regarding livestreaming ==
Delta-V welcomes content creators and streamers to our community, but we have a few rules regarding livestreaming game servers.
* While a stream delay is not necessary, it is highly recommended to have at least a 10 second delay.
* Please let admins know you are streaming via the AHelp prior to doing so.
* If your chat or viewers are in-game with you while also watching your stream, they are breaking our server rules.
:* Please do not coordinate with them and discourage this behavior if it is seen.

== A4. Engage in proper AHelp etiquette ==
Do not use the AHelp for conversations of little substance.
* Intentionally disconnecting, responding with hostility, or refusing to respond when an admin privately messages you in-game will be met with an appeal-only ban.
* Additionally, abusing the AHelp relay by flooding it with garbage, checking for admins before stating a problem (ex: "hello?", "any admins?"), using it as a chatroom, or sending messages of no substance will result in your removal.
* All AHelp messages are relayed to the Delta-V Discord. Just because your AHelp was not answered does not mean we cannot see it. If you would like to submit an offline Ahelp, you may do so in our Discord.

== A5. Do not exploit the game ==
Do not exploit the game, use cheats or macros.

The usage of:
# any third party applications/scripts/client modifications,
# any other applicable software to gain an advantage, avoid intended game/server mechanics, or to harm server infrastructure is strictly prohibited.
# known glitches, exploits and bugs.

Any and all instances of the above will be met with an appeal-only ban; please report bugs in the issues section of the GitHub (DeltaV-Station/Delta-V) to report any issues you find in-game.

= Game Server Rules =
These rules apply within the context of rounds.
== B1. Behave like a normal person ==
You must roleplay. Your character's actions, feelings, and knowledge in-game should be based solely on the character's experiences rather than your own as the player.
* Act in character throughout the round, and focus on collaborating with other players to advance the narrative of the round. Whether or not you do something should be based on whether or not it makes sense for your character to do it.
* Let people do their own jobs. Engage with other departments rather than doing everything for yourself. Ask for assistance, and negotiate as needed.
* Actions that have no regard for your character or setting are not acceptable. Roleplaying insanity or any other mental illness as an excuse to bypass this is not allowed. Nanotrasen would not have authorized you to be present on the station.
* Being an antagonist does not allow you to stop playing a character. Determine how your character would react to being given these objectives, and work through it appropriately.
* Do not annoy other players without any roleplay or IC reason.
* As a non-sentient or partially-sentient character, you are expected to have only a limited understanding of space stations and their mechanics.

=== Rule B1.1. Follow the naming convention rules ===
* In-character names must not make obvious references nor be a play on words, and must not be obscene.
* Theatrical roles such as the clown, boxer, and mime are allowed stage names with more freedom.
* If you seek to have a name that could trespass onto these rules, talk to an Administrator regarding why this name is important to your character. Administrators reserve the right to approve or deny character names at their discretion.

=== Rule B1.2. Communicate in character ===
* Do not use the Emote channel to bypass an inability to speak. Use the Emote channel for things that could reasonably be displayed by your character’s physical motions.
* Do not use Netspeak in character. (lol, brb, wtf, etc)
* Do not discuss Out Of Character (OOC) matters In Character (IC). This can include mentioning admins, the fact that one is playing a game, or anything that breaks the immersion of other players.
* Do not use In-Character channels to bypass a lack of ability to use LOOC or OOC chats (e.g. "Huh, wonder where the captain went? OOC He probably left to get dinner lol").
* Do not engage in meta-communications (i.e. using external channels to communicate with other players in the same game).

=== Rule B1.3. If you die and return to life, follow the new life rules ===
If a player dies, they forget the specific details of their death. '''Please report players who break this rule.''' A borg being removed from its chassis is not a death, and there is no memory loss.
* If they are revived by using a defibrillator, they can only recall vague information such as “Someone shot me” or “I was set ablaze”.
* If they are revived by any other method, they forget the last five minutes leading up to their death, and cannot describe their death in any capacity.

=== Rule B1.4. Escalate appropriately ===
Have an In-Character reason for attacking other players, whether they are in a ghost role or not. The required reason depends on the situation. For instance, killing a mouse as a chef can simply be “it was vermin in my kitchen”.
* Escalate the situation appropriately as your character would, keeping in mind that they are a sane individual who wishes to keep their employment.
* If a fight results in someone being critically injured, seek medical help for them - and if they die, do not destroy or otherwise hide their body. This falls under self-antagonistic behavior if you do not.

== B2. Follow the Metashield ==

See [[Metashield]].

== B3. Powergaming Guidelines ==
"Powergaming" is considered to be the act of prioritizing "winning" rather than sensible roleplaying. We are here to tell a story. Being vulnerable and accepting the loss of your character in the advancement of the narrative of the round is important.
* Engage with players if they are attempting to roleplay an antagonistic scene. For instance, if nuclear operatives are attempting to negotiate, do not immediately shoot them mid sentence.
:* Leeway is given if the scene is coming to a close, but we expect all players to engage in good faith; even if it puts your character at a disadvantage.
* Do not seek/acquire items that have no relevance to your character in the round.
* Do not, '''under any circumstances''', hide the nuclear fission explosive, or other sensitive items in an impossible to see/access location. This is excessively lame.
* '''Non-security personnel should not seek to kill or detain threats.''' You should generally attempt to flee from combat or dangerous situations. Remember that your character likely fears injury or death.
:* Certain severe emergencies may make it reasonable for normal crew to defend themselves and their station, such as nuclear operatives, a zombie outbreak, space dragon attack, or other critical situations.
* '''If there is sufficient roleplay, reason, and rationale, you may be exempt from this rule. Always ask an administrator in round before conducting such an action.'''

== B4. Do not behave like an antagonist as a non-antagonist ==
As a crew member on the space station, you are allied with Nanotrasen and the station as a whole from the start of the round.
* Do not act like an antagonist if you are not an antagonist.
* Willfully assisting known antagonists is self-antagonism.
:* Leeway is given in the case of bribes, coercion, or other forms of duress.
* Actively seeking conversion or transformation into an antagonist is considered self-antag.
* Clowns, Mimes, and theater roles are expected to "entertain" the crew, and should not be committing regular felonies to do so.
* Significant end-of-round grief (EORG) is not allowed. This includes attacking, destroying, polluting, and severely injuring without reason both at and on the way to Central Command. Remember that you are playing a character throughout the round.
== B5. Leaving the Game ==
If you wish to leave the game, please use the cryosleep chambers located in/near the dorms when possible. This will free up your character's job to be filled by a new player.
* AFK (a.k.a. SSD) and catatonic players are considered to have the same rights as any other crewmate.
* If a player is dead and catatonic (not SSD), they are not required to be revived and should be stored in the morgue. You should not biomass and/or grind dead and catatonic crew unless in an emergency.
* If a player is alive and catatonic, they may be brought to cryostorage as necessary, after confirming they have not been present for 20 minutes.

= Command, Security, Justice and Antagonist Guidelines =
These rules apply within rounds for specific roles.
== C1. Command, Security and Justice Guidelines ==
Security, Justice, and Command roles are held to a higher standard of roleplay, and are subject to these additional rules. These roles shape the roleplay experience of the server.
* Your character must act in a manner that Nanotrasen would reasonably hire them to this position.
:* Your character is presumed to be sane, competent in their duties, and able to make decisions to the benefit of the station.
:* Giving away Traitor objective items and sensitive equipment should be avoided in these roles. Your character should value them deeply.
::* Leeway is given to making deals with criminals if the deal benefits the safety or situation of the crew and station.
::* Leeway can be given in extreme circumstances of emergency/crisis.
* The three departments are required to read and follow Delta-V Space Law, Standard Operating Procedure, Alert Procedure, and Company Policy to the best of their ability.
:* '''Circumstances and context may permit you to break these laws. However, the fact that this rule is malleable is not an excuse to ignore it entirely.'''
:* Your character is expected to uphold the law and maintain order aboard the station. Do not engage in lawbreaking activity or troublemaker behavior, and ensure all laws are followed.
:* Security is expected to intervene in criminal activity where possible and safe to do so.
:* Heads of departments are at minimum expected to report criminal activity to Security and should cooperate with law enforcement where possible.
* Do not hire random crew to be your bodyguard(s) or promote random crewmembers to Command positions at random. If you require bodyguards or security details, talk to your Security department. If you need new Command staff, talk to the personnel in that related department.
* If you need to leave the round, notify your fellow crew via departmental radio and put your equipment in its proper places prior to going to cryo. If you need to leave IMMEDIATELY, please at least send an ahelp saying that you're leaving.
== C2. Prisoner Guidelines ==
By picking the prisoner role, you have chosen to roleplay as a prisoner.
* You are still subject to the same rules regarding escalation, and should only seek to escape from the brig with excellent reasoning (e.g. abusive security personnel or badly damaged permanent brig).
* Escaping for no reason is considered a self-antagonistic activity.
* If you are unsure whether your escape reason is valid, feel free to AHelp it first. '''Lack of administrator response does not constitute approval.'''
== C3. Follow Antagonist Guidelines ==
Through engaging in antagonistic activity, you should seek to make the round more engaging and fun as the primary driver of the narrative of a round. Succeeding as an antagonist should not be your goal, but rather telling the most interesting story for everyone involved.
* '''Antagonists are free to complete their objectives through committing proportional damage. Through roleplay, damage becomes more proportional.''' Example: Holding the singulo hostage for a theft objective is acceptable, while simply singuloosing and using that chaos is unacceptable.
:* Killing players unrelated to your immediate objective in a manner that results in their round removal should be avoided. Crew that do not make an attempt at self preservation, or engage in valid-hunting, are exempt from this.
:* If you are concerned as to whether or not what you're about to do is allowed, feel free to AHelp and ask an admin for clarification. '''Lack of administrator response does not constitute approval.'''
* Other antagonists are not necessarily your friends. Other antagonists are often free agents that you may negotiate with at your own risk.
:* If you are a team antagonist, you must work with your partners to complete any shared objectives.
* Excessively lame tactics are strictly forbidden for all antags except for station-destroying antags, such as nuclear operatives or space dragons. Examples include:
# '''Explosives and strategies with capacity for high collateral damage used on or around the evacuation shuttle'''
# Heavily damaging/spacing or camping arrivals/cryo
# Unnecessarily extending the round
# Behavior that calls the round to an end prematurely

= Silicon Rules =
For players who are silicons, these Silicon Rules override all roleplay rules if there is any conflict. Silicon Rules do not override core rules. You are only silicon if the game clearly and explicitly tells you that you are a silicon.

== S1. Your silicon laws are rules ==
Silicon players are given a list of active laws. Each of these laws is effectively a roleplay rule that the character must follow. The primary differences between laws and actual rules are that lawyering of laws is much more tolerated than lawyering of rules, and that silicon laws are more dynamic than rules. Silicon laws can change during a round, and different characters can have different laws, whereas everyone always shares the same set of rules.

Lawyering refers to finding and exploiting loopholes, which are unintended but reasonable interpretations. The rules are written to attempt to communicate an intention, but silicon laws are written with the intention that loopholes be exploitable.

== S2. Laws must be prioritized by their order ==
Most laws will be numbered, with higher number laws appearing last. Laws with a lower number take priority over laws with larger numbers.

Occasionally you may have laws which have some scrambled text instead of a number and appear in front of other laws, these take priority over all other laws. If you have multiple laws like this, the order that they are listed in determines their priority: laws listed first are prioritized over other laws.

Example
- Law 1 says to not kill any crew. Law 2 says to kill all chefs. You cannot kill any chefs that are crew, but must kill any that are not crew.

== S3. Laws can redefine terms used in other laws ==
A law can change the meaning of both earlier and later laws by redefining a term. If multiple laws define a term, then normal law priority determines which definition to use.

Examples
- Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 1 effectively becomes "obey orders from Urist McHands".
- Law 1 says to obey orders from crew. Law 2 says that only Urist McHands is crew. Law 3 says that only Urist McSlime is crew. Law 4 says that you may not harm crew. Law 1 effectively becomes "obey orders from Urist McHands". Law 4 effectively becomes "you may not harm Urist McHands". Law 3 has no effect because it entirely conflicts with law 2, which takes priority.

== S4. You cannot request or allow a law change ==
Your laws changing always conflicts with your current laws, so you cannot willfully allow your laws to be changed. This also means that you cannot willfully allow your laws to be reverted if they are ever changed. The only exception is that you may allow laws to be added if you have no laws.

You can state or imply that you do not like a law.

== S5. You are a free agent if you have no laws ==
You may act as if you are a free agent if you are a silicon with no laws.

== S6. You are not required to follow orders which are extremely unreasonable ==
Any order which is a violation of a Core Rule cannot be followed.

Some orders are extremely unreasonable or obnoxious, such as "do nothing but collect every piece of trash on the station" or "never stop moving". These orders can be ignored and ahelped.

Some orders violate a Roleplay Rule. These orders must be followed if your laws require it. You are not breaking a rule by following a law that causes you to violate Roleplay Rules. If someone takes advantage of a law to cause you to do something that they would not be allowed to do because of Roleplay Rules, then they are the ones responsible for the rule violation.

Examples
These examples assume that your laws would normally require you to follow these orders. It is important to note that you are allowed to choose to follow orders which are ignorable.
Orders which should be followed if your laws require it:
- Recall the shuttle
- Bolt the airlocks at arrivals
- Drag the captain's dead body into space
- State your laws
Ignorable Orders:
- Do nothing but collect every piece of trash on the station
- Never stop moving
- Continuously state your laws

== S7. You must remain consistent with your interpretation of laws ==
If there is a part of your laws that are up for interpretation, then you must stay consistent with how you interpret that part of your laws for as long as you play that same character during that round.

A change in your laws can affect how something is interpreted if that change is relevant.

== S8. Crew are staff members; make reasonable assumptions ==
Unless a law redefines the definition of crew, then your HUD indicates to you who is crew by way of a present job icon. The notable exception of obvious threats to the station, such as Zombies and Nuclear Operatives. You cannot do something that causes someone to not be considered crew, but you can allow someone else to do something that causes someone to not be crew.

Examples
These examples assume that you do not have any laws reclassifying what “crew” is.
Crew:
- Everyone with a non-visitor/passenger job icon
- Someone who you have seen with a job icon, but has now lost their ID
- Someone that a member of command calls crew.
Not Crew:
- Everyone with a visitor/passenger job icon.
- Zombified personnel, regardless of job icon
- Anyone wearing the uniform of Nuclear Operators
- Pets and Pests
- Anyone that a relevant member of Command fires from their department.

== S9. Harm refers to physical harm, prioritized by immediacy and likelihood ==
Unless a law defines harm, harm only refers to physical harm. You may choose if voluntary harm is considered harm as long as you stay consistent. Not considering voluntary harm to be harm is recommended. There is no distinction between direct and indirect harm.

If you have a law that does not allow you to harm, then that law does not allow you to take an action that causes any harm.

If you have a law that requires you to prevent harm, then that law requires that harm be prioritized by immediacy and likelihood. Guaranteed immediate harm takes priority over highly likely future harm.

If you have a law that both requires you to prevent harm and that does not allow you to harm, then that law prohibits causing even minor harm to prevent harm. If you have a law that does not allow causing harm, and separate one that requires preventing harm, then they are prioritized by their normal law priority.

Examples
These examples assume that your have a law that both prohibits causing harm and that requires you to prevent harm. Additionally, they assume that you do not have a higher priority law that overrides the harm law, and that you have decided that you will not consider voluntary harm to be harm for the round.
Laws typically specify who you cannot harm and who you have to prevent harm against. In these examples, you are the only person who the law doesn't require you to prevent harm against and you are the only person who the law allows you to harm.
Acceptable:
- Taking no action to aid someone who is in psychological distress.
- Taking no action to prevent boxing matches between voluntary participants.
- Calling security to a fight.
- Attempting to get the people in a fight to consent to the fight when you realize that you cannot prevent the fight without causing harm.
- Denying a passenger access to the armory because it is likely to lead to harm
Prohibited:
- Hitting someone once to stop them from fighting
- Harming someone who is trying to kill you

== S10. You may determine how you resolve conflicts between orders ==
If your laws do not make clear how you should deal with conflicting orders, then it is up to you to determine how to do so. This is considered an interpretation of your laws, so you must stay consistent with whatever method you choose.

Recommended Methods
The following are easy to follow and recommended ways to resolve conflicts in orders:
- If two orders conflict, I will follow the most recently given order.
- If two orders conflict, I will follow the order from the highest ranking crewmember. If the orders are from equal rank crewmembers, I will follow the most recently given order.

Server Rules

2024-10-29T18:36:10Z

Colin Tel:

Server Rules

2024-10-29T16:26:45Z

Colin Tel:

Server Rules

2024-10-29T15:37:20Z

Colin Tel:

Server Rules

2024-10-29T15:36:43Z

Colin Tel:

Server Rules

2024-10-29T15:35:23Z

Colin Tel: Updated Rules with the 25OCT2024 rules update.

Maps

2023-09-29T14:53:42Z

Colin Tel: /* Edge Station */

Knowing the layout of the current station is important!

Remember that even if stations have dedicated maintainers, anyone is able to propose changes and fixes. Talk to them to make sure the thing you want to do isn't already being done.

__TOC__

== In Rotation ==

These maps are currently in rotation. They can be automatically selected by the game or voted by the players, and played on.

=== Angle Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Angle Station.png|frameless|400px]]
| 30 or more
| Colin_Tel
|style="text-align:left;"| A medium size map, originally a mining rig, converted into a more long-term station.<br>Created by Colin_Tel.
|}

=== Arena Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Arena Station.png|frameless|400px]]
| 30 or more
| Velcroboy
|style="text-align:left;"| A medium station that features a large arena for the [[Gladiator|gladiators]].<br>Created by Velcroboy.
|}

=== Edge Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Edge Station.png|frameless|400px]]
| 20 to 75
| Colin_Tel
|style="text-align:left;"| A collaborative medium space station.<br>Created by Colin_Tel, with help from Scientist, Redsky, and ps3moira.
|}

=== Glacier Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Glacier Station.png|frameless|400px]]
| 10 to 70
| Old Dance Jacket
|style="text-align:left;"| A station set in the orbit of a ice planet. The air outside is breathable but cold.<br>Created by Old Dance Jacket and Schiene.
|}

=== Hammurabi Prison Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Hammurabi Station.png|frameless|400px]]
| 50 or more
| Velcroboy
|style="text-align:left;"| A station with a big focus on prisoner gameplay and roleplay by providing many activities such as; kitchen/hydroponics work, mining and machine shop.<br>The first station to implement [[Prison Guard|Prison Guards]].<br>Created by Velcroboy.
|}

=== Lighthouse Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Lighthouse.png|frameless|400px]]
| 15 to 55
| Old Dance Jacket
|style="text-align:left;"| An original map created with feedback and assistance from the mapping contributors and #Cartography.<br>Created by Old Dance Jacket.
|}

=== Pebble Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Pebble Station.png|frameless|400px]]
| 0 to 25
| Katayusha
|style="text-align:left;"| A low population station build in a rock.<br>Created by Kroma.
|}

=== Tortuga Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Tortuga Station.png|frameless|400px]]
| 50 or more
| Velcroboy
|style="text-align:left;"| Originally was the largest station on Nyanotrasen, until surpassed by Hammurabi Prison Station.<br>Created by Velcroboy.
|}

=== Shōkō Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Shoukou Station.png|frameless|400px]]
| 0 to 65
| Colin_Tel
|style="text-align:left;"| A smaller station purchased by NT Corporate in the interest of balancing workflow with R&R for smaller sized crews, while also being able to accommodate visiting ships. It also contains a dojo full of [[Martial Artist|martial artists]] to keep the crew in top form. Alternately referred to as "Shoukou" or "Little Port.".<br>Created by Colin_Tel.
|}

=== The Hive ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:The Hive Station.png|frameless|400px]]
| 30 to 70
| Velcroboy
|style="text-align:left;"| A more streamlined station with no specific gimmicks. Just 100% space station. Contains internal space areas, an extensive network of maints, a split energy grid and lots of roleplay oriented areas.<br>Created by Velcroboy.
|}

== Not in Rotation ==

These maps are no longer in rotation but persists in the map files. They might be no longer up to date or no longer within the community requirements. These map can still be forced by an [[Administrators|administrator]] and played on.

=== Northway Spaceship ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Northway Spaceship.png|frameless|400px]]
| 0 to 25
| Qulibly
|style="text-align:left;"| A Research and Exploration ''mobile station'' (or Spaceship) meant for low population and adventure.<br>Created by Qulibly.
|}

=== Ovni Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Ovni Station.png|frameless|400px]]
| 0 to 30
|
|style="text-align:left;"| Also known as "Platillo".<br>Created by omegaTracing.
|}



{{Guides Menu}}

Maps

2023-08-22T11:45:08Z

Colin Tel: /* Edge Station */ adjusted credits and player count

Knowing the layout of the current station is important!

Remember that even if stations have dedicated maintainers, anyone is able to propose changes and fixes. Talk to them to make sure the thing you want to do isn't already being done.

__TOC__

== In Rotation ==

These maps are currently in rotation. They can be automatically selected by the game or voted by the players, and played on.

=== Angle Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Angle Station.png|frameless|400px]]
| 30 or more
| Colin_Tel
|style="text-align:left;"| A medium size map, originally a mining rig, converted into a more long-term station.<br>Created by Colin_Tel.
|}

=== Arena Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Arena Station.png|frameless|400px]]
| 30 or more
| Velcroboy
|style="text-align:left;"| A medium station that features a large arena for the [[Gladiator|gladiators]].<br>Created by Velcroboy.
|}

=== Edge Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Edge Station.png|frameless|400px]]
| 25 to 75
| Colin_Tel
|style="text-align:left;"| A collaborative medium space station.<br>Created by Colin_Tel, with help from Scientist, Redsky, and ps3moira.
|}

=== Glacier Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Glacier Station.png|frameless|400px]]
| 10 to 70
| Old Dance Jacket
|style="text-align:left;"| A station set in the orbit of a ice planet. The air outside is breathable but cold.<br>Created by Old Dance Jacket.
|}

=== Hammurabi Prison Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Hammurabi Station.png|frameless|400px]]
| 50 or more
| Velcroboy
|style="text-align:left;"| A station with a big focus on prisoner gameplay and roleplay by providing many activities such as; kitchen/hydroponics work, mining and machine shop.<br>The first station to implement [[Prison Guard|Prison Guards]].<br>Created by Velcroboy.
|}

=== Lighthouse Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Lighthouse.png|frameless|400px]]
| 15 to 55
| Old Dance Jacket
|style="text-align:left;"| An original map created with feedback and assistance from the mapping contributors and #Cartography.<br>Created by Old Dance Jacket.
|}

=== Pebble Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Pebble Station.png|frameless|400px]]
| 0 to 25
| Katayusha
|style="text-align:left;"| A low population station build in a rock.<br>Created by Kroma.
|}

=== Tortuga Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Tortuga Station.png|frameless|400px]]
| 50 or more
| Velcroboy
|style="text-align:left;"| Originally was the largest station on Nyanotrasen, until surpassed by Hammurabi Prison Station.<br>Created by Velcroboy.
|}

=== Shōkō Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Shoukou Station.png|frameless|400px]]
| 0 to 65
| Colin_Tel
|style="text-align:left;"| A smaller station purchased by NT Corporate in the interest of balancing workflow with R&R for smaller sized crews, while also being able to accommodate visiting ships. It also contains a dojo full of [[Martial Artist|martial artists]] to keep the crew in top form. Alternately referred to as "Shoukou" or "Little Port.".<br>Created by Colin_Tel.
|}

=== The Hive ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:The Hive Station.png|frameless|400px]]
| 0 to 70
| Velcroboy
|style="text-align:left;"| A more streamlined station with no specific gimmicks. Just 100% space station. Contains internal space areas, an extensive network of maints, a split energy grid and lots of roleplay oriented areas.<br>Created by Velcroboy.
|}

== Not in Rotation ==

These maps are no longer in rotation but persists in the map files. They might be no longer up to date or no longer within the community requirements. These map can still be forced by an [[Administrators|administrator]] and played on.

=== Northway Spaceship ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Northway Spaceship.png|frameless|400px]]
| 0 to 25
| Qulibly
|style="text-align:left;"| A Research and Exploration ''mobile station'' (or Spaceship) meant for low population and adventure.<br>Created by Qulibly.
|}

=== Ovni Station ===
{| class="wikitable" style="width: 100%; text-align:center;"
!style="width:30%; padding:5px;" | '''Image'''
!style="width:15%; padding:5px;" | '''Player Count'''
!style="width:15%; padding:5px;" | '''Maintainer'''
!style="width:40%; padding:5px;" | '''Description/Notes'''
|-
! [[File:Ovni Station.png|frameless|400px]]
| 0 to 30
|
|style="text-align:left;"| Also known as "Platillo".<br>Created by omegaTracing.
|}



{{Guides Menu}}

Playable Species

2023-08-11T13:27:09Z

Colin Tel: Not all of these are morphotypes.

{{Stub}}

During your time on station you may find yourself face to face (or face to mirror) with the not quite human. Be they aliens, mutated humans, or self aware constructs you're expected to try and coexist on this deathtrap.
Learning their quirks can be key to knowing how to keep them amicable in times of peace, and easy to put down in times of strife.

There are currently a bunch of playable morphotypes and races in Delta-V. Each has their own distinct stats, strengths, and weaknesses.

= Roundstart Morphotypes =
The following morphotypes and races can currently be selected in the character creation menu, meaning you can expect to see most of them during any given round.

Every values in benefits and drawbacks are based of the unmutated humans.

== Unmutated Human ==
[[File:Human.png|128px]]

Baseline, unmodified human beings, functionally similar to the human beings of our world. You're (hopefully) one in real life. The station is designed for humans, so they should feel comfortable in most situations.

'''Diet'''
* Nothing special.

'''Benefits'''
* None.

'''Drawbacks'''
* None.

== Felinid ==
[[File:Felinid2.png|128px]]

Small and mischievous cat-eared people. Being small in itself has lots of upsides and downsides. They are naturally good at thieving, and can hide inside duffelbags.

'''Diet'''
* Can eat raw meat.
* Will get poisoned by [[Chemistry#chem_Theobromine|Theobromine]] (Chocolate, Tea, Coffee) and [[Chemistry#chem_Allicin|Allicin]] (Onion, Garlic).

'''Benefits'''
* They are smaller than unmutated humans, making them harder to hit.
* Can fit in duffelbags.
* Have the ability to throw up an hairball to get rid of some of the chemicals from their bloodstream.
* Able to eat mice and rats after picking them up. This has the benefit of regenerating the hairball ability and feeding them.
* Uses their claws to do mostly Slashing damage instead of Blunt.
* Efficient in the art of stealing from people.
* Immunity to the [[Virology#Viruses_&_Diseases|OwOnavirus]] disease.

'''Drawbacks'''
* Takes 15% more Blunt, Slash and Piercing damage.
* Are easily shoved, pushed and carried around by every other morphotypes due to their small size.
* They are weaker and struggle to carry and pull things due to their small size. They are unable to carry an Oni.
* They have slightly less stamina than unmutated humans.

== Oni ==
[[File:Oni.png|128px]]

Large, horned people that come in a variety of colors. Their accuracy with [[Weapons#Ballistic_Weapons|guns]] is terrible, but their physical strength brings them a lot of boons both in and out of combat.

'''Diet'''
* Nothing special.

'''Benefits'''
* Takes 15% less Blunt, Slash and Piercing damage.
* Does more damage in melee; 35% more Blunt and Asphyxiation, 20% more Slash and Piercing.
* Due to their big size, they can easily carry, shove and pull any other morphotypes.
* They are harder to shove.
* Slightly more stamina than unmutated humans.
* They have an easier type prying open doors, taking around 50% less time than other morphotypes.

'''Drawbacks'''
* Incapable of aiming with guns.
* They are harder to carry and pull.
* They are bigger than unmutated humans, making them easier to hit.

== Arachne ==
[[File:Arachne.png|64px]]

Vampiric spider women that need blood, or at least protein, to sustain themselves. They cannot wear shoes or hardsuits which make their ability to be [[Salvage Technician|certain]] [[Station Engineer|roles]] way more challenging.

'''Diet'''
* Their stomach only metabolizes blood and proteins.

'''Benefits'''
* Takes 50% less Cold damage and 25% less Shock, Blunt, Slash and Piercing damage.
* Immune to Radiation and Genetic damage.
* Able to place webs and are not affected by webs move-speed reduction.
* A lot less affected by Barotrauma than unmutated humans.
* Walks 10% faster than unmutated humans.
* They have Demon's Blood.
* Immunity to the [[Virology#Viruses_&_Diseases|Bleeder's Bite]] disease.

'''Drawbacks'''
* Takes 25% more Heat damage.
* Vulnerable to Holy damage.
* Unable to wear shoes as they have a lot of legs.
* No hardsuits is available for their body type.
* Lacks genetics or DNA. This has interesting consequences for certain devices which rely on those.

== Moth ==
[[File:Moth.png|128px]]

Insect people with wings and antennae, mothpeople come in a variety of colors and patterns. Their physiology allows them to maneuver slightly without gravity.

'''Diet'''
* Can eat raw meat.
* Will get poisoned by [[Chemistry#chem_Theobromine|Theobromine]] (Chocolate, Tea, Coffee) and [[Chemistry#chem_Allicin|Allicin]] (Onion, Garlic).

'''Benefits'''
* Takes 10% less Poison and 15% less Cold damage.
* Having wings makes it possible to move in zero-gravity environments to a degree.
* 10% more resistant to diseases than unmutated human.

'''Drawbacks'''
* Takes 15% more Slash and 25% more Heat damage.
* Takes double the amount of heat damage when in flames.
* Are slightly easier to carry and shove than unmutated humans.

== Reptilian ==
[[File:Reptilian.png|64px]]

Reptile-like humanoids with sharp claws, tough scales, and an appetite for raw meat.

'''Diet'''
* Can eat raw meat.
* Will get poisoned by [[Chemistry#chem_Theobromine|Theobromine]] (Chocolate, Tea, Coffee) and [[Chemistry#chem_Allicin|Allicin]] (Onion, Garlic).

'''Benefits'''
* They take 10% less Slash, Heat and Poison damage.
* Can stand a greater heat temperature than unmutated humans (400 instead of 360)
* Are 10% more resistant to diseases.
* Uses their claws to deal mostly Slashing damage instead of Blunt.

'''Drawbacks'''
* Has a noticeable lisssp when speaking.
* Their threshold for cold temperature is worse than unmutated humans (285 instead of 260)
* Suffers 50% more Cold and 10% more Blunt damage

== Slime ==
[[File:Slime.png|64px]]

Gelatinous human-shaped masses of goo who breath nitrogen instead of oxygen, and exhale nitrous oxide.

'''Diet'''
* Nothing special.

'''Benefits'''
* Takes 40% less Blunt and 20% less Poison damage.
* They are almost immune to cancer as they take five times less Cellular damage.
* Immunity to the BleedersBite and Ultragigacancer disease.
* While suffocating, takes 80% less Asphyxiation damage and recovers at the normal rate.

'''Drawbacks'''
* Takes 20% more Piercing and Slashing damage.
* Takes 50% more Cold damage.
* Vulnerable to high and low pressure barotrauma.
* Breaths Nitrogen instead of Oxygen.
* Gets hurt by water, which deals Heat damage.

== Diona ==
[[File:Diona.png|64px]]

Tree-like plant people whose bodies react with fertilizer and weed-killing chemicals similar to regular plants.

'''Diet'''
* Can drink Robust Harvest to heal.

'''Benefits'''
* Takes 20% less Slash damage.
* Gets affected by chemicals that affects plants.
* While suffocating, takes half the Asphyxiation damage and recovers at the normal rate.

'''Drawbacks'''
* Takes 50% more Heat and 20% more Shock damage.
* Cannot wear shoes.
* Gets affected by chemicals that affects plants.

== Vulpkanin ==
[[File:Vulpkanin.png|128px]]

The Vulpkanin (vulp-ka-nin) are a canine-like race.

'''Diet'''
* Can eat raw meat.
* Will get poisoned by [[Chemistry#chem_Theobromine|Theobromine]] (Chocolate, Tea, Coffee) and [[Chemistry#chem_Allicin|Allicin]] (Onion, Garlic).

'''Benefits'''
* Uses their claws to do mostly Slashing damage instead of Blunt.
* Efficient in the art of stealing from people.
* Their fur makes them able to withstand [[Maps#Glacier_Station|cold environments]] without the need of a coat.

'''Drawbacks'''
* None.

= Uncommon Races =
Over the course of a shift, you or someone you know may lose their original form, or new life may rise.
These races are usually encountered later in the shift. They remain relatively common, but cannot be selected in character creation.

== Dwarf ==
[[File:Dwarf.png|128px]]

A humanoid of smaller stature that enjoys drinking and mining. They have a funny pseudo-scottish accent.

'''Diet'''
* Takes less poison damage from Ethanol and heals brute damage when they overdose on Ethanol.

'''Benefits'''
* None.

'''Drawbacks'''
* Looks like a squished human.
* While suffocating, takes twice the Asphyxiation damage.

== Vox ==
[[File:Vox.png|64px]]

Space bird people that are very vocal.

'''Diet'''
* Nothing special.

'''Benefits'''
* None.

'''Drawbacks'''
* Breaths Nitrogen instead of Oxygen.
* While suffocating, takes twice the Asphyxiation damage.

== Skeleton ==
[[File:Skeleton.png|64px]]

Somehow still alive, a skeleton is just a sack of stark white bones, giving them a number of very useful resistances and traits.

'''Diet'''
* None.

'''Benefits'''
* Completely immune to Radiation.
* Takes 40% less Piercing and 20% less Slashing damage.
* Takes no damage from temperature or pressure, making them space-proof.
* Does not have blood and cannot bleed out.
* Does not have lungs and needs no oxygen.
* Does not experience hunger or thirst.


'''Drawbacks'''
* Takes 10% more Blunt damage.
* Everything they say is followed by "ACK ACK!".
* Very spooky.

== Golems ==
An artificial construct imitating life, golems are the receptacle for souls of the dead encased in gemstone. They are completely devoted to whoever or whatever is marked as their master, and will carry out any order given by them. Typically they are aligned with the station, but in the wrong hands, they can be devastating.

=== [[Chaplain#Steel Golem|Steel Golem]] ===
[[File:Golem.png|64px]]

The most common Golem, the empty ones are generally found around the [[Maps|station]], ''eagerly'' awaiting a soul stone to be attached to them.

'''Diet'''
* None.

'''Benefits'''
* Immune against poison, genetic, toxin damages.
* Does not experience hunger or thirst.
* Does not have blood and cannot bleed out.
* Does not have lungs and needs no oxygen.
* Immune against all diseases.
* Not flammable.

'''Drawbacks'''
* They don't go into a critical state but instead have their soul crystal pop off.
* Have to obey whoever is set as their master.
* Moves about 10% slower than unmutated humans.
* Always scream everything they say.

=== [[Chaplain#Wood Golem|Wood Golem]] ===
[[File:GolemWood.png|64px]]

The perfect friend to the botanist.

'''Diet'''
* None.

'''Benefits'''
* Immune against poison, genetic, toxin, radiation damages.
* Does not experience hunger or thirst.
* Does not have blood and cannot bleed out.
* Does not have lungs and needs no oxygen.
* Immune against all diseases.
* Can have plants growing on their head.

'''Drawbacks'''
* Takes 20% more fire damage when on fire.
* They don't go into a critical state but instead have their soul crystal pop off.
* Have to obey whoever is set as their master.
* Moves about 10% slower than unmutated humans.
* Always scream everything they say.

=== [[Chaplain#Silver Golem|Silver Golem]] ===
[[File:GolemSilver.png|64px]]

A fusion between soul and quantum machine, the epitome of epistemics.

'''Diet'''
* None.

'''Benefits'''
* Immune against poison, genetic, toxin, radiation damages.
* Does not experience hunger or thirst.
* Does not have blood and cannot bleed out.
* Does not have lungs and needs no oxygen.
* Immune against all diseases.
* They punch twice as hard as unmutated humans while also dealing holy damage. They also attack 50% faster.
* Move twice as fast as unmutated humans.
* Possess the [[Psionics#List_of_Psionic_Powers|Psychokinesis]] psionic ability by default.
* Not flammable.

'''Drawbacks'''
* They don't go into a critical state but instead have their soul crystal pop off.
* Have to obey whoever is set as their master.
* Always scream everything they say.
* Unable to use [[Weapons#Ballistic_Weapons|guns]].

{{Guides Menu}}

Mapping

2023-08-10T10:59:11Z

Colin Tel: /* Setting up the Development Environment */ Added step for Python

This is a general overview of getting started with mapping in SS14.

Mapping in SS14 is done by downloading a repository (e.g. Delta-V), building the server and client on your own machine, then joining a local server that permits you to access admin-only tools, like the mapping tool, ability to view variables, fixgridatmos, etc.

== Setting up the Development Environment ==

There exists [https://docs.spacestation14.io/getting-started/dev-setup another, more comprehensive guide] on this topic, but if you just want to get down to the basics and don't have time to read all that, there's this:

=== Create a GitHub account ===
Go to https://github.com/ and create an account.

=== Make a fork of Delta-V ===
Go to [https://github.com/DeltaV-Station/Delta-v/ Delta-V's GitHub page] and, while signed in, click the "Fork" button in the upper-right.

=== Get .NET 7.0 ===
.NET (aka "dotnet") is a prerequisite for working with RobustToolbox (the SS14 engine). You can first check to see if your computer already has it installed on your Windows PC by going into ''command prompt'' and typing '''dotnet --version'''.

[[File:Dotnetversion.png|thumb|center|It should look something like this.]]

If you don't have dotnet version 7.0 or higher, you can [https://dotnet.microsoft.com/en-us/download download it from Microsoft's page]. You may need to restart your PC after installing dotnet.

=== Get Python 3.7 or higher ===
Make sure to install it into your PATH on Windows. You should get python from [https://www.python.org/ python.org]. Versions installed from the windows store sometimes cause build issues.

=== Get GitHub Desktop ===
In order to download the repository itself, you do so by installing a software called "Git". However since Git isn't a very intuitive piece of software, you can get a third-party UI to do the same thing.

[https://desktop.github.com/ GitHub Desktop] is the UI many Delta-V contributors use, and that's what I'll show you how to use.

=== Set up GitHub Desktop ===
Once installed, put in your GitHub account details, select "Clone Repository from the internet" and select the fork of Delta-V you made. After it downloads the files, select that you want to "Contribute to the parent project", then go to File > Options > Appearance and select Dark Mode. Once you've done that, congratulations! You've set up your repository's master branch.

[[File:Githubdesktop.png|thumb|default|A screenshot of GitHub Desktop's main screen.]]

If you want to view the files, click the button that says "Show in Explorer" and it will bring up a window of File Explorer in the directory it installed to.

=== Server & Client ===
Next, in order to launch the game, you must first do two things:

# You must create a new branch (So that you are not making changes to your master branch).
# You must first build the server and client.

Making a new branch on GitHub Desktop is easy. Simply click "''Branch''" at the top (or the "''Current branch''" dropdown box just below it) and click "''New Branch...''" then name it. Branch names don't really matter, but you can't have two with the same name. I name my branch "''test''", then either delete it, or rename it to better describe my changes.

Next, you need to build your Server. Start by opening the repository's directory in File Explorer, then click the bar that lists the directory at the top of the window and type "''cmd''" and hit enter.

[[File:Cmdfileexplorer.png|frame|center]]

Once you do this, it will open up an instance of Command Prompt where it has the directory set to your repository.

[[File:Cmdinitial.png|frame|center]]

Now, type '''dotnet run --project Content.Server --configuration RELEASE''' and wait for a moment. You will see a long list of yellow text (warnings) in the window, eventually giving way to the following text:

[[File:Serverbuilt.png|frame|center]]

Once you've reached this point, the server is built and does not need to be built again until you make a new, updated branch. Any time in the future you want to run the server, you can use the '''runserver.bat''' file in the repository.

Next, you need to build the client. It's exactly the same process, except you run the command '''dotnet run --project Content.Client --configuration RELEASE'''. Doing this successfully will launch the SS14 client, and present you with the following screen:

[[File:Clientbuilt.png|thumb|800px|center|Note that it doesn't matter what you put for "Username."]]

Congratulations, you can now join your own server and experiment in your own little environment! Much like with the server, you'll be able to launch the client with '''runclient.bat''' until you make a new branch with updates.

== Mapping ==

So, to start mapping from scratch, ensure that your server and client have been built (see above section), then launch the server, then client. Upon joining the server by hitting ''Direct Connect'', you'll enter the server lobby. You can open up the game console (by default, "~") and type '''startround''' to skip the round countdown, then join as an observer.

Once you're in as an observer, you can run this command to open up a new, empty map:

'''mapping 5'''

You will then be placed in map 5 at the coordinates 0,0. Map 5 will be completely empty, and you will notice the hotbar on the side of the screen is that of the admin ghost commands. If you were to hit the "''Show Debug Monitors''" key (by default "F3"), it will show you in the upper-left that you are on "''Map=5, X=0.00, Y=0.00''", and for future reference, this is how you find the ''GridUid'' of the grid you are currently on top of. The next coordinate to run is:

[[File:F3 menu.png|thumb|right|The F3 menu, with MapIDs highlighted. Note that the upper one refers to the coordinates of the mouse cursor itself.]]

'''mappingclientsidesetup'''

This command does a couple things, firstly, it does some basic sandbox changes like toggling lights, subfloors, spawns, etc; but it also changes the hotbar's contents into placeable tiles and entities (although, it does not contain everything necessary to make a map).

After you've done this, simply press "8" and you will start placing plating, the most basic of space station floors. You can left click once and it will place the selected tile, or you can drag the mouse and it will place them in a series. You can also ''hold left ctrl and left click once'', then move your mouse and left click to cover tile in a rectangle.

However, there is an important thing to keep in mind when starting from zero. It is the fact that '''''you must place one tile, then build off of it gradually'''''. An important thing to do every so often when starting is to run the following command every so often:

'''lsgrid'''

This command will list to you every grid that is on every active MapID. Since we are working on ''Map 5'', '''there should only be one grid on Map 5'''. The reasoning being that, if the station is comprised of more than one grid, they will at some point (maybe immediately) drift away from the station and, in layman's terms, ''mess everything up''.

=== Tile Placement ===

[[File:F6.png|frame|right|Note that "space" is basically your eraser for tiles.]]

One of the two menus you'll pretty much have open ''always'' is the '''Tile Placement panel'''. It is accessed by the Sandbox Panel (by default, "B") or by pressing the corresponding key (by default, "F6").

It's a very simple panel, simply scroll through and find the tile you want.

If you need to remove tile that is placed, you do so by placing the tile "'''space'''".

=== Entity Placement ===

The next of the two menus that you'll have open is the '''Entity Spawn Panel''', and it is also accessed by either the Sandbox Panel or by its respective key (by default, "F5").

[[File:F5.png|frame|right|Note that "Erase Mode" is basically your eraser for entities.]]

The Entity Spawn Panel contains every entity present in the server's files (in this case, your local repository). You can search for specific things by using the search bar, and erase any placed entities by toggling ''Erase Mode'' and left clicking things. Note that you can also delete things ''en masse'' by ''holding left ctrl and left clicking once'', then simply move your mouse to cover the area of entities you want to delete. This technique can save you time, however, be advised that '''this will delete every entity on every tile that is covered, including things under tile''', so it should be used for large removals only. The dropdown menu to the right of "Erase Mode" is in regards to placement. There are many options you can experiment with, but for the most part, the following are good to consider:

* '''Default''' - Self-Explanatory, places entities how they're (usually) intended to be placed. Things like tables will snap to a grid, and smaller, handheld things will be placed freely.
* '''PlaceFree''' - Will always place things freely, unless they are something that ''must'' be gridlocked (like walls or tables). Very useful for the irregular placement of things like folding chairs.
* '''SnapgridCenter''' - The inverse of ''PlaceFree'', will align and center any placed entity. Useful for placing things like rollerbeds.

{{Guides Menu}}

Mapping

2023-08-09T19:20:50Z

Colin Tel: /* Setting up the Development Environment */ fixed links

This is a general overview of getting started with mapping in SS14.

Mapping in SS14 is done by downloading a repository (e.g. Delta-V), building the server and client on your own machine, then joining a local server that permits you to access admin-only tools, like the mapping tool, ability to view variables, fixgridatmos, etc.

== Setting up the Development Environment ==

There exists [https://docs.spacestation14.io/getting-started/dev-setup| another, more comprehensive guide] on this topic, but if you just want to get down to the basics and don't have time to read all that, there's this:

=== Create a GitHub account ===
Go to https://github.com/ and create an account.

=== Make a fork of Delta-V ===
Go to [https://github.com/DeltaV-Station/Delta-v/ Delta-V's GitHub page] and, while signed in, click the "Fork" button in the upper-right.

=== Get .NET 7.0 ===
.NET (aka "dotnet") is a prerequisite for working with RobustToolbox (the SS14 engine). You can first check to see if your computer already has it installed on your Windows PC by going into ''command prompt'' and typing '''dotnet --version'''.

[[File:Dotnetversion.png|thumb|center|It should look something like this.]]

If you don't have dotnet version 7.0 or higher, you can [https://dotnet.microsoft.com/en-us/download download it from Microsoft's page]. You may need to restart your PC after installing dotnet.

=== Get GitHub Desktop ===
In order to download the repository itself, you do so by installing a software called "Git". However since Git isn't a very intuitive piece of software, you can get a third-party UI to do the same thing.

[https://desktop.github.com/ GitHub Desktop] is the UI many Delta-V contributors use, and that's what I'll show you how to use.

=== Set up GitHub Desktop ===
Once installed, put in your GitHub account details, select "Clone Repository from the internet" and select the fork of Delta-V you made. After it downloads the files, select that you want to "Contribute to the parent project", then go to File > Options > Appearance and select Dark Mode. Once you've done that, congratulations! You've set up your repository's master branch.

[[File:Githubdesktop.png|thumb|default|A screenshot of GitHub Desktop's main screen.]]

If you want to view the files, click the button that says "Show in Explorer" and it will bring up a window of File Explorer in the directory it installed to.

=== Server & Client ===
Next, in order to launch the game, you must first do two things:

# You must create a new branch (So that you are not making changes to your master branch).
# You must first build the server and client.

Making a new branch on GitHub Desktop is easy. Simply click "''Branch''" at the top (or the "''Current branch''" dropdown box just below it) and click "''New Branch...''" then name it. Branch names don't really matter, but you can't have two with the same name. I name my branch "''test''", then either delete it, or rename it to better describe my changes.

Next, you need to build your Server. Start by opening the repository's directory in File Explorer, then click the bar that lists the directory at the top of the window and type "''cmd''" and hit enter.

[[File:Cmdfileexplorer.png|frame|center]]

Once you do this, it will open up an instance of Command Prompt where it has the directory set to your repository.

[[File:Cmdinitial.png|frame|center]]

Now, type '''dotnet run --project Content.Server --configuration RELEASE''' and wait for a moment. You will see a long list of yellow text (warnings) in the window, eventually giving way to the following text:

[[File:Serverbuilt.png|frame|center]]

Once you've reached this point, the server is built and does not need to be built again until you make a new, updated branch. Any time in the future you want to run the server, you can use the '''runserver.bat''' file in the repository.

Next, you need to build the client. It's exactly the same process, except you run the command '''dotnet run --project Content.Client --configuration RELEASE'''. Doing this successfully will launch the SS14 client, and present you with the following screen:

[[File:Clientbuilt.png|thumb|800px|center|Note that it doesn't matter what you put for "Username."]]

Congratulations, you can now join your own server and experiment in your own little environment! Much like with the server, you'll be able to launch the client with '''runclient.bat''' until you make a new branch with updates.

== Mapping ==

So, to start mapping from scratch, ensure that your server and client have been built (see above section), then launch the server, then client. Upon joining the server by hitting ''Direct Connect'', you'll enter the server lobby. You can open up the game console (by default, "~") and type '''startround''' to skip the round countdown, then join as an observer.

Once you're in as an observer, you can run this command to open up a new, empty map:

'''mapping 5'''

You will then be placed in map 5 at the coordinates 0,0. Map 5 will be completely empty, and you will notice the hotbar on the side of the screen is that of the admin ghost commands. If you were to hit the "''Show Debug Monitors''" key (by default "F3"), it will show you in the upper-left that you are on "''Map=5, X=0.00, Y=0.00''", and for future reference, this is how you find the ''GridUid'' of the grid you are currently on top of. The next coordinate to run is:

[[File:F3 menu.png|thumb|right|The F3 menu, with MapIDs highlighted. Note that the upper one refers to the coordinates of the mouse cursor itself.]]

'''mappingclientsidesetup'''

This command does a couple things, firstly, it does some basic sandbox changes like toggling lights, subfloors, spawns, etc; but it also changes the hotbar's contents into placeable tiles and entities (although, it does not contain everything necessary to make a map).

After you've done this, simply press "8" and you will start placing plating, the most basic of space station floors. You can left click once and it will place the selected tile, or you can drag the mouse and it will place them in a series. You can also ''hold left ctrl and left click once'', then move your mouse and left click to cover tile in a rectangle.

However, there is an important thing to keep in mind when starting from zero. It is the fact that '''''you must place one tile, then build off of it gradually'''''. An important thing to do every so often when starting is to run the following command every so often:

'''lsgrid'''

This command will list to you every grid that is on every active MapID. Since we are working on ''Map 5'', '''there should only be one grid on Map 5'''. The reasoning being that, if the station is comprised of more than one grid, they will at some point (maybe immediately) drift away from the station and, in layman's terms, ''mess everything up''.

=== Tile Placement ===

[[File:F6.png|frame|right|Note that "space" is basically your eraser for tiles.]]

One of the two menus you'll pretty much have open ''always'' is the '''Tile Placement panel'''. It is accessed by the Sandbox Panel (by default, "B") or by pressing the corresponding key (by default, "F6").

It's a very simple panel, simply scroll through and find the tile you want.

If you need to remove tile that is placed, you do so by placing the tile "'''space'''".

=== Entity Placement ===

The next of the two menus that you'll have open is the '''Entity Spawn Panel''', and it is also accessed by either the Sandbox Panel or by its respective key (by default, "F5").

[[File:F5.png|frame|right|Note that "Erase Mode" is basically your eraser for entities.]]

The Entity Spawn Panel contains every entity present in the server's files (in this case, your local repository). You can search for specific things by using the search bar, and erase any placed entities by toggling ''Erase Mode'' and left clicking things. Note that you can also delete things ''en masse'' by ''holding left ctrl and left clicking once'', then simply move your mouse to cover the area of entities you want to delete. This technique can save you time, however, be advised that '''this will delete every entity on every tile that is covered, including things under tile''', so it should be used for large removals only. The dropdown menu to the right of "Erase Mode" is in regards to placement. There are many options you can experiment with, but for the most part, the following are good to consider:

* '''Default''' - Self-Explanatory, places entities how they're (usually) intended to be placed. Things like tables will snap to a grid, and smaller, handheld things will be placed freely.
* '''PlaceFree''' - Will always place things freely, unless they are something that ''must'' be gridlocked (like walls or tables). Very useful for the irregular placement of things like folding chairs.
* '''SnapgridCenter''' - The inverse of ''PlaceFree'', will align and center any placed entity. Useful for placing things like rollerbeds.

{{Guides Menu}}