Delta-V Wiki - User contributions [en]

Reviewing Content With Ethos

2026-08-21T23:16:53Z

DV vapetastic: /* Checks and Balances */

This goes over how to review content that has been submitted to the github with ethos. This lays out the policy for how to conduct such reviews, as well as the "Checks and Balances" of reviews.

== This Policy is currently under review, and is not active. ==

== Ethos Policy ==

1. '''CR's will review all content against the expectations of Ethos.''' Minimal effort reviews such as "I don't like this" or reviews that hold little regard for our current vision and outline will '''Not''' be taken into consideration.


2. '''CR's are expected to be well versed in the specific Ethos category when placing a review of the same category.''' For example, If a medical PR is made, You should be well versed in the Ethos of medical PRIOR to posting a review

3. '''Reviews can and should be made against ethos when it is in the best interest of the community, or content.''' If a reviewer is going against the ethos, then the review must be well structured, and list out the reasons why as well as the laying out a consideration for if Ethos should be changed, or if this is a "one-off case". If a reviewer makes a low effort review going against ethos, it will not be considered.

4. '''If a PR is voted by CR to bypass Ethos, a mandatory test period of 14 days is to take place''' Project Managers will be informed of the Bypass via a ping, and will work with Administration and Events to ensure that this content is adequately tested. A community feedback channel will be created, a community poll will be created at the 10 day mark, and will run for 3 days. On the 14th day, Project Management in Tandem with Content Review will examine the test period, as well as submit any proposals to change Ethos as needed.

5. '''Reviews placed at any time that are derogatory or insulting to the creator and/or content of the PR will not be considered.'''

6. '''Reviewers are expected to propose changes to Ethos regularly. Ethos should be ever-evolving with the community, and should not stagnate.''' If Reviewers fail to submit proposed changes to Ethos, Any Head of staff, Including Project Managers, can announce an audit of the Ethos. If no changes are proposed within 30 days of said audit, the responsibility will fall on Project Management to propose changes to Ethos in a way they see fit.

7. '''Proposed Changes to the Ethos (After the preliminary period of 90 days POST-Introduction to the community) shall require a 75% Majority vote of High Command to implement.''' During the 90 day period, Changes shall require a simple majority vote of High Command to establish changes. Errors and small wording changes / closing of loopholes will not require a vote, and simply 3 heads of staff to sign off. 

== Checks and Balances ==

1. '''If a PR that fits Ethos is denied by Content Review, any Head of Staff can bring the PR to review in High Command that is viewable by staff.''' A High Command vote requires a simple 50% majority. High Command can choose to request changes, Ignore CR's requested changes, Approve with no changes, or Deny. If a PR is denied by High Command, it is considered dead. If a reversal / decision is made by High Command that goes ''against'' CR's decision, there should be a detailed explanation as to why, as well as addressing any major concerns that were brought up during the CR process by reviewers.

2. '''If a PR is denied by Content Review, the author may form an appeal, in which case the PR must be voted on as listed above on C&B #1.''' Any denial formed by content review, must disclose the option to appeal.

3. '''Maintainers can deny a PR or feature based on, but not limited to, short- or long-term maintainability concerns, performance concerns, unfixable bugs with implementation, and server stability concerns, regardless of CR’s or High Command’s decision.''' Maintainers must provide analysis, metrics, incidents, bug reports, or any other documentation to support their decision. (aka there has to be a functional reason, they cannot deny because they don’t like it)

Reviewing Content With Ethos

2026-08-21T23:15:22Z

DV vapetastic: /* Checks and Balances */

This goes over how to review content that has been submitted to the github with ethos. This lays out the policy for how to conduct such reviews, as well as the "Checks and Balances" of reviews.

== This Policy is currently under review, and is not active. ==

== Ethos Policy ==

1. '''CR's will review all content against the expectations of Ethos.''' Minimal effort reviews such as "I don't like this" or reviews that hold little regard for our current vision and outline will '''Not''' be taken into consideration.


