Skip to content

Lifecycle of a Project

Lifecycle of a Project

Every project on WesterosCraft follows the same general path, whether it's a small Immersion build or a years-long City Project. The stages below describe how a project moves from an idea to a finished build on the map. Bigger projects mean more planning and stricter review, but the steps are the same.

Stage 1: Find a project

Browse the Projects Page and filter by status. You're looking for two kinds of opportunities:

  • Not Started — No one has applied yet. You'll plan everything from scratch.
  • Available — Previously started but now inactive, either abandoned or outdated. Existing plans and builds may give you a head start, but you'll need to evaluate what's worth keeping.

Pick something that matches your experience level. If this is your first project, start small — a Mini Build or Immersion Project. You can always take on bigger things later. Check the Project Types guide for eligibility requirements.

Before committing, talk to the Warden for that region. They'll tell you if there are constraints you wouldn't know about, like adjacent projects in progress or planned terrain changes.

Stage 2: Research

Dig into the source material. Look up every mention of your location in the books using tools like A Search of Ice and Fire or SearcheRR. Document what the text says explicitly and what it implies.

Study completed projects nearby to understand the regional style — materials, roof shapes, proportions, the general feel. Visit the Repository world in-game for curated style examples. Your project needs to fit its neighbors.

Think about worldbuilding: who lives here, what do they do for a living, what's the terrain like, what roads connect to this place, and why does this settlement exist where it does?

Read more: Application Guidelines | Project Fundamentals

Stage 3: Test builds

Build test structures at a test location or your builder plot, not at the final site. Tests prove you can execute your vision at the required quality level. Reviewers weigh tests heavily.

Build enough variety to cover what you'll actually need: different house classes, key structures, and anything unusual in your plans. One test house isn't enough for a village with a sept, an inn, and three classes of housing.

Common problems at this stage:

  • Style mismatch — Your tests look good on their own but don't fit the region. Study more approved examples before building.
  • Not enough variety — You'll need tests for each building type you're proposing.
  • Quality gap — Tests that are "fine" when the project type demands more. Server and City projects have higher bars.

Stage 4: Plan

Turn your research and tests into a plan. Good plans include:

  • Location — Boundaries, coordinates, terrain description
  • Layout — Where major elements go and how they relate to each other
  • Building specs — How many plots, what types (lower/middle/upper class, professions), how many Mini Builds
  • Special features — Terraforming needs, unique structures, infrastructure like roads or bridges

For Canon and Server projects, plans need more detail. For City projects, you'll need district breakdowns, style guides, and gradient guides before anything gets plotted. See Project Types for what's expected at each level.

Stage 5: Apply

Compile your research, tests, and plans into a single application document — most builders use Google Docs or a PDF. Submit it by creating a post in the appropriate regional forum under the #projects category in Discord.

Title your post: [Project Name] by [Your Username]

Include a link to your application, warp or coordinates to your test builds, and tag the relevant Warden and Maester.

See Application Guidelines for the full submission process and examples of successful applications.

Stage 6: Review and revision

Staff review your application and post feedback in your Discord thread. Most applications go through 1-3 revision rounds before approval — expect some back and forth.

Who approves depends on the project type:

Project TypeApproval RequiredImmersionOne Warden or MaesterCanonOne Warden and one MaesterServerOne Maester and one WardenCityOne Maester and one Warden

If your region has no active Warden, a second Maester fills that role.

Address feedback, update your application, and ping staff when you're ready for another look. If you're stuck on how to address something, ask — Wardens, Maesters, and experienced project leaders are all available to help.

Stage 7: Build

Once approved, set up on-site: create warps, plot out areas, and build your approved tests in their final locations. Then open plots for other builders.

How construction works depends on the project type:

  • Immersion and Canon — You lead the build, open OPEN plots for any Builder or Apprentice, and mark SPECIAL plots for builders who apply to you. Post in your Discord thread to recruit help and share progress.
  • Server — Same structure but with more frequent check-ins from Wardens and Maesters. Higher scrutiny on canon accuracy and polish.
  • City — Foundation work first (style guides, house examples, gradient guides), then district-by-district development with district leads. Community build days help move things forward. See the City Projects section in Project Types for details.

Throughout construction, keep building. Maintain the quality level from your application. Respond to feedback — authoritative feedback from your Warden or Maester must be addressed. Advisory feedback from other builders is worth considering but not mandatory.

If you need to step away, communicate with your Warden or Maester. Projects are considered abandoned after 4 months of inactivity with no communication. See Project Policies for details.

Stage 8: Completion review

When you've finished building, ping your Warden (and a Maester, for Canon and above) in your Discord thread to request a final review.

The reviewer will:

  1. Walk through the completed project in-game
  2. Check that what you built matches what you proposed
  3. Flag anything that needs refinement
  4. Sign off once satisfied, posting approval in your thread

Most projects pass with minor feedback. Occasionally larger revisions are needed before sign-off.

Once approved, your project status changes to Completed on the Projects Page. Your build becomes part of the map — and a reference for future builders studying regional style.