Jump to content

Staff Expectations: Difference between revisions

From Misfits Nuclear Wasteland
m Protected "Staff Expectations" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))
No edit summary
Line 1: Line 1:
__NOTOC__
== <span style="color:#33ff33;">STAFF MANAGEMENT EXPECTATIONS</span> ==
<div style="background:#0a0a0a; color:#33ff33; font-family:'Courier New',monospace; padding:30px; border:2px solid #33ff33; max-width:900px; margin:0 auto;">
 
<div style="text-align:center; border:2px double #33ff33; padding:15px; margin-bottom:25px;">
<span style="font-size:1.4em; letter-spacing:3px;">╔══════════════════════════════════════╗</span>
<br/><span style="font-size:1.6em; font-weight:bold; letter-spacing:2px;">VAULT-TEC STAFF TERMINAL</span>
<br/><span style="font-size:1.1em;">ACCESS LEVEL: STAFF</span>
<br/><span style="font-size:1.4em; letter-spacing:3px;">╚══════════════════════════════════════╝</span>
</div>
 
<div style="color:#22cc22; margin-bottom:20px; line-height:1.8;">
<span style="color:#55ff55;">&gt; Establishing secure staff uplink...</span><br/>
<span style="color:#55ff55;">&gt; Loading administrative expectations...</span><br/>
<span style="color:#55ff55;">&gt; Verifying chain of command...</span><br/>
<span style="color:#55ff55;">&gt; Synchronizing leadership directives...</span><br/>
<br/>
<span style="color:#00ff00; font-weight:bold;">STATUS: STAFF DIRECTIVES LOADED</span>
</div>
 
<div style="border-top:2px solid #33ff33; border-bottom:2px solid #33ff33; padding:20px 0; margin:20px 0; text-align:center;">
<span style="font-size:1.1em; color:#aaffaa;">STAFF EXPECTATIONS FOR</span><br/>
<span style="font-size:1.8em; font-weight:bold; color:#00ff00; letter-spacing:2px;">MISFITS: NUCLEAR WASTELAND</span><br/>
<br/>
<span style="color:#aaffaa;">A Fallout themed Medium Roleplay environment<br/>where staff protect roleplay, fairness, and community trust.</span><br/>
<br/>
<span style="color:#88cc88;">Staff authority depends on:</span><br/>
<span style="color:#55ff55;">• Calm judgment</span><br/>
<span style="color:#55ff55;">• Consistent enforcement</span><br/>
<span style="color:#55ff55;">• Respect for players</span><br/>
<span style="color:#55ff55;">• Alignment with server leadership</span><br/>
<br/>
<span style="color:#668866;">Administrative power exists to serve the community.<br/>It is not personal status, leverage, or ego.</span>
</div>
 
<div style="text-align:center; margin:20px 0; color:#88cc88;">
REVIEW THE STAFF DIRECTIVES BELOW<br/>
BEFORE EXERCISING ADMINISTRATIVE AUTHORITY.
</div>
 
<div style="text-align:center; margin-bottom:15px; color:#446644; font-size:0.9em;">
VAULT-TEC NOTICE: A BETTER COMMUNITY THROUGH ORDER.
</div>
 
== <span style="color:#33ff33;">QUICK STAFF DIRECTIVES</span> ==
 
<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0;">
 
<div style="text-align:center; border:1px solid #33ff33; padding:10px; margin-bottom:20px;">
<span style="font-size:1.2em; font-weight:bold; letter-spacing:2px;">VAULT-TEC STAFF CONDUCT TERMINAL</span><br/>
<span style="color:#88cc88; font-size:0.9em;">QUICK DIRECTIVES</span>
</div>
 
<div style="line-height:2.0;">
<span style="color:#00ff00; font-weight:bold;">1 — BE CALM</span><br/>
<span style="color:#aaffaa; padding-left:20px;">Never get snappy, aggressive, sarcastic, or hostile toward players.</span><br/>
<br/>
<span style="color:#00ff00; font-weight:bold;">2 — BE FAIR</span><br/>
<span style="color:#aaffaa; padding-left:20px;">Enforce rules based on facts, context, severity, player history, and server intent.</span><br/>
<br/>
<span style="color:#00ff00; font-weight:bold;">3 — PROTECT ROLEPLAY</span><br/>
<span style="color:#aaffaa; padding-left:20px;">Staff intervention should protect the round, not replace player-driven story.</span><br/>
<br/>
<span style="color:#00ff00; font-weight:bold;">4 — FOLLOW THE CHAIN OF COMMAND</span><br/>
<span style="color:#aaffaa; padding-left:20px;">Ask upward when unsure and do not skip leadership just because you want a different answer.</span><br/>
<br/>
<span style="color:#00ff00; font-weight:bold;">5 — DOCUMENT SERIOUS ACTIONS</span><br/>
<span style="color:#aaffaa; padding-left:20px;">Major punishments, controversial calls, and repeated behavior problems must be documented.</span><br/>
<br/>
<span style="color:#00ff00; font-weight:bold;">6 — DO NOT ABUSE AUTHORITY</span><br/>
<span style="color:#aaffaa; padding-left:20px;">Do not use staff power to win arguments, protect friends, target enemies, or influence roleplay.</span><br/>
<br/>
<span style="color:#00ff00; font-weight:bold;">7 — REPRESENT THE SERVER</span><br/>
<span style="color:#aaffaa; padding-left:20px;">Every staff interaction affects player trust in Misfits: Nuclear Wasteland.</span>
</div>
 
<div style="text-align:center; margin-top:20px; color:#668866; font-size:0.9em;">
&gt; FULL STAFF DIRECTIVES AVAILABLE BELOW<br/>
&gt; SCROLL TO CONTINUE
</div>
 
