> For the complete documentation index, see [llms.txt](https://test.genericgeopol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://test.genericgeopol.com/staff-rules.md).

# Staff Rules

## Hierarchy

```mermaid
flowchart TD
    O["Owners"]
    CMGR["Community Manager"]
    MMGR["Media Manager"]
    DEV["Developer"]
    SM["Senior Moderator"]
    JM["Junior Moderator"]
    H["Helper"]

    O --> CMGR
    O --> MMGR
    O --> DEV
    O --> SM
    SM --> JM
    JM --> H
```

The **Community Manager**, **Media Manager** and **Developer** report directly to the Owners, outside the moderation chain.

## Ranks and Duties

Listed most senior first. Each moderation rank inherits the duties of the ranks under it.

| Rank                  | Duties                                                                                                                                                                        |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Owners**            | Set the server's direction and handle staffing and major decisions. Keep the server running stably and make sure the staff team has the support it needs to operate smoothly. |
| **Community Manager** | Owns the player-facing side of the community. **Runs the appeals process.**                                                                                                   |
| **Media Manager**     | Owns the server's media presence and public content.                                                                                                                          |
| **Developer**         | Builds and maintains plugins, config and technical systems.                                                                                                                   |
| **Senior Moderator**  | Runs wars, events and build competitions, manages the team day to day, and reviews GDP tickets. **Final say on all punishment decisions.**                                    |
| **Junior Moderator**  | Investigates griefing and insiding reports, issues punishments, and defuses problems early. Assists with wars and events.                                                     |
| **Helper**            | Answers questions and keeps chat in order on Discord and in game. Reports claim violations and flags issues to the team.                                                      |

## Punishments

Senior Moderators have the final say on punishment decisions. Never reverse another staff member's punishment yourself — send the player to appeals.

## Appeals

**How to appeal.** Players submit appeals through the appeals bot on Discord.

**Who handles them.** Only the **Community Manager** and the **Owners** review appeals. No other rank may accept, deny or reopen one — including the staff member who issued the punishment.

**No deadline.** A punishment can be appealed at any time, however old it is.

**If an appeal is denied.** The player may submit a new appeal after **3 days**. Repeatedly appealing the same punishment ends the process — the decision stands and further appeals will not be reviewed.

## Compensation

Depending on overall server performance, senior staff — **Senior Moderators, the Developer, and the Community and Media Managers** — are entitled to payment for their services. Payment is tied to how the server is performing and is not guaranteed for any given period.

## Core Duties

**Log everything.** Every action taken on staff duty goes in the designated Discord channel — bans, mutes, warnings, rollbacks, item grants, build removals. Undocumented actions can't be reviewed or defended on appeal.

**Marking cities takes two.** Only high staff can mark a city, and two of them must sign off together.

## FAQ

**Can I be in a faction?** Yes, as long as you never use your position to give it an advantage.

**What if I mess up?** Own it quickly and tell a higher-up. Mistakes are fine; hiding them isn't.

**How do promotions work?** Activity, conduct and initiative. High staff decide.

**What if I go inactive?** Give the staff lead or a member of high staff notice if you'll be away two weeks or more. Going quiet without warning can mean demotion for inactivity. Nobody expects you online constantly — real life comes first.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://test.genericgeopol.com/staff-rules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.