2. '''CR's are expected to be well versed in the specific Ethos category when placing a review of the same category.''' For example, If a medical PR is made, You should be well versed in the Ethos of medical PRIOR to posting a review

3. '''Reviews can and should be made against ethos when it is in the best interest of the community, or content.''' If a reviewer is going against the ethos, then the review must be well structured, and list out the reasons why as well as the laying out a consideration for if Ethos should be changed, or if this is a "one-off case". If a reviewer makes a low effort review going against ethos, it will not be considered.

4. '''If a PR is voted by CR to bypass Ethos, a mandatory test period of 14 days is to take place''' Project Managers will be informed of the Bypass via a ping, and will work with Administration and Events to ensure that this content is adequately tested. A community feedback channel will be created, a community poll will be created at the 10 day mark, and will run for 3 days. On the 14th day, Project Management in Tandem with Content Review will examine the test period, as well as submit any proposals to change Ethos as needed.

5. '''Reviews placed at any time that are derogatory or insulting to the creator and/or content of the PR will not be considered.'''

6. '''Reviewers are expected to propose changes to Ethos regularly. Ethos should be ever-evolving with the community, and should not stagnate.''' If Reviewers fail to submit proposed changes to Ethos, Any Head of staff, Including Project Managers, can announce an audit of the Ethos. If no changes are proposed within 30 days of said audit, the responsibility will fall on Project Management to propose changes to Ethos in a way they see fit.

7. '''Proposed Changes to the Ethos (After the preliminary period of 90 days POST-Introduction to the community) shall require a 75% Majority vote of High Command to implement.''' During the 90 day period, Changes shall require a simple majority vote of High Command to establish changes. Errors and small wording changes / closing of loopholes will not require a vote, and simply 3 heads of staff to sign off. 

== Checks and Balances ==

1. '''If a PR that fits Ethos is denied by Content Review, any Head of Staff can bring the PR to publicly review in High Command.''' A High Command vote requires a simple 50% majority. High Command can choose to request changes, Ignore CR's requested changes, Approve with no changes, or Deny. If a PR is denied by High Command, it is considered dead. If a reversal / decision is made by High Command that goes ''against'' CR's decision, there should be a detailed explanation as to why, as well as addressing any major concerns that were brought up during the CR process by reviewers.

2. '''If a PR is denied by Content Review, the author may form an appeal, in which case the PR must be voted on as listed above on C&B #1.''' Any denial formed by content review, must disclose the option to appeal.

3. '''Maintainers can deny a PR or feature based on, but not limited to, short- or long-term maintainability concerns, performance concerns, unfixable bugs with implementation, and server stability concerns, regardless of CR’s or High Command’s decision.''' Maintainers must provide analysis, metrics, incidents, bug reports, or any other documentation to support their decision. (aka there has to be a functional reason, they cannot deny because they don’t like it)

Reviewing Content With Ethos

2026-08-21T22:37:41Z

DV vapetastic: /* Ethos Policy */

This goes over how to review content that has been submitted to the github with ethos. This lays out the policy for how to conduct such reviews, as well as the "Checks and Balances" of reviews.

== This Policy is currently under review, and is not active. ==

== Ethos Policy ==

1. '''CR's will review all content against the expectations of Ethos.''' Minimal effort reviews such as "I don't like this" or reviews that hold little regard for our current vision and outline will '''Not''' be taken into consideration.


2. '''CR's are expected to be well versed in the specific Ethos category when placing a review of the same category.''' For example, If a medical PR is made, You should be well versed in the Ethos of medical PRIOR to posting a review

3. '''Reviews can and should be made against ethos when it is in the best interest of the community, or content.''' If a reviewer is going against the ethos, then the review must be well structured, and list out the reasons why as well as the laying out a consideration for if Ethos should be changed, or if this is a "one-off case". If a reviewer makes a low effort review going against ethos, it will not be considered.