</div>
 
== <span style="color:#33ff33;">ALL STAFF EXPECTATIONS</span> ==
 
<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0;">
 
<div style="text-align:center; border:1px solid #33ff33; padding:10px; margin-bottom:20px;">
<span style="font-size:1.2em; font-weight:bold; letter-spacing:2px;">GENERAL STAFF DIRECTIVE</span><br/>
<span style="color:#88cc88; font-size:0.9em;">APPLIES TO ALL STAFF MEMBERS</span>
</div>
 
<div style="color:#aaffaa; line-height:1.8;">
All staff members represent Misfits: Nuclear Wasteland. You are expected to be kind, calm, patient, and professional with players at all times, even when players are rude, wrong, annoying, or difficult.<br/>
<br/>
This server is a Medium Roleplay Fallout environment. Our job is not to control every story or rescue players from every consequence. Our job is to protect the health of the server, enforce the rules fairly, and make sure players are creating meaningful roleplay instead of ruining the round for others.
</div>
 
=== <span style="color:#00ff00;">Required Conduct</span> ===
 
<div style="padding:10px 0; line-height:1.8;">
* Treat players with respect in tickets, Discord, admin messages, and public channels.
* Never get snappy, aggressive, sarcastic, or hostile toward players.
* Enforce rules based on facts, context, severity, and player history.
* Avoid using staff power to win arguments, protect friends, punish enemies, or influence roleplay.
* Keep staff discussions private and do not argue staff decisions publicly.
* Document major punishments, controversial calls, and repeated behavior problems.
* Ask up the chain of command when you are unsure.
* Remember that staff intervention should protect the round, not replace player-driven story.
* Follow the intent of the CEO and the published rules.
* Report bugs, exploits, staff misconduct, and major community issues immediately.
</div>
 
<div style="color:#668866; line-height:1.8;">
Staff are not above the rules. Staff members who abuse authority, mistreat players, ignore chain of command, or damage community trust may be removed from staff.
</div>
 
</div>
 
== <span style="color:#33ff33;">LEADERSHIP EXPECTATIONS</span> ==


<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0;">
<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0;">


=== <span style="color:#00ff00;">CEO Expectations</span> ===
=== <span style="color:#00ff00;">Staff Manager Expectations</span> ===


<div style="padding:10px 0; line-height:1.8;">
<div style="padding:10px 0; line-height:1.8;">
You are the final authority and final responsibility holder for Misfits: Nuclear Wasteland.<br/>
You are responsible for the overall organization, standards, expectations, and accountability of the administrative staff team.<br/>
<br/>
<br/>
You are responsible for everything the server does or does not do. This includes the rules, culture, staff structure, technical direction, enforcement philosophy, player trust, and long-term vision of the project.
Your job is not to personally manage every Moderator or Admin. Your job is to establish what is expected of the staff force, ensure the Lead Admins are properly managing their teams, and make final personnel decisions regarding who is or is not staff.


'''Responsibilities:'''
'''Responsibilities:'''
* Set the overall vision and intent of the server.
* Establish expectations, standards, and procedures for all administrative staff.
* Make final decisions on rule interpretation, staff structure, major punishments, and server direction.
* Determine the behavior and performance expected from Moderators, Admins, and Lead Admins.
* Approve or deny major rule changes.
* Maintain the overall structure of the administrative staff team.
* Approve or deny major gameplay, technical, mapping, and faction-direction changes.
* Assign staff members to Lead Admin teams.
* Hold senior staff accountable for their departments.
* Approve or deny staff recruitment.
* Protect the long-term health of the community over short-term popularity.
* Make final decisions regarding promotions, demotions, transfers, and staff removals.
* Resolve disputes between senior leadership when needed.
* Hold Lead Admins accountable for the performance, activity, and conduct of their teams.
* Make sure the staff team understands the difference between enforcing rules and controlling roleplay.
* Resolve disagreements between Lead Admins when necessary.
* Ensure the server remains consistent with the intended Medium Roleplay Fallout experience.
* Ensure enforcement standards remain consistent between all three teams.
* Step in when staff decisions risk damaging the server, community trust, or project direction.
* Review serious allegations of staff misconduct or abuse of authority.
* Ensure Lead Admins are properly training and developing their staff.
* Identify leadership gaps, inactivity, burnout, poor performance, or staffing shortages.
* Intervene when a team is dysfunctional, improperly managed, or operating outside staff expectations.
* Ensure the administrative staff team follows the direction established by the Server Manager, COO, and CEO.


<span style="color:#668866;">You are not expected to handle every ticket, every bug, or every staff issue personally. You are expected to make sure the correct people are empowered, corrected, or removed when necessary.</span><br/>
<span style="color:#668866;">You should normally manage the staff force through the Lead Admins instead of bypassing them during routine operations.</span><br/>
<br/>
<br/>
<span style="color:#ffaa00; font-weight:bold;">Final rule interpretation rests with you.</span>
<span style="color:#ffaa00; font-weight:bold;">The Staff Manager has final authority over staff membership, promotions, demotions, removals, and team assignments.</span>
</div>
</div>


=== <span style="color:#00ff00;">COO Expectations</span> ===
<div style="padding:10px 0; line-height:1.8;">
You are responsible for day-to-day operations and making sure the CEO's intent is carried out consistently.<br/>
<br/>
Your job is to keep the server functioning smoothly across staff, community, development, and operations. You are the person who makes sure things actually get done.


