> For the complete documentation index, see [llms.txt](https://coppercore-smp.gitbook.io/coppercore-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coppercore-smp.gitbook.io/coppercore-wiki/rules/staff-and-moderation.md).

# ✦ ─ Staff & Moderation

Coppercore staff are volunteers who help keep the server safe, fair, and enjoyable.

Players are expected to cooperate with reasonable staff instructions and use the proper appeal or support process when they disagree with a decision.

***

### Respecting Staff

Treat staff members with the same basic respect expected toward every other player.

Do not:

* insult, harass, threaten, or repeatedly provoke staff
* target staff because of a warning or punishment
* follow staff between chats or platforms to continue an argument
* encourage others to harass or attack a staff member
* abuse staff through tickets or private messages

Disagreeing with staff is allowed. Becoming abusive because you disagree is not.

***

### Following Staff Instructions

Players must follow reasonable instructions given by staff while they are handling a rule violation, safety issue, investigation, or server problem.

Examples include being asked to:

* stop an argument
* leave another player alone
* remove inappropriate content
* change or reduce a laggy build
* stop using a questionable mod or feature
* move away from an active investigation
* provide information through a ticket.

Ignoring repeated staff instructions may result in further action.

***

### Disputing a Decision

Do not argue about punishments or moderation decisions in public chat.

When you disagree with a decision:

1. remain calm
2. open an appeals ticket
3. explain what you believe was incorrect
4. provide any relevant evidence
5. wait for the decision to be reviewed.

A different staff member or higher-ranking staff member may review the situation where appropriate.

Opening a ticket does not guarantee that a decision will be changed.

***

### Punishment Appeals

Appeals should be honest, respectful, and focused on the punishment being appealed.

A good appeal should include:

* your Minecraft username
* the punishment you received
* when it happened
* why you believe it should be reconsidered
* any relevant context or evidence
* acknowledgement of your actions where appropriate.

Do not spam appeals, open multiple tickets for the same punishment, or ask other players to appeal on your behalf unless you do not have access to a Discord account.

***

### Staff Impersonation

Do not pretend to be a staff member or imply that you have staff authority when you do not.

This includes:

* copying staff nicknames
* using a similar username or skin to mislead others
* claiming you can ban, mute, investigate, or punish players
* giving fake staff instructions
* pretending that a decision or event has staff approval
* impersonating official Coppercore accounts or bots.

Harmless jokes are only acceptable when nobody could reasonably mistake them for genuine staff communication.

***

### False Reports and Misleading Staff

Do not knowingly provide false information during a report or investigation.

This includes:

* making up accusations
* editing evidence to change its meaning
* hiding relevant information
* removing context deliberately
* coordinating false stories with other players
* reporting someone purely to inconvenience or punish them
* framing another player for something they did not do

Mistakes made in good faith are not the same as deliberately misleading staff.

***

### Wasting Staff Time

Do not repeatedly open unnecessary tickets, make fake emergency reports, or deliberately create issues to get a reaction from staff.

Staff assistance should not be treated as entertainment.

This does not mean players should be afraid to ask for help. Genuine questions and reports are always welcome.

***

### Staff DMs

Do not contact staff members through direct messages for server-related support.

All server queries, reports, appeals, punishment discussions, purchase issues, account problems, grief reports, and other support requests **must** be handled through the ticket system.

Staff will not provide support through DMs. They may either not respond or direct you to open a ticket instead.

This rule exists so that:

* the correct staff members can access the issue
* conversations and evidence are properly recorded
* support is not lost in private messages
* staff are not pressured individually
* decisions can be reviewed where necessary

Do not DM several staff members hoping to get a faster response or a different answer.

Staff may still contact a player directly when necessary, but players should always use tickets when requesting support.

***

### Staff Privacy and Confidential Information

Do not share private staff messages, ticket content, internal screenshots, leaked logs, or other confidential information without permission.

Do not attempt to gain access to staff-only channels, tools, accounts, or information.

Information shared with staff during a report may be kept private where possible, but complete anonymity cannot always be guaranteed.

***

### Staff Accountability

Staff members are also required to follow Coppercore SMP’s rules and staff guidelines.

Concerns about staff conduct should be reported privately through a ticket and should include clear information or evidence where possible.

Do not start public callout campaigns or encourage harassment. Serious concerns regarding staff behaviour can be taken directly to the Owner's DMs if required.

***

### Staff Discretion

Staff may consider context, intent, previous behaviour, severity, and impact when deciding how to respond to a situation.

Similar incidents may not always receive identical outcomes where the circumstances differ.

Staff discretion does not mean decisions cannot be questioned. It means they should be questioned through the proper process.

{% hint style="warning" %}
**Important:** Staff are here to help, not to win arguments. Cooperate during the situation and raise concerns through a ticket afterwards.
{% endhint %}
