> For the complete documentation index, see [llms.txt](https://augustamc.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://augustamc.gitbook.io/wiki/towny/community-council/recruitment-and-expectations.md).

# Recruitment & Expectations

## Recruitment & Selection

Community Council members are carefully selected by staff rather than publicly voted on. This helps ensure the role is filled by players who consistently demonstrate maturity, reliability, creativity, and a positive impact on the community.

Because Community Council members help organize official server activities and represent AugustaMC publicly during events, staff selection allows the team to evaluate a player's behavior, communication, consistency, teamwork, and overall trustworthiness over time.

The selection process is intended to:

* Prevent popularity contests or favoritism
* Ensure active and dependable members are chosen
* Maintain professionalism within the role
* Protect the quality and consistency of server events
* Select players who genuinely care about community improvement

Staff may observe players over extended periods before considering them for the role. Consistent positivity, engagement, initiative, and healthy interactions with others are often the biggest factors in being selected.

### Requirements

Applicants should generally:

* Be active within the community
* Demonstrate maturity
* Have positive interactions with players
* Show creativity and teamwork
* Be capable of organizing activities
* Understand AugustaMC rules and culture

Previous staffing experience is not required.

***

### Selection Process

Applications may include:

* Basic player information
* Activity history
* Event ideas
* Past community contributions
* Availability
* Why they want the role

Applicants may also be interviewed by staff.

***

## Removal From The Role

Community Council members may be removed for:

* Extended inactivity
* Toxic behavior
* Abuse of permissions
* Repeated rule violations
* Lack of participation
* Damaging the community environment
* Misrepresentation of staff decisions

Removal decisions are handled by server administration.

## Expectations

### Activity

Community Council members should remain reasonably active within:

* Minecraft server activity
* Discord participation
* Event planning discussions
* Community engagement

Long periods of inactivity without notice may result in removal from the role.

***

### Professionalism

Council members represent AugustaMC publicly and are expected to:

* Treat players respectfully
* Avoid unnecessary drama or conflict
* Handle criticism maturely
* Maintain a positive attitude
* Follow all server rules
* Avoid abuse of any permissions or influence

Even outside official events, members should conduct themselves responsibly.

***

### Creativity & Initiative

The Community Council role thrives on creativity.

Members are encouraged to:

* Introduce new event concepts
* Experiment with unique themes
* Collaborate with towns and player groups
* Develop recurring server traditions
* Encourage player participation in creative ways

**Initiative is highly valued within the role.**


---

# 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:

```
GET https://augustamc.gitbook.io/wiki/towny/community-council/recruitment-and-expectations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