'''Responsibilities:'''
=== <span style="color:#00ff00;">Lead Admin Expectations</span> ===
* Manage daily operations of the server.
* Translate CEO intent into practical action for the staff team.
* Coordinate between Security Operations, Engineering, Architecture, and Administration.
* Make sure staff leads are communicating and not working against each other.
* Track unresolved issues, stalled decisions, staff concerns, and operational problems.
* Ensure important issues reach the CEO without overwhelming them with minor details.
* Help resolve staff disagreements before they become public problems.
* Make sure announcements, policy changes, and operational decisions are clear.
* Maintain consistency between the rules, staff enforcement, map direction, and gameplay direction.
* Watch for burnout, inactivity, poor communication, and leadership gaps.
 
<span style="color:#668866;">You do not replace the CEO's authority. You execute the CEO's intent and keep the machine moving.</span><br/>
<br/>
<span style="color:#ffaa00; font-weight:bold;">When in doubt, ask:</span> <span style="color:#aaffaa;">Does this support the CEO's direction and improve the health of the server?</span>
</div>
 
=== <span style="color:#00ff00;">Security Operations Chief Expectations</span> ===


<div style="padding:10px 0; line-height:1.8;">
<div style="padding:10px 0; line-height:1.8;">
You are responsible for building, training, maintaining, and correcting the staff enforcement team.<br/>
You are the leader of an assigned administrative team.<br/>
<br/>
<br/>
Your focus is the people side of server enforcement. You make sure staff members understand their roles, know the rules, enforce them properly, and stay within their authority.
You have full operational authority over the Admins and Moderators assigned to your team and are responsible for their performance, discipline, development, activity, and effectiveness.


'''Responsibilities:'''
'''Responsibilities:'''
* Recruit qualified staff members.
* Direct the day-to-day operations of your assigned team.
* Review staff applicants for maturity, rule knowledge, temperament, and trustworthiness.
* Give instructions and assignments to Admins and Moderators on your team.
* Train new Compliance Officers and guide their development.
* Establish operational priorities during active rounds.
* Maintain staff standards across all enforcement ranks.
* Ensure tickets, reports, investigations, and moderation issues are being handled.
* Make sure staff understand what they are allowed and not allowed to do.
* Ensure your team maintains adequate staff coverage.
* Identify staff who need coaching, correction, demotion, or removal.
* Mentor and develop the Admins assigned to your team.
* Work with Senior Security Administrators to keep rule interpretation consistent.
* Ensure Admins are properly supervising and developing Moderators.
* Make sure punishment standards are fair and not based on emotion.
* Correct improper enforcement or poor staff behavior.
* Ensure staff are empathetic toward players while still enforcing the rules.
* Review significant or controversial actions taken by members of your team.
* Monitor staff activity, ticket handling, and professionalism.
* Ensure your team follows server rules, staff procedures, and Staff Manager expectations.
* Address reports of staff misconduct.
* Recommend recruitment, promotion, demotion, transfer, or removal to the Staff Manager.
* Escalate serious staff problems to the COO or CEO.
* Monitor inactivity and poor performance within your team.
* Resolve disagreements between members of your team.
* Report serious staff concerns to the Staff Manager.
* Coordinate with the other Lead Admins during major incidents or server-wide problems.


<span style="color:#668866;">You are not just recruiting bodies. You are responsible for the quality and trustworthiness of the staff force.</span><br/>
<span style="color:#aaffaa;">Lead Admins are expected to run their teams without requiring the Staff Manager to micromanage routine operations.</span>
<br/>
<span style="color:#aaffaa;">A strong staff team should be calm, consistent, fair, and aligned with the CEO's intent.</span>
</div>
</div>


</div>
== <span style="color:#33ff33;">TECHNICAL AND MAP EXPECTATIONS</span> ==
<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0;">
=== <span style="color:#00ff00;">Chief Engineer Expectations</span> ===
<div style="padding:10px 0; line-height:1.8;">
You are responsible for the gameplay and technical direction of the server.<br/>
<br/>
Your job is to make sure the server's code, systems, balance changes, features, and bug fixes support the intended gameplay experience. You are the final technical gatekeeper before changes enter the repo, unless overruled by the CEO.
'''Responsibilities:'''
* Approve, deny, or request changes to pull requests.
* Set technical standards for engineers.
* Decide whether proposed systems fit the server's gameplay direction.
* Prioritize bug fixes, stability issues, exploits, and performance problems.
* Make sure engineers are working on sanctioned and useful features.
* Prevent unnecessary complexity, broken systems, and unapproved gameplay changes.
* Coordinate with the Chief Architect on map-related technical needs.
* Coordinate with Security Operations when bugs or exploits affect rule enforcement.
* Review suggestions for technical feasibility and gameplay impact.
* Maintain repo health and avoid careless merges.
* Make sure major systems are tested before being pushed live.
* Ensure bugs are tracked, assigned, and fixed instead of ignored.


<span style="color:#668866;">You are expected to protect both the player experience and the codebase.</span><br/>
=== <span style="color:#00ff00;">Lead Admin Cross-Team Authority</span> ===
<br/>
<span style="color:#aaffaa;">Engineers should not push major systems, balance changes, or gameplay-altering features without your approval.</span>
</div>
 
=== <span style="color:#00ff00;">Chief Architect Expectations</span> ===


<div style="padding:10px 0; line-height:1.8;">
<div style="padding:10px 0; line-height:1.8;">
You are responsible for the direction, balance, and structure of the map or maps used by the server.<br/>
Lead Admins are senior operational leaders of the administrative staff force.<br/>
<br/>
<br/>
Your job is to make sure the physical world supports the intended Fallout roleplay experience, faction conflict, travel, exploration, and balance.
Because of this, a Lead Admin may give reasonable operational instructions to an Admin or Moderator belonging to another Lead Admin's team when necessary for server operations.


