Staff Expectations

╔══════════════════════════════════════╗
VAULT-TEC STAFF TERMINAL
ACCESS LEVEL: STAFF
╚══════════════════════════════════════╝

> Establishing secure staff uplink...
> Loading administrative expectations...
> Verifying chain of command...
> Synchronizing leadership directives...

STATUS: STAFF DIRECTIVES LOADED

STAFF EXPECTATIONS FOR
MISFITS: NUCLEAR WASTELAND

A Fallout themed Medium Roleplay environment
where staff protect roleplay, fairness, and community trust.

Staff authority depends on:
• Calm judgment
• Consistent enforcement
• Respect for players
• Alignment with server leadership

Administrative power exists to serve the community.
It is not personal status, leverage, or ego.

REVIEW THE STAFF DIRECTIVES BELOW
BEFORE EXERCISING ADMINISTRATIVE AUTHORITY.

VAULT-TEC NOTICE: A BETTER COMMUNITY THROUGH ORDER.

QUICK STAFF DIRECTIVES

VAULT-TEC STAFF CONDUCT TERMINAL
QUICK DIRECTIVES

1 — BE CALM
Never get snappy, aggressive, sarcastic, or hostile toward players.

2 — BE FAIR
Enforce rules based on facts, context, severity, player history, and server intent.

3 — PROTECT ROLEPLAY
Staff intervention should protect the round, not replace player-driven story.

4 — FOLLOW THE CHAIN OF COMMAND
Ask upward when unsure and do not skip leadership just because you want a different answer.

5 — DOCUMENT SERIOUS ACTIONS
Major punishments, controversial calls, and repeated behavior problems must be documented.

6 — DO NOT ABUSE AUTHORITY
Do not use staff power to win arguments, protect friends, target enemies, or influence roleplay.

7 — REPRESENT THE SERVER
Every staff interaction affects player trust in Misfits: Nuclear Wasteland.

> FULL STAFF DIRECTIVES AVAILABLE BELOW
> SCROLL TO CONTINUE

ALL STAFF EXPECTATIONS

GENERAL STAFF DIRECTIVE
APPLIES TO ALL STAFF MEMBERS

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.

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.

Required Conduct

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

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.

LEADERSHIP EXPECTATIONS

CEO Expectations

You are the final authority and final responsibility holder for Misfits: Nuclear Wasteland.

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.

Responsibilities:

• Set the overall vision and intent of the server.
• Make final decisions on rule interpretation, staff structure, major punishments, and server direction.
• Approve or deny major rule changes.
• Approve or deny major gameplay, technical, mapping, and faction-direction changes.
• Hold senior staff accountable for their departments.
• Protect the long-term health of the community over short-term popularity.
• Resolve disputes between senior leadership when needed.
• Make sure the staff team understands the difference between enforcing rules and controlling roleplay.
• Ensure the server remains consistent with the intended Medium Roleplay Fallout experience.
• Step in when staff decisions risk damaging the server, community trust, or project direction.

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.

Final rule interpretation rests with you.

COO Expectations

You are responsible for day-to-day operations and making sure the CEO's intent is carried out consistently.

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:

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

You do not replace the CEO's authority. You execute the CEO's intent and keep the machine moving.

When in doubt, ask: Does this support the CEO's direction and improve the health of the server?

Security Operations Chief Expectations

You are responsible for building, training, maintaining, and correcting the staff enforcement team.

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.

Responsibilities:

• Recruit qualified staff members.
• Review staff applicants for maturity, rule knowledge, temperament, and trustworthiness.
• Train new Compliance Officers and guide their development.
• Maintain staff standards across all enforcement ranks.
• Make sure staff understand what they are allowed and not allowed to do.
• Identify staff who need coaching, correction, demotion, or removal.
• Work with Senior Security Administrators to keep rule interpretation consistent.
• Make sure punishment standards are fair and not based on emotion.
• Ensure staff are empathetic toward players while still enforcing the rules.
• Monitor staff activity, ticket handling, and professionalism.
• Address reports of staff misconduct.
• Escalate serious staff problems to the COO or CEO.

You are not just recruiting bodies. You are responsible for the quality and trustworthiness of the staff force.

A strong staff team should be calm, consistent, fair, and aligned with the CEO's intent.

TECHNICAL AND MAP EXPECTATIONS

Chief Engineer Expectations

You are responsible for the gameplay and technical direction of the server.

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.

You are expected to protect both the player experience and the codebase.

Engineers should not push major systems, balance changes, or gameplay-altering features without your approval.

Chief Architect Expectations

You are responsible for the direction, balance, and structure of the map or maps used by the server.

Your job is to make sure the physical world supports the intended Fallout roleplay experience, faction conflict, travel, exploration, and balance.

Responsibilities:

• Set the overall direction of the map.
• Decide what maps are used and whether multiple maps are appropriate.
• Define faction territories, neutral zones, contested spaces, and important landmarks.
• Maintain map balance between factions.
• Make sure faction bases are defensible but not impossible to interact with.
• Make sure the map encourages roleplay, travel, conflict, trade, and story.
• 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.

