Staff Policy: Difference between revisions

Latest revision as of 17:48, 27 January 2026

DISCLAIMER: These policies apply to all staff, regardless of position, unless explicitly stated otherwise.

Staff Code of Conduct

Failure to the Code of Conduct can result in removal from staff.

1. Follow the Server rules at all times and abide by DeltaV’s Privacy Policy. The policy can also be found in the Discord rules page

2. Be respectful, helpful, and trustworthy when performing staff actions and interacting with the community.

3. Personal Identifiable Information (PII) such as IP, Email Addresses, UUID, etc is to be shared on a need-to-know basis. Do not share PII with the community or staff without consent of the information’s owner, unless you are sharing this information with other members of staff who need this information to perform their duties.

4. Do not use direct messages for official staff actions or statements.

5. You are expected to recuse yourself from situations involving conflicts of interest, biases, or other interpersonal dynamics. If you find yourself placed in this situation, please request another team member or a Head of Staff take over for you.

6. Staff that are expecting to be taking a break for two or more weeks, please let your team Head know. We understand there are instances where you can vanish without warning due to personal emergency, upon returning please contact your team Head.

Staff Rank Structure

This breaks down each staff rank, their duties, and permissions. Higher ranking staff members, in their respective departments, gain all permissions of lower staff ranks.'

Head Staff

Project Manager (PM) - Handles Internal Affairs, content, staff policies, and all things regarding Delta-V. Oversees all staff. Determines the continuity of the project. Determines the “Future Plans” of the project. Project manager’s have the ability to make “Owner-like” decisions via unanimous PM agreements (with other PM’s) and can bypass this in times of emergencies.

Head Moderator - Handles Internal Affairs, Investigates staff violations and staff reports. Oversees Moderation, the discord and it's rules.

Head Game Administrator (HGA) - Oversight of Administration; including hiring, training, and promoting. Administrative rulings and Administrative policies

Game director (GD) - Oversight of Direction; including hiring, training, and promoting. Direction roadmap approval, Oversight of Content.

Senior Staff

Senior Moderator - Assist Head Moderator in duties as assigned, Standard Moderation, Investigation of staff reports and misconduct.

Senior Administrator - Assist HGA’s in duties as assigned, Standard Administration, Provide guidance.

Senior Curator - Assist GD’s in duties as assigned, Standard Direction, Provide guidance.

Trial Admin Mentor - Training with all Trial Administrators.

Entry-Level and Trial Staff

Moderator - Mhelps, Notes involving the discord, management of discord chats and “Policing them”.

Administrator - Events, Ahelps, Notes & Bans, Rule Clarifications, Ban Appeals, Event Approval (via event policy). Can use Readmin Policy

Curator - Events, Chelps, Event creation, Banning Raiders, Event Approval (via event policy). Content approval (via vote).

Trial Curator - Events, Chelps, Event creation, Banning Raiders, Content approval (via vote).

Trial Administrator - Ahelps, Notes & Bans, Rule Clarifications, and Ban Appeals.

Event Policy

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. Any spawned CC character going to the station, must be armed by security on station. If your character is visiting the station, You are Not Allowed to spawn weapons for them.