'''Responsibilities:'''
'''Examples Include:'''
* Set the overall direction of the map.
* Directing staff to respond to a major incident.
* Decide what maps are used and whether multiple maps are appropriate.
* Assigning available staff to tickets or investigations.
* Define faction territories, neutral zones, contested spaces, and important landmarks.
* Coordinating staff during high-population rounds.
* Maintain map balance between factions.
* Ordering a lower-ranking staff member to stop improper staff behavior.
* Make sure faction bases are defensible but not impossible to interact with.
* Reassigning immediate operational priorities during an emergency.
* Make sure the map encourages roleplay, travel, conflict, trade, and story.
* Coordinating coverage when another team has insufficient staff online.
* Avoid creating areas that give one group unfair mechanical or strategic advantage.
* Coordinate with the Chief Engineer on map-related systems, atmospherics, spawns, access, and technical issues.
* Review and approve map changes before they are merged or used.
* Consider how map layout affects raids, wars, escalation, and player interaction.
* Make sure map changes do not undermine server rules or intended gameplay.
* Keep map design consistent with the Fallout setting and the server's tone.


<span style="color:#668866;">You are not just placing rooms. You are shaping where the server's stories happen.</span><br/>
However, giving operational instructions does '''not''' give a Lead Admin personnel control over another Lead Admin's team.
<br/>
<span style="color:#ffaa00; font-weight:bold;">Every major map decision should answer:</span> <span style="color:#aaffaa;">Does this create better roleplay, better conflict, and better balance?</span>
</div>


=== <span style="color:#00ff00;">Engineer Expectations</span> ===
'''A Lead Admin may not independently:'''
* Add someone to another Lead Admin's team.
* Remove someone from another Lead Admin's team.
* Permanently transfer staff between teams.
* Promote another team's staff member.
* Demote another team's staff member.
* Remove another team's member from staff.
* Override another Lead Admin's long-term personnel decisions.


<div style="padding:10px 0; line-height:1.8;">
If a Lead Admin has a serious issue with another team's staff member, the issue should be documented and brought to that staff member's Lead Admin or the Staff Manager.
You are responsible for writing and maintaining server systems approved by the Chief Engineer.<br/>
<br/>
Your job is to build features, fix bugs, improve systems, and support the technical side of the server without pushing unauthorized gameplay direction.


'''Responsibilities:'''
<span style="color:#ffaa00; font-weight:bold;">Operational Authority:</span> <span style="color:#aaffaa;">Lead Admins may direct lower-ranking staff from any team when reasonably necessary.</span><br/>
* Work on systems sanctioned by the Chief Engineer.
* Write clean, maintainable code.
* Test your changes before submitting them.
* Submit pull requests for review instead of bypassing approval.
* Explain what your changes do and why they are needed.
* Fix bugs assigned to you or discovered in your systems.
* Avoid introducing features that conflict with server rules, map balance, or gameplay direction.
* Coordinate with the Chief Engineer before making large technical or balance changes.
* Coordinate with the Chief Architect when changes affect the map.
* Treat exploits, crashes, and severe bugs as high priority.
* Do not use developer access to gain in-game advantage.
* Do not make secret changes, personal toys, or joke systems without approval.
* Respect code review and accept feedback professionally.
 
<span style="color:#668866;">Your work directly affects the player experience. A broken system, careless merge, or unapproved feature can damage an entire round.</span><br/>
<br/>
<br/>
<span style="color:#aaffaa;">You are expected to build for the server's vision, not just for what is fun to code.</span>
<span style="color:#ffaa00; font-weight:bold;">Personnel Authority:</span> <span style="color:#aaffaa;">Lead Admins only directly control the personnel assigned to their own team.</span>
</div>
 
</div>
</div>


== <span style="color:#33ff33;">SECURITY AND COMPLIANCE EXPECTATIONS</span> ==
<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0;">
=== <span style="color:#00ff00;">Senior Security Administrator Expectations</span> ===
<div style="padding:10px 0; line-height:1.8;">
You are the highest rule-enforcement staff rank below leadership and the primary interpreter of rules for the Security Administrator team.<br/>
<br/>
This rank is reserved for people who understand the rules deeply and interpret them as close as possible to the CEO's intent.


'''Responsibilities:'''
=== <span style="color:#00ff00;">Admin Expectations</span> ===
* Serve as the first point of escalation for Security Administrators.
* Interpret unclear rule situations in line with CEO intent.
* Help create, clarify, or modify rules, subject to CEO approval.
* Ensure punishments are consistent across the staff team.
* Review major bans, controversial punishments, and complicated tickets.
* Mentor Security Administrators and help them improve judgment.
* Correct bad enforcement habits before they spread.
* Help identify gaps, contradictions, or unclear wording in the rules.
* Make sure staff understand context, severity, player history, and intent before punishing.
* Step in when a situation is too complex for lower staff.
* Keep enforcement focused on protecting the round and community, not winning arguments.
* Escalate major policy questions to the CEO.
 
<span style="color:#668866;">You are expected to be calm, precise, and consistent.</span><br/>
<br/>
<span style="color:#aaffaa;">When you make a ruling, staff should be able to understand not just what the decision was, but why it fits the rules and the CEO's intent.</span>
</div>
 
=== <span style="color:#00ff00;">Security Administrator Expectations</span> ===


<div style="padding:10px 0; line-height:1.8;">
<div style="padding:10px 0; line-height:1.8;">
You are a trusted server administrator responsible for enforcing the rules with minimal supervision.<br/>
You are a supervisor and assistant leader within your assigned Lead Admin team.<br/>
<br/>
<br/>
You are expected to know the rules well, understand the server's enforcement philosophy, and make fair punishment decisions based on facts, context, severity, and history.
Your primary responsibility is supervising Moderators, helping them make good decisions, handling situations that require additional experience or authority, and assisting your Lead Admin with the operation of the team.


