Build World & live world
The Build World is the normal development environment for substantial new builds, redesigns, major terrain work, Lore concepts and projects that need review. Direct live-world work should normally be limited to maintenance, approved minor changes, authorised deployments and genuine emergencies.
Proportionate review
The level of process should match the impact of the work. Small repairs should not require a committee, while major settlements or geography changes should not depend on a single person deciding and deploying them.
Restore missing or damaged elements to their intended state; normally handled by authorised Build staff.
Small decorative, interior or landscaping improvements with no material lore or player impact.
Substantial structures, landmarks, settlement additions or terrain work requiring Build review and Lore review where relevant.
Large, permanent or difficult-to-reverse changes requiring senior Build, Lore where relevant, and Administration approval.
When Lore review is required
Builds create implied lore even without a lore document. A giant ruined fortress, temple or destroyed city implies history, inhabitants and purpose. Lore review is required where a project materially affects established settlements, cultural architecture, recognised ruins, political areas, historical sites, geography, important routes or other established canon.
Lore-originated builds
When Lore supplies a concept, the brief should explain what must be represented. Build retains responsibility for scale, palette, architecture, composition, terrain integration, navigation, performance and physical implementation. Review should improve the project rather than transfer ownership away from its original creator without need.
Reworking existing builds
An existing build may be moved, copied or removed for rework where it falls materially below current standards, conflicts with approved lore, causes technical problems or blocks an approved project. Where practical, the concept and existing work should be preserved so it can be collaboratively improved.
Player areas & settlements
Staff should not alter player-owned areas simply because they believe they could build them better. Significant changes to active settlements or player investment require appropriate authority, consultation where practical and consideration of the roleplay consequences.
Deployment & rollback
Before a significant live deployment, authorised staff should confirm the approved version, target location and likely effect on nearby content. High-impact changes should have an appropriate schematic, backup or other recovery method. Staff should not rely on a single WorldEdit undo operation as the only recovery plan for a major deployment.
Emergency world changes
Immediate work may be performed where necessary to stop an exploit, repair serious damage, protect players from broken areas or address a technical risk. The change should be limited to what is necessary and documented afterwards where it was significant.
Approval record
Significant world projects should leave a clear record of the brief, required reviews, amendments and final approval. Where a project is materially changed after approval, affected approval gates should be revisited rather than assuming an earlier reviewer approved the new version.