Organization design · No clan system is live

Chapter 07

Organize people.
Build trust.

Guilds and clans would be persistent player organizations: a way to recruit, assign responsibility, coordinate specialists, communicate, and govern shared activity. Membership would not itself create land, buildings, or tax authority.

Persistent membershipPlayer-defined rolesTerritory is a separate system

Different scales of cooperation

A party, clan, and trade guild would solve different problems.

The final naming remains open, but temporary teams, persistent social organizations, and specialized economic groups should not be treated as one interchangeable structure.

Party

A temporary field team

Players could group for a route, encounter, dungeon, escort, boss, gathering run, or other immediate objective without creating a permanent organization.

Clan

A persistent social organization

Members would share identity, ranks, communication, responsibilities, reputation, and longer-term goals across play sessions.

Trade guild

A specialist economic group

Players could coordinate services, procurement, market activity, or an approved shared treasury without acquiring authority over game rules.

Organization lifecycle

The group would persist beyond one play session.

A clan becomes meaningful through accountable membership and repeated cooperation—not through an automatic land grant.

  1. 01

    Found

    Create the organization identity, rules, founder authority, purpose, and initial membership policy.

  2. 02

    Recruit

    Invite players, review applicants, manage capacity, and establish any probation or reputation requirements.

  3. 03

    Organize

    Assign ranks, permissions, specialist responsibilities, communication access, and approval thresholds.

  4. 04

    Coordinate

    Form parties, schedule goals, commission services, pool approved inputs, and build collective reputation.

  5. 05

    Govern or dissolve

    Change leadership, remove members, resolve disputes, archive history, or wind down shared responsibilities.

What the organization controls

Ranks should grant explicit permissions—not vague power.

A clan record would define who belongs, who may act for the group, and which decisions require additional approval.

  • Membership, invitations, removal, rank assignment, and succession would be authoritative game state.
  • Communication channels, notices, event scheduling, and recruitment tools could support persistent coordination.
  • Shared spending, inventory, or treasury actions would need narrow permissions, logs, and recovery rules.
  • Specialist reputation would remain attached to the individual player even when work is commissioned through a clan.
  • Officers could coordinate eligible territory attempts, but the territory system would validate and execute them separately.
Adult adventurers and specialist artisans coordinate around a planning table inside a dark stone guild hall
Guild and clan organization conceptIllustrative · no organization system is live

From organization to cooperation

Ranks identify the group. DAO modules let it own and act together.

Clan membership, identity, chat, ranks, and ordinary permissions remain authoritative game state. A guild or town that needs shared economic rights could add reviewed DAO modules instead of trusting one officer's personal wallet.

  • Shared treasuries and eligible assets can use collective or share-defined ownership.
  • Contracts can commission specialists, suppliers, builders, guards, and other services.
  • Escrow can protect inputs and payment until milestones or verified results.
  • Member proposals and voting can govern budgets, rights, distributions, and town operations.
  • Personal inventory remains personal until the owner deliberately commits an asset.

Flexible responsibilities

The organization should reflect its players.

These are responsibility categories, not mandatory classes or fixed titles. A clan could define its own ranks while the server limits the permissions attached to them.

Leadership

Direction and accountability

Founders and officers could manage membership, approve policies, assign roles, and handle succession under visible rules.

Field operations

Parties and encounters

Combatants, scouts, healers, explorers, and gatherers could coordinate nearby objectives and longer campaigns.

Production

Craft and specialist services

Minters, smiths, builders, enchanters, cooks, and other specialists could accept internal commissions without surrendering individual mastery.

Logistics

Supply and communication

Members could organize approved storage, procurement, schedules, contracts, deliveries, and service access.

The important boundary

Membership creates eligibility—not territorial property.

A qualifying clan could attempt conquest and later operate a settlement, but those systems would maintain their own state, costs, permissions, and failure rules.

Joining a clan does not grant land ownership.

Territory is a server-controlled game cell, not an NFT or a right over the corresponding real-world place. Buildings, resources, upkeep, local fees, and takeover are explained independently.

Leaving and dissolution

The organization can end without erasing its members.

Individual identity and personal inventory should remain distinct from group authority.

Member exit

Personal progression remains personal

Skills, reputation, personal inventory, currency, and owned NFTs would remain with the character unless an asset was deliberately committed to shared custody.

Leadership failure

Succession needs a safe path

Inactivity, removal, dispute, or account loss would require time-delayed and auditable recovery rather than unilateral seizure.

Dissolution

Shared authority is wound down

Membership and permissions would close; group-held assets, contracts, and any operated territory would follow their own disclosed recovery and vulnerability rules.

Still to be decided.

  • Final distinction between guild, clan, party, and trade guild
  • Founding cost and minimum membership
  • Membership limits and multi-clan participation
  • Rank templates and custom permissions
  • Recruitment, reputation, and moderation tools
  • Alliance, diplomacy, betrayal, and war declarations
  • Shared treasury, storage, and contract safeguards
  • Leadership succession and dissolution recovery

Next chapter

Territory begins only after organization.

See how qualifying groups could conquer a game cell, construct buildings, manage resources and local fees, maintain protection, and risk losing what they operate.