'''Responsibilities:'''
'''Responsibilities:'''
* Handle admin tickets professionally and calmly.
* Supervise Moderators assigned to your team.
* Investigate rule violations before acting.
* Provide guidance when Moderators are uncertain.
* Issue warnings, notes, kicks, bans, or other punishments when appropriate.
* Assist Moderators with complicated tickets, investigations, and player situations.
* Understand the rules well enough to require little help in normal situations.
* Take over situations that exceed Moderator authority or experience.
* Escalate unclear or high-impact cases to a Senior Security Administrator.
* Review Moderator decisions when necessary.
* Support and mentor Compliance Officers.
* Ensure Moderators remain professional and follow staff expectations.
* Answer Compliance Officer questions and help them learn proper enforcement.
* Help train and develop newer Moderators.
* Avoid emotional punishments or snap decisions.
* Assign Moderators to tickets or operational priorities when directed or necessary.
* Keep player interactions respectful, even when issuing discipline.
* Handle enforcement matters requiring greater authority or experience.
* Explain decisions clearly without arguing endlessly.
* Document significant disciplinary actions and unusual incidents.
* Document punishments and important context.
* Identify Moderators who require additional training, correction, or supervision.
* Watch for griefing, metagaming, exploit abuse, escalation violations, harassment, and behavior that harms the round.
* Report serious staff performance problems to your Lead Admin.
* Protect the player experience without over-adminning roleplay.
* Carry out instructions issued by your Lead Admin.
* Help maintain team operations when your Lead Admin is unavailable.
* Coordinate with other Admins during busy rounds and major incidents.


<span style="color:#668866;">You are expected to be a model of good judgment.</span><br/>
<span style="color:#668866;">Admins are supervisors and assistant leaders. They are not independent team commanders.</span><br/>
<br/>
<br/>
<span style="color:#aaffaa;">Compliance Officers should be able to come to you for help, and players should be able to trust that your decisions are fair.</span>
<span style="color:#aaffaa;">Your job is to supervise the frontline staff force, provide escalation support, and make sure Moderators have the leadership they need to succeed.</span>
</div>
</div>


=== <span style="color:#00ff00;">Senior Compliance Officer Expectations</span> ===


<div style="padding:10px 0; line-height:1.8;">
=== <span style="color:#00ff00;">Moderator Expectations</span> ===
You are an experienced frontline staff member who understands how to enforce rules while keeping the server enjoyable.<br/>
<br/>
Your role is to handle routine enforcement, support Compliance Officers, and help maintain public order without overstepping into major administrative decisions unless authorized.
 
'''Responsibilities:'''
* Handle common rule issues calmly and professionally.
* Help players understand expectations before problems become punishments.
* De-escalate conflict when possible.
* Identify when a situation needs Security Administrator involvement.
* Support and guide Compliance Officers during tickets or player issues.
* Help maintain respectful behavior in-game and in community spaces.
* Watch for griefing, toxicity, metagaming, poor escalation, and immersion-breaking behavior.
* Gather facts and context before recommending punishment.
* Avoid jumping to conclusions based on one side of a story.
* Keep the player experience enjoyable while still protecting the rules.
* Ask Security Administrators for help when unsure.
* Set an example for lower staff in tone, patience, and fairness.
 
<span style="color:#668866;">You are trusted to handle more than a basic Compliance Officer, but you are still expected to escalate serious punishments, complicated disputes, or unclear rule interpretations.</span><br/>
<br/>
<span style="color:#aaffaa;">Your goal is to protect the community without making players feel like staff are hunting for mistakes.</span>
</div>
 
=== <span style="color:#00ff00;">Compliance Officer Expectations</span> ===


<div style="padding:10px 0; line-height:1.8;">
<div style="padding:10px 0; line-height:1.8;">
You are the frontline defense of the server.<br/>
You are the primary frontline force of the administrative staff team.<br/>
<br/>
<br/>
Your job is to help maintain public order, assist players, identify rule problems, and keep the community healthy. You are expected to be empathetic, calm, and approachable.
Moderators should handle the majority of routine player issues, tickets, reports, investigations, questions, and normal rule enforcement.


'''Responsibilities:'''
'''Responsibilities:'''
* Help players with questions and basic issues.
* Respond to routine admin tickets.
* Respond to minor problems before they become major incidents.
* Investigate player reports.
* Maintain respectful behavior in public spaces.
* Handle ordinary rule violations within your authority.
* Calm down heated situations when possible.
* Help players with server and rule questions.
* Watch for toxicity, griefing, metagaming, rule confusion, and disruptive behavior.
* Monitor the round for disruptive or rule-breaking behavior.
* Gather information and pass serious issues to Senior Compliance Officers or Security Administrators.
* De-escalate player conflicts when possible.
* Avoid making major punishment decisions unless authorized.
* Gather facts and context before taking administrative action.
* Treat every player with patience, even when they are frustrating.
* Issue routine enforcement actions permitted by your authority.
* Do not argue with players publicly.
* Document incidents and punishments when required.
* Do not use your role to intimidate, threaten, or flex authority.
* Escalate serious, complicated, or unclear situations to an Admin.
* Learn the rules and ask questions when unsure.
* Follow reasonable instructions from Admins and Lead Admins.
* Support roleplay by guiding players toward better behavior instead of immediately escalating everything.
* Maintain calm and professional communication with players.
* Report repeated problem players or serious incidents up the chain.
* Avoid unnecessary interference with legitimate roleplay.
* Report suspected staff misconduct through the chain of command.
* Accept correction and guidance from Admins and Lead Admins.
* Continue developing your knowledge of the rules and enforcement philosophy.
* Maintain an active staff presence during rounds.