4. '''If a PR is voted by CR to bypass Ethos, a mandatory test period of 14 days is to take place''' Project Managers will be informed of the Bypass via a ping, and will work with Administration and Events to ensure that this content is adequately tested. A community feedback channel will be created, a community poll will be created at the 10 day mark, and will run for 3 days. On the 14th day, Project Management in Tandem with Content Review will examine the test period, as well as submit any proposals to change Ethos as needed.

5. '''Reviews placed at any time that are derogatory or insulting to the creator and/or content of the PR will not be considered.'''

6. '''Reviewers are expected to propose changes to Ethos regularly. Ethos should be ever-evolving with the community, and should not stagnate.''' If Reviewers fail to submit proposed changes to Ethos, Any Head of staff, Including Project Managers, can announce an audit of the Ethos. If no changes are proposed within 30 days of said audit, the responsibility will fall on Project Management to propose changes to Ethos in a way they see fit.

7. '''Proposed Changes to the Ethos (After the preliminary period of 90 days POST-Introduction to the community) shall require a 75% Majority vote of High Command to implement.''' During the 90 day period, Changes shall require a simple majority vote of High Command to establish changes. Errors and small wording changes / closing of loopholes will not require a vote, and simply 3 heads of staff to sign off. 

== Checks and Balances ==

1. '''If a PR that fits Ethos is denied by Content Review, any Head of Staff can bring the PR to review in High Command''' A High Command vote requires a simple 50% majority. High Command can choose to request changes, Ignore CR's requested changes, Approve with no changes, or Deny. If a PR is denied by High Command, it is considered dead.

2. '''If a PR is denied by Content Review, the author may form an appeal, in which case the PR must be voted on as listed above on C&B #1.''' Any denial formed by content review, must disclose the option to appeal.

3. '''Maintainers can deny a PR or feature based on, but not limited to, short- or long-term maintainability concerns, performance concerns, unfixable bugs with implementation, and server stability concerns, regardless of CR’s or High Command’s decision.''' Maintainers must provide analysis, metrics, incidents, bug reports, or any other documentation to support their decision. (aka there has to be a functional reason, they cannot deny because they don’t like it)

Staff Policy

2026-08-20T00:48:05Z

DV vapetastic: /* High Command Staff */

'''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 [https://discord.com/channels/968983104247185448/968983104662409239 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.'''

=== High Command 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, and ensures that the Ethos is maintained. PM's are responsible for Massive content that will determine the function / goal of the server. They take precedence and are the determining factor when something crosses over multiple departments. ''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 (Head Mod)'''
- Handles Internal Affairs, Investigates staff violations and staff reports. Oversees Moderation, the discord and it's rules. Arbitrates any situation involving 2 or more heads of staff, and is responsible for being the non-biased party.

'''Head Game Administrator (HGA)'''
- Oversight of Administration; including hiring, training, and promoting. Administrative rulings and Administrative policies. Works with the Game Directors to ensure In-game standards are upheld

'''Game Director (GD)'''
- Oversight of Events; including hiring, training, and promoting Curators (Eventers). Works with the HGA's to ensure In-game standards are upheld

'''Content Director (CD) -''' Oversight of Content Review (CR); including hiring, training and promoting Content Reviewers. Ensures that Ethos is maintained.

'''Head Maintainer (HM)''' - Oversight of the codebase, including hiring and training maintainers, and moderation of the Github. Oversee's all contributors or those active on the github, and can grant or remove access to the github at anytime.

'''Head Mapper''' - Oversees all maps in the codebase, can assign and revoke Mapping Maintainer privileges from Map Maintainers, and oversees promotions of Senior Mappers. Determines all mapping standards.

'''Host''' - Manages the game server, handles any "Real-time" issues related to the game servers.

=== 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).

'''Trial Curator'''
- Events, Chelps, Event creation.

'''Trial Administrator'''
- Events, Ahelps, Notes & Bans, Rule Clarifications, and Ban Appeals. Event Approval (via event policy).

Staff Policy

2026-08-20T00:10:45Z

DV vapetastic: /* Entry-Level and Trial Staff */

'''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 [https://discord.com/channels/968983104247185448/968983104662409239 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.'''

