Policy Library
Policy · Events

Events Policy

The standards for Uros events, including player agency, canon impact, event powers, rewards, permanent consequences and cross-team review.

Status CurrentOwner Story AdminVersion 1.0Effective 29 September 2026Next review 29 March 2027

Key points

  • Create opportunities, not scriptsEvents should create situations for players to act within rather than force every scene toward one predetermined answer.
  • Temporary power stays temporaryEvent permissions, NPC powers and exceptional mechanics exist to run the event, not to benefit staff characters or friends.
  • Permanent consequences need reviewThe greater the lasting effect on canon, the map, economy or players, the greater the required cross-team approval.

Contents

01

Purpose of events

Uros events exist to create roleplay opportunities, introduce conflict or discovery, develop the world and give players meaningful chances to influence stories. Events should support the shared world rather than showcase staff characters or pre-selected winners.

02

Event scale & approval

Small events operating wholly within established lore can normally remain within Event Team authority. Events require additional review where they create major canon, permanently alter recognised locations, introduce significant factions or powers, affect server systems or create major economic or player consequences.

03

Player agency

Event staff may define the premise, risks and boundaries of an event, but reasonable player choices should be allowed to influence how it develops. Unexpected player actions should not be invalidated merely because they differ from the organiser's preferred script, unless they breach rules or exceed the event's agreed boundaries.

04

Event characters & powers

NPCs and event characters may use abilities, equipment or permissions needed for the approved event. Those tools must not be converted into persistent advantage for the staff member's normal character, faction or friends. Exceptional event powers should remain within the approved event context.

05

Builds & locations

Substantial event builds should be coordinated with Build. Temporary event spaces should normally be removed or restored afterwards unless they are separately approved to remain. Permanent event locations follow the normal Build and Lore approval standards.

06

Rewards & economy

Rewards should be proportionate to the event, its risk and ordinary server progression. Staff must not use events to provide excessive items, currency, profession progress or unique advantages to themselves, friends or favoured factions. Significant mechanical or economic rewards should be agreed in advance.

07

Conflict, PvP & moderation

Event conflict remains subject to the Uros Rules. Where an event is likely to generate significant PvP, contested outcomes or player disputes, Moderation support should be planned when an event is likely to need it. Event staff should not try to resolve serious moderation allegations while simultaneously defending their own event decisions.

08

Permanent consequences

Permanent changes to major lore, settlements, territory, important NPCs, the map or server systems require the approval appropriate to that change. An event does not bypass ordinary Lore, Build or Administration governance simply because the change happened through live roleplay.

09

Debrief & record

Significant events should record important outcomes, player decisions, permanent consequences, rewards and any follow-up needed from Lore, Build or Administration. This helps the world react consistently to what actually occurred rather than only to what was originally planned.

Document control & version history
v1.029 September 2026

Initial public Events policy, aligned with the Event Team SOP.

Cannot find what you need? Search the Policy Library, read the server rules, or contact staff.