<span style="color:#668866;">You are not expected to know everything. You are expected to be honest, calm, helpful, and willing to learn.</span><br/>
<span style="color:#668866;">Moderators are expected to perform the majority of normal administrative work.</span><br/>
<br/>
<br/>
<span style="color:#aaffaa;">A good Compliance Officer makes the server feel safer and more welcoming without making it feel over-policed.</span>
<span style="color:#aaffaa;">Admins and Lead Admins exist to supervise, support, coordinate, and handle escalation — not to replace the Moderator force.</span>
</div>
</div>


=== <span style="color:#00ff00;">Junior Compliance Officer Expectations</span> ===
<div style="padding:10px 0; line-height:1.8;">
You are in training.<br/>
<br/>
Your job is to learn the rules, observe how staff handle situations, assist where allowed, and build the judgment needed to become a full Compliance Officer.
'''Responsibilities:'''
* Learn the server rules and enforcement philosophy.
* Observe tickets and staff decisions when permitted.
* Ask questions when you do not understand a rule or decision.
* Help players with basic questions when you know the answer.
* Avoid making punishments or major enforcement calls unless directly authorized.
* Report issues to Compliance Officers, Senior Compliance Officers, or Security Administrators.
* Practice calm and professional communication.
* Do not argue with players.
* Do not pretend to know rules you are unsure about.
* Do not act independently in serious situations.
* Accept correction from higher staff without taking it personally.
* Show that you can be trusted with more responsibility over time.
<span style="color:#668866;">Your goal is to learn how to protect the server without abusing authority or escalating situations unnecessarily.</span><br/>
<br/>
<span style="color:#aaffaa;">You are being evaluated on maturity, attitude, communication, rule knowledge, and ability to follow direction.</span>
</div>
</div>


</div>


== <span style="color:#33ff33;">CHAIN OF COMMAND EXPECTATIONS</span> ==
== <span style="color:#33ff33;">ADMINISTRATIVE CHAIN OF COMMAND</span> ==


<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0;">
<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0;">


<div style="text-align:center; border:1px solid #33ff33; padding:10px; margin-bottom:20px;">
<div style="text-align:center; border:1px solid #33ff33; padding:10px; margin-bottom:20px;">
<span style="font-size:1.2em; font-weight:bold; letter-spacing:2px;">COMMAND ESCALATION DIRECTIVE</span><br/>
<span style="font-size:1.2em; font-weight:bold; letter-spacing:2px;">VAULT-TEC COMMAND STRUCTURE</span><br/>
<span style="color:#88cc88; font-size:0.9em;">USE PROPER ESCALATION UNLESS THERE IS AN EMERGENCY</span>
<span style="color:#88cc88; font-size:0.9em;">CLEAR AUTHORITY. CLEAR RESPONSIBILITY.</span>
</div>
</div>


<div style="padding:10px 0; line-height:1.8;">
<div style="padding:10px 0; line-height:2.0; text-align:center; color:#aaffaa;">
Staff should use the chain of command unless there is an emergency or serious misconduct.
'''Staff Manager'''<br/>
&rarr;<br/>
'''Lead Admin'''<br/>
&rarr;<br/>
'''Admin'''<br/>
&rarr;<br/>
'''Moderator'''
</div>
</div>


=== <span style="color:#00ff00;">Normal Escalation Path</span> ===


<div style="padding:10px 0; line-height:1.8; text-align:center; color:#aaffaa;">
=== <span style="color:#00ff00;">Authority Summary</span> ===
Junior Compliance Officer<br/>
&rarr; Compliance Officer<br/>
&rarr; Senior Compliance Officer<br/>
&rarr; Security Administrator<br/>
&rarr; Senior Security Administrator<br/>
&rarr; Security Operations Chief<br/>
&rarr; COO<br/>
&rarr; CEO
</div>


=== <span style="color:#00ff00;">Technical Escalation Path</span> ===
<div style="padding:10px 0; line-height:1.8;">


<div style="padding:10px 0; line-height:1.8; text-align:center; color:#aaffaa;">
<span style="color:#00ff00; font-weight:bold;">STAFF MANAGER</span><br/>
Engineer<br/>
<span style="color:#aaffaa; padding-left:20px;">Sets staff expectations and controls staff membership.</span><br/>
&rarr; Chief Engineer<br/>
<span style="color:#668866; padding-left:20px;">Final authority over recruitment, promotions, demotions, removals, transfers, and team assignments.</span><br/>
&rarr; COO or CEO
<br/>
</div>


=== <span style="color:#00ff00;">Map Escalation Path</span> ===
<span style="color:#00ff00; font-weight:bold;">LEAD ADMIN</span><br/>
<span style="color:#aaffaa; padding-left:20px;">Commands and manages an assigned staff team.</span><br/>
<span style="color:#668866; padding-left:20px;">Full operational control of their team and operational authority over lower-ranking staff when necessary.</span><br/>
<br/>


<div style="padding:10px 0; line-height:1.8; text-align:center; color:#aaffaa;">
<span style="color:#00ff00; font-weight:bold;">ADMIN</span><br/>
Mapper or Engineer<br/>
<span style="color:#aaffaa; padding-left:20px;">Supervises and assists the Moderator force.</span><br/>
&rarr; Chief Architect<br/>
<span style="color:#668866; padding-left:20px;">Handles escalation, training, supervision, and higher-level administrative situations.</span><br/>
&rarr; Chief Engineer, if technical<br/>
<br/>
&rarr; COO or CEO
</div>
 
=== <span style="color:#00ff00;">Rule Interpretation Path</span> ===
 
<div style="padding:10px 0; line-height:1.8; text-align:center; color:#aaffaa;">
Compliance Officer<br/>
&rarr; Security Administrator<br/>
&rarr; Senior Security Administrator<br/>
&rarr; CEO, if needed
</div>


