> 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/event-guidelines.md). # Event Guidelines ## Event Guidelines ### Event Approval Process To maintain organization and fairness, larger events should be approved by Matt & Abby before being publicly announced. Event proposals should include: * Event name * Event description * Proposed date/time * Required staff assistance * Reward ideas * Estimated player count * Build or resource needs Smaller casual events may not require formal approval depending on staff discretion. *** ### Event Standards Events hosted under AugustaMC should: * Be fair and accessible * Avoid favoritism * Have clear rules * Be understandable for players * Avoid excessive wait times * Respect server performance limitations * Properly advertised by working with Matt & Abby Council members should test events before launch whenever possible. *** ### Rewards & Incentives Possible event rewards may include: * In-game currency * Custom items * Titles or tags * Cosmetic rewards * Event trophies * Discord recognition * Rare collectibles Rewards should remain balanced and approved by staff if necessary. *** ### ❗Survival-Focused Philosophy❗ Community Council is intentionally designed to remain close to the normal player experience. Council members are not intended to function as staff, builders in creative mode, or administrators. The role focuses on creativity, teamwork, and leadership within the natural survival environment of AugustaMC. Because of this: * Most events should be built using survival resources * Players are encouraged to collaborate with towns and communities * Council members should avoid depending on staff intervention * Additional permissions will be minimal or nonexistent in most situations * Success within the role should come from organization, effort, and community participation rather than administrative power This helps maintain fairness, immersion, and authenticity within the server while encouraging players to work together toward larger community projects. --- # 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/event-guidelines.md?ask= ``` 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.