Project Roles

This document covers the roles that structure the volunteer hierarchy on WesterosCraft.

Guest

The default explorer role when you join the server. Check out Things To Do to see where and how you can explore the map.

Apprentice

When you submit an application and get approved, you become an Apprentice. This gives you building privileges on the server and means you're being taught by a Steward.

Builder

The most common rank on WesterosCraft. Builders have access to a wide range of tools and can apply for and build projects on the map.

Steward

Stewards guide new Apprentices through their probationary period, helping them develop building skills, learn how project management works, and understand server culture. They're the primary mentor for an Apprentice's first weeks or months, teaching and supporting them so they grow into confident, capable builders.

The role is for people who enjoy helping others improve and want to give back to the community through teaching.

Responsibilities

Guide Apprentices Through Probation

Each Apprentice you take on is yours to mentor through the full probation period. The process runs in four stages.

Step 1: Claim an Apprentice. When a new builder application is approved by a Maester:

• All Stewards receive a ping in #steward-chat on Discord from a Maester
• Stewards willing to take on the Apprentice post their interest in #steward-chat
• You claim the Apprentice by introducing yourself in their application thread

You become their designated mentor for the entire probation period. You can take on multiple Apprentices, but be realistic about your capacity. Quality mentorship takes time and attention.

Step 2: Review builds. Each Apprentice completes five builds in five different locations. For each one, you:

• Visit the build in-game and assess it thoroughly
• Leave detailed feedback using melon blocks with signs
• Post an assessment in their application thread covering what they did well, what needs improvement, and advice for future builds
• Return to verify they've addressed your feedback before marking it complete

Step 3: Provide ongoing support. Beyond reviewing builds, you answer questions, help Apprentices find appropriate plots, explain confusing feedback from others, teach regional styles, and connect new members with the broader community.

Step 4: Recommend promotion. Once an Apprentice has completed their five builds and shown responsiveness to feedback, consistent activity, and a positive attitude over roughly one month, you recommend them for promotion to full Builder. A Maester reviews your recommendation and makes the final decision.

Help Apprentices Find Appropriate Plots

One of the biggest early hurdles is finding builds that match an Apprentice's skill level. Point them toward projects with clear style guides, recommend starting with simpler low-class houses, and steer them away from plots that might overwhelm them. Check the Active Plots post in the #projects-forum channel on Discord and stay familiar with what's available.

Give Constructive, Actionable Feedback

Good feedback explains the "why," stays specific, and balances praise with areas to improve. See the Feedback section of Fundamentals for the full principles. They apply to your Apprentices' builds just as they do everywhere else on the server.

Mentor Effectively

Your approach to mentoring matters as much as your building knowledge.

• Be welcoming and approachable. Apprentices are new and may feel uncertain. Introduce yourself warmly, and let them know you're there to help them succeed, not to catch them making mistakes.
• Adjust to their skill level. Some arrive with strong fundamentals and need mostly stylistic guidance; others need more foundational help with interiors, block variation, or spatial planning. Tailor your feedback to where they are, not where you wish they were.
• Encourage independence. As they progress, shift from prescriptive feedback ("change this block to that block") to guiding questions ("what do you think could improve the flow of this room?"). After several builds, they should be catching many issues themselves.
• Be patient with learning curves. Everyone learns at a different pace. If an Apprentice isn't improving or isn't receptive, document the pattern and discuss it with a Maester rather than getting frustrated.
• Communicate clearly and regularly. Respond to questions within a reasonable timeframe. If you'll be away for a while, let your Apprentices know and coordinate with a Maester to cover for you.

Document Concerns and Escalate to Maesters

If an Apprentice consistently ignores feedback, shows a negative attitude, or isn't progressing, don't wait until the end of probation to raise it. You're the primary guide, but Maesters oversee the program. Bring in a Maester when:

• An Apprentice consistently ignores feedback or shows a negative attitude
• You have concerns about promoting someone but aren't sure how to proceed
• An Apprentice needs an extension beyond the typical one-month period
• Conflicts arise that you can't resolve
• You need to step away and want someone else to take over
• You're ready to recommend someone for promotion to full Builder

Maesters trust your judgment and are there to support you. You're the eyes on the ground, but they make the final calls on promotions and extensions. Don't hesitate to reach out.

Becoming a Steward

Requirements

To apply for the Steward role, you should have:

• Been an active Builder for at least 5 months
• A strong understanding of WesterosCraft's building standards, feedback practices, and project management
• An active presence on Discord and in-game
• Good standing in the community with no recent moderation issues
• A genuine interest in mentoring and helping new builders succeed

You should understand both the building standards and the project management processes Apprentices will eventually engage with, and be someone who can teach, communicate clearly, and make others feel welcome.

How to Apply