<div style="color:#668866; line-height:1.8;">
<span style="color:#00ff00; font-weight:bold;">MODERATOR</span><br/>
Staff should not skip the chain of command just because they want a different answer. However, serious misconduct, abuse of power, harassment, corruption, or urgent server-threatening issues may be escalated directly to senior leadership.
<span style="color:#aaffaa; padding-left:20px;">Primary frontline administrative force.</span><br/>
</div>
<span style="color:#668866; padding-left:20px;">Handles the majority of tickets, player reports, routine investigations, and normal rule enforcement.</span>


</div>
</div>


== <span style="color:#33ff33;">ENFORCEMENT PHILOSOPHY</span> ==


<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0;">
=== <span style="color:#00ff00;">Command Principle</span> ===


<div style="text-align:center; border:1px solid #33ff33; padding:10px; margin-bottom:20px;">
<div style="padding:10px 0; line-height:1.8; text-align:center;">
<span style="font-size:1.2em; font-weight:bold; letter-spacing:2px;">ENFORCEMENT DIRECTIVE</span><br/>
<span style="color:#88cc88; font-size:0.9em;">PROTECT ROLEPLAY, FAIRNESS, AND COMMUNITY TRUST</span>
</div>


<div style="color:#aaffaa; line-height:1.8;">
<span style="color:#55ff55; font-weight:bold;">Staff Manager sets the standard.</span><br/>
Staff should enforce the rules to protect roleplay, fairness, and community trust.<br/>
<span style="color:#55ff55; font-weight:bold;">Lead Admins command the teams.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Admins supervise the force.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Moderators execute the mission.</span><br/>
<br/>
<br/>
We are not here to remove consequences from roleplay. We are here to stop behavior that damages the round, abuses mechanics, ignores the setting, or ruins the experience of others.
</div>


=== <span style="color:#00ff00;">Before Punishing, Consider</span> ===
<span style="color:#ffaa00; font-weight:bold;">VAULT-TEC NOTICE:</span><br/>
<span style="color:#aaffaa;">Authority should be exercised at the lowest appropriate level while responsibility remains clearly defined.</span>


<div style="padding:10px 0; line-height:1.8;">
* What actually happened?
* Was there roleplay reasoning?
* Was there malicious intent?
* How much damage did it cause?
* Is this a first-time mistake or repeated behavior?
* Did the player cooperate?
* Did the player understand the rule?
* Does the situation need correction, warning, temporary removal, or a ban?
* Would staff intervention improve the round or make the situation worse?
</div>
<div style="color:#668866; line-height:1.8;">
Punishment should be firm when needed, but never emotional.<br/>
<br/>
Players should leave staff interactions understanding what they did wrong, what is expected next time, and that staff handled the situation fairly.
</div>
</div>
== <span style="color:#33ff33;">STAFF CONDUCT STANDARD</span> ==
<div style="background:#111; border:1px solid #33ff33; padding:20px; margin:15px 0; text-align:center;">
<span style="color:#aaffaa;">All staff are expected to follow this standard:</span><br/>
<br/>
<span style="color:#55ff55; font-weight:bold;">Be calm.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Be fair.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Be consistent.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Be respectful.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Ask when unsure.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Document serious actions.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Do not abuse power.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Do not argue publicly.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Do not protect friends.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Do not target enemies.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Do not escalate emotionally.</span><br/>
<span style="color:#55ff55; font-weight:bold;">Protect the server first.</span><br/>
<br/>
<span style="color:#ffaa00; font-weight:bold;">Staff authority exists to serve the community, not personal ego.</span><br/>
<br/>
<span style="color:#446644; font-size:0.9em;">VAULT-TEC NOTICE: A BETTER COMMUNITY THROUGH ORDER.</span>
</div>
</div>


</div>
</div>
[[Category:Staff]]
[[Category:Server]]

Revision as of 17:16, 11 August 2026

STAFF MANAGEMENT EXPECTATIONS

Staff Manager Expectations

You are responsible for the overall organization, standards, expectations, and accountability of the administrative staff team.

Your job is not to personally manage every Moderator or Admin. Your job is to establish what is expected of the staff force, ensure the Lead Admins are properly managing their teams, and make final personnel decisions regarding who is or is not staff.

Responsibilities:

  • Establish expectations, standards, and procedures for all administrative staff.
  • Determine the behavior and performance expected from Moderators, Admins, and Lead Admins.
  • Maintain the overall structure of the administrative staff team.
  • Assign staff members to Lead Admin teams.
  • Approve or deny staff recruitment.
  • Make final decisions regarding promotions, demotions, transfers, and staff removals.
  • Hold Lead Admins accountable for the performance, activity, and conduct of their teams.
  • Resolve disagreements between Lead Admins when necessary.
  • Ensure enforcement standards remain consistent between all three teams.
  • Review serious allegations of staff misconduct or abuse of authority.
  • Ensure Lead Admins are properly training and developing their staff.
  • Identify leadership gaps, inactivity, burnout, poor performance, or staffing shortages.
  • Intervene when a team is dysfunctional, improperly managed, or operating outside staff expectations.
  • Ensure the administrative staff team follows the direction established by the Server Manager, COO, and CEO.

You should normally manage the staff force through the Lead Admins instead of bypassing them during routine operations.

The Staff Manager has final authority over staff membership, promotions, demotions, removals, and team assignments.


Lead Admin Expectations

You are the leader of an assigned administrative team.

You have full operational authority over the Admins and Moderators assigned to your team and are responsible for their performance, discipline, development, activity, and effectiveness.

