> For the complete documentation index, see [llms.txt](https://wiki.mmorealms.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.mmorealms.gg/team-roles-and-applications.md).

# Team Roles and Applications

Here you will find all the relevant information about different supporting roles we have available on the server, and how to go about applying to join one.

**Contents:**

1. [Why join the team?](#why-join-the-team)
2. [Available Roles](#available-roles)
   1. [Support](#support)
      1. [Helper](#helper)
   2. [Builder](#builder)
   3. [Tester](#tester)
   4. [Feedback](#feedback)
   5. [Developer](#developer)

***

## Why join the team?

Our server is always growing, welcoming new players, creating new features and providing support to those who need it. However in order to produce a worthwhile result a large amount of effort and work is put into the server.

Joining our team is a fantastic way to become more deeply involved with the community and help support and shape the future of the server. By taking on one of the roles below you will find yourself in a position to directly impact users experience with the server in some capacity.

## Available Roles

Below you will find a range of roles which we are always taking applications for, along with information about what the role may entail, the requirements to be considered for the role, and most importantly how to go about applying for said role.

There is no limit to the number of roles for which you may apply, so if you find yourself interested in multiple you are more than welcome to try out for them all. However please do note that to maintain a role on the server, you will be expected to perform the duties tied to the specific role, so make sure not to overwhelm yourself.

### Support

The support team is the welcoming face of our community. When you hear "Staff" on the server, this is most likely the team in reference being the group of members who directly assist the players with any issues they may face.

Within the support team there are many different roles, each of which come with their own duties and responsibilities. Some examples of duties carried out by members of this team include:

* Answering player questions
* Dealing with player opened tickets
* Enforcing server rules
* Hosting server based events
* Testing new server features

<div align="center" data-with-frame="true"><figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FjO8i0UWPZBsZGWbDos3V%2FUntitled.png?alt=media&amp;token=0dcc07e3-bba0-4998-b424-b934b41cadfe" alt="" width="188"><figcaption></figcaption></figure></div>

#### Helper

When joining the support team, you will be applying for and starting with the role of Helper which possesses the least amount of duties from all the roles as a means to give yourself a chance to build up your understanding and knowledge. Based on your performance and contributions you may be offered a promotion to a higher role which then comes with the additional responsibilities.

The requirements for applying to join the staff team are as follows and additional information can be found on our [Forums](https://forum.mmorealms.gg/d/5-general-information-staff):

> * At least **24 hours of playtime** within the current reset.
> * **Aged 16** or over.
> * Have access to a Microphone. (*required for Interview process*)
> * No form of **Ban or Permanent Mute** within the past 2 months.
> * No **active Ban or Mute** (*Appealable or Not*) on the server.

If you would like to apply, we take support staff applications via our Forums. Using the below link, select the `Start a Discussion` option to begin your application, and answer the provided questions. We aim to give a response within a week of creation, so please remain patient whilst it's reviewed.

{% embed url="<https://forum.mmorealms.gg/t/staff-application>" %}

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2F3p9lQpWdfUya9iSLCU5p%2Fimage.png?alt=media&amp;token=c4fe1808-a859-4dcb-bf2d-33fa16b4221d" alt="" width="563"><figcaption></figcaption></figure>

### Builder

Builders are responsible for making many of the amazing maps you will find on our server, with past examples shown below. We have a range of projects available so there should always be something to keep your interest. If you have the relevant skills, we would love to hear more about yourself and your past work, in order to get new creations from yourself implemented on the server for everyone to see.

{% tabs %}
{% tab title="Spawn" %}

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FUK7oyDcmv3jseYGVJ2TN%2Fimage.png?alt=media&amp;token=6ccd2a95-9352-4efb-8f9c-4501ea736b32" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FHf003jI6fTeMe07TFfl1%2Fimage.png?alt=media&amp;token=866ad793-e23c-4158-84d6-700f374f742d" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Gyms" %}

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2F6paJqWJcIvGp4An0l5Jf%2Fimage.png?alt=media&amp;token=a205a9b5-6814-4fce-bc0a-6aced6945c47" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2F0KuRnFi7f7xTbSOsWTyj%2Fimage.png?alt=media&amp;token=7c364307-3409-4600-8ca4-a052ce4c4b4d" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="EV Training" %}

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2F5zvsuYeEqp0JHSMy0t1k%2Fimage.png?alt=media&amp;token=0ffdda8e-a94a-4b2b-af0a-a518141b08c7" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Boat Races" %}

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FknOrolTOhcVM7cOL7VEw%2Fimage.png?alt=media&amp;token=ea64a438-7d38-494d-b5c0-193e5889dfa3" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FQiZGZVKyaRVswqnlZUbC%2Fimage.png?alt=media&amp;token=5533fe26-38c9-4426-ac61-7bb786152a0a" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Creator" %}

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2F4gCJ88tyZgBpDN7RMeWR%2Fimage.png?alt=media&amp;token=64d677ab-3fc6-46fc-84d8-e26c6683701f" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2F9RV9veOfH9U5lMl3uVNq%2Fimage.png?alt=media&amp;token=2d617058-8ac8-448b-a331-6727dec51a23" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Arena" %}

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FgelNBWKgoQZgpHsq25sp%2Fimage.png?alt=media&amp;token=e0bc126c-184a-4ec8-9edd-6f61f82b3077" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

The requirements for applying to join the build team are as follows and additional information can be found on our [Forums](https://forum.mmorealms.gg/d/2-general-information-builder):

> * **You need a Portfolio of previous builds you have created.** This must include at least 5 different types of builds and show a good range of your skills. \[`We won't be accepting different types of buildings from the same build for example.`].
> * At least **24 hours of playtime** within the current reset.
> * No form of **Ban or Permanent Mute** within the past **2 months**.
> * **No active Ban or Mute** (*Appealable or Not*) on the server.

If you would like to apply, we take builder applications via our Forums. Using the below link, select the `Start a Discussion` option to begin your application, and answer the provided questions. We aim to give a response within a week of creation, so please remain patient whilst it's reviewed.

{% embed url="<https://forum.mmorealms.gg/t/builder-application>" %}

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FKFs4eG5k0d1Vq2MrdhCa%2Fimage.png?alt=media&amp;token=6008eb0e-8d59-422d-ba02-988c62470213" alt="" width="563"><figcaption></figcaption></figure>

### Tester

Testers are responsible for quality control by ensuring that new content created meets our servers standards before release. This involves thoroughly playing with new developmental features in a separate environment to provide feedback on both bugs and suggestions to ensure it turns out great. When you see new features launch smoothly, this is the team that worked behind the scenes to iron out the issues.

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FVil7ldGn2NFqu3hQBz4n%2Fimage.png?alt=media&amp;token=3d50a2cd-b529-4c21-b16d-086551115ae1" alt="" width="174"><figcaption><p>Example Bug</p></figcaption></figure>

The requirements for applying to join the tester team are as follows:

> * At **least 24 hours of playtime** within the current reset.
> * No form of **Ban or Permanent Mute** within the past **2 months**.
> * No **active Ban or Mute** (*Appealable or Not*) on the server.

If you would like to apply, we take tester applications via [tickets](https://discord.com/channels/1332431737694982209/1332431740563755106) in our Discord server. If you mention you're looking to apply, we will provide you the questions to answer. We aim to give a response within a week of creation, so please remain patient whilst it's reviewed.

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FEft1MA5B1xsVimkH0da8%2Fimage.png?alt=media&amp;token=2c63807e-55dc-4ceb-a252-3ee1fdff3fdd" alt="" width="563"><figcaption></figcaption></figure>

### Feedback

The feedback team acts as the primary voice of our community, bridging the gap between player opinions and server development. This team heavily focuses on analysing how certain updates and other releases are perceived by the player base, to ensure ideas are heard and changes can be made.

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FyZYUqAJuBnQuaD3Ed8to%2Fimage.png?alt=media&amp;token=c7cf668d-b457-4397-bb62-36b97a192de1" alt=""><figcaption></figcaption></figure>

The requirements for applying to join the feedback team are as follows:

> * At least 24 hours of playtime within the current reset.
> * No form of Ban or Permanent Mute within the past 2 months.
> * No active Ban or Mute (Appealable or Not) on the server.

If you would like to apply, we take tester applications via [tickets](https://discord.com/channels/1332431737694982209/1332431740563755106) in our Discord server. If you mention you're looking to apply, we will provide you the questions to answer. We aim to give a response within a week of creation, so please remain patient whilst it's reviewed.

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FEft1MA5B1xsVimkH0da8%2Fimage.png?alt=media&amp;token=2c63807e-55dc-4ceb-a252-3ee1fdff3fdd" alt="" width="563"><figcaption></figcaption></figure>

### Developer

Developers are responsible for maintaining the server infrastructure, and creating new features and bug fixes that directly impact player experience. When you see custom mechanics, smooth sever performance or brand new systems added to the game, this is the team driving those technical updates.

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FBEXyeOLaDFEepUxFkVU5%2Fimage.png?alt=media&amp;token=9b1c4055-22e7-41ce-8ad0-5ace8b69cb71" alt="" width="563"><figcaption></figcaption></figure>

The requirements for applying to join the developer team aren't strict, and additional information can be found on our [Forums](https://forum.mmorealms.gg/t/developer-application). We are looking for a developer who brings genuine depth in one or more of the following areas:

> * Java & Modding - Fabric, NeoForge, Velocity, Architectury API, Cobblemon/Pixelmon
> * Data & Infrastructure - MariaDB/PostgreSQL, Redis, Docker, Kubernetes, Hibernate
> * DevOps & Observability - GitHub Actions CI/CD, Prometheus, Grafana, Loki, Spark profiling
> * Tooling & Scripting - Gradle (Kotlin DSL), multi-module projects, Python automation

If you would like to apply, we take developer applications via our Forums. Using the below link, select the `Start a Discussion` option to begin your application, and answer the provided questions. We aim to give a response within a week of creation, so please remain patient whilst it's reviewed.

{% embed url="<https://forum.mmorealms.gg/t/developer-application>" %}

<figure><img src="https://1136757732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaGML4Zd5tMQdGofzRFUX%2Fuploads%2FkcZ2zlJRRiyLdiJRlmqC%2Fimage.png?alt=media&amp;token=8631780e-5c84-4ac9-8e5f-ea0aba0f25f6" alt="" width="563"><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.mmorealms.gg/team-roles-and-applications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