It takes time, patience, and genuine care for others, but if you love this community and want to help it grow, the Steward role is a meaningful way to contribute. To apply, fill out this form.

Warden

Role Description

Wardens are the regional project managers of WesterosCraft. Named after the title given to rulers of major regions in Westeros, Wardens oversee entire regions, such as the Crownlands or the Iron Islands, ensuring projects there maintain stylistic consistency, historical accuracy, and quality standards.

A Warden is the primary point of contact for anyone working on a project in their region. The work centers on approvals, consistency, support, and coordination. Wardens don't micromanage every build or dictate every detail, but they do guide and check that everything follows the region's requirements and expectations. They're resources, reviewers, planners, and coordinators who help projects succeed while keeping an entire kingdom coherent.

How the role operates day to day:

• Wardens are the sole approvers of projects on the server. Maesters can see and participate in #warden-chat on Discord, but project decisions rest with the Wardens.
• Wardens coordinate and manage projects within their region's Discord channel (#stormlands-chat, #riverlands-chat, etc.), which is central to project management.
• Wardens flag builds that need updating by tagging projects in their region channel with the "Needs Updating" tag. Details on what needs updating live in the project discussion itself.
• Wardens organize City Project build days alongside the city's project leader.
• Wardens keep their region's plot in the Repository world organized in-game.

Responsibilities

Review and Approve Project Applications

Every Immersion, Canon, Server, and City project in your region requires your approval before work begins. You're confirming the applicant has done their canon research, that their plans are realistic, and that their vision aligns with the region's broader development. When someone submits an application for a location in your region, you:

