Delta-V Wiki - User contributions [en]

Administrative Rulings

2026-08-21T20:01:46Z

DV disposablecrewmember42: revert beacon ruling for now, under discussion again

{{Important|Title=Making changes to this page|Note=You need to be in the projectstaff wiki group to be able to edit this page, ping our host to be added to it. If you don't have access yet, please post missing rulings in [https://discord.com/channels/968983104247185448/1486398865459515574 this #admin-general thread] or on the [[Talk:Administrative Rulings|talk page]].|Color=#ffffff|Image=BookSpaceLaw.png}}

== Concerning antagonists ==

=== General ===
* The positronic brain of a Borg may be shut off and disposed of by an antagonist if it witnessed a crime. {{AnchorLink|antag-posi-shutoff}}
** We strongly suggest you turn the brain back on afterwards, so the Borg player can continue playing their role. However, not doing so is not a rule-break per se.
** This ruling was put in place because there is no functioning Borg death system.
* Antagonists may not stall the round by repeatedly recalling the shuttle. {{AnchorLink|antag-stalling}}
** Antagonists may recall the shuttle exactly once if it helps them accomplish their objectives.

=== Antagonistic Ghost Roles ===
* Playing Xeno, Rat King, Entropic Colossus and similar ghost roles as non-hostile is not allowed. {{AnchorLink|antag-ghostroles-friendly}}
** You may feign friendliness towards crew to mislead and trap them or otherwise aid you in your objectives.

=== Cosmic Cultists ===
* Cultists may not place the monument off-station. It must be placed on the station's grid. {{AnchorLink|cosmic-monument-placement}}

=== Revenants ===

* Revenants may not spill jugs, drag people or interact with the round in other unintended ways while they are invisible. {{AnchorLink|revenant-spill-drag-invis}}
** '''The Revenant being able to melee people while invisible is intended.'''
** ''Rule of thumb:'' If you can do something as an invisible, invincible ghost to affect other players and it's not specifically advertised as a power of the Revenant, you probably shouldn't be doing it. Counterplay to your antagonistic actions should be possible.
** This is considered excessively lame and borderline bug-abuse.

=== Space Ninjas ===
* Ninjas may be treated as crit-to-detain or KOS, even if they have not taken antagonistic action yet. {{AnchorLink|ninjas-kos}}
** You should still respect their attempts at roleplay.

=== Nuclear Operatives ===
* Nukies may round-remove crew for any reason. They are not tied to round-removal rules. {{AnchorLink|nukies-rr-crew}}
** You should still be focused on blowing up the station as a Nukie:
*** Do feel free to round-remove crew you come across while completing your objective.
*** Don't roam the station focused solely on finding and round-removing as many people as you can.

=== Traitors ===
* Crew, including Security, may capture and compromise syndicate comms with proper permits. {{AnchorLink|traitors-comms-compromise}}
* Crew may not test for disguised items, '''even after discovering an open uplink'''. {{AnchorLink|traitors-disguised-items-uplink}}
** This means you should never assume toys or other disguised items are illegal gear just because you know such items exist. There has to have been a strong indication that the item is not what it seems, such as seeing it in use or seeing a situation that cannot be explained in any other way, for you to confiscate it.
** As is explicitly stated in the [[Metashield]]: ''Stealth items should not be "tested" for their functionality, but items that are clearly producing some sort of stealth effect can be confiscated.''
* Traitors may not assist Nuclear Operatives, including Lone Operatives, unless they have the "Die a glorious death" objective. {{AnchorLink|traitors-no-elp-nukie}}

=== Zombies ===

* Zombies may not attack borgs unless they were provoked. {{AnchorLink|zombies-borg-attack}}
** They do not inherently view them as food.
** If provoked, they may continue attacking the borg until their chassis is destroyed.
* Zombies may not attack or destroy structures unless they know there is food (living beings) behind them. {{AnchorLink|zombies-structure-damage}}
* Zombies may not be non-hostile. {{AnchorLink|zombies-always-hostile}}
* Zombies may not hide in disposal chutes or flush them. {{AnchorLink|zombies-chutes}}

== Concerning other roles ==

=== Prisoner ===

* Prisoners may not seek to escape Perma without reason, but they may escape opportunistically if presented with a significant opportunity. {{AnchorLink|prisoner-escape-opportunity}}
** This means you should not run out of the perma airlock every time it is opened, but you could escape if, for example, a Traitor blew a hole into wall to facilitate your escape.
** Your character does not have to like being in perma. They can absolutely want to be free, but keep in mind Prisoner is not an antagonistic role.

== Concerning mechanics ==
=== General ===
* Felinids and other species that can enter duffel bags may not abuse this mechanic to avoid being damaged. {{AnchorLink|felinid-bag-cheese}}
** This means: They may hide in them if they are still "undetected", but they should not enter a bag during combat or while being pursued in order to make being damaged impossible.

=== Borging ===
* Any laws you receive after being borged supersede your antag objectives. {{AnchorLink|borging-objectives}}
** This means: A borged nukie in a Crewsimov chassis may not attack people.

=== Engineering ===
* GarTEGs and other constructions that abuse game implementation details to produce something in vast quantities are not allowed. {{AnchorLink|garteg}}
** They make little sense ICly, look and feel unsafe and are generally too "game-y".
** ''Rule of thumb:'' The things you construct should make sense and not recklessly expose other crew to danger from an IC perspective.

== Concerning specific rules ==

=== [[Server Rules#S4. You cannot request or allow a law change|S4 - You cannot request or allow a law change]] ===

* Borgs may not directly request for the station AI to override their laws. {{AnchorLink|s4-borg-ai-request}}
** They may work around this by, for example, mentioning to the AI that a specific law is preventing them from accomplishing a specific task.

=== [[Metashield|B2 - Metashield]] ===
* The "Current gamemode, and any antagonists that could exist as a result" shield prohibits attempts at guessing the gamemode based on otherwise innocuous character behavior. {{AnchorLink|metashield-no-guessing}}
** This means: If someone orders monkey cubes and Zombies have not been called out yet, you should not assume they are an Initial Infected. Your character should not anticipate an attack like this without a sound current-round reason.

Administrative Rulings

2026-08-21T19:33:29Z

DV disposablecrewmember42: added station beacon announcement cheese ruling (https://discord.com/channels/968983104247185448/973884953911787520/1540366967184298005), missing round stalling ruling

{{Important|Title=Making changes to this page|Note=You need to be in the projectstaff wiki group to be able to edit this page, ping our host to be added to it. If you don't have access yet, please post missing rulings in [https://discord.com/channels/968983104247185448/1486398865459515574 this #admin-general thread] or on the [[Talk:Administrative Rulings|talk page]].|Color=#ffffff|Image=BookSpaceLaw.png}}

== Concerning antagonists ==

=== General ===
* The positronic brain of a Borg may be shut off and disposed of by an antagonist if it witnessed a crime. {{AnchorLink|antag-posi-shutoff}}
** We strongly suggest you turn the brain back on afterwards, so the Borg player can continue playing their role. However, not doing so is not a rule-break per se.
** This ruling was put in place because there is no functioning Borg death system.
* Antagonists may not stall the round by repeatedly recalling the shuttle. {{AnchorLink|antag-stalling}}
** Antagonists may recall the shuttle exactly once if it helps them accomplish their objectives.

=== Antagonistic Ghost Roles ===
* Playing Xeno, Rat King, Entropic Colossus and similar ghost roles as non-hostile is not allowed. {{AnchorLink|antag-ghostroles-friendly}}
** You may feign friendliness towards crew to mislead and trap them or otherwise aid you in your objectives.

=== Cosmic Cultists ===
* Cultists may not place the monument off-station. It must be placed on the station's grid. {{AnchorLink|cosmic-monument-placement}}

=== Revenants ===

* Revenants may not spill jugs, drag people or interact with the round in other unintended ways while they are invisible. {{AnchorLink|revenant-spill-drag-invis}}
** '''The Revenant being able to melee people while invisible is intended.'''
** ''Rule of thumb:'' If you can do something as an invisible, invincible ghost to affect other players and it's not specifically advertised as a power of the Revenant, you probably shouldn't be doing it. Counterplay to your antagonistic actions should be possible.
** This is considered excessively lame and borderline bug-abuse.

=== Space Ninjas ===
* Ninjas may be treated as crit-to-detain or KOS, even if they have not taken antagonistic action yet. {{AnchorLink|ninjas-kos}}
** You should still respect their attempts at roleplay.

=== Nuclear Operatives ===
* Nukies may round-remove crew for any reason. They are not tied to round-removal rules. {{AnchorLink|nukies-rr-crew}}
** You should still be focused on blowing up the station as a Nukie:
*** Do feel free to round-remove crew you come across while completing your objective.
*** Don't roam the station focused solely on finding and round-removing as many people as you can.

=== Traitors ===
* Crew, including Security, may capture and compromise syndicate comms with proper permits. {{AnchorLink|traitors-comms-compromise}}
* Crew may not test for disguised items, '''even after discovering an open uplink'''. {{AnchorLink|traitors-disguised-items-uplink}}
** This means you should never assume toys or other disguised items are illegal gear just because you know such items exist. There has to have been a strong indication that the item is not what it seems, such as seeing it in use or seeing a situation that cannot be explained in any other way, for you to confiscate it.
** As is explicitly stated in the [[Metashield]]: ''Stealth items should not be "tested" for their functionality, but items that are clearly producing some sort of stealth effect can be confiscated.''
* Traitors may not assist Nuclear Operatives, including Lone Operatives, unless they have the "Die a glorious death" objective. {{AnchorLink|traitors-no-elp-nukie}}

=== Zombies ===

* Zombies may not attack borgs unless they were provoked. {{AnchorLink|zombies-borg-attack}}
** They do not inherently view them as food.
** If provoked, they may continue attacking the borg until their chassis is destroyed.
* Zombies may not attack or destroy structures unless they know there is food (living beings) behind them. {{AnchorLink|zombies-structure-damage}}
* Zombies may not be non-hostile. {{AnchorLink|zombies-always-hostile}}
* Zombies may not hide in disposal chutes or flush them. {{AnchorLink|zombies-chutes}}

== Concerning other roles ==

=== Prisoner ===

* Prisoners may not seek to escape Perma without reason, but they may escape opportunistically if presented with a significant opportunity. {{AnchorLink|prisoner-escape-opportunity}}
** This means you should not run out of the perma airlock every time it is opened, but you could escape if, for example, a Traitor blew a hole into wall to facilitate your escape.
** Your character does not have to like being in perma. They can absolutely want to be free, but keep in mind Prisoner is not an antagonistic role.

== Concerning mechanics ==
=== General ===
* Felinids and other species that can enter duffel bags may not abuse this mechanic to avoid being damaged. {{AnchorLink|felinid-bag-cheese}}
** This means: They may hide in them if they are still "undetected", but they should not enter a bag during combat or while being pursued in order to make being damaged impossible.
* Players may not place or modify station beacons in order to alter the location shown in announcements such as the nuke arm announcement. {{AnchorLink|announcement-anchors-cheese}}
** Abusing the announcements' implementation details in this way is considered excessively lame.

=== Borging ===
* Any laws you receive after being borged supersede your antag objectives. {{AnchorLink|borging-objectives}}
** This means: A borged nukie in a Crewsimov chassis may not attack people.

=== Engineering ===
* GarTEGs and other constructions that abuse game implementation details to produce something in vast quantities are not allowed. {{AnchorLink|garteg}}
** They make little sense ICly, look and feel unsafe and are generally too "game-y".
** ''Rule of thumb:'' The things you construct should make sense and not recklessly expose other crew to danger from an IC perspective.

== Concerning specific rules ==

=== [[Server Rules#S4. You cannot request or allow a law change|S4 - You cannot request or allow a law change]] ===

* Borgs may not directly request for the station AI to override their laws. {{AnchorLink|s4-borg-ai-request}}
** They may work around this by, for example, mentioning to the AI that a specific law is preventing them from accomplishing a specific task.

=== [[Metashield|B2 - Metashield]] ===
* The "Current gamemode, and any antagonists that could exist as a result" shield prohibits attempts at guessing the gamemode based on otherwise innocuous character behavior. {{AnchorLink|metashield-no-guessing}}
** This means: If someone orders monkey cubes and Zombies have not been called out yet, you should not assume they are an Initial Infected. Your character should not anticipate an attack like this without a sound current-round reason.

Event Policy

2026-08-19T18:28:59Z

DV disposablecrewmember42: Reverted edit by DV disposablecrewmember42 (talk) to last revision by Vape

''This policy refers to Administrators and Curators, Unless otherwise specified.''

1. '''Actions of Staff during round must be reported to the #Event-log in discord.''' This includes all “One-off” spawns. Spawns and actions pertaining to an approved event can be skipped as long as the event itself has been reported. Major changes to an event in-round must be logged. This excludes small actions that are taken to preserve the integrity of the game, such as moving players & addressing small bugs.

2. '''Never''' '''use a “smite” against a player character that is in round.''' This includes possible raiders. Smites have the capacity to be irreversible and game breaking. They should not be used outside of the admin arena.

3. '''Events should be allowed to play out at their own pace.''' Events will almost invariably be affected by the crew, antagonists, or natural occurrences within the round; let the round flow organically and allow players to interact with the event rather than forcing them to follow a script. Let them fail if needed.


4. '''Events must meet or exceed our MRP Standard.''' Both the rationale and implementation of an event must demonstrate evidence of a story, or be beneficial to the story unfolding on the station currently.

5. '''Events must not feature staff-level ghost roles such as deathsquad unless directly authorized by a Head of Staff.''' These roles should be filled by staff and represent both Administration and Curation in an in-character fashion.

6. '''Events should never portray ''NanoTrasen'' or ''Central Command'' as directly antagonistic to the crew.''' While Central Command is expected to be strict - especially on matters of policy and procedure - they should be supportive where possible, politely evasive when pressed, and only authoritative in extreme circumstances.

7. '''Events should not disrupt the balance of the round.''' Don't introduce overpowered, unique, or usually unobtainable ghost roles, entities, or items, and should not overwhelm the round, the station, or its resources. This includes objective items, spawn-only items, leviathings, etc.

8. '''Event roles should be reserved for players.''' Staff are expected to organize and oversee the event, not partake in it. If a ghost role is not taken for '''more than 5 minutes''', the eventing staff member may join the queue .

9. '''aGhosts are welcome to take any ghost roles.''' Refer to the previous rule regarding roles you have spawned.

10. '''Do not test unknown commands on the game servers.''' All testing of Console commands, VVwrites, and other “Unused” aGhost powers should take place on a personal dev environment, not on the game servers.

11. '''You may not take ERT Leadership roles unless 5 minutes has passed without anyone taking the role.'''

12. '''Any spawned CC character going to the station, must be armed by security on station.''' If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them. You may take 1 sidearm EQUIVALENT to the one spawned by the loadout menu.

= Event Categories =

* '''Low Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' or above without approval.
Low impact events either:
* Do not interact with players in a meaningful way
* Are a direct response to a player request or interaction, and do not affect the round to a greater degree
-> Such as responding to faxes or answering prayers

* '''Medium Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' with approval from a '''Curator'''. '''Game Administrators''' / '''Curators''' without approval. '''Senior Curators''' / '''Senior Administrators''' and above do not need approval.
Medium impact events either
* Considerable affect players or the round without derailing the round, round-removing
players, or taking significant resources and manpower from departments.
* Add a new gamerule unlikely to cause significant effect on players or the round
* Are a direct response to a player request or interaction that affects the round to a considerable degree.
-> Such as adding a Clown Spider spawn or adding a single round ending antag

* '''High Impact''' - Following the mandatory notice and when approved by a '''Senior Curator''' or above.
High impact events either:
* Heavily affect players or the round, possibly derailing the round, round-removing
players, or taking significant resources and manpower from departments
* Add a new gamemode, causing significant effect on players or the round
* Are a direct response to a player request or interaction that results in a High Impact event.
-> Some Examples include setting the game mode or spawning multiple round ending antagonists

⚠️'''High impact events must be planned, written in Directions event library, and approved. Additionally, a mandatory 30 minute notice must be posted & *approved* in the event log prior to running these events, unless otherwise authorized by at least *2 Senior Curators, or 1 Head of Staff*. An event plan should include entity/role requirements, event goals, players and departments involved, and “Staffing” needs.'''⚠️

== Exceptions to event policy ==

1. '''Staff are permitted to spawn in Central Command characters for the purpose of greeting crew or writing faxes.''' CC Characters should be competent, reasonably named, and disconnected from any “In-game” characters.

2. '''Staff are permitted to create ghost bars.''' Spawning ghost roles on a separate map from the station for the purpose of a gag, sandbox construction, ETC

3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval

4. '''Staff are permitted to Spawn ERT following the chart listed below.''' Any exceptions require approval from a Senior Administrator/Senior Curator or above.

[[File:ERT chart.jpg|thumb]]

= Epsilon Procedure =

''In the event that Epsilon is or will be needed, Permission is required by a HEAD OF STAFF or SENIOR CURATOR. If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.

Event Policy

2026-08-19T18:12:58Z

DV disposablecrewmember42: link chart in knowledgebase instead

''This policy refers to Administrators and Curators, Unless otherwise specified.''

1. '''Actions of Staff during round must be reported to the #Event-log in discord.''' This includes all “One-off” spawns. Spawns and actions pertaining to an approved event can be skipped as long as the event itself has been reported. Major changes to an event in-round must be logged. This excludes small actions that are taken to preserve the integrity of the game, such as moving players & addressing small bugs.

2. '''Never''' '''use a “smite” against a player character that is in round.''' This includes possible raiders. Smites have the capacity to be irreversible and game breaking. They should not be used outside of the admin arena.

3. '''Events should be allowed to play out at their own pace.''' Events will almost invariably be affected by the crew, antagonists, or natural occurrences within the round; let the round flow organically and allow players to interact with the event rather than forcing them to follow a script. Let them fail if needed.


4. '''Events must meet or exceed our MRP Standard.''' Both the rationale and implementation of an event must demonstrate evidence of a story, or be beneficial to the story unfolding on the station currently.

5. '''Events must not feature staff-level ghost roles such as deathsquad unless directly authorized by a Head of Staff.''' These roles should be filled by staff and represent both Administration and Curation in an in-character fashion.

6. '''Events should never portray ''NanoTrasen'' or ''Central Command'' as directly antagonistic to the crew.''' While Central Command is expected to be strict - especially on matters of policy and procedure - they should be supportive where possible, politely evasive when pressed, and only authoritative in extreme circumstances.

7. '''Events should not disrupt the balance of the round.''' Don't introduce overpowered, unique, or usually unobtainable ghost roles, entities, or items, and should not overwhelm the round, the station, or its resources. This includes objective items, spawn-only items, leviathings, etc.

8. '''Event roles should be reserved for players.''' Staff are expected to organize and oversee the event, not partake in it. If a ghost role is not taken for '''more than 5 minutes''', the eventing staff member may join the queue .

9. '''aGhosts are welcome to take any ghost roles.''' Refer to the previous rule regarding roles you have spawned.

10. '''Do not test unknown commands on the game servers.''' All testing of Console commands, VVwrites, and other “Unused” aGhost powers should take place on a personal dev environment, not on the game servers.

11. '''You may not take ERT Leadership roles unless 5 minutes has passed without anyone taking the role.'''

12. '''Any spawned CC character going to the station, must be armed by security on station.''' If your character is visiting the station or leaving CC in any capacity, You are not allowed to spawn weapons for them. You may take 1 sidearm EQUIVALENT to the one spawned by the loadout menu.

= Event Categories =

* '''Low Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' or above without approval.
Low impact events either:
* Do not interact with players in a meaningful way
* Are a direct response to a player request or interaction, and do not affect the round to a greater degree
-> Such as responding to faxes or answering prayers

* '''Medium Impact''' - '''Trial-Game Administrators''' / '''Trial-Curators''' with approval from a '''Curator'''. '''Game Administrators''' / '''Curators''' without approval. '''Senior Curators''' / '''Senior Administrators''' and above do not need approval.
Medium impact events either
* Considerable affect players or the round without derailing the round, round-removing
players, or taking significant resources and manpower from departments.
* Add a new gamerule unlikely to cause significant effect on players or the round
* Are a direct response to a player request or interaction that affects the round to a considerable degree.
-> Such as adding a Clown Spider spawn or adding a single round ending antag

* '''High Impact''' - Following the mandatory notice and when approved by a '''Senior Curator''' or above.
High impact events either:
* Heavily affect players or the round, possibly derailing the round, round-removing
players, or taking significant resources and manpower from departments
* Add a new gamemode, causing significant effect on players or the round
* Are a direct response to a player request or interaction that results in a High Impact event.
-> Some Examples include setting the game mode or spawning multiple round ending antagonists

⚠️'''High impact events must be planned, written in Directions event library, and approved. Additionally, a mandatory 30 minute notice must be posted & *approved* in the event log prior to running these events, unless otherwise authorized by at least *2 Senior Curators, or 1 Head of Staff*. An event plan should include entity/role requirements, event goals, players and departments involved, and “Staffing” needs.'''⚠️

== Exceptions to event policy ==

1. '''Staff are permitted to spawn in Central Command characters for the purpose of greeting crew or writing faxes.''' CC Characters should be competent, reasonably named, and disconnected from any “In-game” characters.

2. '''Staff are permitted to create ghost bars.''' Spawning ghost roles on a separate map from the station for the purpose of a gag, sandbox construction, ETC

3. '''Staff are permitted to remodel “Midpoint” to reflect events that occurred during the round, and to remodel “Midpoint” to reflect a more artistic and “Destressed” environment for players to end their round.''' The latter requires appropriate documentation in the Event-log, and following “Medium-Impact” approval

4. '''Staff are permitted to Spawn ERT following [https://knowledge.deltav.gay/ingame/eventing/ERT.html#emergency-call this chart].''' Any exceptions require approval from a Senior Administrator/Senior Curator or above.

= Epsilon Procedure =

''In the event that Epsilon is or will be needed, Permission is required by a HEAD OF STAFF or SENIOR CURATOR. If either of these options are unavailable after 10 minutes, you may call gamma and resolve the situation without violence.

File:ERT chart.jpg

2026-08-19T17:28:55Z

DV disposablecrewmember42: DV disposablecrewmember42 uploaded a new version of File:ERT chart.jpg

a chart describing the standard for summoning ERT