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.

Chapter 07
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.
Different scales of cooperation
The final naming remains open, but temporary teams, persistent social organizations, and specialized economic groups should not be treated as one interchangeable structure.
Players could group for a route, encounter, dungeon, escort, boss, gathering run, or other immediate objective without creating a permanent organization.
Members would share identity, ranks, communication, responsibilities, reputation, and longer-term goals across play sessions.
Players could coordinate services, procurement, market activity, or an approved shared treasury without acquiring authority over game rules.
Organization lifecycle
A clan becomes meaningful through accountable membership and repeated cooperation—not through an automatic land grant.
Create the organization identity, rules, founder authority, purpose, and initial membership policy.
Invite players, review applicants, manage capacity, and establish any probation or reputation requirements.
Assign ranks, permissions, specialist responsibilities, communication access, and approval thresholds.
Form parties, schedule goals, commission services, pool approved inputs, and build collective reputation.
Change leadership, remove members, resolve disputes, archive history, or wind down shared responsibilities.
What the organization controls
A clan record would define who belongs, who may act for the group, and which decisions require additional approval.

From organization to cooperation
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.
Flexible responsibilities
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.
Founders and officers could manage membership, approve policies, assign roles, and handle succession under visible rules.
Combatants, scouts, healers, explorers, and gatherers could coordinate nearby objectives and longer campaigns.
Minters, smiths, builders, enchanters, cooks, and other specialists could accept internal commissions without surrendering individual mastery.
Members could organize approved storage, procurement, schedules, contracts, deliveries, and service access.
The important boundary
A qualifying clan could attempt conquest and later operate a settlement, but those systems would maintain their own state, costs, permissions, and failure rules.
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
Individual identity and personal inventory should remain distinct from group authority.
Skills, reputation, personal inventory, currency, and owned NFTs would remain with the character unless an asset was deliberately committed to shared custody.
Inactivity, removal, dispute, or account loss would require time-delayed and auditable recovery rather than unilateral seizure.
Membership and permissions would close; group-held assets, contracts, and any operated territory would follow their own disclosed recovery and vulnerability rules.
Next chapter
See how qualifying groups could conquer a game cell, construct buildings, manage resources and local fees, maintain protection, and risk losing what they operate.