@@ Line 1: / Line 1: @@
-===== DISCLAIMER: These policies apply to all staff, regardless of position, unless explicitly stated otherwise. =====
+'''DISCLAIMER: These policies apply to all staff, regardless of position, unless explicitly stated otherwise.'''
-=== 1. General Standards ===
+== Staff Code of Conduct ==
-''As a member of staff, your actions and behaviour reflect on the rest of your team and on DeltaV as a whole, and may be scrutinised heavily by members of the community. Be sure to remain respectful, professional, and helpful, and adhere to the guidelines and policies relevant to you.''
+''Failure to the Code of Conduct can result in removal from staff.''
-'''1.1 Every member of staff is required to follow the community standards and rules at all times.''' Violating these rules and guidelines, encouraging community members to break either, even in a joking manner, or intentionally ignoring infractions committed by staff and community members may result in demotion or dismissal. Members of staff are empowered and encouraged to end conversations and interactions that violate these rules and standards in public-facing channels and notify Moderation as necessary.
+.  Follow the Server rules at all times and abide by DeltaV’s Privacy Policy. The policy can also be found in the [https://discord.com/channels/968983104247185448/968983104662409239 Discord rules page]
-'''1.2''' '''Staff are expected to be professional and respectful when performing staff actions.''' Such actions include but are not limited to: AHelps, CHelps, Community Management, tickets, and announcements. If a community member is being disrespectful or abusive, or if you feel uncomfortable handling a situation, please escalate to other team members or your head of staff, notify Moderation as necessary, and recuse yourself from further involvement.
+.  Be respectful, helpful, and trustworthy when performing staff actions and interacting with the community.
-'''1.3 Members of staff are expected to be helpful and trustworthy in their interactions with the community.''' Intentionally spreading misinformation, inciting witch hunts, or provoking community outlash are all actions that may result in demotion or dismissal from staff.
+.  Personal Identifiable Information (PII) such as IP, Email Addresses, UUID, etc is to be shared on a need-to-know basis. Do not share PII with the community or staff without consent of the information’s owner, unless you are sharing this information with other members of staff who need this information to perform their duties.
-=== 2. Privacy & Confidentiality ===
+. Do not use direct messages for official staff actions or statements.
-''As a member of staff, you may be privy to community members’ personal identifying information. Abuse of your power to distribute PII without consent or authorisation constitutes an ethical violation and may additionally cause legal issues; be sure to read this section carefully if interacting with PII and double-check with your head of staff on anything you’re uncertain about.''
-'''2.1''' '''Staff are expected to read and abide by DeltaV’s Privacy Policy.''' The policy can be found in #information on our Discord.
+.  You are expected to recuse yourself from situations involving conflicts of interest, biases, or other interpersonal dynamics. If you find yourself placed in this situation, please request another team member or a Head of Staff take over for you.
-'''2.2 PII is to be shared on a need-to-know basis.''' Do not, under any circumstances, share PII with members of staff or the community, unless: you have the consent of the information’s owner, or; you are sharing this information with other members of staff who require this information to perform their duties. Examples of PII include: IP/HWID, UUID, email address, etc.
+.  Staff that are expecting to be taking a break for two or more weeks, please let your team Head know.  We understand there are instances where you can vanish without warning due to personal emergency, upon returning please contact your team Head.
-'''2.3''' '''Staff must not share sensitive, personal, or confidential information in public or unrelated channels, or with unrelated individuals.''' This includes any information regarding a player’s bans or watchlists, moderator actions relating to members of the community, or other private information. Sharing such information without the consent of that person will result in remediative action, without exception, up to and including immediate dismissal irrelevant of position.
-'''2.4''' '''Staff members must not share the contents of staff channels in public or unrelated channels, or with unrelated individuals.''' Sharing screenshots or excerpts from staff channels without the consent of a head of staff, project manager, or all staff members involved may result in remediative action.
+== Staff Rank Structure ==
-=== 3. Responsibility & Accountability ===
+''This breaks down each staff rank, their duties, and permissions.  Higher ranking staff members, in their respective departments, gain all permissions of lower staff ranks.'''
-''As a member of staff, you hold greater power and authority than most members of the community. Correspondingly, you are expected to be accountable for your actions within the community - and, to an extent, without. When acting in the capacity of staff, be sure to exercise responsibility, employ critical thinking, and involve other members of your team including heads of staff where necessary.''
-'''3.1''' '''Staff members should not use direct messages for official staff actions or statements.''' This includes rule clarifications, player action notifications, or staff report follow-ups, and is to ensure that both staff and recipients can be held accountable for their statements and actions.
+=== Head Staff ===
-'''3.2 Staff members acting outside of their immediate responsibilities answer to and are held accountable by the relevant head of staff.''' For example, timeouts are overseen by the Head Discord Moderator, in-game kicks and bans are overseen by the Head Game Administrator, etc. Where possible, members are encouraged to cooperate on situations that may require the involvement of more than one branch of staff.
+'''Project Manager (PM)'''
+- Handles Internal Affairs, content, staff policies, and all things regarding Delta-V. Oversees all staff. Determines the continuity of the project. Determines the “Future Plans” of the project. ''Project manager’s have the ability to make “Owner-like” decisions via unanimous PM agreements (with other PM’s) and can bypass this in times of emergencies.''
-'''3.3''' '''Staff members are expected to avoid situations involving conflicts of interest, biases, or other interpersonal dynamics that make impartial staff action difficult.''' If you find yourself placed in this situation, please report it to other team members or your head of staff and recuse yourself from further involvement. Known conflicts of interest, biases, or other dynamics between staff and players should be noted on the player’s record where applicable.
+'''Head Moderator'''
+- Handles Internal Affairs, Investigates staff violations and staff reports. Oversees Moderation, the discord and it's rules.
-'''3.4''' '''Staff preparing to be absent from their duties for an extended period of time are expected to notify their team or their head of staff.''' Especially long periods away from staff may necessitate mandatory training; please check in with your head of staff when returning from a leave of absence.
+'''Head Game Administrator (HGA)'''
+- Oversight of Administration; including hiring, training, and promoting. Administrative rulings and Administrative policies
-'''3.5''' '''Staff are expected only to perform duties that they have been trained in, are confident in performing, and have been permitted or authorised to complete.''' Staff members acting outside of their scope may be subject to action from Staff Moderation and relevant heads of staff; if you are asked to perform a duty outside of your scope (due to inadequate training, lack of confidence/familiarity, or lack of authorisation) then you should refuse the request, explain why you are unable to fulfil the request, and have it delegated to another member of the staff team by a head of staff.
+'''Game director (GD)'''
+- Oversight of Direction; including hiring, training, and promoting. Direction roadmap approval, Oversight of Content.
-=== 4. Staff Management ===
+=== Senior Staff ===
-''This section applies to heads of staff, members of staff in charge of teams, and senior members of the staff team. Each has additional sets of responsibilities and are expected to use their extended authority and power appropriately.''
-'''4.1''' '''Heads of staff must manage their branches appropriately and be responsible for the actions of their staff.''' Heads of staff are expected to ensure that their staff, including themselves, follow the general policies and server rules, as well as policies specific to their branch.
+'''Senior Moderator'''
+- Assist Head Moderator in duties as assigned, Standard Moderation, Investigation of staff reports and misconduct.
-'''4.2 Senior members of staff are responsible for assisting their heads of staff in setting an example, training junior members of staff, and management.''' Greater experience, extended authority, and increased oversight necessitate higher standards; infractions against rules and policy are expected to reflect this accordingly.
+'''Senior Administrator'''
+- Assist HGA’s in duties as assigned, Standard Administration, Provide guidance.
-'''4.3 Heads of staff are expected to take responsibility for the performance of their team.''' In particular, they are expected to identify issues in the areas under their purview, implement plans and goals to address them, and evaluate their efficacy and success independently of Project Manager intervention - in essence, to actively run their team.
+'''Senior Curator'''
+- Assist GD’s in duties as assigned, Standard Direction, Provide guidance.
-'''4.4''' '''Heads of staff should handle remediative action within their own team.''' They hold the right to investigate possible infractions within their team and the ability to warn, demote, or remove staff from their branch - and are expected to do both where necessary.
+'''Trial Admin Mentor'''
+- Training with all Trial Administrators.
-'''4.5 Heads of staff intending to make a public announcement must first notify the Moderation team.''' Any public-facing Discord announcement requires a minimum 2 hour notice for Moderation, posted in #moderation-announcements, for the purpose of allowing moderators to prepare for community response; the exception being the Head Discord Moderator, who can monitor public channels themselves.
+=== Entry-Level and Trial Staff ===
+'''Moderator'''
+- Mhelps, Notes involving the discord, management of discord chats and “Policing them”.
+'''Administrator'''
+- Events, Ahelps, Notes & Bans, Rule Clarifications, Ban Appeals, Event Approval (via event policy). Can use Readmin Policy
+'''Curator'''
+- Events, Chelps, Event creation, Banning Raiders, Event Approval (via event policy).  Content approval (via vote).
+'''Trial Curator'''
+- Events, Chelps, Event creation, Banning Raiders, Content approval (via vote).
+'''Trial Administrator'''
+-  Ahelps, Notes & Bans,  Rule Clarifications, and Ban Appeals.
+== Event Policy ==
+''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.'''
+Any spawned CC character going to the station, must be armed by security on station. If your character is visiting the station, You are Not Allowed to spawn weapons for them.