Responsibilities:

  • Direct the day-to-day operations of your assigned team.
  • Give instructions and assignments to Admins and Moderators on your team.
  • Establish operational priorities during active rounds.
  • Ensure tickets, reports, investigations, and moderation issues are being handled.
  • Ensure your team maintains adequate staff coverage.
  • Mentor and develop the Admins assigned to your team.
  • Ensure Admins are properly supervising and developing Moderators.
  • Correct improper enforcement or poor staff behavior.
  • Review significant or controversial actions taken by members of your team.
  • Ensure your team follows server rules, staff procedures, and Staff Manager expectations.
  • Recommend recruitment, promotion, demotion, transfer, or removal to the Staff Manager.
  • Monitor inactivity and poor performance within your team.
  • Resolve disagreements between members of your team.
  • Report serious staff concerns to the Staff Manager.
  • Coordinate with the other Lead Admins during major incidents or server-wide problems.

Lead Admins are expected to run their teams without requiring the Staff Manager to micromanage routine operations.


Lead Admin Cross-Team Authority

Lead Admins are senior operational leaders of the administrative staff force.

Because of this, a Lead Admin may give reasonable operational instructions to an Admin or Moderator belonging to another Lead Admin's team when necessary for server operations.

Examples Include:

  • Directing staff to respond to a major incident.
  • Assigning available staff to tickets or investigations.
  • Coordinating staff during high-population rounds.
  • Ordering a lower-ranking staff member to stop improper staff behavior.
  • Reassigning immediate operational priorities during an emergency.
  • Coordinating coverage when another team has insufficient staff online.

However, giving operational instructions does not give a Lead Admin personnel control over another Lead Admin's team.

A Lead Admin may not independently:

  • Add someone to another Lead Admin's team.
  • Remove someone from another Lead Admin's team.
  • Permanently transfer staff between teams.
  • Promote another team's staff member.
  • Demote another team's staff member.
  • Remove another team's member from staff.
  • Override another Lead Admin's long-term personnel decisions.

If a Lead Admin has a serious issue with another team's staff member, the issue should be documented and brought to that staff member's Lead Admin or the Staff Manager.

Operational Authority: Lead Admins may direct lower-ranking staff from any team when reasonably necessary.

Personnel Authority: Lead Admins only directly control the personnel assigned to their own team.


Admin Expectations

You are a supervisor and assistant leader within your assigned Lead Admin team.

Your primary responsibility is supervising Moderators, helping them make good decisions, handling situations that require additional experience or authority, and assisting your Lead Admin with the operation of the team.

Responsibilities:

  • Supervise Moderators assigned to your team.
  • Provide guidance when Moderators are uncertain.
  • Assist Moderators with complicated tickets, investigations, and player situations.
  • Take over situations that exceed Moderator authority or experience.
  • Review Moderator decisions when necessary.
  • Ensure Moderators remain professional and follow staff expectations.
  • Help train and develop newer Moderators.
  • Assign Moderators to tickets or operational priorities when directed or necessary.
  • Handle enforcement matters requiring greater authority or experience.
  • Document significant disciplinary actions and unusual incidents.
  • Identify Moderators who require additional training, correction, or supervision.
  • Report serious staff performance problems to your Lead Admin.
  • Carry out instructions issued by your Lead Admin.
  • Help maintain team operations when your Lead Admin is unavailable.
  • Coordinate with other Admins during busy rounds and major incidents.

Admins are supervisors and assistant leaders. They are not independent team commanders.

Your job is to supervise the frontline staff force, provide escalation support, and make sure Moderators have the leadership they need to succeed.


Moderator Expectations

You are the primary frontline force of the administrative staff team.

Moderators should handle the majority of routine player issues, tickets, reports, investigations, questions, and normal rule enforcement.

Responsibilities:

  • Respond to routine admin tickets.
  • Investigate player reports.
  • Handle ordinary rule violations within your authority.
  • Help players with server and rule questions.
  • Monitor the round for disruptive or rule-breaking behavior.
  • De-escalate player conflicts when possible.
  • Gather facts and context before taking administrative action.
  • Issue routine enforcement actions permitted by your authority.
  • Document incidents and punishments when required.
  • Escalate serious, complicated, or unclear situations to an Admin.
  • Follow reasonable instructions from Admins and Lead Admins.
  • Maintain calm and professional communication with players.
  • Avoid unnecessary interference with legitimate roleplay.
  • Report suspected staff misconduct through the chain of command.
  • Accept correction and guidance from Admins and Lead Admins.
  • Continue developing your knowledge of the rules and enforcement philosophy.
  • Maintain an active staff presence during rounds.

Moderators are expected to perform the majority of normal administrative work.

Admins and Lead Admins exist to supervise, support, coordinate, and handle escalation — not to replace the Moderator force.


ADMINISTRATIVE CHAIN OF COMMAND

VAULT-TEC COMMAND STRUCTURE
CLEAR AUTHORITY. CLEAR RESPONSIBILITY.

Staff Manager

Lead Admin

Admin

Moderator


Authority Summary

STAFF MANAGER
Sets staff expectations and controls staff membership.
Final authority over recruitment, promotions, demotions, removals, transfers, and team assignments.

LEAD ADMIN
Commands and manages an assigned staff team.
Full operational control of their team and operational authority over lower-ranking staff when necessary.

ADMIN
Supervises and assists the Moderator force.
Handles escalation, training, supervision, and higher-level administrative situations.

MODERATOR
Primary frontline administrative force.
Handles the majority of tickets, player reports, routine investigations, and normal rule enforcement.


Command Principle

Staff Manager sets the standard.
Lead Admins command the teams.
Admins supervise the force.
Moderators execute the mission.

VAULT-TEC NOTICE:
Authority should be exercised at the lowest appropriate level while responsibility remains clearly defined.