Warden

Wardens are the regional project managers of WesterosCraft, overseeing entire regions such as the Crownlands or the Iron Islands and making sure 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 primary approvers of projects that get built on the server. Maesters or the admins can also influence project approvals, 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 where builders apply for projects. This involves frequent check-ins and communication with the builders responsible for projects in your region.

• Wardens organize project build days alongside project leaders for city or server builds or other events

• A region is run by one or two co-Wardens, who share the workload and cover for each other during absences.

• Wardens have moderation tools: they can kick and mute

• A Warden covers a single region and cannot be Warden of more than one at a time. You can hold the Maester role alongside Warden, though.

• A Warden may step in as a Steward only if they have previously held the Steward role; otherwise the two roles stay separate.

• Wardens aren't siloed. Each Warden owns a region, but you're encouraged to discuss plans and lend a hand across regions.

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)
• When you lead a project in your own region, another Warden approves it, or a Maester if no Warden is available

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 helps guard these distinctions:

• Creating and maintaining the 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

Wardens don't force everyone to build the same way. They ensure 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.

Pre-Plan Unstarted Projects

Wardens shape the big picture of their region before individual projects begin. For locations still marked Not Started, you can lay out the macro: where settlements, roads, and major landmarks sit, what industries fit the area, and the rough size and placement of towns. This top-down planning gives anyone applying for a project a clear reference to build from, and it helps builders and terraformers fill in the detail without having to invent everything themselves.

Hold the line between macro and micro:

• Wardens plan the macro: project locations, road networks, major landmarks, regional worldbuilding, assumed industries, and rough boundaries and sizes for settlements.
• Project leaders plan the mid-level: once someone takes on a project, they decide where the castle or manor goes, the specific settlements and their sizes, and which industries sit where. This detailed planning belongs to the project applicant.
• Builders and terraformers plan the micro: individual buildings, interiors, and fine terrain work.

The intent is to guide worldbuilding and set rough direction, not to set hard requirements or take creative ownership away from a project leader. Plans should stay flexible and adapt to a leader's vision once they apply. Pre-planning is not required for every project, but every project should at least be plotted on the map.

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. Selection is decided by the Admin together with the Maesters, at least to start. Because communication and managing others are central to the role, how you engage across the whole community is part of what is weighed.

Candidates are held to a quality threshold, not simply judged best of the current field. A region may go without a Warden for a while if no candidate of the right caliber is available, and that is fine. Each region has a maximum of two co-Wardens, who share the work and cover for each other during absences.

To apply, fill out the application form: Warden Application Form (opens in a new tab)