=== High Command 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, and ensures that the Ethos is maintained. PM's are responsible for Massive content that will determine the function / goal of the server. They take precedence and are the determining factor when something crosses over multiple departments. ''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 (Head Mod)'''
- Handles Internal Affairs, Investigates staff violations and staff reports. Oversees Moderation, the discord and it's rules. Arbitrates any situation involving 2 or more heads of staff, and is responsible for being the non-biased party.

'''Head Game Administrator (HGA)'''
- Oversight of Administration; including hiring, training, and promoting. Administrative rulings and Administrative policies. Works with the Game Directors to ensure In-game standards are upheld

'''Game Director (GD)'''
- Oversight of Events; including hiring, training, and promoting Curators (Eventers). Works with the HGA's to ensure In-game standards are upheld

'''Content Director (CD) -''' Oversight of Content Review (CR); including hiring, training and promoting Content Reviewers. Oversees the Ethos, and ensures that Ethos is maintained.

'''Head Maintainer (HM)''' - Oversight of the codebase, including hiring and training maintainers, and moderation of the Github. Oversee's all contributors or those active on the github, and can grant or remove access to the github at anytime.

'''Head Mapper''' - Oversees all maps in the codebase, can assign and revoke Mapping Maintainer privileges from Map Maintainers, and oversees promotions of Senior Mappers. Determines all mapping standards.

'''Host''' - Manages the game server, handles any "Real-time" issues related to the game servers.

=== 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).

'''Trial Curator'''
- Events, Chelps, Event creation.

'''Trial Administrator'''
- Events, Ahelps, Notes & Bans, Rule Clarifications, and Ban Appeals. Event Approval (via event policy).

Staff Policy

2026-08-20T00:09:20Z

DV vapetastic: /* High Command Staff */

'''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 [https://discord.com/channels/968983104247185448/968983104662409239 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.'''

=== High Command 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, and ensures that the Ethos is maintained. PM's are responsible for Massive content that will determine the function / goal of the server. They take precedence and are the determining factor when something crosses over multiple departments. ''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 (Head Mod)'''
- Handles Internal Affairs, Investigates staff violations and staff reports. Oversees Moderation, the discord and it's rules. Arbitrates any situation involving 2 or more heads of staff, and is responsible for being the non-biased party.

'''Head Game Administrator (HGA)'''
- Oversight of Administration; including hiring, training, and promoting. Administrative rulings and Administrative policies. Works with the Game Directors to ensure In-game standards are upheld

'''Game Director (GD)'''
- Oversight of Events; including hiring, training, and promoting Curators (Eventers). Works with the HGA's to ensure In-game standards are upheld

'''Content Director (CD) -''' Oversight of Content Review (CR); including hiring, training and promoting Content Reviewers. Oversees the Ethos, and ensures that Ethos is maintained.

'''Head Maintainer (HM)''' - Oversight of the codebase, including hiring and training maintainers, and moderation of the Github. Oversee's all contributors or those active on the github, and can grant or remove access to the github at anytime.

'''Head Mapper''' - Oversees all maps in the codebase, can assign and revoke Mapping Maintainer privileges from Map Maintainers, and oversees promotions of Senior Mappers. Determines all mapping standards.

'''Host''' - Manages the game server, handles any "Real-time" issues related to the game servers.

=== 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.

Staff Policy

2026-08-20T00:08:00Z

DV vapetastic: /* Head Staff corrections and changes*/

'''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 [https://discord.com/channels/968983104247185448/968983104662409239 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.'''

=== High Command 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, and ensures that the Ethos is maintained. PM's are responsible for Massive content that will determine the function / goal of the server. They take precedence and are the determining factor when something crosses over multiple departments. ''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 (Head Mod)'''
- 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. Works with the Game Directors to ensure In-game standards are upheld

'''Game Director (GD)'''
- Oversight of Events; including hiring, training, and promoting Curators (Eventers). Works with the HGA's to ensure In-game standards are upheld