You are not just placing rooms. You are shaping where the server's stories happen.

Every major map decision should answer: Does this create better roleplay, better conflict, and better balance?

Engineer Expectations

You are responsible for writing and maintaining server systems approved by the Chief Engineer.

Your job is to build features, fix bugs, improve systems, and support the technical side of the server without pushing unauthorized gameplay direction.

Responsibilities:

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

Your work directly affects the player experience. A broken system, careless merge, or unapproved feature can damage an entire round.

You are expected to build for the server's vision, not just for what is fun to code.

SECURITY AND COMPLIANCE EXPECTATIONS

Senior Security Administrator Expectations

You are the highest rule-enforcement staff rank below leadership and the primary interpreter of rules for the Security Administrator team.

This rank is reserved for people who understand the rules deeply and interpret them as close as possible to the CEO's intent.

Responsibilities:

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

You are expected to be calm, precise, and consistent.

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.

Security Administrator Expectations

You are a trusted server administrator responsible for enforcing the rules with minimal supervision.

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.

Responsibilities:

• Handle admin tickets professionally and calmly.
• Investigate rule violations before acting.
• Issue warnings, notes, kicks, bans, or other punishments when appropriate.
• Understand the rules well enough to require little help in normal situations.
• Escalate unclear or high-impact cases to a Senior Security Administrator.
• Support and mentor Compliance Officers.
• Answer Compliance Officer questions and help them learn proper enforcement.
• Avoid emotional punishments or snap decisions.
• Keep player interactions respectful, even when issuing discipline.
• Explain decisions clearly without arguing endlessly.
• Document punishments and important context.
• Watch for griefing, metagaming, exploit abuse, escalation violations, harassment, and behavior that harms the round.
• Protect the player experience without over-adminning roleplay.

You are expected to be a model of good judgment.

Compliance Officers should be able to come to you for help, and players should be able to trust that your decisions are fair.

Senior Compliance Officer Expectations

You are an experienced frontline staff member who understands how to enforce rules while keeping the server enjoyable.

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.

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.

Your goal is to protect the community without making players feel like staff are hunting for mistakes.

Compliance Officer Expectations

You are the frontline defense of the server.

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.

Responsibilities:

• Help players with questions and basic issues.
• Respond to minor problems before they become major incidents.
• Maintain respectful behavior in public spaces.
• Calm down heated situations when possible.
• Watch for toxicity, griefing, metagaming, rule confusion, and disruptive behavior.
• Gather information and pass serious issues to Senior Compliance Officers or Security Administrators.
• Avoid making major punishment decisions unless authorized.
• Treat every player with patience, even when they are frustrating.
• Do not argue with players publicly.
• Do not use your role to intimidate, threaten, or flex authority.
• Learn the rules and ask questions when unsure.
• Support roleplay by guiding players toward better behavior instead of immediately escalating everything.
• Report repeated problem players or serious incidents up the chain.

You are not expected to know everything. You are expected to be honest, calm, helpful, and willing to learn.

A good Compliance Officer makes the server feel safer and more welcoming without making it feel over-policed.

Junior Compliance Officer Expectations

You are in training.

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.

Your goal is to learn how to protect the server without abusing authority or escalating situations unnecessarily.

You are being evaluated on maturity, attitude, communication, rule knowledge, and ability to follow direction.

CHAIN OF COMMAND EXPECTATIONS

COMMAND ESCALATION DIRECTIVE
USE PROPER ESCALATION UNLESS THERE IS AN EMERGENCY

Staff should use the chain of command unless there is an emergency or serious misconduct.

Normal Escalation Path

Junior Compliance Officer
→ Compliance Officer
→ Senior Compliance Officer
→ Security Administrator
→ Senior Security Administrator
→ Security Operations Chief
→ COO
→ CEO

Technical Escalation Path

Engineer
→ Chief Engineer
→ COO or CEO

Map Escalation Path

Mapper or Engineer
→ Chief Architect
→ Chief Engineer, if technical
→ COO or CEO

Rule Interpretation Path

Compliance Officer
→ Security Administrator
→ Senior Security Administrator
→ CEO, if needed

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.

ENFORCEMENT PHILOSOPHY

ENFORCEMENT DIRECTIVE
PROTECT ROLEPLAY, FAIRNESS, AND COMMUNITY TRUST

Staff should enforce the rules to protect roleplay, fairness, and community trust.

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.

Before Punishing, Consider

• 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?

Punishment should be firm when needed, but never emotional.

Players should leave staff interactions understanding what they did wrong, what is expected next time, and that staff handled the situation fairly.

STAFF CONDUCT STANDARD

All staff are expected to follow this standard:

Be calm.
Be fair.
Be consistent.
Be respectful.
Ask when unsure.
Document serious actions.
Do not abuse power.
Do not argue publicly.
Do not protect friends.
Do not target enemies.
Do not escalate emotionally.
Protect the server first.

Staff authority exists to serve the community, not personal ego.

VAULT-TEC NOTICE: A BETTER COMMUNITY THROUGH ORDER.