• Review their research, plans, and test builds to ensure they understand the location's role in the world
• Assess whether their approach fits regional style and lore (a Dornish castle shouldn't look like a Northern keep)
• Approve it, request changes, or suggest a different approach
• For Server and City Projects, coordinate with a second Warden, since those require two Warden approvals (see Project Types)

Maintain Regional Style Consistency

Each region of Westeros has distinct architecture, materials, and cultural influences. The North uses stone and wood in harsh climates. Dorne has sun-baked adobe and open courtyards. The Reach has prosperous timber-framed towns and fertile farmland. A Warden guards these distinctions:

• Creating and maintaining regional style guides in the Repository world for project leaders to reference
• Ensuring new projects don't clash with established builds in materials, scale, or approach, keeping regional and sub-regional styles consistent
• Identifying when older builds need updates, and keeping your region's projects current on the Projects page (updates, redos, fostering)
• Keeping your region's area in the Repository organized as a source of good examples

You're not forcing everyone to build the same way. You're ensuring everything feels like it belongs in the same kingdom. Think of how game development works: the overall style is set at the top level and distributed to 3D artists. Builders, in this case, are the 3D artists.

Conduct Post-Approval Reviews

When a project leader marks their project complete, you conduct a final review before sign-off. They'll ping their Warden (and a second Warden for Server and City Projects) in their application thread. The review involves:

• Walking through the completed project in-game to assess quality, completeness, and consistency
• Checking that major elements from the application were implemented
• Providing feedback on anything that needs refinement before final approval
• Coordinating with the project leader to address any issues
• Signing off once you're satisfied, by posting your approval in the application thread

Most projects pass with minor feedback; occasionally larger revisions are needed. This step helps ensure every completed project reflects well on the region.

Support and Mentor Project Leaders

Project leaders will have questions, hit roadblocks, and need guidance. The Warden is their primary resource for regional matters:

• Answering questions about regional lore, geography, and culture that affect their builds, catching issues early
• Helping them navigate challenges like coordinating with neighboring projects or resolving style questions
• Providing feedback during the building process when requested or when you notice issues developing
• Connecting them with other builders who might help or collaborate

Becoming a Warden

Wardens are selected from experienced Builders who have demonstrated project leadership, deep regional knowledge, and strong community standing.

Requirements

• Led and completed at least one major Canon Project
• Active Builder for at least six months to a year
• Deep knowledge of the region's lore, geography, and culture from the books
• Strong understanding of project management processes
• Demonstrated ability to give constructive feedback
• Consistent activity on Discord and in-game

How to Apply

Warden positions are filled based on regional need, experience, and community fit. Not every application is accepted immediately, and you can reapply as you gain more experience.

Maester

Role Description

Maesters are WesterosCraft's community moderators and the guides who bring new members onto the server. Their two jobs are keeping the community healthy and shepherding applicants from their first post through to full Builder. Project approvals and project management sit with the Wardens, not Maesters.

Responsibilities

Community Moderation

Maesters enforce the Server Rules and Community Charter, keeping an eye on in-game chat, player behavior, and other spaces like Discord. They're usually the ones addressing problems, through friendly warnings, kicks, or bans, and they answer questions and watch for griefing or unauthorized changes.

When disputes between members surface, Maesters step in to mediate and make final rulings (or the Admin does). They also help develop the policies that govern the server. When server rules or community guidelines need revision, a Maester is part of that conversation.

Guiding New Members

Maesters own the start of the builder journey. They:

• Review and run builder applications, issuing build challenges and deciding when an applicant is ready for the Apprentice role
• Work alongside Stewards to supervise probationary periods
• Confirm promotions to full Builder once a Steward recommends an Apprentice

How Decisions Get Made

Maesters use collective decision-making for major server-wide issues. These usually require discussion among the group:

• Changes to server rules and building guidelines
• Promotions to Maester or Warden rank
• Major server initiatives and events
• Disciplinary actions for serious violations
• Server-wide policy decisions

Individual Maesters also carry some independent authority: any of them can open an investigation when they suspect a rule violation, and the role comes with advanced logging tools. For anything touching project approvals or regional building standards, point members to the Wardens and the Project Types page.

Day-to-Day Conduct

A Maester sets the tone for the community, so the role is as much about presence as authority:

• When you log in, say hi. Answer questions in chat and respond to Discord DMs. No builder's question should go unattended.
• If a builder needs help, address it, whether that's terraforming, a question about forum rules, or guidance on a current build.
• Encourage builders with both compliments and constructive criticism. It genuinely motivates people to improve. Set a good example.
• Stay relatively available on Discord and keep an eye on the staff channels. Let the team know if you're taking an extended break.

We also provide an anonymous feedback form for community members to raise concerns about staff behavior, policy, or other sensitive matters. Maesters review and discuss these submissions as they come in.

Handling Misconduct

You have discretion to mute, tempban, demote, or ban, but never act rashly or emotionally. Open a mod-report first, and for controversial or unpopular calls, start a private discussion with other Maesters before acting.

• With a Builder: stay calm and ask them to stop the behavior. If they don't heed the warning, use your best judgment: a mute, tempban, demotion, or ban. Some bans can be appealed after a stated period, decided case by case.
• With a Guest: give one warning. If they ignore it, ban them. Racist, sexist, or otherwise intentionally offensive behavior is a ban without warning.
• With another Maester: contact the Admin. If they're not available, try to resolve it privately or stay out of it.

Becoming a Maester

The Maester role is appointed by the Admin and existing Maesters rather than applied for. What current Maesters have in common:

• At least 6 months as a Builder, with real experience
• At least one completed Canon Project led from start to finish
• Consistent, positive community engagement and receptiveness to feedback
• A strong understanding of building standards and server lore
• A proven ability to give constructive feedback

Tools and Access

The role comes with the tools to do the job: advanced WorldEdit and Axiom terraforming tools, player management commands (kick, ban, mute), the private Maester Discord channel, project application channel moderation, and audit tools.

Terms and Stepping Down

This is a volunteer project, so Maesters can step down at any time. Just give the team a heads-up about extended inactivity so we can keep an active staff on the server. A member who goes completely dark for a long stretch without a word may be demoted for inactivity, and in cases of serious violations a Maester may be removed from the role.

Terraformer

Role Description

Terraformers are landscaping specialists on WesterosCraft. The role recognizes Builders who have developed advanced skill with our terrain tools, FAWE and Axiom, and are willing to lend that skill to others. Westeros is as much its mountains, coastlines, forests, and farmland as its castles, and good terrain is what makes a build feel like it belongs in the world. Terraformers help the wider builder base get that terrain right.

A Terraformer is not a project manager or an approver. The role is advisory and supportive. You're a resource other builders can call on when a project needs landscaping help, whether that's shaping the ground around a new keep, blending a build into its surroundings, or planning terrain for a larger area before construction begins.

Terraformers receive advanced access to features in FAWE and Axiom. That access comes with responsibility: these features are powerful, and misuse can affect large areas quickly, so use them carefully and within the scope of the projects you're helping with.

Responsibilities

Assist Builders With Landscaping

• Help project leaders and Builders plan and execute terrain work, from small grading around a single structure to larger regional landforms.
• Advise on technique and approach rather than taking every job over yourself. The goal is to raise the quality of terrain across the server and help others build their own skills, not to become the only person who can terraform.
• Respond to requests for terraforming help in [coordination channel TBD].

Maintain Tool Knowledge

• Stay current on FAWE and Axiom, including new features and best practices.
• Contribute to or help maintain the FAWE and Axiom guides so the wider community can learn the tools. See [Axiom and FAWE guides].

Becoming a Terraformer

Requirements

• Builder rank or above
• Demonstrated competency with our builder tools, especially FAWE and Axiom
• Ideally, at least one completed project
• Willingness to assist other Builders with their landscaping needs

How to Apply

Coming soon!