'''Content Director (CD) -''' Oversight of Content Review (CR); including hiring, training and promoting Content Reviewers. Oversees the Ethos, and ensures that Ethos is maintained.

'''Head Maintainer (HM)''' - Oversight of the codebase, including hiring and training maintainers, and moderation of the Github. Oversee's all contributors or those active on the github, and can grant or remove access to the github at anytime.

'''Head Mapper''' - Oversees all maps in the codebase, can assign and revoke Mapping Maintainer privileges from Map Maintainers, and oversees promotions of Senior Mappers. Determines all mapping standards.

'''Host''' - Manages the game server, handles any "Real-time" issues related to the game servers.

=== 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.

Staff Policy

2026-08-19T23:40:31Z

DV vapetastic: Removed event policy from staff policy, outdated redundancy

'''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 [https://discord.com/channels/968983104247185448/968983104662409239 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.

Reviewing Content With Ethos

2026-08-19T23:36:35Z

DV vapetastic:

This goes over how to review content that has been submitted to the github with ethos. This lays out the policy for how to conduct such reviews, as well as the "Checks and Balances" of reviews.

== This Policy is currently under review, and is not active. ==

== Ethos Policy ==

1. '''CR's will review all content against the expectations of Ethos.''' Minimal effort reviews such as "I don't like this" or reviews that hold little regard for our current vision and outline will '''Not''' be taken into consideration.


2. '''CR's are expected to be well versed in the specific Ethos category when placing a review of the same category.''' For example, If a medical PR is made, You should be well versed in the Ethos of medical PRIOR to posting a review

3. '''Reviews can and should be made against ethos when it is in the best interest of the community, or content.''' If a reviewer is going against the ethos, then the review must be well structured, and list out the reasons why as well as the laying out a consideration for if Ethos should be changed, or if this is a "one-off case". If a reviewer makes a low effort review going against ethos, it will not be considered.

4. '''If a PR is voted by CR to bypass Ethos, a mandatory test period of 14 days is to take place''' Project Managers will be informed of the Bypass via a ping, and will work with Administration and Events to ensure that this content is adequately tested. A community feedback channel will be created, a community poll will be created at the 10 day mark, and will run for 3 days. On the 14th day, Project Management in Tandem with Content Review will examine the test period, as well as submit any proposals to change Ethos as needed.

5. '''Reviews placed at any time that are derogatory or insulting to the creator of the PR will not be considered.'''

6. '''Reviewers are expected to propose changes to Ethos regularly. Ethos should be ever-evolving with the community, and should not stagnate.''' If Reviewers fail to submit proposed changes to Ethos, Any Head of staff, Including Project Managers, can announce an audit of the Ethos. If no changes are proposed within 30 days of said audit, the responsibility will fall on Project Management to propose changes to Ethos in a way they see fit.

7. '''Proposed Changes to the Ethos (After the preliminary period of 90 days POST-Introduction to the community) shall require a 75% Majority vote of High Command to implement.''' During the 90 day period, Changes shall require a simple majority vote of High Command to establish changes. Errors and small wording changes / closing of loopholes will not require a vote, and simply 3 heads of staff to sign off. 

== Checks and Balances ==

1. '''If a PR that fits Ethos is denied by Content Review, any Head of Staff can bring the PR to review in High Command''' A High Command vote requires a simple 50% majority. High Command can choose to request changes, Ignore CR's requested changes, Approve with no changes, or Deny. If a PR is denied by High Command, it is considered dead.

2. '''If a PR is denied by Content Review, the author may form an appeal, in which case the PR must be voted on as listed above on C&B #1.''' Any denial formed by content review, must disclose the option to appeal.

3. '''Maintainers can deny a PR or feature based on, but not limited to, short- or long-term maintainability concerns, performance concerns, unfixable bugs with implementation, and server stability concerns, regardless of CR’s or High Command’s decision.''' Maintainers must provide analysis, metrics, incidents, bug reports, or any other documentation to support their decision. (aka there has to be a functional reason, they cannot deny because they don’t like it)