BlueGit

timfa questward

Files

questward / tile_mmo_server_technical_design_v0.6.md

tile_mmo_server_technical_design_v0.6.md

tile_mmo_server_technical_design_v0.6.md 131.2 KiB Download Raw

--- title: Tile MMO Server Technical Design version: 0.12 status: proposed format: living-design-document ---

Tile MMO Server Technical Design

Version: 0.12 Status: Proposed architecture; intended to be iterated as implementation decisions are made. Scope: Authoritative Node.js/ECS backend, FrameworkV3-based game client (16×16 sprites, player-centered viewport), chunk/region streaming, SQLite persistence, admin world editor with per-chunk changelogs, player inventory and items, combat, player communication, banking/cheques, shopkeepers, marketplace/economy systems, skill progression, automatic restart/update orchestration, and future player scripting hooks.

1. Design goals

  • Support a large tile-based MMO world without simulating unused areas.
  • Keep the server fully authoritative: clients send actions and

intentions, never authoritative state changes.

  • Authenticate accounts via auth.timfalken.com (with an admin-<n> stub

until that service is live). An account may have unlimited characters, one in the world at a time, with delayed deletion and an inheritance bank tab.

  • Use ECS composition for entities and systems, while using chunks and

regions for spatial ownership and simulation lifecycle.

  • Allow simulation work to scale across Node.js workers and permit

entities to cross worker-managed region boundaries safely.

  • Keep client replication small: a player receives only the current

16×16 chunk and the eight neighbouring chunks.

  • Keep authored world data separate from ephemeral simulation state.
  • Persist only entities that explicitly need persistence; ordinary

spawned mobs disappear when their chunk is unloaded.

  • Avoid constant chunk writes. Normal chunk persistence occurs on

unload; graceful shutdown is implemented as a forced unload of all resident chunks.

  • Provide an admin-only graphical world editor for painting tiles,

opening or closing chunks, and placing/configuring spawners, with a per-chunk changelog of who changed what and when. Unedited chunks are grass-only and closed.

  • Automatically schedule a graceful midnight restart when live code or

authored world data changes, with an admin-triggered immediate restart path.

  • Reserve a clean control abstraction for a later sandboxed player

scripting language without requiring the scripting system in the initial release.

  • Build the player-facing client on the shared FrameworkV3 library, vendored

as a git submodule and built first so game-specific client code can layer on top of it, while keeping the server-side ECS an implementation detail of the backend. All world sprites are 16×16 pixels. The play viewport stays centered on the local player.

  • Authoritative movement is tile-to-tile at a global walk/run cadence

(default walk 2 tiles/s, run double), not a per-mob speed. Admins edit that cadence and other tick timers in a world-settings modal. World calendar time is server time minus 1200 years. At night the client darkens unlit tiles; static light reach is baked by raycast when a chunk is saved.

  • Give every player a 32-slot inventory in which stackable items occupy a

single slot, and treat dropped items as temporary, non-blocking ground objects rather than tile occupancy.

  • Make ordinary communication spatial rather than global: nearby speech is

progressively degraded by distance, while long-distance exchange is a physical item or currency delivery by carrier pigeon. A letter is simply a paper item with player-written text.

  • Support persistent player groups without turning them into an instant

long-distance chat channel.

  • Provide a shared, unlimited player bank near the marketplace, with later

banks all reading the same vault, plus bearer cheques and free pigeon deposits.

  • Make the central marketplace an order-matching service rather than a public

auction list, with durable escrow and asynchronous pigeon delivery.

  • Keep the economy predominantly player-driven: most ingredients are gathered,

final goods are normally crafted by players, and finished-item drops come from enemies/bosses rather than ordinary NPC shops.

  • Let every combatant — players and other mobs — attack. Melee requires an

adjacent tile including diagonals; ranged attacks and spells use the range of the weapon or spell. A hit roll uses the weapon skill; damage uses Strength, Dexterity or Mind. Attack XP is split equally between those two skills.

  • Let shop NPCs sell items at a seed value that lerps toward the last

player-market sale price over a configurable duration (default one hour), with a hidden per-shop discount. Item inspection shows name, description, origin and the undiscounted current value, refreshed at most once per minute.

  • Use skill-based progression with no player classes. Every gameplay action is

governed by a skill and awards XP to that skill when successfully performed. Combat is the explicit dual-skill exception: hit skill and damage skill share the XP.

2. Core world model

2.1 Spatial hierarchy

World └── Region: 4 × 4 chunks └── Chunk: 16 × 16 tiles └── Tile

One chunk contains 256 tiles. One region is 64×64 tiles and contains 16 chunks (4,096 tiles). World tile coordinates are canonical; chunk and region coordinates are derived from them.

chunkX = floor(tileX / 16) chunkY = floor(tileY / 16) regionX = floor(chunkX / 4) regionY = floor(chunkY / 4)

If negative world coordinates are allowed, use true floor division rather than JavaScript integer truncation.

2.2 Three independent spatial states

The design deliberately separates region residency, chunk simulation, and client visibility.

ConcernUnitMeaning
ResidencyRegionWhether the region and its required chunk data exist in server memory and have a worker owner.
SimulationChunkWhether ECS systems actively simulate entities and gameplay in this chunk.
VisibilityChunkWhether a specific client is subscribed to the chunk and receives its snapshot/deltas.

2.3 Region states

UNLOADED ↓ load RESIDENT ↓ no residency references + grace period UNLOADED

A resident region is assigned to exactly one simulation worker. An unloaded region has no active ECS representation.

2.4 Chunk states

DORMANT ⇄ SIMULATING

A dormant chunk can remain resident in memory while normal gameplay systems ignore it. A simulating chunk participates in movement, combat, AI, spawners and other active systems.

3. Tile layers and occupancy

3.1 Ground layer

Every tile has a ground type. Ground is visual only. It does not by itself block movement, cause collision, or create gameplay behaviour.

TileGround { groundTypeId: GroundTypeId }

3.2 Block layer

A tile may also contain one block. The block is the actual world object standing on the tile and can determine collision and behaviour.

TileBlock { blockTypeId: BlockTypeId \| null config?: BlockConfig }

Examples include walls, doors, trees, torches and other lights, containers, spawners, marketplace counters and banks. Block definitions determine properties such as passability, interaction behaviour, whether a block participates in navigation, and whether it emits light (lightRangeTiles).

3.3 MOBile entities

A moving game entity — player, enemy, animal, NPC or any other mobile actor — is represented by an ECS entity rather than being painted into the static tile map. A mobile entity may inhabit a tile in addition to the tile’s ground and block layers, subject to collision rules.

Tile ├── Ground (visual layer) ├── Block (static/world-object layer; optional) ├── Ground item stacks (ephemeral, non-blocking) └── Mobile ECS entities (dynamic occupancy)

The spatial chunk index maintains which mobile entity IDs currently occupy each tile, allowing collision, nearby queries and replication without scanning the global ECS. Ground item stacks are indexed per tile as well, but they never contribute to movement collision and never prevent a mobile entity from standing on that tile.

4. ECS model

4.1 Entity composition

Entities are numeric identities plus components. Behaviour comes from systems querying component combinations rather than deep class inheritance.

Player Position Movement Health Combat Skills Inventory Currency Equipment Player NetworkIdentity ChunkLoader Persistent

Ordinary enemy Position Movement Health Combat Skills Creature AI

Named NPC Position Movement Health NPC AI Persistent

4.2 Global identity versus local ECS handle

Use a globally meaningful EntityId for storage, networking and cross-worker transfer, and a compact worker-local EntityHandle for hot ECS arrays. A transferred entity keeps its EntityId but may receive a different local handle on the destination worker.

4.3 Recommended initial components

CategoryComponents
SpatialPosition, Movement, Path, Collision
LivingHealth, Combat, Creature, Mob, Skills
PlayerPlayer, NetworkIdentity, Inventory, Currency, Equipment
AIAI, Target, BehaviourState
LifecycleChunkLoader, Persistent, SpawnOrigin
PresentationRenderable / Appearance
Future controlController / ScriptController / OfflineUntil

5. ChunkLoader and simulation activation

5.1 Generic ChunkLoader component

World activation is component-driven rather than player-specific. Any entity may carry a ChunkLoader component that says “keep the surrounding world resident and simulated”.

ChunkLoader { simulationRadiusChunks: 1, regionLoadRadius: 1 }

A normal player can therefore stimulate a 3×3 chunk area while keeping the surrounding 3×3 regions resident. Bosses, travelling NPCs, machines, scripted actors or administrative anchors can use the same mechanism.

5.2 Reference counting

Chunk simulation and region residency should use reference counts. Overlapping loaders increment the same references; leaving decrements them. A chunk sleeps only when its simulation reference count reaches zero. A region becomes eligible for unload only when its residency references reach zero.

5.3 Grace period

After the last residency reference disappears, retain the region briefly before unloading. This prevents repeated SQLite reads and writes when a loader oscillates around a boundary. The delay should be configurable.

6. Chunk lifecycle and persistence

6.1 No periodic chunk saves

Normal gameplay does not periodically rewrite loaded chunks. A chunk is saved as part of the unload path only.

Resident chunk ↓ last residency / forced shutdown unload Prepare unload ↓ Persist required chunk state once ↓ Persist required entities ↓ Remove ECS/runtime representation

A graceful server restart does not introduce a second save mechanism. It force-unloads every resident region/chunk, so the normal unload persistence path remains the single source of truth.

6.2 Persistent versus non-persistent entities

Persistence is an entity property, not a property of the chunk or spawner. An entity with Persistent is serialised when its owning chunk/region unloads. A non-persistent entity is simply discarded.

Non-persistent wolf spawn → simulate → chunk unload → disappear

Persistent named NPC load → simulate → chunk unload → save → recreate when area loads

6.3 Persistent is independent of ChunkLoader

These traits must remain independent. A persistent entity does not automatically keep its area active, and a ChunkLoader does not automatically become persistent.

7. Storage architecture

7.1 Separate authored world and runtime state

Use two SQLite databases with different responsibilities.

DatabaseResponsibility
world.sqliteAdmin-authored ground tiles, block tiles, light maps, world settings, spawner configuration, per-chunk editor changelogs, world revisions and world metadata.
state.sqliteAccounts, characters, inventories, carried currency, character vaults, inheritance tabs, cheque reservations, skills, groups, courier cargo/transit, unexpired ground items, market orders/escrow/trades, per-item last player-market sale, persistent ECS entities, offline-script state, optional persistent runtime chunk overrides, and other durable live-game state.

This prevents editor authoring changes from becoming entangled with live player/entity persistence.

7.2 Chunk writes in runtime state

If initial gameplay does not allow permanent tile/block modification, runtime chunks require no writes at all. If permanent runtime world changes are later added, dirty chunk overrides are held in memory and written to state.sqlite only when that chunk unloads. Shutdown uses forced unload and therefore follows the same rule.

7.3 Central persistence service

Simulation workers should not independently compete for SQLite writes. A persistence service owns the write connection, batches transactions, and receives logical save requests from workers.

Simulation workers │ save/unload messages ▼ Persistence service │ ▼ SQLite (WAL)

Live ECS state remains authoritative while loaded; SQLite is durable state, not a per-tick synchronisation mechanism.

8. World authoring and revision model

8.1 Admin-only world editor

The server includes a separate admin-only world editor UI. It is not part of the normal player client.

  • Display one 16×16 chunk at a time.
  • Provide Up, Down, Left and Right navigation buttons that move the

editor exactly one chunk in that direction.

  • Show the current chunk coordinates prominently, and whether the chunk

is open or closed.

  • Toggle the current chunk open or closed. Closed chunks remain visible

to nearby players but cannot be entered.

  • Allow painting a ground type on a tile.
  • Allow painting, replacing or erasing the block type on a tile.
  • Render both layers together so the block appears on top of the ground.
  • Do not display ordinary mobile entities as editable map paint.
  • Allow selecting/configuring special block types such as Spawner, Bank,

Marketplace and light-emitting blocks (lightRangeTiles).

  • Open a world settings modal for global tick timers and constants

(movement cadence, shop lerp duration, drop lifetime, and other values listed in section 8.5).

  • Provide a night-to-day slider that only previews lighting; it does

not change live world time. Preview uses the same baked light maps as play, including light that reaches this chunk from neighbouring chunks.

  • Later: allow configuring ground-item spawners analogously to mob

spawners. Exact item tables remain a later content decision.

  • Save changes through an authenticated admin API; the browser never

opens SQLite directly.

  • Show that chunk's changelog: a chronological list of saves, each with

which admin made the edit, when, and a bullet-point diff of the change.

The editor camera is not locked to a player character. It frames the currently selected chunk. This is the only intended exception to the player-centered play viewport in section 21.4.

8.2 World editor save behaviour

Saving a chunk or world settings writes the authored result to world.sqlite. It does not live-patch the currently running simulation. Instead, the change creates or updates a pending world revision and schedules a server restart for the next server-local midnight.

The running game remains pinned to the world revision selected at its own startup. This avoids a dangerous mixed state where some loaded chunks use old authored data and newly loaded chunks use newer editor data.

8.3 Versioned authored chunks

A practical schema is to give every editor change a monotonically increasing world revision. The game process pins one active revision for its entire lifetime. Chunk lookup selects the latest authored version not newer than that pinned revision.

world_revisions revision_id created_at created_by status // pending / active / superseded

world_chunk_versions chunk_x chunk_y revision_id open // player-enterable; default false until set data_blob

world_meta active_revision pending_revision

world_settings revision_id settings_blob // walk speed, tick timers, shop lerp, drop TTL, ...

world_chunk_edit_log log_id chunk_x chunk_y revision_id editor_admin_id edited_at diff_entries // structured bullets for this save

On the next planned restart, startup promotes/selects the latest valid pending revision before world loading begins.

8.4 Per-chunk changelog

Every successful chunk save appends one changelog record for that chunk. The record is durable in world.sqlite and is not gameplay state.

The server diffs the newly saved chunk against the previous authored version of that same chunk (the latest world_chunk_versions row for those coordinates that this save replaces). Unchanged tiles produce no bullets. Each changed tile becomes one of:

- Ground at X, Y changed from Prev to New.
- Block <type> placed at X, Y.
- Block at X, Y changed from Prev to New.
- Chunk opened.
- Chunk closed.

X, Y are world tile coordinates. Prev / New / <type> are the ground or block definition display names. A block paint on an empty block layer is a placement. Replacing one block type (or its config, such as a spawner) with another is a change. Erasing a block is a removal. Ground is never absent; a ground paint is always a change from one type to another.

The editor UI lists records newest-last or newest-first consistently, each headed by admin identity and timestamp, with that save's bullets underneath. The changelog is an audit trail, not an undo stack. Undo/redo remains an open editor-UX decision. Derived light maps are not changelog bullets; they are regenerated on save (section 8.6).

8.5 World settings

Global gameplay constants live in authored world_settings for the world revision. They are not per-mob and not client-authored. Admins edit them from a modal in the world-editor UI. Saving the modal writes into the pending world revision and schedules the same midnight restart as a chunk save. The running process keeps the settings it loaded at startup.

Minimum initial settings and defaults:

WorldSettings
- walkTilesPerSecond          // default 2
- simulationTickHz            // default 20; implementation default, still a setting
- shopPriceLerpDuration       // default 1 hour
- groundItemDespawnDuration   // default 10 minutes
- regionUnloadGracePeriod     // configurable grace after last residency
- defaultGroundTypeId         // grass used for never-edited chunks
- characterDeletionDelay      // default 24 hours

Running is always double walking speed. It is not a separate per-entity field. From walkTilesPerSecond:

runTilesPerSecond   = walkTilesPerSecond * 2     // default 4
movementTickHz      = runTilesPerSecond          // default 4 Hz
walk: commit a tile every 2 movement ticks
run:  commit a tile every 1 movement tick

All ground mobiles — players, enemies, NPCs — use this same cadence. A mob definition does not set move speed. Gait (walk | run) is the only per-entity choice; it selects every-other vs every movement tick.

Other tick-duration constants that already exist in this document (shop lerp, ground-item despawn, residency grace, and later ones of the same kind) are edited here rather than hardcoded. Adding a new global timer means adding a field to WorldSettings and a row in this modal.

8.6 Baked lighting

Light from authored blocks is precomputed when a chunk is saved, not raytraced every simulation tick.

A block definition may set lightRangeTiles > 0. That tile is a static light source. Light travels only through passable tiles (the same passability as walking). Ground type does not block light. Mobiles and ground items do not block light.

For every tile within a source's range, the baker runs a simple grid raycast (for example Bresenham through tile centres). If the ray hits an impassable block before the destination, that source does not light that tile. A tile is lit if any source can reach it. Light does shine across chunk boundaries.

Saving a chunk rebakes:

1. that chunk's 16×16 light map, and 2. every neighbouring chunk that could be affected (chunks within the maximum lightRangeTiles of the saved chunk).

Neighbor rebakes use light sources and walls from the pending revision, including the chunk just saved. Those neighbor light maps are written into the same pending revision so play never mixes old and new lighting.

The light map is stored in the chunk data_blob (a 16×16 reachable-or- not mask, optionally with distance to the nearest reaching source). It is replicated to clients in CHUNK_SNAPSHOT / CHUNK_DELTA.

Runtime door open/close does not rebake static light unless a later iteration adds live lighting. Baked light is authored geometry.

The editor night-to-day slider interpolates preview ambient from full night (dark except baked-lit tiles) to full day (no ambient darkening). It does not persist and does not change server/world clock.

8.7 Default chunks and open / closed

A chunk the editor has never saved does not exist in world_chunk_versions. At runtime it is synthesised as:

  • every tile defaultGroundTypeId (grass),
  • no blocks,
  • closed,
  • no baked lights.

The world is therefore an infinite grass field until admins paint it, and players cannot walk onto it until an admin opens the chunk.

Closed chunks can still appear in a player's 3×3 view. They cannot be entered: MOVE_TO, pathfinding, spawning, and other player-entry actions treat every tile in a closed chunk as impassable. Visibility and lighting previews are unchanged.

Open chunks are the playable map. Opening or closing is an authored chunk flag, saved with the pending revision like paint.

Spawners in a closed chunk do not spawn. Ground movement, including AI, does not step into a closed chunk. If a future bug or admin tool places an entity there, it can still be replicated to observers, but players cannot walk in after it.

9. Spawner blocks

9.1 Spawner data

A Spawner is a block in the authored block layer, with per-instance configuration stored as part of the chunk data.

SpawnerConfig { spawnerId: SpawnerId, mobTypeId: MobTypeId, maxAlive: number, spawnRangeTiles: number }

Additional parameters such as minimum/maximum spawn delay can be added later without changing the core model.

9.2 Spawner editor

Selecting a Spawner tile in the world editor opens a configuration panel containing at minimum: mob type, maximum alive count and spawn range. Validation happens server-side before the pending world revision is written.

9.3 Spawned entity persistence

The spawner never decides whether its mob is persistent. The mob definition/archetype does. When the spawner creates an entity, the entity receives Persistent only if that mob type is defined as persistent.

MobDefinition: deer persistent = false

MobDefinition: named_guard_captain persistent = true

9.4 SpawnOrigin

Spawned mobs receive a SpawnOrigin component referencing the spawner. This lets maxAlive count only entities belonging to that spawner and avoids expensive geometric searches.

SpawnOrigin { spawnerId: SpawnerId }

For non-persistent mobs, disappearance on chunk unload naturally decreases the count. For persistent mobs, SpawnOrigin is persisted so the spawner can recognise an existing persistent instance even after it has moved or been unloaded elsewhere. A lightweight persistence index by spawnerId prevents duplicate persistent spawns.

9.5 Spawner simulation

SpawnerSystem runs only while the spawner’s chunk is simulating and open, and at a much lower frequency than movement. A spawn candidate must satisfy block collision, bounds, an open chunk, and mobile-occupancy rules. Ground type does not affect passability unless a later gameplay system explicitly introduces a separate rule for it.

9.6 Future ground-item spawners

Some items will later spawn naturally on the ground, using a world-editor block analogous to a mob spawner. Those spawned stacks should use the same non-blocking ground-item representation as player drops, but their lifetime, respawn and maxOnGround rules belong to the spawner configuration rather than the 10-minute player-drop timer.

Exact item lists, harvest interactions and spawner parameters are later content decisions and do not block the inventory/bank model.

10. Startup and loading order

Loading order is explicit so authored world state exists before persistent entities are instantiated into it.

> 1. Start process and load configuration, including server time > zone and storage paths. > > 2. Open world.sqlite and validate/migrate its schema. > > 3. Select/promote the world revision to use for this process and > pin it for the lifetime of the process. > > 4. Load static registries: ground definitions, block definitions, > item definitions, material definitions, spell definitions, mob archetypes and component serializers. > > 5. Open state.sqlite and run runtime-state migrations. > > 6. Start the persistence service, durable domain services (such as courier, bank, market and shop-price services when enabled), region coordinator and simulation workers. > > 7. Load the index of persistent entities that themselves require > world activation (for example persistent ChunkLoaders or future > offline scripted players). > > 8. For each required region, load authored chunk data from the > pinned world revision first. > > 9. Apply any durable runtime chunk override state, if the game > supports such modifications. > > 10. Instantiate persistent entities into the already-created > world/chunks. > > 11. Recalculate ChunkLoader references and begin chunk simulation. > > 12. Only after the world reports READY does the gateway accept > normal player logins.

This ordering solves the bootstrap problem for persistent entities that keep their own chunks active: a compact persistence index can locate them without first loading the entire world.

11. Simulation workers and region ownership

11.1 Ownership invariant

Exactly one worker authoritatively owns a region at any instant. Every authoritative entity belongs to the worker that owns the entity’s current region.

11.2 Coordinator

A central region coordinator maintains RegionId → WorkerId and assigns/migrates regions based on actual measured simulation effort, while preferring neighbouring regions on the same worker when load permits.

11.3 Work measurement

  • Average and high-percentile tick execution time.
  • Number of simulating chunks.
  • Number of active entities and AI entities.
  • Pathfinding work and queued searches.
  • Cross-worker boundary message volume.
  • Backlog / tick lateness.

Actual time spent simulating is more important than raw player count or raw region count.

11.4 Node.js implementation

Start with Node.js worker_threads for simulation workers. Keep mutable ECS worlds isolated per worker and use message passing between them. Do not begin with a shared mutable ECS in SharedArrayBuffer.

12. Cross-worker communication

12.1 No remote mutation

A worker may inspect a limited read-only representation of neighbouring entities but never directly mutates authoritative state owned by another worker.

12.2 Border ghosts

Neighbouring workers can exchange compact border/ghost entity data for nearby interaction and AI: EntityId, position, collision footprint, type and minimal combat metadata. Ghosts are not full ECS entities and are never authoritative.

12.3 Remote actions

Worker A goblin targets Player 42 (owned by Worker B) Worker A → REMOTE_ACTION(attack intent) → Worker B Worker B validates range/state and applies authoritative result

12.4 Entity transfer

When an entity crosses from a region owned by Worker A into one owned by Worker B, ownership is handed off at a simulation tick boundary using a sequence-numbered transfer protocol. There is never more than one authoritative copy.

A: prepare transfer B: validate / accept A: freeze at handoff boundary B: instantiate authoritative entity at effective tick Coordinator: update ownership mapping A: remove authoritative copy

13. Server tick and stimulation

13.1 Fixed simulation tick

Use a fixed server simulation tick. The default is 20 Hz (50 ms), stored as WorldSettings.simulationTickHz. This is not a protocol promise.

Movement does not commit a new tile on every simulation tick. See section 13.4.

1\. Drain validated incoming commands 2. Apply completed worker/entity transfers 3. Recalculate activation changes 4. Movement / collision 5. Combat 6. Scheduled AI 7. Scheduled spawners/environment, including ground-item expiry in simulating chunks 8. Produce cross-worker messages 9. Produce client replication deltas 10. Queue unload/persistence work

13.2 Different system frequencies

Not every ECS system should run every tick. Ground movement commits only on the global movement cadence (section 13.4). AI decisions, target searches and spawner checks can run at lower frequencies. Sleeping chunks are not “slow ticked”; they are omitted from normal simulation.

13.3 Timestamp-based inactive progression

Long-lived timers such as growth, cooldowns, ground-item expiry and shop price lerps should store future timestamps where possible. When an area wakes, the system catches up from the timestamp instead of executing missed ticks. An expired ground item is discarded on catch-up without ever reappearing. Shop and tooltip prices are evaluated from last-sale timestamps when observed; they are not ticked. Durations such as shop lerp and ground-item despawn come from WorldSettings, not from hardcoded literals in systems.

13.4 Global movement cadence

All ground-moving entities share one walk speed and one run speed.

  • Default walk: 2 tiles per second (walkTilesPerSecond).
  • Run: always double walk (default 4 tiles per second).
  • Movement ticks fire at runTilesPerSecond (default 4 Hz).
  • Walk: the entity may advance one path tile on every other movement

tick.

  • Run: the entity may advance one path tile on every movement tick.

Mobs do not define their own move speed. Movement.gait is walk or run. Players send SetGait. AI may set gait; it still uses the global cadence. Flying pigeon transit is not this cadence; it keeps its own route clock.

If the path is blocked on a movement tick, the entity stays on its tile and retries on a later legal tick. Occupancy, combat range and pickup always use the last committed tile.

13.5 World calendar time

World time is server time 1:1, in the same configured IANA zone used for midnight restarts, with 1200 years subtracted from the calendar date. A server clock of 24 Aug 2026 21:00 is world 24 Aug 826 21:00. Clock-of-day, including night, therefore matches the host's zone.

The gateway includes current world time (or server unix time plus the year offset) in the status sent to clients so shading does not depend on the player's device clock. Lighting is presentation; combat and movement do not wait on the day/night overlay.

14. Client gateway and authority

14.1 Stable connection ownership

Client WebSocket/TCP connections belong to a gateway rather than simulation workers. When the player crosses into a region owned by another worker, the socket stays connected to the same gateway; only internal routing changes.

14.2 Client commands are intentions

A client sends commands such as MoveTo, Interact, Attack, UseItem, EquipItem, UnequipItem, SelectSpell, SetGait, DropItem, PickupItem, BankDeposit, BankWithdraw, BuyFromShop or SendPigeon. The authenticated account determines the actor; after character select, commands apply to that account's active character. The client never supplies an authoritative resulting position, health value or inventory result.

14.3 Input queue

Socket handlers validate message shape and enqueue commands. Simulation workers consume commands at tick boundaries. WebSocket callbacks do not mutate ECS state directly.

14.4 Authentication

Live login uses auth.timfalken.com. The game server never stores a password. It receives an authenticated account identity (and email) from that service and maps it to a durable accountId in state.sqlite.

Until auth.timfalken.com is available, the gateway uses a stub identity: each new connection is admin-<n>, where n is the number of currently connected clients including this one (the first connection is admin-1). Stub accounts are treated as admins so the world editor can be used during development. Stub accounts have no email; deletion “emails” are logged instead of sent.

When real auth ships, the stub is removed. Admin rights come from that service, not from the admin- name prefix.

An account may have only one active play session at a time (one character in the world).

14.5 Characters

An account has unlimited characters and plays one at a time. First login with no characters must create one before entering the world. Later logins show a character-selection menu: create, choose, mark for deletion, or cancel deletion.

Initial character setup (may change later):

CreateCharacter
- firstName     // not globally unique
- lastName      // unique surname, owned by this account
- sex           // male | female

Rules:

  • Last names are globally unique. The first character to take a surname

claims it for that account. The same player may reuse that last name on their other characters. Another account cannot use it.

  • First names need not be unique globally.
  • For a given account, firstName + lastName must be unique among

characters that still exist (including those pending deletion).

  • Uniqueness is case-insensitive; display uses the casing the player typed.
Account
- accountId
- authSubject               // from auth.timfalken.com, or stub admin-<n>
- email?                    // from auth; absent on stub
- surnameClaims[]

Character
- characterId
- accountId
- firstName
- lastName
- sex
- deletionScheduledAt?      // null if not deleting
- inventory, equipment, currency, vault, skills, ...

The in-world ECS player entity is a character, not the account.

14.6 Character deletion and inheritance

From character select, the player may mark a character for deletion.

  • The character cannot be played while deletion is pending.
  • Permanent delete happens after characterDeletionDelay (default **24

hours**). Until then the player may cancel.

  • The server always notifies the account email when deletion is

marked (and should notify again on cancel and on actual delete). Stub auth logs the message instead.

  • On permanent delete, the name pair is freed. If this account has no

remaining characters with that last name, the surname claim is released.

  • Before the vault is moved, BankService voids outstanding filled

cheques issued by this character (reservations return to the vault).

  • All items in inventory, equipment, carried currency, and the character

vault are moved to that account's inheritance bank tab.

Any living character of the same account may, at a bank, claim inheritance stacks (and currency) into that character's own vault. Claiming is a move from the account tab to the character vault, not a second copy.

15. Client chunk subscription and replication

15.1 3×3 visibility

A player receives the current chunk and the eight surrounding chunks, a maximum viewport of 48×48 tiles. Neighbouring closed chunks are still sent so scenery remains visible; the player simply cannot walk onto them.

┌───┬───┬───┐ │ V │ V │ V │ ├───┼───┼───┤ │ V │ P │ V │ ├───┼───┼───┤ │ V │ V │ V │ └───┴───┴───┘

15.2 Incremental subscription changes

Crossing one chunk east subscribes only the three newly visible eastern chunks and unsubscribes only the three old western chunks. The rest of the 3×3 view remains subscribed.

15.3 Snapshots and deltas

Initial subscription sends a CHUNK_SNAPSHOT containing authored/runtime tile state, currently visible entities and unexpired ground item stacks. Afterwards, revisioned CHUNK_DELTA messages report tile changes, entity spawn/move/change/despawn events and ground-item appear/change/despawn events. Full chunks are not retransmitted every tick.

Entity move events carry the new integer tile and the current gait so the client can lerp over the walk or run interval. They do not carry a fractional in-between position. Smooth walking is a client visual lerp (section 21.5), not part of the replication payload.

Chunk snapshots include the baked light map (section 8.6).

Visible equipment is replicated as a compact appearance payload (body sprite plus worn overlay layers and recolour parameters), not as the entity's full inventory. Nearby clients can draw another player's armour without receiving their bags.

15.4 Visibility can span workers

The gateway can source visible chunks from multiple workers. A player may be authoritative on Worker A while one or more of the eight neighbouring visible chunks are owned by Worker B. Client visibility must never force simulation-region reassignment.

16. Click-to-move and A\* pathfinding

16.1 Command flow

Client: MOVE_TO(tileX, tileY) ↓ Gateway validates/authenticates ↓ Owning worker validates target ↓ A\ calculates authoritative route ↓ Path component attached/updated ↓ MovementSystem advances the entity one tile at a time* on the global walk/run cadence (section 13.4)

Authoritative Position is always an integer tileX, tileY. The server does not store a sub-tile location for walking mobiles. When a movement tick allows this gait to step, MovementSystem commits the next path tile in a single jump. Combat, occupancy, pickup and interaction all use that committed tile.

Flying pigeons still ignore the ground navigation grid, but their replicated ECS position is likewise a tile. The transit clock determines which tile they occupy at a given time; the client may lerp the sprite between those tiles like any other mobile.

16.2 Initial A\* implementation

For normal player clicks within the visible 3×3 chunks, the search space is at most 48×48 = 2,304 tiles, so conventional A\* is a strong starting point.

  • Binary heap priority queue for the open set.
  • Manhattan heuristic for four-direction movement; octile heuristic if

diagonal movement is later allowed.

  • Reusable typed-array or pooled search buffers for hot paths to reduce

allocation and garbage collection.

  • Rate-limit path requests per player and avoid recalculation every

tick.

  • Use block passability, open-chunk bounds, and dynamic occupancy;

ground is visual only. Tiles in closed or never-edited chunks are not legal path targets for players.

16.3 Navigation revisions

Each chunk maintains a navigation revision that increments when a movement-affecting block changes. A path records the relevant revisions. Static geometry changes can invalidate paths; temporary mobile occupancy normally causes a short wait or small local re-path rather than rebuilding every path.

16.4 Long-distance extension

If long-distance autonomous travel is added later, introduce hierarchical pathfinding: region graph → chunk portals/edges → local tile A\*. The client movement command interface does not need to change. Server movement remains discrete tile steps; only the path length changes.

17. Automatic update and restart scheduler

17.1 Restart triggers

A graceful restart is scheduled for the next midnight in configured server-local time when either of these conditions occurs:

  • A new commit is detected on origin/master. The master branch is the

live branch.

  • An administrator saves a world-editor change, creating/updating a

pending authored world revision.

Multiple triggers coalesce into one scheduled restart. The scheduler stores all reasons so players and admins can see why a restart is pending.

17.2 Detecting live-code changes

The running server periodically performs a non-destructive remote check, for example git fetch origin master followed by comparison of the running commit with origin/master. It does not update the checked-out code while the game is live.

17.3 Server-local midnight

Midnight is calculated in a configured IANA time zone rather than by adding 24 hours to the current time. This keeps behaviour correct across daylight-saving transitions.

17.4 Player-visible restart state

Restart status is part of the server status sent to clients. Connected players see that a restart is scheduled and the scheduled local time. The server can also issue configurable countdown notices as the restart approaches and includes the state immediately when a player logs in.

RestartStatus { scheduled: true, scheduledAt: timestamp, reasons: \["code-update", "world-update"\] }

17.5 Manual admin restart

An authorised admin action can invoke the same graceful restart pipeline immediately. This is not a separate “hard restart” path; it differs only in scheduled time.

17.6 Graceful restart sequence

> 1. Enter DRAINING / RESTARTING state and reject new logins. > > 2. Broadcast the final restart notice. > > 3. Disconnect player sessions cleanly and persist session state. > Shutdown handling overrides normal offline-script retention so chunk > unload cannot be blocked by a retiring process. > > 4. Stop accepting new gameplay commands and finish the current > safe tick boundary. > > 5. Force-unload every resident region/chunk, ignoring normal > ChunkLoader references. This invokes the ordinary chunk/entity unload > persistence path exactly once. > > 6. Flush the persistence service and close SQLite connections > cleanly. > > 7. Atomically write a restart request manifest. It records the > restart reasons, whether a code deployment is requested, the target Git > commit if known, and the pending world revision if one exists. > > 8. Exit the Node.js game process cleanly. At this point the game > process has no responsibility for updating or relaunching itself.

17.7 systemd process supervisor

The production Node.js process is owned by a systemd service. systemd therefore already knows when the process has fully exited; no separate polling process is needed. Only after the previous ExecStart process is gone does systemd begin the next service start.

The preferred lifecycle is:

Running Node.js server
        |
        | graceful planned restart or crash
        v
Node.js process fully exits
        |
        v
systemd starts the service again
        |
        +--> conditional update hook
        |       |
        |       +--> planned code deployment: git fetch/pull --ff-only
        |       +--> world-only restart: no Git mutation
        |       +--> crash/no restart manifest: no Git mutation
        |
        +--> optional dependency/build step if deployment changed code
        |
        v
Start Node.js server
        |
        v
Startup selects the new active world revision
        |
        v
Gateway opens when the world reports READY

17.7.1 Why Git pull must be conditional

A naive ExecStartPre=git pull on every restart is unsafe. Suppose a new commit is detected at 14:00 and correctly scheduled for midnight, but the game process crashes at 16:00. An unconditional pull would deploy the new commit immediately during crash recovery, bypassing the scheduled maintenance window.

Therefore the restart manifest distinguishes an intentional deployment restart from an ordinary process failure:

{
  "reason": ["code-update", "world-update"],
  "deployCode": true,
  "targetCommit": "<optional commit hash>",
  "pendingWorldRevision": 184
}

The manifest should be written using a temporary file plus atomic rename so the supervisor never consumes a half-written request. The supervisor consumes/removes the request only after it has successfully interpreted it.

If the Node.js process dies without a valid deployment request, systemd restarts the currently checked-out version. This gives fast crash recovery without prematurely deploying pending code.

17.7.2 Suggested systemd shape

A production unit can conceptually look like this:

[Unit]
Description=Tile MMO Server
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=tilemmo
Group=tilemmo
WorkingDirectory=/srv/tile-mmo/current

# This hook checks the restart manifest. It pulls/builds only when an
# intentional deployment was requested. Prefixing with '+' optionally
# allows the hook to run with privileges different from the game user.
ExecStartPre=+/usr/local/sbin/tile-mmo-update-if-requested
ExecStart=/usr/bin/node /srv/tile-mmo/current/dist/server.js

Restart=always
RestartSec=5s
TimeoutStopSec=120s
KillSignal=SIGTERM

[Install]
WantedBy=multi-user.target

Restart=always is appropriate here because an explicit systemctl stop tile-mmo does not cause systemd to restart the unit, while a clean in-game restart exit and an unexpected crash both do.

The exact paths, build command and privilege split are deployment details, but the important invariant is that the Node.js process does not pull Git itself.

17.7.3 Code-update, world-update and crash behaviour

SituationRestart manifestGit pull before restartWorld revision
Scheduled code updatedeployCode=trueYes, fast-forward onlyActivate pending revision if present
World-editor-only updatedeployCode=falseNoActivate pending revision
Manual deployment restartExplicit admin intentAs requestedActivate pending revision if present
Unexpected Node.js crashMissing/invalidNoContinue current active revision
systemctl stopIrrelevantNo automatic restartN/A

This preserves the midnight deployment promise even when the game crashes before the scheduled maintenance window.

17.8 Failure behaviour

Deployment should fail closed. If Git cannot fast-forward, a build or migration fails, or startup validation fails, the game must not open to players on a partially updated state. The update hook should log the failure clearly and return non-zero; systemd may retry according to its restart/start-limit policy. Databases remain intact, and backups or snapshots before schema migrations are recommended.

A failed crash recovery that did not request deployment must not silently switch to a newer Git commit as a recovery strategy.

18. Future player scripting architecture

18.1 Scope

The custom scripting language is explicitly a later feature. Version 1 only needs architectural hooks so adding scripts does not require replacing the player-control or simulation model.

18.2 Controller abstraction

All player actions should already pass through an internal command interface. Manual client input is therefore one possible controller. A future script is another controller that emits the same validated action intentions.

ClientController ─┐
                  ├─> ActionCommand queue ─> authoritative game systems
ScriptController ─┘

Scripts never mutate ECS components directly. They request actions such as MoveTo, Interact or Attack and receive the same validation as a human client.

18.3 Online scripted mode

A logged-in player may enable the script while remaining connected and observing the game. Control mode explicitly determines whether manual input or the script is currently producing gameplay commands. The server remains authoritative either way.

18.4 Logout with active script

If a player has configured offline script execution, logout removes the network/controller connection but keeps the player entity alive. The entity changes to an offline script-controlled state and continues acting until it dies or its configured offline duration expires.

Player online Player + NetworkIdentity + ChunkLoader + Controller ↓ logout with offline scripting Player + ScriptController + ChunkLoader + OfflineUntil ↓ death OR expiry persist player state → remove runtime entity

18.5 Offline scripted players and loading

An offline scripted player must continue to stimulate the world it traverses, so it retains a ChunkLoader. This is powerful but potentially expensive: thousands of offline scripts could keep large parts of the world active. Offline duration, script CPU budget and concurrent offline-script limits therefore become explicit resource policy, not implementation accidents.

18.6 Restart continuity

A planned restart persists the offline-script state and expiry time, force-unloads the old process, and rehydrates still-valid offline scripted players during startup. This is why the startup index for persistent ChunkLoaders is part of the base architecture.

18.7 Scripting language safety requirements

When the language is implemented, it should be interpreted/compiled into a purpose-built sandbox rather than evaluated as JavaScript. At minimum it should enforce:

  • No file-system, operating-system, database or arbitrary network

access.

  • No eval or escape into Node.js objects.
  • Per-tick/per-event instruction budgets and bounded memory.
  • Rate-limited expensive operations such as path requests and world

queries.

  • Capability-based read APIs for nearby visible/known world state.
  • Action output only through the normal server command pipeline.
  • Persistable script variables/state if offline execution must survive

restarts.

  • Deterministic or tightly controlled timing semantics where practical.

An event-driven language is preferable to running every player script continuously at full simulation frequency. Events such as arrival, attack, nearby entity changes or timer expiration can wake scripts only when useful.

19. Security and administration

  • World-editor endpoints require an explicit admin role and separate

server-side authorisation checks.

  • Client-supplied entity/player IDs are never trusted as authority;

authenticated connection/session context identifies the actor.

  • World-editor data is validated against known ground, block, item and mob

definitions before database write.

  • Admin restart and deployment controls use the same authenticated

administration layer.

  • The Node.js game process should run as a dedicated unprivileged user.

Where practical, source-update permission belongs only to the systemd update hook (for example a privileged ExecStartPre helper), leaving the running Node.js process unable to modify its own checkout.

  • SQLite writes are parameterised and centralised through

persistence/editor services.

  • Inventory, vault, cheque and courier mutations are server-authoritative.

Clients cannot invent cheque IDs, forge cargo, or credit a vault.

  • Attack hit/miss and damage are server-authoritative. Clients cannot supply

a roll or a damage result. Shop purchase prices are computed at buy time on the server.

20. Recommended process topology

Clients
  |
  v
WebSocket/API Gateway
  |
  +-- Region Coordinator ----> Simulation Worker A
  |                              <--> Simulation Worker B
  |
  +-- Communication Service --> proximity speech
  |
  +-- CourierService ---------> pigeon cargo / transit
  |
  +-- BankService ------------> shared vaults / cheques / reservations
  |
  +-- MarketService ----------> order book / escrow / trades / last-sale index
  |
  +-- Persistence Service ----> state.sqlite
  |
  +-- Admin / World Editor ---> world.sqlite

External process supervision:
systemd ---> conditional deployment hook ---> Node.js relaunch

21. Player client architecture

21.1 FrameworkV3 as a git submodule

The player-facing client is built on the shared FrameworkV3 library:

<https://gitlab.com/Timfa/frameworkv3>

FrameworkV3 contains generic reusable client-side code. Game-specific rendering, UI, input, assets and protocol handling live in this repository, on top of that library. They are not patched into FrameworkV3 unless they are genuinely reusable across games.

This repository vendors FrameworkV3 as a git submodule rather than copying its source or depending on an unpublished global install.

mmo/
  client/
    frameworkv3/     # git submodule → gitlab.com/Timfa/frameworkv3
    src/             # this game's client: protocol, UI, world view, assets
  server/            # Node.js ECS backend; does not import FrameworkV3

The submodule path is client/frameworkv3. A clone of this repo is not client-buildable until submodules are present:

git clone --recurse-submodules <this-repo>
# or, in an existing checkout:
git submodule update --init --recursive

The submodule records a pinned commit. Bumping FrameworkV3 is an explicit commit in this repository (new submodule SHA). Game code must not rely on an uncommitted dirty checkout of the submodule.

Build order:

1. Build FrameworkV3 from client/frameworkv3
2. Build this game's client against that output
3. The Node.js server is a separate build and does not link FrameworkV3

The exact FrameworkV3 build command follows that project's own instructions. This game's client build must consume the framework's public/build artefacts, not fork its internals.

CI and developer machines check out submodules before the client job. A missing or uninitialized submodule is a failed client build, not a fallback to a system copy of FrameworkV3.

If this repo's master also ships the built web/desktop client from the same process that deploys the game server, a submodule bump is just another commit and follows the normal midnight restart/deploy path. The running Node.js game process still does not compile or import FrameworkV3.

The backend remains the authoritative Node.js ECS simulation described in this document. The client does not need to use ECS. It receives only a small 3×3-chunk view plus player/UI state, so a conventional object/view-model model is simpler and entirely appropriate.

21.2 Server/client model separation

Backend ECS components are not treated as a shared client object model. Network messages form the contract between the two sides.

Authoritative Node.js ECS
        |
        | snapshots / deltas / UI state
        v
Network protocol DTOs
        |
        v
Built FrameworkV3 (from client/frameworkv3 submodule)
        |
        v
This game's client code (client/src)

The two projects may share protocol schemas, enums or generated message types, but the client must not depend on the internal layout of ECS component storage. That allows server internals to be optimised without forcing corresponding client rewrites.

21.3 Sprites are 16×16

Every world sprite — ground tiles, blocks, mobs, item icons and other in-world art — is exactly 16×16 pixels. Sprites are not individually stretched to a different size. One sprite corresponds to one tile on the world pixel grid.

At load time, any image whose width or height is not 16 is rejected. The asset must not enter the runtime atlas or definition registry. The failure should name the file and its actual dimensions.

A unit test walks the sprite asset tree (grounds, blocks, mobs, items, equipment overlays, recolour masks, and any other world-sprite folders) and performs the same check. It reports every offender and fails if any are found. This test belongs in CI so a non-16×16 sprite cannot ship even if a local load path is skipped. Recolour masks are 16×16 world sprites too; a mismatched mask is a failed test.

Camera zoom (section 21.4) scales the whole viewport uniformly. It is not a per-sprite size override. Rendering should use nearest-neighbour sampling so 16×16 pixels stay sharp.

21.4 Viewport, camera and zoom

In normal play the viewport is always centered on the local player's character. The camera does not free-pan. Scrolling the world happens only because the player moved.

The player may zoom in and out within configured minimum and maximum bounds (for example 1× to 4×; the exact numbers are a game setting). Zoom does not move the camera off the player and does not change server visibility: the client still receives only the 3×3 chunk window.

The admin world editor is the exception: it frames the selected 16×16 chunk and navigates by chunk, as in section 8.1.

21.5 Client movement interpolation

The server jumps mobiles from tile to tile. The client draws a visual lerp between the previous replicated tile and the new one over the interval implied by gait and WorldSettings (walk: 1 / walkTilesPerSecond, run: half of that). If a delta arrives late, clamp the remaining lerp. That lerp is presentation only:

  • Hit tests, range, pickup and occupancy use the authoritative tile.
  • A corrected server position snaps the interpolation target; the client

does not accumulate drift.

  • Interpolation does not entitle the client to send fractional positions.

21.6 Equipment layers and recolouring

A mob (including a player character) is drawn as a stack of 16×16 sprites on the same tile: the body sprite (male or female from character sex, or the mob archetype body), then each piece of visible equipment. Overlays are not baked into the body art.

draw order (back → front, default)
  1. body / mob base
  2. boots
  3. legs
  4. chest
  5. head
  6. off-hand
  7. weapon

Slot draw order is data so a cloak or a two-handed sprite can be inserted without a renderer rewrite. Every overlay sprite, like every other world sprite, is exactly 16×16 and is rejected on load / CI if it is not.

Equipment items stay in dedicated equipment slots, not in the 32 inventory slots, while worn. EquipItem(slotIndex) moves a legal item from inventory into the matching equipment slot, returning any previously worn item to inventory if there is space. UnequipItem(equipSlot) does the reverse. The weapon equipment slot is what combat uses; it replaces the older “wielded flag on an inventory slot” idea.

Non-player mobs may carry an Equipment component or a simpler appearance list on the mob definition so a guard can show armour without a player inventory.

Equipment
- slots: { head?, chest?, legs?, boots?, weapon?, offhand?, ... }

ItemDefinition.equipment?
- slot
- overlaySpriteId
- recolourableChannels?: ["metal"]   // omitted if the art is not recoloured
- materialId?                        // e.g. iron, steel; used with "metal"

Inventory icons and worn overlays may be different 16×16 files. Both are world sprites and both go through the size check.

Recolourable equipment

Some gear shares one overlay and is tinted per material. Metal armour is the initial case: iron, steel and later metals are not separate full-size art sets.

MaterialDefinition
- materialId            // iron, steel, ...
- displayName
- channel               // metal for armour; later channels may include cloth
- colour                // destination RGB for that channel

A recolourable overlay is authored as:

  • the 16×16 overlay sprite, with shading in the channel regions, and
  • an optional 16×16 channel mask of the same dimensions, whose pixels

name which recolour channel they belong to (for example a reserved mask colour meaning metal). Unmasked pixels are drawn unchanged.

At draw time, masked pixels keep the overlay’s relative brightness (highlights and shadows) and replace the hue/saturation with the item’s MaterialDefinition.colour. The client must not invent a colour; the server sends the material id (or the already-resolved colour) on the appearance layer.

Iron plate and steel plate therefore share overlaySpriteId = platebody and differ only by materialId. Non-metal unique art omits recolourableChannels and is blitted as authored.

Recolour happens on the client as a presentation step. It does not change item identity, combat stats or inventory. Nearby observers receive enough appearance data to apply the same layers and tints.

21.7 World time and night shading

The client treats world time as server time minus 1200 years (section 13.5). It uses that clock-of-day to shade the 3×3 view.

At night, tiles that the baked light map says are unreachable from any static light are drawn darker. Tiles a light can reach stay brighter. Light does not bleed through walls: the mask was raycast through passable tiles at editor save, including across chunk borders, so a torch on the edge of one chunk can light tiles in the next.

By day, ambient light is full and the baked mask does not darken the ground. The day/night curve (how dark “night” is, dusk length) can stay a world setting or a later tuning value; the invariant is that night uses baked reachability, not a per-frame raycast.

The world-editor night-to-day slider is the same shading function, driven by the slider instead of the clock, so an admin can preview a chunk at any light level without changing live world time.

22. Items, inventory and ground drops

22.1 Item definitions

Every obtainable object is an ItemDefinition. Stacking, uniqueness and later economy rules are data on that definition, not special cases in UI code.

ItemDefinition
- itemId
- displayName
- description
- seedValue               // base price before player-market adaptation
- stackable
- maxStackSize            // default 99 for stackable items
- uniqueInstance          // true for letters, filled cheques, and similar
- category: ingredient | intermediate | finished | document | other
- npcShopAllowed
- gatherSources
- craftingRecipe(s)
- dropTableSources
- attack?: AttackProfile  // weapons; omitted for non-weapons
- equipment?:             // worn/wielded visuals; see 21.6
    slot
    overlaySpriteId
    recolourableChannels?
    materialId?

A stackable item with no instance data merges with an identical itemId in the same container up to maxStackSize. Unique-instance items never merge; each occupies its own slot at quantity 1.

Currency is not an inventory item. Carried money is a numeric Currency balance on the player. Banked money is a numeric balance on that player's vault. Coins do not occupy inventory slots and cannot be dropped on the ground in this model.

How most items are obtained is specified later. Two source families already fit this model without changing it:

  • Ground-item spawners in the world editor, analogous to mob spawners.
  • Later harvesting from the environment by players.

Paper, blank cheques and letters are specified now because communication, banking and pigeons depend on them.

22.2 Player inventory

A player inventory has exactly 32 slots.

Inventory
- slots[32]: empty | ItemStack

ItemStack
- itemId
- quantity                 // 1 for unique-instance items
- instance?: ItemInstance  // present only when uniqueInstance is true
- origin?: ItemOrigin      // crafter or shop NPC; see 22.6

Rules:

  • A stack occupies exactly one slot, regardless of quantity.
  • Inserting a stackable item first tries to merge into an existing compatible

stack whose combined quantity would not exceed maxStackSize. Stacks are compatible only when itemId matches and origin matches (including both being empty). Any remainder needs an empty slot, or the whole action fails.

  • Moving, swapping and splitting stacks are ordinary server-validated

commands. The client never asserts the resulting inventory.

  • Inventory, wallet and vault contents are player-private UI state. They

are not part of 3×3 chunk replication. Other clients see ground items and pigeon entities, not another player's bags or a pigeon's cargo.

  • Logout and restart persist the full inventory and carried currency in

state.sqlite.

22.3 Paper and letters

Blank paper is a stackable item.

Writing consumes one paper and produces a letter: a unique-instance item whose instance data is text written by a player. A letter is not a mail record and has no inherent recipient. It is just paper with writing on it.

LetterInstance
- letterId
- authorPlayerId
- body
- writtenAt

If the paper stack's quantity is 1, the slot may be converted in place into the letter. If quantity is greater than 1, writing requires a free inventory slot for the new letter and decrements the paper stack.

Reading a letter inspects its instance data. Sending a letter is the same pigeon-cargo action used for any other item stack.

Maximum letter length is a defined game rule and can be chosen during implementation.

22.4 Dropping items

A player may drop an item stack, or part of a stack, onto their current tile.

GroundItem
- groundItemId
- tileX / tileY
- ItemStack
- droppedAt
- expiresAt               // droppedAt + WorldSettings.groundItemDespawnDuration
- source                  // player-drop | later: item-spawner
- droppedByPlayerId?

Rules:

  • Player-dropped items remain for WorldSettings.groundItemDespawnDuration

(default 10 minutes), then vanish forever.

  • Anyone may pick up a ground item. There is no owner lock and no loot-rights

delay.

  • Ground items do not block movement and do not prevent a player from

standing on that tile.

  • Pickup requires the player to stand on that tile. The command names the

groundItemId when several stacks share the tile.

  • Pickup fails if the player's inventory cannot accept the stack (no legal

merge and no empty slot). The ground item is unchanged.

  • Several distinct stacks may occupy one tile at once.
  • Later naturally spawned ground items use the same non-blocking

representation, but their lifetime and respawn belong to the item spawner rather than this 10-minute player-drop timer.

Dropped items are not ChunkLoaders and do not keep a chunk simulated.

They do survive chunk unload until expiresAt, using timestamp expiry rather than a per-tick countdown. On unload, unexpired ground items are written to state.sqlite. On load or wake, items whose expiresAt is in the past are discarded and never replicated. Simulating chunks also remove them when the timestamp elapses.

If a unique-instance item that encodes a bank reservation (a filled cheque) expires on the ground or is otherwise destroyed without being redeemed, that reservation is released and the reserved goods become available in the issuer's vault again.

22.5 Pickup and drop commands

DROP_ITEM(slotIndex, quantity?)
PICKUP_ITEM(groundItemId)

Both are intentions. The owning worker validates the actor's tile, inventory space and stack rules, then applies the result. Standing on a tile that has ground items does not pick them up automatically.

22.6 Item inspection, origin and displayed value

Hovering an item — in inventory, a shop stock list, or on the ground — shows at least:

ItemTooltip
- displayName
- description
- originLabel              // who crafted it, or the shop NPC if bought there
- currentValue             // undiscounted adapted value; see section 27

Origin is stored on the stack:

ItemOrigin
- kind: crafted | shop | unknown
- playerId?                // when crafted by a player
- npcId?                   // when bought from a shop NPC

The origin label is the crafting player's name, or the shop NPC's name when the stack was bought from that NPC. Harvested, looted or otherwise unstamped stacks use unknown and omit the origin line until later content says otherwise. Buying from a shop stamps that NPC as origin. Crafting stamps the crafter. Shop-bought goods are not treated as crafted by the NPC; the NPC name simply occupies that inspection field.

currentValue uses the same last-sale lerp as shopkeepers (section 27.6) but without the per-shop discount. It is informational. The client must not recompute it every simulation tick. The player UI may refresh displayed values at most once per minute, from the last-sale record plus seedValue. The actual shop purchase price is always computed server-side at the moment of purchase.

23. Player communication and carrier pigeons

23.1 Proximity chat is the default

Ordinary chat is spatial. A player speaks from a world position and only nearby players receive a useful version of the message. Legibility decreases as the recipient gets farther from the speaker.

For example:

Near:       I'm really far away
Farther:    I'm re...y far aw.y
Very far:   I'...re..ly..ar.aw.y
Beyond range: no message

The exact distance bands/function are configurable game rules.

Crucially, degradation is performed server-side. The server must not send the full plaintext to a distant client and merely ask that client to obscure it, because a modified client could then recover speech it was not supposed to understand.

A chat message therefore conceptually contains:

ChatSpeech
- messageId
- speakerEntityId
- originX / originY
- createdAt
- text

The communication service performs a spatial recipient query and derives the recipient-specific legible representation before routing it through the gateway. Chat routing is separate from normal 3×3 chunk replication, so the eventual hearing/text range does not have to equal the visual chunk-subscription radius.

23.2 Persistent player groups

Players can create permanent groups and invite other players into them. Groups are durable social entities stored in state.sqlite, with membership surviving logout and server restart.

A minimal model contains:

PlayerGroup
- groupId
- name
- owner / roles
- createdAt

PlayerGroupMember
- groupId
- playerId
- role
- joinedAt

Invite, accept, leave, kick and role-management operations are authoritative server actions.

Group membership does not create magical long-distance communication. If members are close enough, they can communicate through the normal proximity rules. Communication to distant group members means sending items — including letters — by carrier pigeon, the same mechanism available to any player.

If group-wide letter sending is later supported, it is an addressing convenience that still consumes one paper/letter item and one pigeon dispatch per recipient. The group is not a global instant chat channel.

23.3 Pigeons carry cargo, not messages

A carrier pigeon is a free physical courier. It does not send a chat packet. It carries either:

  • an amount of the sender's carried currency, or
  • exactly one item stack (a letter, a filled cheque, blank paper, or any

other stack)

One pigeon cannot carry both money and an item, and cannot carry two item stacks. Dispatching a pigeon is free, so a player who wants to move several stacks sends several pigeons one after another.

Cargo is removed from the sender immediately and placed into durable transit. A crash or restart cannot duplicate that cargo or silently erase it.

Pigeons are not inventory items. Any player may dispatch one from anywhere, provided they have valid cargo.

SendPigeon
- destination: Player(playerId) | Bank
- cargo: Money(amount) | Item(slotIndex, quantity?)

23.4 Destinations

Player destination. The pigeon flies toward the named player. On arrival:

  • Money is added to the recipient's carried Currency if they are online;

otherwise it is deposited into the recipient's bank.

  • An item stack is placed in the recipient's inventory if they are online and

have space (a legal merge or an empty slot). If they are offline or cannot accept the stack, the pigeon continues to the nearest bank and deposits the stack into the recipient's vault.

This keeps offline and full-inventory delivery durable without a separate mailbox object.

Bank destination. The pigeon flies to the nearest bank to the dispatch tile. Travel time is that aerial journey, even though every bank shares the same vault. On arrival the cargo is deposited into the sender's vault, except for the filled-cheque special case in section 24.7.

"Nearest bank" is computed from authored Bank block positions in the pinned world revision. If additional banks are added later, a pigeon sent to Bank still lands at whichever bank is closest to where it was dispatched; the goods then appear in the shared vault.

23.5 Carrier pigeon transit

A carrier pigeon must take time to cross the world; long-distance item and currency delivery is intentionally not instantaneous.

At MMO scale, however, every delivery should not keep an entire trail of regions fully stimulated merely so a pigeon can advance. The recommended model is a persistent courier transit record with world position/route/progress that can advance through dormant space using coarse path segments and timestamps.

CourierTransit
- courierId
- cargo                   // Money(amount) | ItemStack
- senderPlayerId
- destination             // Player(playerId) | Bank
- currentPosition
- route
- speed / timing state
- status

A carrier pigeon is part of the shared physical world, not a private visual belonging only to its sender or recipient. Whenever its calculated route passes through a simulating chunk, the courier should materialise there as a normal ECS Mob entity, regardless of whether the sender or recipient is nearby. Any client whose normal 3x3 chunk subscription includes that pigeon receives it like any other visible mobile entity and can therefore see unrelated pigeons flying past in the distance.

The visible pigeon does not receive ChunkLoader. It exists because the chunk is already simulating for some other reason. If it leaves the last relevant simulating chunk, its exact position/progress is folded back into the durable CourierTransit record and the ECS instance can disappear while the journey continues abstractly. If a dormant/unloaded part of its route later becomes simulated while the pigeon should currently be inside it, the owning worker materialises the pigeon at the position implied by the transit clock and route.

Dormant route                 Simulating chunk                 Dormant route

abstract transit  -------->  ECS pigeon visible to clients  -------->  abstract transit
                                  |       |       |
                               Player A Player B unrelated observer

This means a player standing halfway between sender and recipient can see the pigeon fly through their area even though the cargo has nothing to do with them. Unrelated clients receive the pigeon entity, not the cargo contents. It preserves the sense that deliveries physically cross the world without requiring thousands of deliveries to become thousands of permanent ChunkLoaders.

Because pigeons fly rather than use the ground navigation grid, their coarse route can initially be represented by direct or waypoint-based aerial segments. This makes deterministic materialisation from route + elapsed time considerably simpler than it would be for a ground-based courier.

If future gameplay allows pigeons to be intercepted, killed or rerouted anywhere along their journey, the transit model can be made progressively more detailed; that interaction is not required by the initial courier design.

23.6 Courier service

A dedicated CourierService should own durable cargo and delivery state. Simulation workers may own visible pigeon entities while the service owns the durable fact that a delivery exists.

Player action -> CourierService -> durable cargo/transit
                                  |
                                  +-> visible pigeon when needed
                                  |
                                  +-> inventory, wallet or BankService deposit

This separation is also useful for marketplace settlement, which uses the same carrier-pigeon delivery infrastructure for remote counterparties.

24. Bank, cheques and shared vaults

24.1 Bank location and access

A bank exists at or near the central marketplace as an authored Bank block. Deposit, withdraw, cheque issue and in-person cheque redemption require server-validated access to a bank interaction; the bank is not a global menu usable from anywhere.

Pigeon dispatch to Bank is the exception: that command may be issued from anywhere, and the goods become available only after the pigeon arrives.

24.2 One shared vault

Each character has a single vault in state.sqlite:

CharacterVault
- characterId
- bankedCurrency
- stacks[]
- reservations[]

Capacity is unlimited: there is no slot cap. Per-stack stacking rules still apply (maxStackSize; unique instances never merge), so 200 blank paper is stored as 99 + 99 + 2 rather than one unbounded pile.

If more banks are authored later, all banks are linked. Withdrawing at bank B can retrieve goods deposited at bank A. The vault is not per-branch.

Pigeon deposits affect when goods become available, not which vault they enter. After the pigeon arrives at the nearest bank, the goods appear in the same shared vault accessible from every bank.

24.3 Deposit and withdraw

While interacting with a bank, a player may:

  • Deposit any carried currency and any inventory stacks, in whole or in part.
  • Withdraw currency into the carried wallet.
  • Withdraw an item stack, or part of a stack, into inventory, subject to the

32-slot and merge rules.

  • Claim items or currency from the account inheritance tab into this

character's vault (section 24.9).

Goods reserved by an outstanding filled cheque cannot be withdrawn by the issuer until that cheque is redeemed or voided.

24.4 Blank cheques

A player at a bank may request blank cheques.

  • Blank cheques are a stackable item with maxStackSize 99.
  • The bank counts blank cheques already in the player's inventory (not

the vault) and issues only enough to bring that total to 99.

  • If the player already holds 99, the bank issues none.
  • Issued cheques go into inventory, merging into an existing blank-cheque

stack when possible. If the player holds none and has no empty slot, the request fails.

The bank will not issue more than 99 blank cheques into inventory, even on repeated requests.

24.5 Filling a cheque

Using a blank cheque at a bank lets the issuer pick vault goods and a quantity. For stackable items they choose an itemId and quantity; the quantity may be larger than one maxStackSize, and the reservation covers that many available (unreserved) items of that type in the vault. For unique-instance items they choose that exact instance and the quantity is 1.

FilledChequeInstance
- chequeId
- issuerPlayerId
- itemId
- quantity
- instance?: ItemInstance   // set when the reserved goods are unique
- createdAt

Filling:

1. Validates that the vault has at least quantity of that item available (not already reserved). Unique instances must still be present and unreserved. 2. Reserves those goods in the issuer's vault. Reserved goods cannot be withdrawn, sold or reserved again. 3. Consumes one blank cheque. If that was the last cheque in the slot, the slot becomes the filled cheque in place; otherwise a free slot is required for the filled cheque.

A filled cheque is a unique-instance bearer item. It does not stack. Whoever holds it may redeem it. Cheques specify vault items and a quantity, not carried currency. Money is moved with a pigeon, or by depositing and withdrawing at a bank.

24.6 Redeeming a cheque in person

The bearer interacts with any bank and redeems the filled cheque.

  • The server moves the reserved goods from the issuer's vault into the

bearer's inventory, subject to inventory space. A quantity larger than maxStackSize becomes as many stacks as needed.

  • The cheque item is consumed.
  • If inventory cannot accept the resulting stacks, redemption fails and both

cheque and reservation remain unchanged.

The bearer may then deposit those goods into their own vault if they wish.

24.7 Redeeming a cheque by pigeon

If the bearer dispatches a pigeon whose cargo is a filled cheque and whose destination is Bank:

  • The pigeon flies to the nearest bank from the dispatch tile.
  • On arrival, BankService transfers the reserved goods from the issuer's

vault into the pigeon's sender's vault.

  • The cheque is consumed in transit; it is not deposited as an item.

The receiver of the transfer is whoever sent that pigeon, not the original cheque issuer. This is how a cheque moves goods from one vault to another without the receiver standing at a bank.

Sending a filled cheque to a player delivers the cheque item itself (or into that player's bank if they cannot hold it). It does not redeem it.

24.8 Bank service

Vault mutation, cheque issue, reservation, in-person redemption and pigeon-arrival deposits are owned by a single authoritative BankService (or an equivalently serialised service) so two concurrent withdrawals, cheque fills or pigeon arrivals cannot double-spend the same goods.

Bank interaction or pigeon arrival
        |
        v
BankService
  - shared vault
  - reservations
  - cheque issue / redeem
        |
        +-> inventory / currency on the acting player when in person
        |
        +-> vault credit on pigeon arrival

Cheque identifiers are server-issued. A client cannot forge a claim against another player's vault.

24.9 Inheritance bank tab

Each account has one inheritance tab, separate from every character vault:

AccountInheritance
- accountId
- currency
- stacks[]

It is written only when a character of that account is permanently deleted (section 14.6). Any of that player's living characters can move stacks and currency from this tab into their own vault at a bank. They cannot deposit into inheritance except through character deletion.

25. Central marketplace and order matching

25.1 Marketplace location

A central marketplace exists at or near the centre of the game world. Creating, modifying or cancelling market orders requires server-validated access to the marketplace interaction; the marketplace is not intended to be a global menu that can be used from anywhere.

Orders themselves remain durable after the player leaves the marketplace or logs out.

25.2 No public list of sell orders

The market is an order book, but players do not browse a list of individual items currently offered for sale.

A seller submits:

SellOrder
- item / item definition
- quantity
- minimum unit/total price

A buyer submits:

BuyOrder
- requested item / matching criteria
- quantity
- maximum unit/total price

The UI may know which item types exist and may eventually show historical data, but it does not expose the live asks in a way that lets a buyer simply pick a listed seller.

25.3 Escrow

Market orders escrow the asset required to honour them. Escrow is taken from carried inventory and carried currency. The marketplace sits next to the bank, so a player can withdraw from the vault immediately before placing an order.

  • Creating a sell order removes/reserves the offered item stack from the

seller's inventory.

  • Creating a buy order removes/reserves the buyer's maximum offered currency.
  • Cancelling an unmatched order returns the escrowed asset through the defined

settlement/delivery rules.

This prevents double spending, selling the same item twice, or a buyer spending currency after placing a bid.

25.4 Matching rules

A buy and sell order match when:

buyerMaximum >= sellerMinimum

Sell orders are considered cheapest first. Within the same minimum price, a stable creation sequence/FIFO rule should be used unless later game rules choose otherwise.

For a symmetric order book, buy orders are naturally prioritised by highest maximum bid and then oldest sequence. This means a newly submitted sell order matches the best compatible existing bid, while a newly submitted buy order matches the cheapest compatible existing ask.

The trade price is exactly the midpoint between the two limits:

tradePrice = midpoint(buyerMaximum, sellerMinimum)

Example:

Seller minimum:  80
Buyer maximum:  100
Trade price:      90

The exact rounding rule when integer currency produces a half-unit midpoint is a defined-but-still-open game rule and must be deterministic.

25.5 Immediate side versus pigeon side

The order that is submitted last is the order that triggers the match.

The player who submitted that matching order receives the acquired asset immediately because they are currently present at the marketplace interaction (item stack into inventory, or currency into the carried wallet). The pre-existing counterparty receives their acquired item or currency through a carrier pigeon whose destination is Bank, landing at the nearest bank to the marketplace. On arrival the settlement is deposited into that counterparty's shared vault. This remains valid if they are offline.

Existing sell + new matching buy
-> new buyer receives item immediately
-> existing seller receives payment by pigeon to bank

Existing buy + new matching sell
-> new seller receives payment immediately
-> existing buyer receives item by pigeon to bank

If a trade requires more than one item stack (for example a quantity that does not fit in a single maxStackSize), the older counterparty receives as many free sequential pigeons as needed. Each pigeon still carries only one stack or only currency.

Any unused part of buy-order currency escrow caused by the midpoint price is returned immediately to the triggering player when they are the buyer, and returned by the settlement pigeon into the older counterparty's vault when they were the buyer.

25.6 Market service and atomicity

Marketplace matching should not live inside an arbitrary region worker. Use a single authoritative MarketService (or an equivalently serialised partitioned service later) so two simultaneous orders cannot both consume the same escrow.

Order insertion, matching, escrow movement and creation of the resulting settlement deliveries are committed atomically in state.sqlite.

Conceptually:

Marketplace interaction
        |
        v
MarketService
  - durable order book
  - escrow
  - deterministic matching
  - trade record
        |
        +-> immediate settlement to triggering player's inventory or wallet
        |
        +-> CourierService pigeon to Bank for the older counterparty
        |
        +-> last-sale index update for that itemId

The system should also retain an immutable trade record for auditing and recovery.

25.7 Last player-market sale per item

Each successful player-market match updates a single durable record for that itemId. There is no price history series — only the latest sale:

ItemLastMarketSale
- itemId
- lastTradePrice           // unit price of that match (the midpoint)
- lastTradeAt
- priceFrom                // evaluated undiscounted value at lastTradeAt

priceFrom is not a history log. It is the lerp origin captured at the moment of this sale so the displayed price does not jump back to seed when a new trade occurs:

1. Evaluate the current undiscounted value at now using the previous last-sale record (or seedValue if none exists). 2. Store that value as priceFrom, store the new trade's unit price as lastTradePrice, and store now as lastTradeAt.

Shopkeepers and item tooltips both read this record. They do not tick it; they evaluate it from timestamps when a shop is opened, a purchase is attempted, or a tooltip refresh is requested.

26. Combat

26.1 Every combatant can attack

Players, enemies, animals and any other mobile with a Combat component can attack. Shopkeepers and other non-fighting NPCs simply omit Combat, or never issue attack commands.

Attacking is an intention. The client (or AI, or a future script) sends ATTACK(targetEntityId). The owning worker validates range, line-of-use, the current attack profile and cooldown, then resolves hit and damage authoritatively. The client never supplies a hit result or a damage number.

Cross-worker attacks already use REMOTE_ACTION(attack intent): the worker that owns the target applies the authoritative result.

26.2 Attack profiles

The current attack comes from the wielder's selected profile: a wielded weapon's AttackProfile, a selected spell, or a default unarmed melee profile when nothing is wielded.

AttackProfile
- attackId
- mode: melee | ranged | magic
- rangeTiles               // melee is always 1; ranged/magic from the item or spell
- hitSkillId
- damageSkillId
SpellDefinition
- spellId
- displayName
- AttackProfile            // mode = magic, hitSkillId = Magic, damageSkillId = Mind
- other costs/effects      // later content

Typical weapon mappings:

Sword     -> melee,  range 1,           hit Swordfighting, damage Strength
Axe       -> melee,  range 1,           hit Axefighting,   damage Strength
Bow       -> ranged, range from item,   hit Archery,       damage Dexterity
Spell     -> magic,  range from spell,  hit Magic,         damage Mind
Unarmed   -> melee,  range 1,           hit Unarmed,       damage Strength

The exact weapon and spell catalogue is content. The pairing rule is not: melee weapons use a weapon skill plus Strength, ranged weapons use a weapon skill plus Dexterity, and spells use Magic plus Mind.

EquipItem(slotIndex) moves a legal item from inventory into the matching equipment slot (section 21.6). The weapon slot supplies the current AttackProfile. SelectSpell(spellId) selects a spell the actor is allowed to use. The selected profile determines range and both skills.

26.3 Melee range

A melee attack is legal only when the attacker stands on one of the eight tiles surrounding the target's tile: orthogonal or diagonal, Chebyshev distance exactly 1. The attacker cannot melee from the target's own tile.

. . .
. T .     attacker must occupy one of the eight `.` tiles
. . .

This adjacency rule is independent of whether ordinary walking is four- or eight-directional.

26.4 Ranged attacks and spells

Ranged weapons and spells may fire from further away. Maximum Chebyshev distance is rangeTiles on that item or spell. Distance 0 (same tile) is not a legal ranged/spell attack unless a later exception is defined.

The attacker must still occupy a simulating chunk and satisfy any later line-of-sight rule. Exact obstruction rules are an open content decision; range itself is not.

26.5 Hit roll

Whether the attack lands is a server-side roll driven by the hit skill of the current profile (Swordfighting, Axefighting, Archery, Magic, Unarmed, and so on). The client does not roll.

The exact hit curve, any defender contribution from Defence, and the RNG are later tuning. The invariant is that the hit chance is a function of the attacker's hit-skill level, not of Strength, Dexterity or Mind.

A miss deals no damage.

26.6 Damage

On a hit, damage is determined by the damage skill:

  • Melee → Strength
  • Ranged → Dexterity
  • Magic → Mind

Weapon or spell base damage and the defender's mitigation (including whether Defence reduces damage) are later tuning. The governing damage skill is not.

26.7 Experience split

When a player successfully hits, the attack's XP award is split equally between the hit skill and the damage skill:

totalXp = attack xp formula for this successful hit
hitSkill     += totalXp / 2
damageSkill  += totalXp / 2

Example: a sword hit awards half its XP to Swordfighting and half to Strength. A bow hit splits Archery and Dexterity. A spell hit splits Magic and Mind.

If an unusual profile ever named the same skill twice, XP is awarded once, not doubled. Misses award no combat XP. Ordinary mobs do not earn XP; their Skills component is filled from the mob archetype and stays at those levels.

Non-combat actions remain single-skill as in section 27.4.

26.8 Mob combat stats

MobDefinition
- ...
- skillLevels: { skillId → level }
- defaultAttack: attackId | unarmed

A wolf might have Unarmed and Strength. An archer guard might have Archery and Dexterity. Those levels feed the same hit and damage resolution as players.

27. Player-driven economy and skill progression

27.1 Item-source philosophy

The economy is intentionally player-driven.

Normal NPC shops should sell only basic ingredients. The vast majority of materials are gathered directly from the world by players. Finished goods are normally produced by player crafting/professions.

The only normal non-player source of finished items is enemy or boss loot.

This gives four broad source paths, with ground-item spawners as an additional early world source once content defines them:

World gathering / harvesting -> ingredients
Ground-item spawners --------> some world items, later specified
Basic NPC shops -------------> limited basic ingredients
Player production -----------> intermediate/final products
Enemies and bosses ----------> loot, including possible finished items

Stacking, unique instances, letters and cheques are defined in section 22. Economy-facing fields remain on the same ItemDefinition:

ItemDefinition
- itemId
- displayName / description / seedValue
- stackable / maxStackSize / uniqueInstance
- category: ingredient | intermediate | finished | document | other
- npcShopAllowed
- gatherSources
- craftingRecipe(s)
- dropTableSources
- attack?: AttackProfile
- equipment?: slot / overlaySpriteId / recolourableChannels / materialId

Content validation can then reject an ordinary shop inventory that accidentally contains a finished product unless explicitly permitted by a future exception.

27.2 No player classes

Players do not choose a class. Capabilities and progression come from independent skills.

Examples include:

  • Swordfighting, Axefighting, Archery, Magic, Unarmed
  • Strength, Dexterity, Mind
  • Defence
  • Lumbering
  • Fishing
  • Smithing

The final skill list is game content and is not limited to skills found in any particular inspiration game.

27.3 Skill state

Skill progression is persistent player state.

SkillProgress
- skillId
- xp

Level should preferably be derived from XP and the skill's level curve rather than stored as an independent source of truth, although it may be cached.

SkillDefinition
- skillId
- displayName
- levelCurve
- maxLevel (if any)

27.4 Actions are governed by skills

Every gameplay action that participates in progression is associated with a governing skill. Combat attacks are the explicit exception: they have a hit skill and a damage skill, and split XP equally between them (section 26.7).

ActionDefinition
- actionId
- governingSkillId
- requiredLevel
- xpAward / xpFormula
- other requirements

Examples:

Cut tree        -> Lumbering
Catch fish      -> Fishing
Forge sword     -> Smithing
Sword hit       -> Swordfighting + Strength (equal split)
Bow hit         -> Archery + Dexterity (equal split)
Spell hit       -> Magic + Mind (equal split)
Defensive act   -> Defence

The server validates the action, performs the authoritative outcome, and then awards XP according to the action result. A client cannot claim XP independently.

27.5 Skills replace class restrictions

Equipment, recipes, actions, gathering nodes and other content may require skill levels, but there is no permanent class gate. A player can train any combination of skills over time.

This also fits the future scripting model: scripts issue normal actions, and successful scripted actions use exactly the same skill checks and XP rules as manual player actions.

27.6 NPC shops and market-adapted prices

Named shop NPCs can sell items to players. They are not the player marketplace and they do not expose live sell orders. A shop interaction requires being at that NPC.

Stock remains constrained by npcShopAllowed and the ingredient-only rule in 27.1. Each shop NPC has a hidden discount that players never see:

ShopNpc
- npcId
- hiddenDiscount           // multiplier, e.g. 0.9; not shown to clients
- stock[]                  // itemIds this NPC sells

Until an itemId has a player-market last-sale record, the undiscounted value is seedValue from the item definition.

When a last-sale record exists, both tooltips and shops evaluate a timestamp lerp that does not require a per-tick update:

t = min(1, (now - lastTradeAt) / WorldSettings.shopPriceLerpDuration)
undiscounted = lerp(priceFrom, lastTradePrice, t)
shopPrice    = undiscounted * thatNpc.hiddenDiscount

lerp(a, b, t) = a + (b - a) * t. After the configured lerp duration (default one hour), t is capped at 100% and the value rests on the last player-market unit price (times discount, for shops) until another player-market sale occurs.

A new player-market sale captures the then-current undiscounted value as priceFrom (section 25.7), so the lerp restarts toward the new last price without jumping back to seed.

Integer currency must be rounded deterministically at evaluation time. Shop purchase price is computed on the server at the instant of BuyFromShop. Displayed tooltip value is the undiscounted figure and may be refreshed at most once per minute (section 22.6).

Buying from a shop removes the listed price from the player's carried currency, puts the stack in inventory subject to the 32-slot rules, and stamps ItemOrigin.kind = shop with that NPC. Shops in this model sell to players; they do not buy player goods unless a later iteration adds that.

28. Suggested implementation phases

Phase 1 — Single-worker playable core

  • World coordinate helpers, 16×16 chunks and 4×4-chunk regions.
  • Ground/block tile model and chunk spatial occupancy.
  • Basic ECS and fixed simulation tick.
  • ChunkLoader reference counting and sleeping/unloading.
  • Single simulation worker behind the same worker interface planned for

later scaling.

  • world.sqlite read path and state.sqlite persistence service.
  • Admin world editor: chunk navigation, open/closed flag, default grass for

unsaved chunks, ground/block paint, light-emitting blocks, baked cross-chunk light maps, night-to-day preview slider, world settings modal, per-chunk changelog, save to pending revision.

  • SpawnerSystem for at least one non-persistent mob archetype.
  • WebSocket gateway, stub admin-<n> auth until auth.timfalken.com,

character create/select/delete, authoritative command queue and 3×3 chunk replication.

  • Click-to-move with server-side A\*, global walk/run cadence (default 2

tiles/s walk, run every movement tick, walk every other), and SetGait.

  • FrameworkV3 git submodule at client/frameworkv3, built first, then a

game-specific client on top of it with 16×16 sprites, load-time and CI rejection of wrong-sized art (including equipment overlays and recolour masks), layered worn equipment with material recolouring, a player-centered viewport with bounded zoom, client-only lerp of tile-to-tile movement, and night shading from baked light maps.

  • 32-slot player inventory, stack merging, drop/pickup, and 10-minute

non-blocking ground items.

  • Paper items that can be written into unique letter items.
  • Basic proximity chat with server-side distance degradation.
  • Persistent player skill state, including Strength, Dexterity and Mind, and

at least a small initial set of skill-governed actions.

  • Melee and ranged/spell attack validation (8-tile melee adjacency, item/spell

range), server-side hit rolls, damage from the matching damage skill, and equal XP split on a successful player hit.

  • Graceful forced-unload shutdown.

Phase 2 — Operations and live deployment

  • RestartScheduler and player-visible scheduled restart state.
  • origin/master change detection.
  • systemd service supervision and conditional deployment hook.
  • World-revision activation on restart.
  • Admin immediate restart.
  • Migration, backup and startup readiness checks.

Phase 3 — Multi-worker world

  • Multiple worker_threads simulation workers.
  • Region coordinator and dynamic region ownership.
  • Cross-worker entity transfers.
  • Border ghosts and remote actions.
  • Gateway subscriptions spanning multiple workers.
  • Load metrics and neighbour-aware region balancing.

Phase 4 — World depth, social systems and economy

  • Persistent named NPCs and other persistent mob archetypes.
  • Spawner persistent-instance index and duplicate prevention.
  • Optional durable gameplay chunk overrides, written only on unload.
  • Hierarchical pathfinding if long-distance autonomous travel needs it.
  • Persistent player groups and invitations.
  • Carrier-pigeon cargo transit: free dispatch, money or one item stack,

player or nearest-bank destinations, including offline/full-inventory fallback to the recipient vault.

  • Shared unlimited character bank near the marketplace, account

inheritance tab on character delete, blank cheques filled to 99, reserved filled cheques, in-person redemption and pigeon-to-bank cheque transfers.

  • Central marketplace, escrow, deterministic order matching, pigeon-to-bank

settlement for the older counterparty, and a per-item last-sale record for shop/tooltip adaptation.

  • NPC shops that sell npcShopAllowed stock at seed value lerped toward the

last player-market price over shopPriceLerpDuration, with a hidden per-shop discount.

  • Item inspection: name, description, origin (crafter or shop NPC) and

undiscounted current value, refreshed at most once per minute.

  • Player crafting/gathering economy rules and shop-content validation.
  • Broader skill catalogue, progression curves and skill-gated content.

Phase 5 — Player scripting

  • Custom language grammar/compiler/interpreter.
  • ScriptController and event API.
  • CPU/memory/query quotas and sandboxing.
  • Online scripted control mode.
  • Offline retained player entities with expiry and ChunkLoader

behaviour.

  • Persisted/restart-safe script state.

29. Core invariants

InvariantRule
Server authorityClients send intent; the server computes and owns outcomes.
Region ownershipExactly one simulation worker authoritatively owns a region.
Entity ownershipExactly one worker authoritatively owns an entity.
Remote mutationWorkers never directly mutate remote authoritative state.
Spatial separationRegion residency, chunk simulation and client visibility remain distinct.
Persistence separationPersistent and ChunkLoader are independent entity traits.
Chunk persistenceNormal dirty chunk state is written on unload, not periodically.
World authoringEditor changes create pending authored state; the running server stays pinned to its startup revision. Each chunk save appends an admin-attributed diff changelog.
Restart pathPlanned restart force-unloads the world and reuses the ordinary unload save path.
ControlHuman and future scripted control both emit validated action commands.
DeploymentThe game exits gracefully; systemd relaunches it and only pulls/builds when an intentional deployment manifest requests it.
Client architectureFrameworkV3 is a git submodule under client/frameworkv3, built before game client code; backend ECS internals do not become the client object model.
SpritesAll world sprites are exactly 16×16 pixels; any other size is rejected on load and fails CI. Equipment overlays and recolour masks are included.
AppearanceVisible gear is layered 16×16 overlays on the mob; recolourable channels (such as metal) use material colour without duplicate art sets. Nearby clients receive appearance layers, not another player's inventory.
Play cameraThe play viewport is centered on the local player. Only the admin world editor uses a free chunk camera.
MovementAll ground mobiles share a global walk/run cadence from world settings; the server commits integer tiles; clients lerp for presentation only.
World timeWorld calendar time is server time minus 1200 years. Night darkens tiles the baked light map cannot reach.
World settingsTick timers and global constants are authored in the editor modal, pinned to the world revision, and not hot-patched into a live process.
Baked lightStatic light reach is raycast through passable tiles on chunk save, may cross chunks, and is not recomputed every tick.
Ground itemsPlayer drops last groundItemDespawnDuration (default 10 minutes), block nobody, and are picked up only by a player standing on that tile.
Shop pricesNPC shop prices lerp from the captured pre-sale value toward the last player-market unit price over shopPriceLerpDuration (default one hour), times a hidden per-shop discount.
Proximity speechDistant clients never receive unobscured plaintext that game rules say they cannot understand.
Courier cargoPigeons carry money or one item stack, never a chat packet; cargo is durable in transit and remains delayed.
InventoryA player has 32 slots; a stack occupies one slot; the client never asserts inventory, wallet or vault results.
Shared bankEvery bank reads the same character vault; pigeon deposits become available only after arrival at the nearest bank.
Closed chunksClosed or never-edited chunks are visible but not enterable; never-edited terrain is default grass with no blocks.
AccountsLogin is auth.timfalken.com (or admin-<n> stub). Characters belong to an account; one may be in the world at a time.
NamesSurnames are globally unique per account; first+last is unique per account; names free only after permanent delete.
InheritanceDeleted characters dump inventory, equipment, wallet and vault into an account inheritance tab other characters can claim.
ChequesFilling a cheque reserves vault goods; the bearer item is the claim; destruction without redemption releases the reservation.
Marketplace escrowEvery open order is fully backed by escrow and matching/settlement is atomic and deterministic.
CombatMelee requires an 8-neighbour tile; ranged/spell range comes from the item or spell; hit uses the weapon skill; damage uses Strength, Dexterity or Mind.
ProgressionPlayers have no classes; non-combat actions award XP to one governing skill; a successful attack splits XP equally between hit and damage skills.

30. Important edge cases to preserve during implementation

  • A ChunkLoader crossing a region boundary can change

residency/simulation references and worker ownership in the same tick; ordering must avoid temporary double ownership.

  • A player at a worker boundary may receive visible chunks from multiple

workers without moving ownership solely for rendering.

  • A planned restart must ignore normal ChunkLoader retention when

forcing the world to unload.

  • A world-editor save must never cause newly loaded chunks in the

current process to use the pending revision. It must append a changelog record naming the admin, timestamp and tile diffs.

  • Pathfinding and player movement must reject tiles in closed or

never-edited chunks even when those chunks are in the 3×3 view.

  • Two accounts must not claim the same surname. One account may reuse its

surname; first+last must stay unique on that account until permanent delete.

  • Marking a character for deletion must not free the name or move items

until the delay elapses. Cancelling must restore playability.

  • Character deletion must notify the account email (or log, on stub auth).

Permanent delete must void that character's issued cheques, then move inventory, equipment, wallet and vault into the account inheritance tab.

  • Saving a chunk must rebake that chunk's light map and any neighbour

chunks within max light range, using passable-tile raycasts. Light from a source in chunk A may appear in chunk B.

  • A mob definition must not carry its own walk/run speed; gait only

selects every-other vs every movement tick on the global cadence.

  • World-settings saves must not apply to the live process; they wait for

the same pending-revision restart as chunk edits.

  • Night shading must not light a tile the baked mask marks unreachable,

even if a torch is nearby through a wall.

  • A sprite whose pixel size is not 16×16 must be rejected at load and must

fail the sprite-dimension unit test. Equipment overlays and recolour masks are included.

  • Equipping must not leave two items in the same equipment slot. Unequip

into a full inventory must fail and leave the item worn.

  • Nearby clients must not receive another player's inventory in order to

draw their armour; appearance layers and material ids are sufficient.

  • A client build without client/frameworkv3 initialized must fail rather

than silently using some other FrameworkV3 install.

  • Client interpolation of movement must not be treated as authority. Combat

range and pickup use the server tile, not the lerped draw position.

  • The play camera must remain centered on the local player. Zoom must not

expand the subscribed chunk set.

  • A persistent mob spawned by a spawner must not be duplicated merely

because it moved out of the spawner’s loaded area.

  • A non-persistent mob disappears when its chunk is actually unloaded,

not merely when it becomes dormant.

  • If a persistent ChunkLoader or offline scripted player exists after

restart, startup must discover it from an index without loading the entire world.

  • A pending code update followed by an unrelated Node.js crash must

restart the currently deployed commit rather than deploying early.

  • Negative coordinates, daylight-saving midnight calculation, duplicate

transfer messages and failed deployment migrations should all have explicit tests.

  • Proximity chat degradation must happen before plaintext reaches an unauthorised

distant client; rendering-only obfuscation is not sufficient.

  • Carrier-pigeon deliveries must survive restarts and recipient logout without

requiring every traversed chunk to remain stimulated.

  • A pigeon carrying an item to a player whose inventory cannot accept it must

not destroy the cargo; it deposits into that player's vault via the nearest bank.

  • Two concurrent bank withdrawals, cheque fills or pigeon-arrival deposits must

not spend the same vault goods twice.

  • Filling two cheques against the same vault stack must reserve disjoint

quantities or reject the second fill.

  • A filled cheque that expires on the ground must release its reservation and

must not remain redeemable.

  • A player-dropped ground item must not block movement, must not keep its chunk

loaded, and must still be present after a chunk unload/reload if expiresAt has not passed.

  • Pickup of a ground item from a tile the player is not standing on must fail.
  • Requesting blank cheques must never raise the player's carried blank-cheque

count above 99.

  • A marketplace match must atomically consume both escrows exactly once, even if

two compatible orders arrive concurrently.

  • A matching market order from an online player may settle immediately for that

player while the older/offline counterparty's delivery remains durable.

  • Skill XP is awarded only after authoritative action resolution, never directly

from a client-reported result. A successful player attack splits that XP; a miss awards none.

  • A melee attack from the target's own tile, or from Chebyshev distance greater

than 1, must fail. A ranged or spell attack beyond that item or spell's rangeTiles must fail.

  • A new player-market sale must capture the then-current undiscounted lerp

value as priceFrom so shop and tooltip prices do not jump back to seed.

  • Two shop NPCs may charge different prices for the same item at the same

instant because each applies its own hidden discount to the same lerp.

  • Item tooltip value must not be recomputed every tick; a one-minute refresh

is sufficient. Purchase price is still evaluated at the moment of buy.

31. Decisions through version 0.12

  • Chunk persistence is unload-driven rather than periodic.
  • The authored tile model has separate visual ground and functional

block layers.

  • Mobile actors remain ECS entities and are not authored as painted tile

contents.

  • Spawner blocks are editor-placeable and configurable per instance;

persistence belongs to the spawned mob type.

  • world.sqlite is an authored, revisioned world source; state.sqlite

holds runtime durable state.

  • Editor changes are staged for activation on restart instead of

hot-patching the running world.

  • Code/world changes schedule a player-visible midnight restart; admins

can trigger the same graceful pipeline immediately.

  • Git pull/build/relaunch belongs to systemd supervision after the

game process has safely exited.

  • Deployment is manifest-driven: crash recovery restarts the currently

checked-out commit, while only an intentional deployment restart may fast-forward master.

  • Future player scripting is modelled as an alternative controller

producing normal server action commands.

  • Offline scripted players may remain in-world as ChunkLoaders until

death or expiry and must survive planned restarts through persistence.

  • The player client is built on FrameworkV3, included as the git submodule

client/frameworkv3 and built first so this game's client code can layer on top. The client does not need an ECS and consumes protocol state independently of backend ECS storage. The Node.js server does not import FrameworkV3.

  • All world sprites (tiles, blocks, mobs, items) are exactly 16×16 pixels.

Other sizes are rejected at load. A unit test lists offenders and fails if any exist. Sprites are not individually resized; the player may zoom the whole viewport within configured bounds.

  • Visible equipment is drawn as extra 16×16 layers on the mob, including

players. Worn items occupy equipment slots, not the 32 inventory slots. Nearby clients replicate appearance layers only, never another player's inventory.

  • Recolourable gear (metal armour) shares one overlay sprite and a 16×16

channel mask. Material definitions supply the metal colour; luminance of the overlay is preserved. Iron and steel plate are different items with the same art and different materialId.

  • The play camera is always centered on the local player. The admin world

editor is the only exception, and it frames one chunk at a time.

  • Authoritative movement is a tile-to-tile jump on a global cadence:

default walk 2 tiles/s, run double. Walk steps every other movement tick; run steps every movement tick. Mobs do not set their own speed. Clients lerp for visuals only and never send interpolated positions.

  • Admins edit global tick timers and constants in a world-settings modal.

Those values live in the pending world revision and apply on the next process start, like other editor saves.

  • World calendar time is server time minus 1200 years, same IANA zone as

midnight restarts. At night the client darkens tiles the baked light map cannot reach.

  • Static light is baked on chunk save by raycast through passable tiles,

including across chunk borders. The editor has a night-to-day slider for preview only.

  • Each world-editor chunk save stores who edited it, when, and a bullet

diff of ground changes, block placements, block replacements and block removals at world tile coordinates.

  • Default speech is proximity-based and becomes less legible with distance.

Long-distance exchange is physical: a pigeon carries money or one item stack. A letter is paper with player-written text, not a separate mail record.

  • Permanent player groups are social/addressing structures and do not create an

instant global chat channel.

  • Carrier-pigeon transit is persistent but does not automatically keep every

traversed chunk simulated. Whenever a pigeon passes through a chunk that is already simulating, it materialises as an ECS Mob and is visible to any nearby client whose normal chunk subscription includes it, even if that client is unrelated to the delivery. Unrelated clients do not receive cargo contents.

  • A player has a 32-slot inventory. Stackable items occupy one slot. Currency is

a numeric wallet/vault balance, not an inventory item.

  • Player-dropped items lie on the tile for groundItemDespawnDuration

(default 10 minutes), block nobody, and may be picked up by anyone standing on that tile. They survive unload until expiry via timestamps.

  • The bank near the marketplace holds an unlimited character vault.

Later banks are linked to the same vault. Pigeons may deposit money or one stack into the sender's vault after arriving at the nearest bank. An account-level inheritance tab receives a deleted character's goods.

  • Blank cheques are issued at a bank up to a carried total of 99. Filling a

cheque reserves a vault item quantity. The filled cheque is a bearer item. In-person redemption withdraws into the bearer's inventory. Sending the cheque to the bank by pigeon transfers the reserved goods into the pigeon's sender's vault.

  • The central marketplace hides individual live sell listings and matches durable

escrowed buy/sell orders at the midpoint of compatible bid/ask limits. Quantities are item stacks.

  • The newest matching market participant receives the trade result locally; the

older counterparty receives theirs by pigeon into their bank.

  • NPC shops remain restricted to npcShopAllowed basic ingredients. They sell

to players at lerp(priceFrom, lastTradePrice, min(1, (now - lastTradeAt) / shopPriceLerpDuration)) times a hidden per-shop discount. With no player-market sale yet, the undiscounted value is seedValue. Tooltips use the same lerp without the discount and refresh at most once per minute.

  • Hovering an item shows name, description, origin (crafter, or shop NPC name

if bought there) and current undiscounted value.

  • All combatants can attack. Melee requires standing on one of the eight

neighbouring tiles. Ranged attacks and spells use the item's or spell's range. The hit roll uses the weapon skill; damage uses Strength (melee), Dexterity (ranged) or Mind (magic). Successful player-attack XP is split equally between those two skills.

  • Player progression is skill-based rather than class-based. Non-combat

actions award XP to one governing skill; combat hits split XP as above.

  • Never-edited chunks are default grass, no blocks, and closed. The

editor opens or closes each chunk. Closed chunks are visible but not enterable.

  • Accounts authenticate at auth.timfalken.com. Until that service is up,

each connection is stub admin-<n> (n = connected client count including this one) and is treated as admin.

  • An account has unlimited characters and plays one at a time. Creation

takes first name (not globally unique), last name (globally unique to the account, reusable on that account's other characters), and male/female. first+last must be unique for that account. This setup may change later.

  • Character deletion is a 24-hour (configurable) delay with email notify

and cancel. Permanent delete frees names and moves inventory, equipment, wallet and vault to the account inheritance tab, which any of that player's characters can claim into their own vault.

32. Open design decisions for later iterations

These do not block the initial implementation, but should eventually be specified explicitly:

  • Whether multiple mobile entities may occupy one tile and, if so, which

categories can overlap.

  • Whether player movement is four-direction only or also supports

diagonals. Combat melee adjacency already includes diagonals.

  • Exact hit-chance and damage curves, attack intervals/cooldowns, whether

Defence modifies incoming hit chance or damage, and ranged/spell line-of-sight or obstruction rules.

  • Deterministic rounding when shop discount or lerp produces a fractional

currency amount.

  • Exact equipment slot list, per-slot draw order exceptions (cloaks,

two-handed weapons), and whether worn overlays have facing frames to match the mob.

  • Additional recolour channels beyond metal (for example cloth dyes) and

the exact luminance-preserving remap function.

  • Exact camera zoom minimum, maximum and whether zoom is restricted to

integer steps.

  • Exact night ambient curve (how dark, dusk length) and whether baked light

stores a boolean reach mask or a distance/falloff value per tile.

  • Whether opening a door at runtime should rebake or ignore static light.
  • Exact simulation tick rate stays a world setting; lower-frequency AI and

spawner cadences can still be tuned independently.

  • Exact world/chunk binary serialisation format and schema/version

migration strategy.

  • Whether gameplay can permanently modify ground/block tiles in the

initial release.

  • Spawner timing rules, spawn-point restrictions and behaviour when

persistent spawned mobs travel very far away.

  • World-editor undo/redo and rollback UI. The per-chunk changelog is an audit

log, not by itself an undo stack.

  • Exact restart warning intervals and whether admins can

cancel/reschedule a planned restart.

  • Worker rebalance thresholds and whether regions may migrate while

players are actively crossing their boundaries.

  • Future scripting language syntax, event model and resource quotas.
  • Exact proximity-chat distance curve, maximum range and character degradation

algorithm.

  • Group naming/roles, membership limits and whether group-wide letter sending

is offered as an addressing convenience that still dispatches one pigeon and consumes one paper/letter per recipient.

  • Whether pigeons can eventually be intercepted, killed or redirected in transit.
  • Marketplace partial fills, cancellation rules, fees/taxes (if any),

tie-breaking details and midpoint rounding for indivisible currency.

  • Whether market price history or aggregate statistics are visible despite live

order listings remaining hidden.

  • Initial skill catalogue, XP curves, level caps, action XP formulas and the

remaining interpretation of skills such as Defence.

  • Maximum letter body length and whether writing paper requires a desk or can be

done from inventory anywhere.

  • Exact item catalogue, which items stack, per-item maxStackSize exceptions,

harvest interactions and ground-item spawner parameters.

  • Whether death drops inventory, and whether dropped unique items other than

cheques have destruction side-effects.

  • Whether the issuer can void a filled cheque without the bearer item being

destroyed, and whether cheques can ever represent currency rather than items.

  • Whether a short dispatch interval is needed so many pigeons cannot leave in a

single tick, even though sending remains free.

  • New-character spawn location (must be an open chunk) and name length /

allowed-character rules.

  • Later changes to character creation beyond first name, last name and sex.

33. Architectural summary

ECS → what an entity is and what systems can act on it Chunk → tile data, spatial lookup, simulation and client subscription Region → residency and simulation-worker ownership Coordinator→ where regions execute Gateway → stable client connections, auth, character select, and command/update routing world.sqlite→ authored versioned ground/block/spawner/light/settings world; unedited chunks are closed grass state.sqlite→ accounts, characters, vaults, inheritance, and other durable live-game state systemd → process supervision and relaunch Deployment hook → conditional Git update/build only for intentional deployment restarts Controller → manual client input today; sandboxed player scripts later FrameworkV3 → git submodule at client/frameworkv3; built first; game client code layers on top Sprites → all world art is 16×16; reject and CI-fail any other size Equipment → layered 16×16 overlays on mobs; metal armour shares art and recolours by material Camera → play view centered on the local player; bounded zoom; editor is chunk-framed Movement → global walk/run cadence (default 2 tiles/s walk, run double); server tile steps; client visual lerp World time → server clock minus 1200 years; night darkens unlit tiles Light → baked passable-tile raycast on editor save; shines across chunks World settings → admin modal for tick timers and global constants; pending revision Inventory → 32 slots; stacks occupy one slot; letters are written paper items Bank → per-character vault; account inheritance tab on character delete Auth → auth.timfalken.com, stub admin-<n> until live; unlimited characters, one in world Chunks → editor open/closed; default grass and closed until painted Ground items → non-blocking, 10-minute player drops, pickup only while standing on the tile Communication service → proximity speech CourierService → pigeons carrying money or one item stack through durable transit BankService → shared unlimited vaults, cheque reservations and redemption MarketService → durable escrowed order book, matching, last-sale index and pigeon-to-bank settlement Shop NPCs → sell allowed stock; price lerps toward last player-market sale over shopPriceLerpDuration, times a hidden discount Combat → 8-tile melee, item/spell ranged range; hit skill roll; Strength / Dexterity / Mind damage; equal XP split Skills → classless progression; non-combat XP to one skill; attack XP split hit/damage

34. Version history

0.12

  • Chunks are open or closed in the world editor. Closed chunks stay visible

but cannot be entered. Never-edited chunks are default grass with no blocks and are closed.

  • Login uses auth.timfalken.com; until that is live, connections are stub

admin-<n> (connected-client count including this one) and are admins.

  • Accounts have unlimited characters, one in the world at a time. Creation

is first name, unique account-owned last name, and male/female.

  • Character deletion waits 24 hours with email and cancel. Permanent delete

frees names and moves goods to an account inheritance bank tab.

0.11

  • Made walk/run a global cadence from world settings (default 2 tiles/s

walk, run double): walk steps every other movement tick, run every tick. Mob definitions do not set move speed.

  • Added an admin world-settings modal for tick timers and global constants

(shop lerp duration, drop lifetime, simulation tick, and the same class of values). Settings ride the pending world revision.

  • World calendar time is server time minus 1200 years.
  • Baked static lighting by passable-tile raycast on chunk save, including

across chunk borders. Clients darken unreachable tiles at night. The editor has a night-to-day preview slider.

0.10

  • Drew visible equipment as 16×16 overlay layers on mobs (including players),

with worn items in equipment slots rather than the 32-slot inventory.

  • Replicated compact appearance layers to nearby clients instead of another

player's inventory.

  • Recolourable metal armour shares one overlay plus a 16×16 channel mask;

material definitions supply the metal colour while preserving shading.

0.9

  • Vendored FrameworkV3 as the git submodule client/frameworkv3. The game

client builds that library first and implements game-specific code on top of it. The Node.js server does not import the submodule.

0.8

  • Required all world sprites (tiles, blocks, mobs, items) to be 16×16 pixels,

rejected at load, with a CI unit test that reports and fails on any other size. Sprites are not individually scaled; the player may zoom the viewport within configured bounds.

  • Locked the play camera to the local player. The admin world editor remains

the only non-player-centered view.

  • Made authoritative movement integer tile-to-tile steps. Clients lerp

mobiles for presentation only.

  • Added a per-chunk world-editor changelog: admin, timestamp, and bullet

diffs for ground changes, block place/change/remove.

0.7

  • Added combat for all mobs including players: melee from any of the eight

neighbouring tiles, ranged and spells from the item or spell range.

  • Hit rolls use the weapon skill (Swordfighting, Axefighting, Archery, Magic,

and so on). Damage uses Strength, Dexterity or Mind according to melee, ranged or magic.

  • Successful player-attack XP is split equally between the hit skill and the

damage skill. Ordinary mobs use archetype skill levels and do not earn XP.

  • Shop NPCs sell items at seed value adapted to the last player-market unit

price, lerping over one hour, multiplied by a hidden per-shop discount.

  • Only the latest player-market sale per item is stored (price, timestamp, and

lerp origin). No historical series.

  • Item hover shows name, description, origin (crafter or shop NPC) and the

undiscounted current value, refreshed at most once per minute.

0.6

  • Added a 32-slot player inventory, stackable items, carried currency as a

numeric wallet, and unique-instance items for letters and filled cheques.

  • Redefined letters as paper items with player-written text rather than a

separate mail record.

  • Redefined carrier pigeons as free couriers that carry money or one item

stack to a player or to the nearest bank.

  • Added a shared unlimited bank near the marketplace, blank cheques filled to

99, vault reservations on fill, in-person redemption and pigeon-to-bank cheque transfers between vaults.

  • Added player-dropped ground items: 10-minute lifetime, non-blocking, pickup

only while standing on the tile, timestamp persistence across unload.

  • Specified later ground-item spawners and harvesting as content that reuses

this item model.

  • Routed offline/full-inventory pigeon delivery and older-side market

settlement into the recipient's shared bank vault.

0.5

  • Made carrier pigeons shared world-visible entities whenever their route crosses an already-simulating chunk.
  • Unrelated nearby players can see pigeons in their normal 3x3 chunk view; pigeons do not keep chunks loaded themselves.
  • Added deterministic materialisation/dematerialisation between durable abstract transit and worker-owned ECS pigeon entities.

0.4

  • Added FrameworkV3 as the shared player-client foundation while keeping backend ECS internal to the server.
  • Added server-side proximity chat degradation, persistent player groups and durable carrier-pigeon letters.
  • Added scalable courier transit that can cross dormant world space without forcing normal chunk simulation.
  • Added the central marketplace, escrowed hidden order book, midpoint pricing and pigeon-based remote settlement.
  • Added the player-driven item-source philosophy and restrictions on NPC shop inventories.
  • Added classless, skill-based player progression and authoritative skill XP.

0.3

  • Converted the living design document to Markdown as the canonical format.
  • Defined systemd as the production process supervisor.
  • Added a conditional, manifest-driven deployment path so crashes do not deploy pending code early.
  • Added a concrete example systemd service shape and clarified privilege separation.

0.2

  • Added unload-driven chunk persistence, authored world revisions, the admin world editor, spawner blocks, graceful scheduled restarts and future player scripting hooks.
Source
1---
2title: Tile MMO Server Technical Design
3version: 0.12
4status: proposed
5format: living-design-document
6---
7
8# Tile MMO Server Technical Design
9
10**Version:** 0.12
11**Status:** Proposed architecture; intended to be iterated as implementation decisions are made.
12**Scope:** Authoritative Node.js/ECS backend, FrameworkV3-based game client (16×16 sprites, player-centered viewport), chunk/region streaming, SQLite persistence, admin world editor with per-chunk changelogs, player inventory and items, combat, player communication, banking/cheques, shopkeepers, marketplace/economy systems, skill progression, automatic restart/update orchestration, and future player scripting hooks.
13
14# 1. Design goals
15
16- Support a large tile-based MMO world without simulating unused areas.
17
18- Keep the server fully authoritative: clients send actions and
19 intentions, never authoritative state changes.
20
21- Authenticate accounts via auth.timfalken.com (with an `admin-<n>` stub
22 until that service is live). An account may have unlimited characters,
23 one in the world at a time, with delayed deletion and an inheritance
24 bank tab.
25
26- Use ECS composition for entities and systems, while using chunks and
27 regions for spatial ownership and simulation lifecycle.
28
29- Allow simulation work to scale across Node.js workers and permit
30 entities to cross worker-managed region boundaries safely.
31
32- Keep client replication small: a player receives only the current
33 16×16 chunk and the eight neighbouring chunks.
34
35- Keep authored world data separate from ephemeral simulation state.
36
37- Persist only entities that explicitly need persistence; ordinary
38 spawned mobs disappear when their chunk is unloaded.
39
40- Avoid constant chunk writes. Normal chunk persistence occurs on
41 unload; graceful shutdown is implemented as a forced unload of all
42 resident chunks.
43
44- Provide an admin-only graphical world editor for painting tiles,
45 opening or closing chunks, and placing/configuring spawners, with a
46 per-chunk changelog of who changed what and when. Unedited chunks are
47 grass-only and closed.
48
49- Automatically schedule a graceful midnight restart when live code or
50 authored world data changes, with an admin-triggered immediate restart
51 path.
52
53- Reserve a clean control abstraction for a later sandboxed player
54 scripting language without requiring the scripting system in the
55 initial release.
56
57- Build the player-facing client on the shared FrameworkV3 library, vendored
58 as a git submodule and built first so game-specific client code can layer
59 on top of it, while keeping the server-side ECS an implementation detail of
60 the backend. All world sprites are 16×16 pixels. The play viewport stays
61 centered on the local player.
62
63- Authoritative movement is tile-to-tile at a **global** walk/run cadence
64 (default walk 2 tiles/s, run double), not a per-mob speed. Admins edit
65 that cadence and other tick timers in a world-settings modal. World
66 calendar time is server time minus 1200 years. At night the client
67 darkens unlit tiles; static light reach is baked by raycast when a
68 chunk is saved.
69
70- Give every player a 32-slot inventory in which stackable items occupy a
71 single slot, and treat dropped items as temporary, non-blocking ground
72 objects rather than tile occupancy.
73
74- Make ordinary communication spatial rather than global: nearby speech is
75 progressively degraded by distance, while long-distance exchange is a
76 physical item or currency delivery by carrier pigeon. A letter is simply a
77 paper item with player-written text.
78
79- Support persistent player groups without turning them into an instant
80 long-distance chat channel.
81
82- Provide a shared, unlimited player bank near the marketplace, with later
83 banks all reading the same vault, plus bearer cheques and free pigeon
84 deposits.
85
86- Make the central marketplace an order-matching service rather than a public
87 auction list, with durable escrow and asynchronous pigeon delivery.
88
89- Keep the economy predominantly player-driven: most ingredients are gathered,
90 final goods are normally crafted by players, and finished-item drops come from
91 enemies/bosses rather than ordinary NPC shops.
92
93- Let every combatant — players and other mobs — attack. Melee requires an
94 adjacent tile including diagonals; ranged attacks and spells use the range
95 of the weapon or spell. A hit roll uses the weapon skill; damage uses
96 Strength, Dexterity or Mind. Attack XP is split equally between those two
97 skills.
98
99- Let shop NPCs sell items at a seed value that lerps toward the last
100 player-market sale price over a configurable duration (default one hour),
101 with a hidden per-shop discount.
102 Item inspection shows name, description, origin and the undiscounted
103 current value, refreshed at most once per minute.
104
105- Use skill-based progression with no player classes. Every gameplay action is
106 governed by a skill and awards XP to that skill when successfully performed.
107 Combat is the explicit dual-skill exception: hit skill and damage skill
108 share the XP.
109
110# 2. Core world model
111
112## 2.1 Spatial hierarchy
113
114World
115└── Region: 4 × 4 chunks
116└── Chunk: 16 × 16 tiles
117└── Tile
118
119One chunk contains 256 tiles. One region is 64×64 tiles and contains 16
120chunks (4,096 tiles). World tile coordinates are canonical; chunk and
121region coordinates are derived from them.
122
123chunkX = floor(tileX / 16)
124chunkY = floor(tileY / 16)
125regionX = floor(chunkX / 4)
126regionY = floor(chunkY / 4)
127
128If negative world coordinates are allowed, use true floor division
129rather than JavaScript integer truncation.
130
131## 2.2 Three independent spatial states
132
133The design deliberately separates region residency, chunk simulation,
134and client visibility.
135
136| **Concern** | **Unit** | **Meaning** |
137|-------------|----------|------------------------------------------------------------------------------------------------|
138| Residency | Region | Whether the region and its required chunk data exist in server memory and have a worker owner. |
139| Simulation | Chunk | Whether ECS systems actively simulate entities and gameplay in this chunk. |
140| Visibility | Chunk | Whether a specific client is subscribed to the chunk and receives its snapshot/deltas. |
141
142## 2.3 Region states
143
144UNLOADED
145↓ load
146RESIDENT
147↓ no residency references + grace period
148UNLOADED
149
150A resident region is assigned to exactly one simulation worker. An
151unloaded region has no active ECS representation.
152
153## 2.4 Chunk states
154
155DORMANT ⇄ SIMULATING
156
157A dormant chunk can remain resident in memory while normal gameplay
158systems ignore it. A simulating chunk participates in movement, combat,
159AI, spawners and other active systems.
160
161# 3. Tile layers and occupancy
162
163## 3.1 Ground layer
164
165Every tile has a ground type. Ground is visual only. It does not by
166itself block movement, cause collision, or create gameplay behaviour.
167
168TileGround {
169groundTypeId: GroundTypeId
170}
171
172## 3.2 Block layer
173
174A tile may also contain one block. The block is the actual world object
175standing on the tile and can determine collision and behaviour.
176
177TileBlock {
178blockTypeId: BlockTypeId \| null
179config?: BlockConfig
180}
181
182Examples include walls, doors, trees, torches and other lights, containers,
183spawners, marketplace counters and banks. Block definitions determine
184properties such as passability, interaction behaviour, whether a block
185participates in navigation, and whether it emits light (`lightRangeTiles`).
186
187## 3.3 MOBile entities
188
189A moving game entity — player, enemy, animal, NPC or any other mobile
190actor — is represented by an ECS entity rather than being painted into
191the static tile map. A mobile entity may inhabit a tile in addition to
192the tile’s ground and block layers, subject to collision rules.
193
194Tile
195├── Ground (visual layer)
196├── Block (static/world-object layer; optional)
197├── Ground item stacks (ephemeral, non-blocking)
198└── Mobile ECS entities (dynamic occupancy)
199
200The spatial chunk index maintains which mobile entity IDs currently
201occupy each tile, allowing collision, nearby queries and replication
202without scanning the global ECS. Ground item stacks are indexed per
203tile as well, but they never contribute to movement collision and never
204prevent a mobile entity from standing on that tile.
205
206# 4. ECS model
207
208## 4.1 Entity composition
209
210Entities are numeric identities plus components. Behaviour comes from
211systems querying component combinations rather than deep class
212inheritance.
213
214Player
215Position
216Movement
217Health
218Combat
219Skills
220Inventory
221Currency
222Equipment
223Player
224NetworkIdentity
225ChunkLoader
226Persistent
227
228Ordinary enemy
229Position
230Movement
231Health
232Combat
233Skills
234Creature
235AI
236
237Named NPC
238Position
239Movement
240Health
241NPC
242AI
243Persistent
244
245## 4.2 Global identity versus local ECS handle
246
247Use a globally meaningful EntityId for storage, networking and
248cross-worker transfer, and a compact worker-local EntityHandle for hot
249ECS arrays. A transferred entity keeps its EntityId but may receive a
250different local handle on the destination worker.
251
252## 4.3 Recommended initial components
253
254| **Category** | **Components** |
255|----------------|----------------------------------------------|
256| Spatial | Position, Movement, Path, Collision |
257| Living | Health, Combat, Creature, Mob, Skills |
258| Player | Player, NetworkIdentity, Inventory, Currency, Equipment |
259| AI | AI, Target, BehaviourState |
260| Lifecycle | ChunkLoader, Persistent, SpawnOrigin |
261| Presentation | Renderable / Appearance |
262| Future control | Controller / ScriptController / OfflineUntil |
263
264# 5. ChunkLoader and simulation activation
265
266## 5.1 Generic ChunkLoader component
267
268World activation is component-driven rather than player-specific. Any
269entity may carry a ChunkLoader component that says “keep the surrounding
270world resident and simulated”.
271
272ChunkLoader {
273simulationRadiusChunks: 1,
274regionLoadRadius: 1
275}
276
277A normal player can therefore stimulate a 3×3 chunk area while keeping
278the surrounding 3×3 regions resident. Bosses, travelling NPCs, machines,
279scripted actors or administrative anchors can use the same mechanism.
280
281## 5.2 Reference counting
282
283Chunk simulation and region residency should use reference counts.
284Overlapping loaders increment the same references; leaving decrements
285them. A chunk sleeps only when its simulation reference count reaches
286zero. A region becomes eligible for unload only when its residency
287references reach zero.
288
289## 5.3 Grace period
290
291After the last residency reference disappears, retain the region briefly
292before unloading. This prevents repeated SQLite reads and writes when a
293loader oscillates around a boundary. The delay should be configurable.
294
295# 6. Chunk lifecycle and persistence
296
297## 6.1 No periodic chunk saves
298
299Normal gameplay does not periodically rewrite loaded chunks. A chunk is
300saved as part of the unload path only.
301
302Resident chunk
303↓ last residency / forced shutdown unload
304Prepare unload
305↓
306Persist required chunk state once
307↓
308Persist required entities
309↓
310Remove ECS/runtime representation
311
312A graceful server restart does not introduce a second save mechanism. It
313force-unloads every resident region/chunk, so the normal unload
314persistence path remains the single source of truth.
315
316## 6.2 Persistent versus non-persistent entities
317
318Persistence is an entity property, not a property of the chunk or
319spawner. An entity with Persistent is serialised when its owning
320chunk/region unloads. A non-persistent entity is simply discarded.
321
322Non-persistent wolf
323spawn → simulate → chunk unload → disappear
324
325Persistent named NPC
326load → simulate → chunk unload → save → recreate when area loads
327
328## 6.3 Persistent is independent of ChunkLoader
329
330These traits must remain independent. A persistent entity does not
331automatically keep its area active, and a ChunkLoader does not
332automatically become persistent.
333
334# 7. Storage architecture
335
336## 7.1 Separate authored world and runtime state
337
338Use two SQLite databases with different responsibilities.
339
340| **Database** | **Responsibility** |
341|--------------|-----------------------------------------------------------------------------------------------------------------------------------------|
342| world.sqlite | Admin-authored ground tiles, block tiles, light maps, world settings, spawner configuration, per-chunk editor changelogs, world revisions and world metadata. |
343| state.sqlite | Accounts, characters, inventories, carried currency, character vaults, inheritance tabs, cheque reservations, skills, groups, courier cargo/transit, unexpired ground items, market orders/escrow/trades, per-item last player-market sale, persistent ECS entities, offline-script state, optional persistent runtime chunk overrides, and other durable live-game state. |
344
345This prevents editor authoring changes from becoming entangled with live
346player/entity persistence.
347
348## 7.2 Chunk writes in runtime state
349
350If initial gameplay does not allow permanent tile/block modification,
351runtime chunks require no writes at all. If permanent runtime world
352changes are later added, dirty chunk overrides are held in memory and
353written to state.sqlite only when that chunk unloads. Shutdown uses
354forced unload and therefore follows the same rule.
355
356## 7.3 Central persistence service
357
358Simulation workers should not independently compete for SQLite writes. A
359persistence service owns the write connection, batches transactions, and
360receives logical save requests from workers.
361
362Simulation workers
363│ save/unload messages
364▼
365Persistence service
366│
367▼
368SQLite (WAL)
369
370Live ECS state remains authoritative while loaded; SQLite is durable
371state, not a per-tick synchronisation mechanism.
372
373# 8. World authoring and revision model
374
375## 8.1 Admin-only world editor
376
377The server includes a separate admin-only world editor UI. It is not
378part of the normal player client.
379
380- Display one 16×16 chunk at a time.
381
382- Provide Up, Down, Left and Right navigation buttons that move the
383 editor exactly one chunk in that direction.
384
385- Show the current chunk coordinates prominently, and whether the chunk
386 is **open** or **closed**.
387
388- Toggle the current chunk open or closed. Closed chunks remain visible
389 to nearby players but cannot be entered.
390
391- Allow painting a ground type on a tile.
392
393- Allow painting, replacing or erasing the block type on a tile.
394
395- Render both layers together so the block appears on top of the ground.
396
397- Do not display ordinary mobile entities as editable map paint.
398
399- Allow selecting/configuring special block types such as Spawner, Bank,
400 Marketplace and light-emitting blocks (`lightRangeTiles`).
401
402- Open a **world settings** modal for global tick timers and constants
403 (movement cadence, shop lerp duration, drop lifetime, and other values
404 listed in section 8.5).
405
406- Provide a **night-to-day slider** that only previews lighting; it does
407 not change live world time. Preview uses the same baked light maps as
408 play, including light that reaches this chunk from neighbouring chunks.
409
410- Later: allow configuring ground-item spawners analogously to mob
411 spawners. Exact item tables remain a later content decision.
412
413- Save changes through an authenticated admin API; the browser never
414 opens SQLite directly.
415
416- Show that chunk's changelog: a chronological list of saves, each with
417 which admin made the edit, when, and a bullet-point diff of the change.
418
419The editor camera is **not** locked to a player character. It frames the
420currently selected chunk. This is the only intended exception to the
421player-centered play viewport in section 21.4.
422
423## 8.2 World editor save behaviour
424
425Saving a chunk **or world settings** writes the authored result to
426world.sqlite. It does not live-patch the currently running simulation.
427Instead, the change creates or updates a pending world revision and
428schedules a server restart for the next server-local midnight.
429
430The running game remains pinned to the world revision selected at its
431own startup. This avoids a dangerous mixed state where some loaded
432chunks use old authored data and newly loaded chunks use newer editor
433data.
434
435## 8.3 Versioned authored chunks
436
437A practical schema is to give every editor change a monotonically
438increasing world revision. The game process pins one active revision for
439its entire lifetime. Chunk lookup selects the latest authored version
440not newer than that pinned revision.
441
442world_revisions
443revision_id
444created_at
445created_by
446status // pending / active / superseded
447
448world_chunk_versions
449chunk_x
450chunk_y
451revision_id
452open // player-enterable; default false until set
453data_blob
454
455world_meta
456active_revision
457pending_revision
458
459world_settings
460revision_id
461settings_blob // walk speed, tick timers, shop lerp, drop TTL, ...
462
463world_chunk_edit_log
464log_id
465chunk_x
466chunk_y
467revision_id
468editor_admin_id
469edited_at
470diff_entries // structured bullets for this save
471
472On the next planned restart, startup promotes/selects the latest valid
473pending revision before world loading begins.
474
475## 8.4 Per-chunk changelog
476
477Every successful chunk save appends one changelog record for that chunk.
478The record is durable in `world.sqlite` and is not gameplay state.
479
480The server diffs the newly saved chunk against the previous authored
481version of that same chunk (the latest `world_chunk_versions` row for
482those coordinates that this save replaces). Unchanged tiles produce no
483bullets. Each changed tile becomes one of:
484
485```text
486- Ground at X, Y changed from Prev to New.
487- Block <type> placed at X, Y.
488- Block at X, Y changed from Prev to New.
489- Chunk opened.
490- Chunk closed.
491```
492
493`X, Y` are world tile coordinates. `Prev` / `New` / `<type>` are the
494ground or block definition display names. A block paint on an empty block
495layer is a placement. Replacing one block type (or its config, such as a
496spawner) with another is a change. Erasing a block is a removal. Ground is
497never absent; a ground paint is always a change from one type to another.
498
499The editor UI lists records newest-last or newest-first consistently, each
500headed by admin identity and timestamp, with that save's bullets underneath.
501The changelog is an audit trail, not an undo stack. Undo/redo remains an
502open editor-UX decision. Derived light maps are not changelog bullets;
503they are regenerated on save (section 8.6).
504
505## 8.5 World settings
506
507Global gameplay constants live in authored `world_settings` for the world
508revision. They are **not** per-mob and **not** client-authored. Admins
509edit them from a modal in the world-editor UI. Saving the modal writes
510into the pending world revision and schedules the same midnight restart
511as a chunk save. The running process keeps the settings it loaded at
512startup.
513
514Minimum initial settings and defaults:
515
516```text
517WorldSettings
518- walkTilesPerSecond // default 2
519- simulationTickHz // default 20; implementation default, still a setting
520- shopPriceLerpDuration // default 1 hour
521- groundItemDespawnDuration // default 10 minutes
522- regionUnloadGracePeriod // configurable grace after last residency
523- defaultGroundTypeId // grass used for never-edited chunks
524- characterDeletionDelay // default 24 hours
525```
526
527Running is always **double** walking speed. It is not a separate per-entity
528field. From `walkTilesPerSecond`:
529
530```text
531runTilesPerSecond = walkTilesPerSecond * 2 // default 4
532movementTickHz = runTilesPerSecond // default 4 Hz
533walk: commit a tile every 2 movement ticks
534run: commit a tile every 1 movement tick
535```
536
537All ground mobiles — players, enemies, NPCs — use this same cadence. A
538mob definition does not set move speed. Gait (`walk` | `run`) is the only
539per-entity choice; it selects every-other vs every movement tick.
540
541Other tick-duration constants that already exist in this document (shop
542lerp, ground-item despawn, residency grace, and later ones of the same
543kind) are edited here rather than hardcoded. Adding a new global timer
544means adding a field to `WorldSettings` and a row in this modal.
545
546## 8.6 Baked lighting
547
548Light from authored blocks is precomputed when a chunk is saved, not
549raytraced every simulation tick.
550
551A block definition may set `lightRangeTiles > 0`. That tile is a static
552light source. Light travels only through **passable** tiles (the same
553passability as walking). Ground type does not block light. Mobiles and
554ground items do not block light.
555
556For every tile within a source's range, the baker runs a simple grid
557raycast (for example Bresenham through tile centres). If the ray hits an
558impassable block before the destination, that source does not light that
559tile. A tile is lit if **any** source can reach it. Light **does** shine
560across chunk boundaries.
561
562Saving a chunk rebakes:
563
5641. that chunk's 16×16 light map, and
5652. every neighbouring chunk that could be affected (chunks within the
566 maximum `lightRangeTiles` of the saved chunk).
567
568Neighbor rebakes use light sources and walls from the pending revision,
569including the chunk just saved. Those neighbor light maps are written
570into the same pending revision so play never mixes old and new lighting.
571
572The light map is stored in the chunk `data_blob` (a 16×16 reachable-or-
573not mask, optionally with distance to the nearest reaching source). It is
574replicated to clients in `CHUNK_SNAPSHOT` / `CHUNK_DELTA`.
575
576Runtime door open/close does not rebake static light unless a later
577iteration adds live lighting. Baked light is authored geometry.
578
579The editor night-to-day slider interpolates preview ambient from full
580night (dark except baked-lit tiles) to full day (no ambient darkening).
581It does not persist and does not change server/world clock.
582
583## 8.7 Default chunks and open / closed
584
585A chunk the editor has never saved does not exist in `world_chunk_versions`.
586At runtime it is synthesised as:
587
588- every tile `defaultGroundTypeId` (grass),
589- no blocks,
590- **closed**,
591- no baked lights.
592
593The world is therefore an infinite grass field until admins paint it, and
594players cannot walk onto it until an admin **opens** the chunk.
595
596**Closed** chunks can still appear in a player's 3×3 view. They cannot be
597entered: `MOVE_TO`, pathfinding, spawning, and other player-entry actions
598treat every tile in a closed chunk as impassable. Visibility and lighting
599previews are unchanged.
600
601**Open** chunks are the playable map. Opening or closing is an authored
602chunk flag, saved with the pending revision like paint.
603
604Spawners in a closed chunk do not spawn. Ground movement, including AI,
605does not step into a closed chunk. If a future bug or admin tool places an
606entity there, it can still be replicated to observers, but players cannot
607walk in after it.
608
609# 9. Spawner blocks
610
611## 9.1 Spawner data
612
613A Spawner is a block in the authored block layer, with per-instance
614configuration stored as part of the chunk data.
615
616SpawnerConfig {
617spawnerId: SpawnerId,
618mobTypeId: MobTypeId,
619maxAlive: number,
620spawnRangeTiles: number
621}
622
623Additional parameters such as minimum/maximum spawn delay can be added
624later without changing the core model.
625
626## 9.2 Spawner editor
627
628Selecting a Spawner tile in the world editor opens a configuration panel
629containing at minimum: mob type, maximum alive count and spawn range.
630Validation happens server-side before the pending world revision is
631written.
632
633## 9.3 Spawned entity persistence
634
635The spawner never decides whether its mob is persistent. The mob
636definition/archetype does. When the spawner creates an entity, the
637entity receives Persistent only if that mob type is defined as
638persistent.
639
640MobDefinition: deer
641persistent = false
642
643MobDefinition: named_guard_captain
644persistent = true
645
646## 9.4 SpawnOrigin
647
648Spawned mobs receive a SpawnOrigin component referencing the spawner.
649This lets maxAlive count only entities belonging to that spawner and
650avoids expensive geometric searches.
651
652SpawnOrigin {
653spawnerId: SpawnerId
654}
655
656For non-persistent mobs, disappearance on chunk unload naturally
657decreases the count. For persistent mobs, SpawnOrigin is persisted so
658the spawner can recognise an existing persistent instance even after it
659has moved or been unloaded elsewhere. A lightweight persistence index by
660spawnerId prevents duplicate persistent spawns.
661
662## 9.5 Spawner simulation
663
664SpawnerSystem runs only while the spawner’s chunk is simulating **and
665open**, and at a much lower frequency than movement. A spawn candidate
666must satisfy block collision, bounds, an open chunk, and mobile-occupancy
667rules. Ground type does not affect passability unless a later gameplay
668system explicitly introduces a separate rule for it.
669
670## 9.6 Future ground-item spawners
671
672Some items will later spawn naturally on the ground, using a world-editor
673block analogous to a mob spawner. Those spawned stacks should use the same
674non-blocking ground-item representation as player drops, but their lifetime,
675respawn and `maxOnGround` rules belong to the spawner configuration rather
676than the 10-minute player-drop timer.
677
678Exact item lists, harvest interactions and spawner parameters are later
679content decisions and do not block the inventory/bank model.
680
681# 10. Startup and loading order
682
683Loading order is explicit so authored world state exists before
684persistent entities are instantiated into it.
685
686> **1.** Start process and load configuration, including server time
687> zone and storage paths.
688>
689> **2.** Open world.sqlite and validate/migrate its schema.
690>
691> **3.** Select/promote the world revision to use for this process and
692> pin it for the lifetime of the process.
693>
694> **4.** Load static registries: ground definitions, block definitions,
695> item definitions, material definitions, spell definitions, mob archetypes and component serializers.
696>
697> **5.** Open state.sqlite and run runtime-state migrations.
698>
699> **6.** Start the persistence service, durable domain services (such as courier, bank, market and shop-price services when enabled), region coordinator and simulation workers.
700>
701> **7.** Load the index of persistent entities that themselves require
702> world activation (for example persistent ChunkLoaders or future
703> offline scripted players).
704>
705> **8.** For each required region, load authored chunk data from the
706> pinned world revision first.
707>
708> **9.** Apply any durable runtime chunk override state, if the game
709> supports such modifications.
710>
711> **10.** Instantiate persistent entities into the already-created
712> world/chunks.
713>
714> **11.** Recalculate ChunkLoader references and begin chunk simulation.
715>
716> **12.** Only after the world reports READY does the gateway accept
717> normal player logins.
718
719This ordering solves the bootstrap problem for persistent entities that
720keep their own chunks active: a compact persistence index can locate
721them without first loading the entire world.
722
723# 11. Simulation workers and region ownership
724
725## 11.1 Ownership invariant
726
727Exactly one worker authoritatively owns a region at any instant. Every
728authoritative entity belongs to the worker that owns the entity’s
729current region.
730
731## 11.2 Coordinator
732
733A central region coordinator maintains RegionId → WorkerId and
734assigns/migrates regions based on actual measured simulation effort,
735while preferring neighbouring regions on the same worker when load
736permits.
737
738## 11.3 Work measurement
739
740- Average and high-percentile tick execution time.
741
742- Number of simulating chunks.
743
744- Number of active entities and AI entities.
745
746- Pathfinding work and queued searches.
747
748- Cross-worker boundary message volume.
749
750- Backlog / tick lateness.
751
752Actual time spent simulating is more important than raw player count or
753raw region count.
754
755## 11.4 Node.js implementation
756
757Start with Node.js worker_threads for simulation workers. Keep mutable
758ECS worlds isolated per worker and use message passing between them. Do
759not begin with a shared mutable ECS in SharedArrayBuffer.
760
761# 12. Cross-worker communication
762
763## 12.1 No remote mutation
764
765A worker may inspect a limited read-only representation of neighbouring
766entities but never directly mutates authoritative state owned by another
767worker.
768
769## 12.2 Border ghosts
770
771Neighbouring workers can exchange compact border/ghost entity data for
772nearby interaction and AI: EntityId, position, collision footprint, type
773and minimal combat metadata. Ghosts are not full ECS entities and are
774never authoritative.
775
776## 12.3 Remote actions
777
778Worker A goblin targets Player 42 (owned by Worker B)
779Worker A → REMOTE_ACTION(attack intent) → Worker B
780Worker B validates range/state and applies authoritative result
781
782## 12.4 Entity transfer
783
784When an entity crosses from a region owned by Worker A into one owned by
785Worker B, ownership is handed off at a simulation tick boundary using a
786sequence-numbered transfer protocol. There is never more than one
787authoritative copy.
788
789A: prepare transfer
790B: validate / accept
791A: freeze at handoff boundary
792B: instantiate authoritative entity at effective tick
793Coordinator: update ownership mapping
794A: remove authoritative copy
795
796# 13. Server tick and stimulation
797
798## 13.1 Fixed simulation tick
799
800Use a fixed server simulation tick. The default is 20 Hz (50 ms), stored
801as `WorldSettings.simulationTickHz`. This is not a protocol promise.
802
803Movement does **not** commit a new tile on every simulation tick. See
804section 13.4.
805
8061\. Drain validated incoming commands
8072. Apply completed worker/entity transfers
8083. Recalculate activation changes
8094. Movement / collision
8105. Combat
8116. Scheduled AI
8127. Scheduled spawners/environment, including ground-item expiry in simulating chunks
8138. Produce cross-worker messages
8149. Produce client replication deltas
81510. Queue unload/persistence work
816
817## 13.2 Different system frequencies
818
819Not every ECS system should run every tick. Ground movement commits only
820on the global movement cadence (section 13.4). AI decisions, target
821searches and spawner checks can run at lower frequencies. Sleeping chunks
822are not “slow ticked”; they are omitted from normal simulation.
823
824## 13.3 Timestamp-based inactive progression
825
826Long-lived timers such as growth, cooldowns, ground-item expiry and shop
827price lerps should store future timestamps where possible. When an area
828wakes, the system catches up from the timestamp instead of executing missed
829ticks. An expired ground item is discarded on catch-up without ever
830reappearing. Shop and tooltip prices are evaluated from last-sale timestamps
831when observed; they are not ticked. Durations such as shop lerp and
832ground-item despawn come from `WorldSettings`, not from hardcoded
833literals in systems.
834
835## 13.4 Global movement cadence
836
837All ground-moving entities share one walk speed and one run speed.
838
839- Default walk: **2 tiles per second** (`walkTilesPerSecond`).
840- Run: always **double** walk (default 4 tiles per second).
841- Movement ticks fire at `runTilesPerSecond` (default 4 Hz).
842- **Walk:** the entity may advance one path tile on every other movement
843 tick.
844- **Run:** the entity may advance one path tile on every movement tick.
845
846Mobs do not define their own move speed. `Movement.gait` is `walk` or
847`run`. Players send `SetGait`. AI may set gait; it still uses the global
848cadence. Flying pigeon transit is not this cadence; it keeps its own
849route clock.
850
851If the path is blocked on a movement tick, the entity stays on its tile
852and retries on a later legal tick. Occupancy, combat range and pickup
853always use the last committed tile.
854
855## 13.5 World calendar time
856
857World time is server time **1:1**, in the same configured IANA zone used
858for midnight restarts, with **1200 years subtracted** from the calendar
859date. A server clock of 24 Aug 2026 21:00 is world 24 Aug 826 21:00.
860Clock-of-day, including night, therefore matches the host's zone.
861
862The gateway includes current world time (or server unix time plus the
863year offset) in the status sent to clients so shading does not depend on
864the player's device clock. Lighting is presentation; combat and movement
865do not wait on the day/night overlay.
866
867# 14. Client gateway and authority
868
869## 14.1 Stable connection ownership
870
871Client WebSocket/TCP connections belong to a gateway rather than
872simulation workers. When the player crosses into a region owned by
873another worker, the socket stays connected to the same gateway; only
874internal routing changes.
875
876## 14.2 Client commands are intentions
877
878A client sends commands such as MoveTo, Interact, Attack, UseItem,
879EquipItem, UnequipItem, SelectSpell, SetGait, DropItem, PickupItem, BankDeposit,
880BankWithdraw, BuyFromShop or SendPigeon. The authenticated **account**
881determines the actor; after character select, commands apply to that
882account's **active character**. The
883client never supplies an authoritative resulting position, health
884value or inventory result.
885
886## 14.3 Input queue
887
888Socket handlers validate message shape and enqueue commands. Simulation
889workers consume commands at tick boundaries. WebSocket callbacks do not
890mutate ECS state directly.
891
892## 14.4 Authentication
893
894Live login uses **auth.timfalken.com**. The game server never stores a
895password. It receives an authenticated account identity (and email) from
896that service and maps it to a durable `accountId` in `state.sqlite`.
897
898Until auth.timfalken.com is available, the gateway uses a **stub identity**:
899each new connection is `admin-<n>`, where `n` is the number of currently
900connected clients **including this one** (the first connection is
901`admin-1`). Stub accounts are treated as admins so the world editor can be
902used during development. Stub accounts have no email; deletion “emails”
903are logged instead of sent.
904
905When real auth ships, the stub is removed. Admin rights come from that
906service, not from the `admin-` name prefix.
907
908An account may have only **one active play session** at a time (one
909character in the world).
910
911## 14.5 Characters
912
913An account has unlimited characters and plays **one** at a time. First
914login with no characters must create one before entering the world. Later
915logins show a character-selection menu: create, choose, mark for deletion,
916or cancel deletion.
917
918Initial character setup (may change later):
919
920```text
921CreateCharacter
922- firstName // not globally unique
923- lastName // unique surname, owned by this account
924- sex // male | female
925```
926
927Rules:
928
929- **Last names** are globally unique. The first character to take a surname
930 claims it for that **account**. The same player may reuse that last name
931 on their other characters. Another account cannot use it.
932- **First names** need not be unique globally.
933- For a given account, `firstName` + `lastName` must be unique among
934 characters that still exist (including those pending deletion).
935- Uniqueness is case-insensitive; display uses the casing the player typed.
936
937```text
938Account
939- accountId
940- authSubject // from auth.timfalken.com, or stub admin-<n>
941- email? // from auth; absent on stub
942- surnameClaims[]
943
944Character
945- characterId
946- accountId
947- firstName
948- lastName
949- sex
950- deletionScheduledAt? // null if not deleting
951- inventory, equipment, currency, vault, skills, ...
952```
953
954The in-world ECS player entity is a **character**, not the account.
955
956## 14.6 Character deletion and inheritance
957
958From character select, the player may mark a character for deletion.
959
960- The character cannot be played while deletion is pending.
961- Permanent delete happens after `characterDeletionDelay` (default **24
962 hours**). Until then the player may cancel.
963- The server **always** notifies the account email when deletion is
964 marked (and should notify again on cancel and on actual delete). Stub
965 auth logs the message instead.
966- On permanent delete, the name pair is freed. If this account has no
967 remaining characters with that last name, the surname claim is released.
968- Before the vault is moved, `BankService` voids outstanding filled
969 cheques **issued by** this character (reservations return to the vault).
970- All items in inventory, equipment, carried currency, and the character
971 vault are moved to that **account's inheritance bank tab**.
972
973Any living character of the same account may, at a bank, **claim**
974inheritance stacks (and currency) into that character's own vault. Claiming
975is a move from the account tab to the character vault, not a second copy.
976
977# 15. Client chunk subscription and replication
978
979## 15.1 3×3 visibility
980
981A player receives the current chunk and the eight surrounding chunks, a
982maximum viewport of 48×48 tiles. Neighbouring **closed** chunks are still
983sent so scenery remains visible; the player simply cannot walk onto them.
984
985┌───┬───┬───┐
986│ V │ V │ V │
987├───┼───┼───┤
988│ V │ P │ V │
989├───┼───┼───┤
990│ V │ V │ V │
991└───┴───┴───┘
992
993## 15.2 Incremental subscription changes
994
995Crossing one chunk east subscribes only the three newly visible eastern
996chunks and unsubscribes only the three old western chunks. The rest of
997the 3×3 view remains subscribed.
998
999## 15.3 Snapshots and deltas
1000
1001Initial subscription sends a CHUNK_SNAPSHOT containing authored/runtime
1002tile state, currently visible entities and unexpired ground item stacks.
1003Afterwards, revisioned CHUNK_DELTA messages report tile changes, entity
1004spawn/move/change/despawn events and ground-item appear/change/despawn
1005events. Full chunks are not retransmitted every tick.
1006
1007Entity `move` events carry the new integer tile and the current gait so
1008the client can lerp over the walk or run interval. They do not carry a
1009fractional in-between position. Smooth walking is a client visual lerp
1010(section 21.5), not part of the replication payload.
1011
1012Chunk snapshots include the baked light map (section 8.6).
1013
1014Visible equipment is replicated as a compact appearance payload (body
1015sprite plus worn overlay layers and recolour parameters), not as the
1016entity's full inventory. Nearby clients can draw another player's armour
1017without receiving their bags.
1018
1019## 15.4 Visibility can span workers
1020
1021The gateway can source visible chunks from multiple workers. A player
1022may be authoritative on Worker A while one or more of the eight
1023neighbouring visible chunks are owned by Worker B. Client visibility
1024must never force simulation-region reassignment.
1025
1026# 16. Click-to-move and A\* pathfinding
1027
1028## 16.1 Command flow
1029
1030Client: MOVE_TO(tileX, tileY)
1031↓
1032Gateway validates/authenticates
1033↓
1034Owning worker validates target
1035↓
1036A\* calculates authoritative route
1037↓
1038Path component attached/updated
1039↓
1040MovementSystem advances the entity **one tile at a time** on the global
1041walk/run cadence (section 13.4)
1042
1043Authoritative `Position` is always an integer `tileX`, `tileY`. The server
1044does not store a sub-tile location for walking mobiles. When a movement
1045tick allows this gait to step, `MovementSystem` commits the next path
1046tile in a single jump. Combat, occupancy, pickup and interaction all use
1047that committed tile.
1048
1049Flying pigeons still ignore the ground navigation grid, but their
1050replicated ECS position is likewise a tile. The transit clock determines
1051which tile they occupy at a given time; the client may lerp the sprite
1052between those tiles like any other mobile.
1053
1054## 16.2 Initial A\* implementation
1055
1056For normal player clicks within the visible 3×3 chunks, the search space
1057is at most 48×48 = 2,304 tiles, so conventional A\* is a strong starting
1058point.
1059
1060- Binary heap priority queue for the open set.
1061
1062- Manhattan heuristic for four-direction movement; octile heuristic if
1063 diagonal movement is later allowed.
1064
1065- Reusable typed-array or pooled search buffers for hot paths to reduce
1066 allocation and garbage collection.
1067
1068- Rate-limit path requests per player and avoid recalculation every
1069 tick.
1070
1071- Use block passability, **open-chunk** bounds, and dynamic occupancy;
1072 ground is visual only. Tiles in closed or never-edited chunks are not
1073 legal path targets for players.
1074
1075## 16.3 Navigation revisions
1076
1077Each chunk maintains a navigation revision that increments when a
1078movement-affecting block changes. A path records the relevant revisions.
1079Static geometry changes can invalidate paths; temporary mobile occupancy
1080normally causes a short wait or small local re-path rather than
1081rebuilding every path.
1082
1083## 16.4 Long-distance extension
1084
1085If long-distance autonomous travel is added later, introduce
1086hierarchical pathfinding: region graph → chunk portals/edges → local
1087tile A\*. The client movement command interface does not need to change.
1088Server movement remains discrete tile steps; only the path length changes.
1089
1090# 17. Automatic update and restart scheduler
1091
1092## 17.1 Restart triggers
1093
1094A graceful restart is scheduled for the next midnight in configured
1095server-local time when either of these conditions occurs:
1096
1097- A new commit is detected on origin/master. The master branch is the
1098 live branch.
1099
1100- An administrator saves a world-editor change, creating/updating a
1101 pending authored world revision.
1102
1103Multiple triggers coalesce into one scheduled restart. The scheduler
1104stores all reasons so players and admins can see why a restart is
1105pending.
1106
1107## 17.2 Detecting live-code changes
1108
1109The running server periodically performs a non-destructive remote check,
1110for example git fetch origin master followed by comparison of the
1111running commit with origin/master. It does not update the checked-out
1112code while the game is live.
1113
1114## 17.3 Server-local midnight
1115
1116Midnight is calculated in a configured IANA time zone rather than by
1117adding 24 hours to the current time. This keeps behaviour correct across
1118daylight-saving transitions.
1119
1120## 17.4 Player-visible restart state
1121
1122Restart status is part of the server status sent to clients. Connected
1123players see that a restart is scheduled and the scheduled local time.
1124The server can also issue configurable countdown notices as the restart
1125approaches and includes the state immediately when a player logs in.
1126
1127RestartStatus {
1128scheduled: true,
1129scheduledAt: timestamp,
1130reasons: \["code-update", "world-update"\]
1131}
1132
1133## 17.5 Manual admin restart
1134
1135An authorised admin action can invoke the same graceful restart pipeline
1136immediately. This is not a separate “hard restart” path; it differs only
1137in scheduled time.
1138
1139## 17.6 Graceful restart sequence
1140
1141> **1.** Enter `DRAINING` / `RESTARTING` state and reject new logins.
1142>
1143> **2.** Broadcast the final restart notice.
1144>
1145> **3.** Disconnect player sessions cleanly and persist session state.
1146> Shutdown handling overrides normal offline-script retention so chunk
1147> unload cannot be blocked by a retiring process.
1148>
1149> **4.** Stop accepting new gameplay commands and finish the current
1150> safe tick boundary.
1151>
1152> **5.** Force-unload every resident region/chunk, ignoring normal
1153> `ChunkLoader` references. This invokes the ordinary chunk/entity unload
1154> persistence path exactly once.
1155>
1156> **6.** Flush the persistence service and close SQLite connections
1157> cleanly.
1158>
1159> **7.** Atomically write a restart request manifest. It records the
1160> restart reasons, whether a code deployment is requested, the target Git
1161> commit if known, and the pending world revision if one exists.
1162>
1163> **8.** Exit the Node.js game process cleanly. At this point the game
1164> process has no responsibility for updating or relaunching itself.
1165
1166## 17.7 systemd process supervisor
1167
1168The production Node.js process is owned by a `systemd` service. `systemd`
1169therefore already knows when the process has **fully exited**; no separate
1170polling process is needed. Only after the previous `ExecStart` process is
1171gone does `systemd` begin the next service start.
1172
1173The preferred lifecycle is:
1174
1175```text
1176Running Node.js server
1177 |
1178 | graceful planned restart or crash
1179 v
1180Node.js process fully exits
1181 |
1182 v
1183systemd starts the service again
1184 |
1185 +--> conditional update hook
1186 | |
1187 | +--> planned code deployment: git fetch/pull --ff-only
1188 | +--> world-only restart: no Git mutation
1189 | +--> crash/no restart manifest: no Git mutation
1190 |
1191 +--> optional dependency/build step if deployment changed code
1192 |
1193 v
1194Start Node.js server
1195 |
1196 v
1197Startup selects the new active world revision
1198 |
1199 v
1200Gateway opens when the world reports READY
1201```
1202
1203### 17.7.1 Why Git pull must be conditional
1204
1205A naive `ExecStartPre=git pull` on **every** restart is unsafe. Suppose a
1206new commit is detected at 14:00 and correctly scheduled for midnight, but
1207the game process crashes at 16:00. An unconditional pull would deploy the
1208new commit immediately during crash recovery, bypassing the scheduled
1209maintenance window.
1210
1211Therefore the restart manifest distinguishes an intentional deployment
1212restart from an ordinary process failure:
1213
1214```json
1215{
1216 "reason": ["code-update", "world-update"],
1217 "deployCode": true,
1218 "targetCommit": "<optional commit hash>",
1219 "pendingWorldRevision": 184
1220}
1221```
1222
1223The manifest should be written using a temporary file plus atomic rename
1224so the supervisor never consumes a half-written request. The supervisor
1225consumes/removes the request only after it has successfully interpreted
1226it.
1227
1228If the Node.js process dies without a valid deployment request, `systemd`
1229restarts the **currently checked-out version**. This gives fast crash
1230recovery without prematurely deploying pending code.
1231
1232### 17.7.2 Suggested systemd shape
1233
1234A production unit can conceptually look like this:
1235
1236```ini
1237[Unit]
1238Description=Tile MMO Server
1239After=network-online.target
1240Wants=network-online.target
1241
1242[Service]
1243Type=simple
1244User=tilemmo
1245Group=tilemmo
1246WorkingDirectory=/srv/tile-mmo/current
1247
1248# This hook checks the restart manifest. It pulls/builds only when an
1249# intentional deployment was requested. Prefixing with '+' optionally
1250# allows the hook to run with privileges different from the game user.
1251ExecStartPre=+/usr/local/sbin/tile-mmo-update-if-requested
1252ExecStart=/usr/bin/node /srv/tile-mmo/current/dist/server.js
1253
1254Restart=always
1255RestartSec=5s
1256TimeoutStopSec=120s
1257KillSignal=SIGTERM
1258
1259[Install]
1260WantedBy=multi-user.target
1261```
1262
1263`Restart=always` is appropriate here because an explicit
1264`systemctl stop tile-mmo` does not cause systemd to restart the unit,
1265while a clean in-game restart exit and an unexpected crash both do.
1266
1267The exact paths, build command and privilege split are deployment
1268details, but the important invariant is that the **Node.js process does
1269not pull Git itself**.
1270
1271### 17.7.3 Code-update, world-update and crash behaviour
1272
1273| Situation | Restart manifest | Git pull before restart | World revision |
1274|---|---|---|---|
1275| Scheduled code update | `deployCode=true` | Yes, fast-forward only | Activate pending revision if present |
1276| World-editor-only update | `deployCode=false` | No | Activate pending revision |
1277| Manual deployment restart | Explicit admin intent | As requested | Activate pending revision if present |
1278| Unexpected Node.js crash | Missing/invalid | **No** | Continue current active revision |
1279| `systemctl stop` | Irrelevant | No automatic restart | N/A |
1280
1281This preserves the midnight deployment promise even when the game crashes
1282before the scheduled maintenance window.
1283
1284## 17.8 Failure behaviour
1285
1286Deployment should fail closed. If Git cannot fast-forward, a build or
1287migration fails, or startup validation fails, the game must not open to
1288players on a partially updated state. The update hook should log the
1289failure clearly and return non-zero; systemd may retry according to its
1290restart/start-limit policy. Databases remain intact, and backups or
1291snapshots before schema migrations are recommended.
1292
1293A failed **crash recovery** that did not request deployment must not
1294silently switch to a newer Git commit as a recovery strategy.
1295
1296# 18. Future player scripting architecture
1297
1298## 18.1 Scope
1299
1300The custom scripting language is explicitly a later feature. Version 1
1301only needs architectural hooks so adding scripts does not require
1302replacing the player-control or simulation model.
1303
1304## 18.2 Controller abstraction
1305
1306All player actions should already pass through an internal command
1307interface. Manual client input is therefore one possible controller. A
1308future script is another controller that emits the same validated action
1309intentions.
1310
1311```text
1312ClientController ─┐
1313 ├─> ActionCommand queue ─> authoritative game systems
1314ScriptController ─┘
1315```
1316
1317Scripts never mutate ECS components directly. They request actions such
1318as MoveTo, Interact or Attack and receive the same validation as a human
1319client.
1320
1321## 18.3 Online scripted mode
1322
1323A logged-in player may enable the script while remaining connected and
1324observing the game. Control mode explicitly determines whether manual
1325input or the script is currently producing gameplay commands. The server
1326remains authoritative either way.
1327
1328## 18.4 Logout with active script
1329
1330If a player has configured offline script execution, logout removes the
1331network/controller connection but keeps the player entity alive. The
1332entity changes to an offline script-controlled state and continues
1333acting until it dies or its configured offline duration expires.
1334
1335Player online
1336Player + NetworkIdentity + ChunkLoader + Controller
1337↓ logout with offline scripting
1338Player + ScriptController + ChunkLoader + OfflineUntil
1339↓ death OR expiry
1340persist player state → remove runtime entity
1341
1342## 18.5 Offline scripted players and loading
1343
1344An offline scripted player must continue to stimulate the world it
1345traverses, so it retains a ChunkLoader. This is powerful but potentially
1346expensive: thousands of offline scripts could keep large parts of the
1347world active. Offline duration, script CPU budget and concurrent
1348offline-script limits therefore become explicit resource policy, not
1349implementation accidents.
1350
1351## 18.6 Restart continuity
1352
1353A planned restart persists the offline-script state and expiry time,
1354force-unloads the old process, and rehydrates still-valid offline
1355scripted players during startup. This is why the startup index for
1356persistent ChunkLoaders is part of the base architecture.
1357
1358## 18.7 Scripting language safety requirements
1359
1360When the language is implemented, it should be interpreted/compiled into
1361a purpose-built sandbox rather than evaluated as JavaScript. At minimum
1362it should enforce:
1363
1364- No file-system, operating-system, database or arbitrary network
1365 access.
1366
1367- No eval or escape into Node.js objects.
1368
1369- Per-tick/per-event instruction budgets and bounded memory.
1370
1371- Rate-limited expensive operations such as path requests and world
1372 queries.
1373
1374- Capability-based read APIs for nearby visible/known world state.
1375
1376- Action output only through the normal server command pipeline.
1377
1378- Persistable script variables/state if offline execution must survive
1379 restarts.
1380
1381- Deterministic or tightly controlled timing semantics where practical.
1382
1383An event-driven language is preferable to running every player script
1384continuously at full simulation frequency. Events such as arrival,
1385attack, nearby entity changes or timer expiration can wake scripts only
1386when useful.
1387
1388# 19. Security and administration
1389
1390- World-editor endpoints require an explicit admin role and separate
1391 server-side authorisation checks.
1392
1393- Client-supplied entity/player IDs are never trusted as authority;
1394 authenticated connection/session context identifies the actor.
1395
1396- World-editor data is validated against known ground, block, item and mob
1397 definitions before database write.
1398
1399- Admin restart and deployment controls use the same authenticated
1400 administration layer.
1401
1402- The Node.js game process should run as a dedicated unprivileged user.
1403 Where practical, source-update permission belongs only to the systemd
1404 update hook (for example a privileged `ExecStartPre` helper), leaving
1405 the running Node.js process unable to modify its own checkout.
1406
1407- SQLite writes are parameterised and centralised through
1408 persistence/editor services.
1409
1410- Inventory, vault, cheque and courier mutations are server-authoritative.
1411 Clients cannot invent cheque IDs, forge cargo, or credit a vault.
1412
1413- Attack hit/miss and damage are server-authoritative. Clients cannot supply
1414 a roll or a damage result. Shop purchase prices are computed at buy time
1415 on the server.
1416
1417# 20. Recommended process topology
1418
1419```text
1420Clients
1421 |
1422 v
1423WebSocket/API Gateway
1424 |
1425 +-- Region Coordinator ----> Simulation Worker A
1426 | <--> Simulation Worker B
1427 |
1428 +-- Communication Service --> proximity speech
1429 |
1430 +-- CourierService ---------> pigeon cargo / transit
1431 |
1432 +-- BankService ------------> shared vaults / cheques / reservations
1433 |
1434 +-- MarketService ----------> order book / escrow / trades / last-sale index
1435 |
1436 +-- Persistence Service ----> state.sqlite
1437 |
1438 +-- Admin / World Editor ---> world.sqlite
1439
1440External process supervision:
1441systemd ---> conditional deployment hook ---> Node.js relaunch
1442```
1443
1444# 21. Player client architecture
1445
1446## 21.1 FrameworkV3 as a git submodule
1447
1448The player-facing client is built on the shared FrameworkV3 library:
1449
1450<https://gitlab.com/Timfa/frameworkv3>
1451
1452FrameworkV3 contains generic reusable client-side code. Game-specific rendering,
1453UI, input, assets and protocol handling live in this repository, on top of
1454that library. They are not patched into FrameworkV3 unless they are genuinely
1455reusable across games.
1456
1457This repository vendors FrameworkV3 as a **git submodule** rather than
1458copying its source or depending on an unpublished global install.
1459
1460```text
1461mmo/
1462 client/
1463 frameworkv3/ # git submodule → gitlab.com/Timfa/frameworkv3
1464 src/ # this game's client: protocol, UI, world view, assets
1465 server/ # Node.js ECS backend; does not import FrameworkV3
1466```
1467
1468The submodule path is `client/frameworkv3`. A clone of this repo is not
1469client-buildable until submodules are present:
1470
1471```text
1472git clone --recurse-submodules <this-repo>
1473# or, in an existing checkout:
1474git submodule update --init --recursive
1475```
1476
1477The submodule records a **pinned commit**. Bumping FrameworkV3 is an explicit
1478commit in this repository (new submodule SHA). Game code must not rely on an
1479uncommitted dirty checkout of the submodule.
1480
1481Build order:
1482
1483```text
14841. Build FrameworkV3 from client/frameworkv3
14852. Build this game's client against that output
14863. The Node.js server is a separate build and does not link FrameworkV3
1487```
1488
1489The exact FrameworkV3 build command follows that project's own instructions.
1490This game's client build must consume the framework's public/build artefacts,
1491not fork its internals.
1492
1493CI and developer machines check out submodules before the client job. A
1494missing or uninitialized submodule is a failed client build, not a fallback
1495to a system copy of FrameworkV3.
1496
1497If this repo's `master` also ships the built web/desktop client from the
1498same process that deploys the game server, a submodule bump is just another
1499commit and follows the normal midnight restart/deploy path. The running
1500Node.js game process still does not compile or import FrameworkV3.
1501
1502The backend remains the authoritative Node.js ECS simulation described in this
1503document. The client does **not** need to use ECS. It receives only a small
15043×3-chunk view plus player/UI state, so a conventional object/view-model model is
1505simpler and entirely appropriate.
1506
1507## 21.2 Server/client model separation
1508
1509Backend ECS components are not treated as a shared client object model. Network
1510messages form the contract between the two sides.
1511
1512```text
1513Authoritative Node.js ECS
1514 |
1515 | snapshots / deltas / UI state
1516 v
1517Network protocol DTOs
1518 |
1519 v
1520Built FrameworkV3 (from client/frameworkv3 submodule)
1521 |
1522 v
1523This game's client code (client/src)
1524```
1525
1526The two projects may share protocol schemas, enums or generated message types,
1527but the client must not depend on the internal layout of ECS component storage.
1528That allows server internals to be optimised without forcing corresponding
1529client rewrites.
1530
1531## 21.3 Sprites are 16×16
1532
1533Every world sprite — ground tiles, blocks, mobs, item icons and other
1534in-world art — is exactly **16×16 pixels**. Sprites are not individually
1535stretched to a different size. One sprite corresponds to one tile on the
1536world pixel grid.
1537
1538At load time, any image whose width or height is not 16 is **rejected**.
1539The asset must not enter the runtime atlas or definition registry. The
1540failure should name the file and its actual dimensions.
1541
1542A unit test walks the sprite asset tree (grounds, blocks, mobs, items,
1543equipment overlays, recolour masks, and any other world-sprite folders)
1544and performs the same check. It reports every offender and **fails if any
1545are found**. This test belongs in CI so a non-16×16 sprite cannot ship even
1546if a local load path is skipped. Recolour masks are 16×16 world sprites
1547too; a mismatched mask is a failed test.
1548
1549Camera zoom (section 21.4) scales the whole viewport uniformly. It is not
1550a per-sprite size override. Rendering should use nearest-neighbour
1551sampling so 16×16 pixels stay sharp.
1552
1553## 21.4 Viewport, camera and zoom
1554
1555In normal play the viewport is **always centered on the local player's
1556character**. The camera does not free-pan. Scrolling the world happens
1557only because the player moved.
1558
1559The player may zoom in and out within configured minimum and maximum
1560bounds (for example 1× to 4×; the exact numbers are a game setting). Zoom
1561does not move the camera off the player and does not change server
1562visibility: the client still receives only the 3×3 chunk window.
1563
1564The admin world editor is the exception: it frames the selected 16×16
1565chunk and navigates by chunk, as in section 8.1.
1566
1567## 21.5 Client movement interpolation
1568
1569The server jumps mobiles from tile to tile. The client draws a visual
1570lerp between the previous replicated tile and the new one over the
1571interval implied by gait and `WorldSettings` (walk: `1 / walkTilesPerSecond`,
1572run: half of that). If a delta arrives late, clamp the remaining lerp.
1573That lerp is presentation only:
1574
1575- Hit tests, range, pickup and occupancy use the authoritative tile.
1576- A corrected server position snaps the interpolation target; the client
1577 does not accumulate drift.
1578- Interpolation does not entitle the client to send fractional positions.
1579
1580## 21.6 Equipment layers and recolouring
1581
1582A mob (including a player character) is drawn as a **stack of 16×16
1583sprites** on the same tile: the body sprite (male or female from character
1584sex, or the mob archetype body), then each piece of visible equipment.
1585Overlays are not baked into the body art.
1586
1587```text
1588draw order (back → front, default)
1589 1. body / mob base
1590 2. boots
1591 3. legs
1592 4. chest
1593 5. head
1594 6. off-hand
1595 7. weapon
1596```
1597
1598Slot draw order is data so a cloak or a two-handed sprite can be inserted
1599without a renderer rewrite. Every overlay sprite, like every other world
1600sprite, is exactly 16×16 and is rejected on load / CI if it is not.
1601
1602Equipment items stay in dedicated **equipment slots**, not in the 32
1603inventory slots, while worn. `EquipItem(slotIndex)` moves a legal item
1604from inventory into the matching equipment slot, returning any previously
1605worn item to inventory if there is space. `UnequipItem(equipSlot)` does
1606the reverse. The weapon equipment slot is what combat uses; it replaces
1607the older “wielded flag on an inventory slot” idea.
1608
1609Non-player mobs may carry an `Equipment` component or a simpler appearance
1610list on the mob definition so a guard can show armour without a player
1611inventory.
1612
1613```text
1614Equipment
1615- slots: { head?, chest?, legs?, boots?, weapon?, offhand?, ... }
1616
1617ItemDefinition.equipment?
1618- slot
1619- overlaySpriteId
1620- recolourableChannels?: ["metal"] // omitted if the art is not recoloured
1621- materialId? // e.g. iron, steel; used with "metal"
1622```
1623
1624Inventory icons and worn overlays may be different 16×16 files. Both are
1625world sprites and both go through the size check.
1626
1627### Recolourable equipment
1628
1629Some gear shares one overlay and is tinted per material. Metal armour is
1630the initial case: iron, steel and later metals are not separate full-size
1631art sets.
1632
1633```text
1634MaterialDefinition
1635- materialId // iron, steel, ...
1636- displayName
1637- channel // metal for armour; later channels may include cloth
1638- colour // destination RGB for that channel
1639```
1640
1641A recolourable overlay is authored as:
1642
1643- the 16×16 overlay sprite, with shading in the channel regions, and
1644- an optional 16×16 **channel mask** of the same dimensions, whose pixels
1645 name which recolour channel they belong to (for example a reserved mask
1646 colour meaning `metal`). Unmasked pixels are drawn unchanged.
1647
1648At draw time, masked pixels keep the overlay’s relative brightness
1649(highlights and shadows) and replace the hue/saturation with the
1650item’s `MaterialDefinition.colour`. The client must not invent a colour;
1651the server sends the material id (or the already-resolved colour) on the
1652appearance layer.
1653
1654Iron plate and steel plate therefore share `overlaySpriteId = platebody`
1655and differ only by `materialId`. Non-metal unique art omits
1656`recolourableChannels` and is blitted as authored.
1657
1658Recolour happens on the client as a presentation step. It does not change
1659item identity, combat stats or inventory. Nearby observers receive enough
1660appearance data to apply the same layers and tints.
1661
1662## 21.7 World time and night shading
1663
1664The client treats **world time** as server time minus 1200 years (section
166513.5). It uses that clock-of-day to shade the 3×3 view.
1666
1667At night, tiles that the baked light map says are unreachable from any
1668static light are drawn darker. Tiles a light can reach stay brighter.
1669Light does not bleed through walls: the mask was raycast through passable
1670tiles at editor save, including across chunk borders, so a torch on the
1671edge of one chunk can light tiles in the next.
1672
1673By day, ambient light is full and the baked mask does not darken the
1674ground. The day/night curve (how dark “night” is, dusk length) can stay a
1675world setting or a later tuning value; the invariant is that night uses
1676baked reachability, not a per-frame raycast.
1677
1678The world-editor night-to-day slider is the same shading function, driven
1679by the slider instead of the clock, so an admin can preview a chunk at
1680any light level without changing live world time.
1681
1682# 22. Items, inventory and ground drops
1683
1684## 22.1 Item definitions
1685
1686Every obtainable object is an `ItemDefinition`. Stacking, uniqueness and
1687later economy rules are data on that definition, not special cases in UI
1688code.
1689
1690```text
1691ItemDefinition
1692- itemId
1693- displayName
1694- description
1695- seedValue // base price before player-market adaptation
1696- stackable
1697- maxStackSize // default 99 for stackable items
1698- uniqueInstance // true for letters, filled cheques, and similar
1699- category: ingredient | intermediate | finished | document | other
1700- npcShopAllowed
1701- gatherSources
1702- craftingRecipe(s)
1703- dropTableSources
1704- attack?: AttackProfile // weapons; omitted for non-weapons
1705- equipment?: // worn/wielded visuals; see 21.6
1706 slot
1707 overlaySpriteId
1708 recolourableChannels?
1709 materialId?
1710```
1711
1712A stackable item with no instance data merges with an identical `itemId` in
1713the same container up to `maxStackSize`. Unique-instance items never merge;
1714each occupies its own slot at quantity 1.
1715
1716**Currency is not an inventory item.** Carried money is a numeric `Currency`
1717balance on the player. Banked money is a numeric balance on that player's
1718vault. Coins do not occupy inventory slots and cannot be dropped on the
1719ground in this model.
1720
1721How most items are obtained is specified later. Two source families already
1722fit this model without changing it:
1723
1724- Ground-item spawners in the world editor, analogous to mob spawners.
1725- Later harvesting from the environment by players.
1726
1727Paper, blank cheques and letters are specified now because communication,
1728banking and pigeons depend on them.
1729
1730## 22.2 Player inventory
1731
1732A player inventory has exactly **32 slots**.
1733
1734```text
1735Inventory
1736- slots[32]: empty | ItemStack
1737
1738ItemStack
1739- itemId
1740- quantity // 1 for unique-instance items
1741- instance?: ItemInstance // present only when uniqueInstance is true
1742- origin?: ItemOrigin // crafter or shop NPC; see 22.6
1743```
1744
1745Rules:
1746
1747- A stack occupies exactly one slot, regardless of quantity.
1748- Inserting a stackable item first tries to merge into an existing compatible
1749 stack whose combined quantity would not exceed `maxStackSize`. Stacks are
1750 compatible only when `itemId` matches and `origin` matches (including both
1751 being empty). Any remainder needs an empty slot, or the whole action fails.
1752- Moving, swapping and splitting stacks are ordinary server-validated
1753 commands. The client never asserts the resulting inventory.
1754- Inventory, wallet and vault contents are **player-private UI state**. They
1755 are not part of 3×3 chunk replication. Other clients see ground items and
1756 pigeon entities, not another player's bags or a pigeon's cargo.
1757- Logout and restart persist the full inventory and carried currency in
1758 `state.sqlite`.
1759
1760## 22.3 Paper and letters
1761
1762Blank paper is a stackable item.
1763
1764Writing consumes one paper and produces a **letter**: a unique-instance item
1765whose instance data is text written by a player. A letter is not a mail
1766record and has no inherent recipient. It is just paper with writing on it.
1767
1768```text
1769LetterInstance
1770- letterId
1771- authorPlayerId
1772- body
1773- writtenAt
1774```
1775
1776If the paper stack's quantity is 1, the slot may be converted in place into
1777the letter. If quantity is greater than 1, writing requires a free inventory
1778slot for the new letter and decrements the paper stack.
1779
1780Reading a letter inspects its instance data. Sending a letter is the same
1781pigeon-cargo action used for any other item stack.
1782
1783Maximum letter length is a defined game rule and can be chosen during
1784implementation.
1785
1786## 22.4 Dropping items
1787
1788A player may drop an item stack, or part of a stack, onto their current tile.
1789
1790```text
1791GroundItem
1792- groundItemId
1793- tileX / tileY
1794- ItemStack
1795- droppedAt
1796- expiresAt // droppedAt + WorldSettings.groundItemDespawnDuration
1797- source // player-drop | later: item-spawner
1798- droppedByPlayerId?
1799```
1800
1801Rules:
1802
1803- Player-dropped items remain for `WorldSettings.groundItemDespawnDuration`
1804 (default **10 minutes**), then vanish forever.
1805- Anyone may pick up a ground item. There is no owner lock and no loot-rights
1806 delay.
1807- Ground items **do not block movement** and do not prevent a player from
1808 standing on that tile.
1809- Pickup requires the player to **stand on that tile**. The command names the
1810 `groundItemId` when several stacks share the tile.
1811- Pickup fails if the player's inventory cannot accept the stack (no legal
1812 merge and no empty slot). The ground item is unchanged.
1813- Several distinct stacks may occupy one tile at once.
1814- Later naturally spawned ground items use the same non-blocking
1815 representation, but their lifetime and respawn belong to the item spawner
1816 rather than this 10-minute player-drop timer.
1817
1818Dropped items are not `ChunkLoader`s and do not keep a chunk simulated.
1819
1820They **do** survive chunk unload until `expiresAt`, using timestamp expiry
1821rather than a per-tick countdown. On unload, unexpired ground items are
1822written to `state.sqlite`. On load or wake, items whose `expiresAt` is in
1823the past are discarded and never replicated. Simulating chunks also remove
1824them when the timestamp elapses.
1825
1826If a unique-instance item that encodes a bank reservation (a filled cheque)
1827expires on the ground or is otherwise destroyed without being redeemed, that
1828reservation is released and the reserved goods become available in the
1829issuer's vault again.
1830
1831## 22.5 Pickup and drop commands
1832
1833```text
1834DROP_ITEM(slotIndex, quantity?)
1835PICKUP_ITEM(groundItemId)
1836```
1837
1838Both are intentions. The owning worker validates the actor's tile, inventory
1839space and stack rules, then applies the result. Standing on a tile that has
1840ground items does not pick them up automatically.
1841
1842## 22.6 Item inspection, origin and displayed value
1843
1844Hovering an item — in inventory, a shop stock list, or on the ground — shows
1845at least:
1846
1847```text
1848ItemTooltip
1849- displayName
1850- description
1851- originLabel // who crafted it, or the shop NPC if bought there
1852- currentValue // undiscounted adapted value; see section 27
1853```
1854
1855Origin is stored on the stack:
1856
1857```text
1858ItemOrigin
1859- kind: crafted | shop | unknown
1860- playerId? // when crafted by a player
1861- npcId? // when bought from a shop NPC
1862```
1863
1864The origin label is the crafting player's name, or the shop NPC's name when
1865the stack was bought from that NPC. Harvested, looted or otherwise unstamped
1866stacks use `unknown` and omit the origin line until later content says
1867otherwise. Buying from a shop stamps that NPC as origin. Crafting stamps the
1868crafter. Shop-bought goods are not treated as crafted by the NPC; the NPC
1869name simply occupies that inspection field.
1870
1871`currentValue` uses the same last-sale lerp as shopkeepers (section 27.6) but
1872**without** the per-shop discount. It is informational. The client must not
1873recompute it every simulation tick. The player UI may refresh displayed
1874values at most once per minute, from the last-sale record plus `seedValue`.
1875The actual shop purchase price is always computed server-side at the moment
1876of purchase.
1877
1878# 23. Player communication and carrier pigeons
1879
1880## 23.1 Proximity chat is the default
1881
1882Ordinary chat is spatial. A player speaks from a world position and only nearby
1883players receive a useful version of the message. Legibility decreases as the
1884recipient gets farther from the speaker.
1885
1886For example:
1887
1888```text
1889Near: I'm really far away
1890Farther: I'm re...y far aw.y
1891Very far: I'...re..ly..ar.aw.y
1892Beyond range: no message
1893```
1894
1895The exact distance bands/function are configurable game rules.
1896
1897Crucially, degradation is performed **server-side**. The server must not send the
1898full plaintext to a distant client and merely ask that client to obscure it,
1899because a modified client could then recover speech it was not supposed to
1900understand.
1901
1902A chat message therefore conceptually contains:
1903
1904```text
1905ChatSpeech
1906- messageId
1907- speakerEntityId
1908- originX / originY
1909- createdAt
1910- text
1911```
1912
1913The communication service performs a spatial recipient query and derives the
1914recipient-specific legible representation before routing it through the gateway.
1915Chat routing is separate from normal 3×3 chunk replication, so the eventual
1916hearing/text range does not have to equal the visual chunk-subscription radius.
1917
1918## 23.2 Persistent player groups
1919
1920Players can create permanent groups and invite other players into them. Groups
1921are durable social entities stored in `state.sqlite`, with membership surviving
1922logout and server restart.
1923
1924A minimal model contains:
1925
1926```text
1927PlayerGroup
1928- groupId
1929- name
1930- owner / roles
1931- createdAt
1932
1933PlayerGroupMember
1934- groupId
1935- playerId
1936- role
1937- joinedAt
1938```
1939
1940Invite, accept, leave, kick and role-management operations are authoritative
1941server actions.
1942
1943Group membership does **not** create magical long-distance communication. If
1944members are close enough, they can communicate through the normal proximity
1945rules. Communication to distant group members means sending items — including
1946letters — by carrier pigeon, the same mechanism available to any player.
1947
1948If group-wide letter sending is later supported, it is an addressing
1949convenience that still consumes one paper/letter item and one pigeon dispatch
1950per recipient. The group is not a global instant chat channel.
1951
1952## 23.3 Pigeons carry cargo, not messages
1953
1954A carrier pigeon is a free physical courier. It does not send a chat packet.
1955It carries **either**:
1956
1957- an amount of the sender's carried currency, or
1958- exactly one item stack (a letter, a filled cheque, blank paper, or any
1959 other stack)
1960
1961One pigeon cannot carry both money and an item, and cannot carry two item
1962stacks. Dispatching a pigeon is **free**, so a player who wants to move
1963several stacks sends several pigeons one after another.
1964
1965Cargo is removed from the sender immediately and placed into durable transit.
1966A crash or restart cannot duplicate that cargo or silently erase it.
1967
1968Pigeons are not inventory items. Any player may dispatch one from anywhere,
1969provided they have valid cargo.
1970
1971```text
1972SendPigeon
1973- destination: Player(playerId) | Bank
1974- cargo: Money(amount) | Item(slotIndex, quantity?)
1975```
1976
1977## 23.4 Destinations
1978
1979**Player destination.** The pigeon flies toward the named player. On arrival:
1980
1981- Money is added to the recipient's carried `Currency` if they are online;
1982 otherwise it is deposited into the recipient's bank.
1983- An item stack is placed in the recipient's inventory if they are online and
1984 have space (a legal merge or an empty slot). If they are offline or cannot
1985 accept the stack, the pigeon continues to the **nearest bank** and deposits
1986 the stack into the recipient's vault.
1987
1988This keeps offline and full-inventory delivery durable without a separate
1989mailbox object.
1990
1991**Bank destination.** The pigeon flies to the **nearest bank** to the dispatch
1992tile. Travel time is that aerial journey, even though every bank shares the
1993same vault. On arrival the cargo is deposited into the **sender's** vault,
1994except for the filled-cheque special case in section 24.7.
1995
1996"Nearest bank" is computed from authored Bank block positions in the pinned
1997world revision. If additional banks are added later, a pigeon sent to `Bank`
1998still lands at whichever bank is closest to where it was dispatched; the
1999goods then appear in the shared vault.
2000
2001## 23.5 Carrier pigeon transit
2002
2003A carrier pigeon must take time to cross the world; long-distance item and
2004currency delivery is intentionally not instantaneous.
2005
2006At MMO scale, however, every delivery should not keep an entire trail of regions
2007fully stimulated merely so a pigeon can advance. The recommended model is a
2008persistent courier transit record with world position/route/progress that can
2009advance through dormant space using coarse path segments and timestamps.
2010
2011```text
2012CourierTransit
2013- courierId
2014- cargo // Money(amount) | ItemStack
2015- senderPlayerId
2016- destination // Player(playerId) | Bank
2017- currentPosition
2018- route
2019- speed / timing state
2020- status
2021```
2022
2023A carrier pigeon is part of the shared physical world, not a private visual
2024belonging only to its sender or recipient. Whenever its calculated route passes
2025through a **simulating chunk**, the courier should materialise there as a normal
2026ECS `Mob` entity, regardless of whether the sender or recipient is nearby. Any
2027client whose normal 3x3 chunk subscription includes that pigeon receives it like
2028any other visible mobile entity and can therefore see unrelated pigeons flying
2029past in the distance.
2030
2031The visible pigeon does **not** receive `ChunkLoader`. It exists because the chunk
2032is already simulating for some other reason. If it leaves the last relevant
2033simulating chunk, its exact position/progress is folded back into the durable
2034`CourierTransit` record and the ECS instance can disappear while the journey
2035continues abstractly. If a dormant/unloaded part of its route later becomes
2036simulated while the pigeon should currently be inside it, the owning worker
2037materialises the pigeon at the position implied by the transit clock and route.
2038
2039```text
2040Dormant route Simulating chunk Dormant route
2041
2042abstract transit --------> ECS pigeon visible to clients --------> abstract transit
2043 | | |
2044 Player A Player B unrelated observer
2045```
2046
2047This means a player standing halfway between sender and recipient can see the
2048pigeon fly through their area even though the cargo has nothing to do with
2049them. Unrelated clients receive the pigeon entity, not the cargo contents. It
2050preserves the sense that deliveries physically cross the world without
2051requiring thousands of deliveries to become thousands of permanent
2052`ChunkLoader`s.
2053
2054Because pigeons fly rather than use the ground navigation grid, their coarse
2055route can initially be represented by direct or waypoint-based aerial segments.
2056This makes deterministic materialisation from route + elapsed time considerably
2057simpler than it would be for a ground-based courier.
2058
2059If future gameplay allows pigeons to be intercepted, killed or rerouted anywhere
2060along their journey, the transit model can be made progressively more detailed;
2061that interaction is not required by the initial courier design.
2062
2063## 23.6 Courier service
2064
2065A dedicated `CourierService` should own durable cargo and delivery state.
2066Simulation workers may own visible pigeon entities while the service owns the
2067durable fact that a delivery exists.
2068
2069```text
2070Player action -> CourierService -> durable cargo/transit
2071 |
2072 +-> visible pigeon when needed
2073 |
2074 +-> inventory, wallet or BankService deposit
2075```
2076
2077This separation is also useful for marketplace settlement, which uses the same
2078carrier-pigeon delivery infrastructure for remote counterparties.
2079
2080# 24. Bank, cheques and shared vaults
2081
2082## 24.1 Bank location and access
2083
2084A bank exists at or near the central marketplace as an authored Bank block.
2085Deposit, withdraw, cheque issue and in-person cheque redemption require
2086server-validated access to a bank interaction; the bank is not a global menu
2087usable from anywhere.
2088
2089Pigeon dispatch to `Bank` is the exception: that command may be issued from
2090anywhere, and the goods become available only after the pigeon arrives.
2091
2092## 24.2 One shared vault
2093
2094Each **character** has a single vault in `state.sqlite`:
2095
2096```text
2097CharacterVault
2098- characterId
2099- bankedCurrency
2100- stacks[]
2101- reservations[]
2102```
2103
2104Capacity is unlimited: there is no slot cap. Per-stack stacking rules still
2105apply (`maxStackSize`; unique instances never merge), so 200 blank paper is
2106stored as 99 + 99 + 2 rather than one unbounded pile.
2107
2108If more banks are authored later, **all banks are linked**. Withdrawing at
2109bank B can retrieve goods deposited at bank A. The vault is not per-branch.
2110
2111Pigeon deposits affect *when* goods become available, not *which* vault they
2112enter. After the pigeon arrives at the nearest bank, the goods appear in the
2113same shared vault accessible from every bank.
2114
2115## 24.3 Deposit and withdraw
2116
2117While interacting with a bank, a player may:
2118
2119- Deposit any carried currency and any inventory stacks, in whole or in part.
2120- Withdraw currency into the carried wallet.
2121- Withdraw an item stack, or part of a stack, into inventory, subject to the
2122 32-slot and merge rules.
2123- Claim items or currency from the account **inheritance tab** into this
2124 character's vault (section 24.9).
2125
2126Goods reserved by an outstanding filled cheque cannot be withdrawn by the
2127issuer until that cheque is redeemed or voided.
2128
2129## 24.4 Blank cheques
2130
2131A player at a bank may request blank cheques.
2132
2133- Blank cheques are a stackable item with `maxStackSize` 99.
2134- The bank counts blank cheques already in the player's **inventory** (not
2135 the vault) and issues only enough to bring that total to 99.
2136- If the player already holds 99, the bank issues none.
2137- Issued cheques go into inventory, merging into an existing blank-cheque
2138 stack when possible. If the player holds none and has no empty slot, the
2139 request fails.
2140
2141The bank will not issue more than 99 blank cheques into inventory, even on
2142repeated requests.
2143
2144## 24.5 Filling a cheque
2145
2146Using a blank cheque at a bank lets the issuer pick vault goods and a
2147**quantity**. For stackable items they choose an `itemId` and quantity; the
2148quantity may be larger than one `maxStackSize`, and the reservation covers
2149that many available (unreserved) items of that type in the vault. For
2150unique-instance items they choose that exact instance and the quantity is 1.
2151
2152```text
2153FilledChequeInstance
2154- chequeId
2155- issuerPlayerId
2156- itemId
2157- quantity
2158- instance?: ItemInstance // set when the reserved goods are unique
2159- createdAt
2160```
2161
2162Filling:
2163
21641. Validates that the vault has at least `quantity` of that item available
2165 (not already reserved). Unique instances must still be present and unreserved.
21662. Reserves those goods in the issuer's vault. Reserved goods cannot be
2167 withdrawn, sold or reserved again.
21683. Consumes one blank cheque. If that was the last cheque in the slot, the
2169 slot becomes the filled cheque in place; otherwise a free slot is required
2170 for the filled cheque.
2171
2172A filled cheque is a unique-instance **bearer** item. It does not stack.
2173Whoever holds it may redeem it. Cheques specify vault items and a quantity,
2174not carried currency. Money is moved with a pigeon, or by depositing and
2175withdrawing at a bank.
2176
2177## 24.6 Redeeming a cheque in person
2178
2179The bearer interacts with any bank and redeems the filled cheque.
2180
2181- The server moves the reserved goods from the **issuer's** vault into the
2182 **bearer's inventory**, subject to inventory space. A quantity larger than
2183 `maxStackSize` becomes as many stacks as needed.
2184- The cheque item is consumed.
2185- If inventory cannot accept the resulting stacks, redemption fails and both
2186 cheque and reservation remain unchanged.
2187
2188The bearer may then deposit those goods into their own vault if they wish.
2189
2190## 24.7 Redeeming a cheque by pigeon
2191
2192If the bearer dispatches a pigeon whose cargo is a filled cheque and whose
2193destination is `Bank`:
2194
2195- The pigeon flies to the nearest bank from the dispatch tile.
2196- On arrival, `BankService` transfers the reserved goods from the **issuer's**
2197 vault into the **pigeon's sender's** vault.
2198- The cheque is consumed in transit; it is not deposited as an item.
2199
2200The receiver of the transfer is whoever sent that pigeon, not the original
2201cheque issuer. This is how a cheque moves goods from one vault to another
2202without the receiver standing at a bank.
2203
2204Sending a filled cheque to a **player** delivers the cheque item itself (or
2205into that player's bank if they cannot hold it). It does not redeem it.
2206
2207## 24.8 Bank service
2208
2209Vault mutation, cheque issue, reservation, in-person redemption and
2210pigeon-arrival deposits are owned by a single authoritative `BankService`
2211(or an equivalently serialised service) so two concurrent withdrawals,
2212cheque fills or pigeon arrivals cannot double-spend the same goods.
2213
2214```text
2215Bank interaction or pigeon arrival
2216 |
2217 v
2218BankService
2219 - shared vault
2220 - reservations
2221 - cheque issue / redeem
2222 |
2223 +-> inventory / currency on the acting player when in person
2224 |
2225 +-> vault credit on pigeon arrival
2226```
2227
2228Cheque identifiers are server-issued. A client cannot forge a claim against
2229another player's vault.
2230
2231## 24.9 Inheritance bank tab
2232
2233Each **account** has one inheritance tab, separate from every character
2234vault:
2235
2236```text
2237AccountInheritance
2238- accountId
2239- currency
2240- stacks[]
2241```
2242
2243It is written only when a character of that account is permanently deleted
2244(section 14.6). Any of that player's living characters can move stacks and
2245currency from this tab into their own vault at a bank. They cannot deposit
2246into inheritance except through character deletion.
2247
2248# 25. Central marketplace and order matching
2249
2250## 25.1 Marketplace location
2251
2252A central marketplace exists at or near the centre of the game world. Creating,
2253modifying or cancelling market orders requires server-validated access to the
2254marketplace interaction; the marketplace is not intended to be a global menu
2255that can be used from anywhere.
2256
2257Orders themselves remain durable after the player leaves the marketplace or
2258logs out.
2259
2260## 25.2 No public list of sell orders
2261
2262The market is an order book, but players do not browse a list of individual
2263items currently offered for sale.
2264
2265A seller submits:
2266
2267```text
2268SellOrder
2269- item / item definition
2270- quantity
2271- minimum unit/total price
2272```
2273
2274A buyer submits:
2275
2276```text
2277BuyOrder
2278- requested item / matching criteria
2279- quantity
2280- maximum unit/total price
2281```
2282
2283The UI may know which item types exist and may eventually show historical data,
2284but it does not expose the live asks in a way that lets a buyer simply pick a
2285listed seller.
2286
2287## 25.3 Escrow
2288
2289Market orders escrow the asset required to honour them. Escrow is taken from
2290carried inventory and carried currency. The marketplace sits next to the bank,
2291so a player can withdraw from the vault immediately before placing an order.
2292
2293- Creating a sell order removes/reserves the offered item stack from the
2294 seller's inventory.
2295- Creating a buy order removes/reserves the buyer's maximum offered currency.
2296- Cancelling an unmatched order returns the escrowed asset through the defined
2297 settlement/delivery rules.
2298
2299This prevents double spending, selling the same item twice, or a buyer spending
2300currency after placing a bid.
2301
2302## 25.4 Matching rules
2303
2304A buy and sell order match when:
2305
2306```text
2307buyerMaximum >= sellerMinimum
2308```
2309
2310Sell orders are considered cheapest first. Within the same minimum price, a
2311stable creation sequence/FIFO rule should be used unless later game rules choose
2312otherwise.
2313
2314For a symmetric order book, buy orders are naturally prioritised by highest
2315maximum bid and then oldest sequence. This means a newly submitted sell order
2316matches the best compatible existing bid, while a newly submitted buy order
2317matches the cheapest compatible existing ask.
2318
2319The trade price is exactly the midpoint between the two limits:
2320
2321```text
2322tradePrice = midpoint(buyerMaximum, sellerMinimum)
2323```
2324
2325Example:
2326
2327```text
2328Seller minimum: 80
2329Buyer maximum: 100
2330Trade price: 90
2331```
2332
2333The exact rounding rule when integer currency produces a half-unit midpoint is a
2334defined-but-still-open game rule and must be deterministic.
2335
2336## 25.5 Immediate side versus pigeon side
2337
2338The order that is submitted last is the order that triggers the match.
2339
2340The player who submitted that matching order receives the acquired asset
2341immediately because they are currently present at the marketplace interaction
2342(item stack into inventory, or currency into the carried wallet). The
2343pre-existing counterparty receives their acquired item or currency through a
2344carrier pigeon whose destination is `Bank`, landing at the nearest bank to the
2345marketplace. On arrival the settlement is deposited into that counterparty's
2346shared vault. This remains valid if they are offline.
2347
2348```text
2349Existing sell + new matching buy
2350-> new buyer receives item immediately
2351-> existing seller receives payment by pigeon to bank
2352
2353Existing buy + new matching sell
2354-> new seller receives payment immediately
2355-> existing buyer receives item by pigeon to bank
2356```
2357
2358If a trade requires more than one item stack (for example a quantity that does
2359not fit in a single `maxStackSize`), the older counterparty receives as many
2360free sequential pigeons as needed. Each pigeon still carries only one stack or
2361only currency.
2362
2363Any unused part of buy-order currency escrow caused by the midpoint price is
2364returned immediately to the triggering player when they are the buyer, and
2365returned by the settlement pigeon into the older counterparty's vault when
2366they were the buyer.
2367
2368## 25.6 Market service and atomicity
2369
2370Marketplace matching should not live inside an arbitrary region worker. Use a
2371single authoritative `MarketService` (or an equivalently serialised partitioned
2372service later) so two simultaneous orders cannot both consume the same escrow.
2373
2374Order insertion, matching, escrow movement and creation of the resulting
2375settlement deliveries are committed atomically in `state.sqlite`.
2376
2377Conceptually:
2378
2379```text
2380Marketplace interaction
2381 |
2382 v
2383MarketService
2384 - durable order book
2385 - escrow
2386 - deterministic matching
2387 - trade record
2388 |
2389 +-> immediate settlement to triggering player's inventory or wallet
2390 |
2391 +-> CourierService pigeon to Bank for the older counterparty
2392 |
2393 +-> last-sale index update for that itemId
2394```
2395
2396The system should also retain an immutable trade record for auditing and recovery.
2397
2398## 25.7 Last player-market sale per item
2399
2400Each successful player-market match updates a single durable record for that
2401`itemId`. There is no price history series — only the latest sale:
2402
2403```text
2404ItemLastMarketSale
2405- itemId
2406- lastTradePrice // unit price of that match (the midpoint)
2407- lastTradeAt
2408- priceFrom // evaluated undiscounted value at lastTradeAt
2409```
2410
2411`priceFrom` is not a history log. It is the lerp origin captured at the
2412moment of this sale so the displayed price does not jump back to seed when
2413a new trade occurs:
2414
24151. Evaluate the current undiscounted value at `now` using the previous
2416 last-sale record (or `seedValue` if none exists).
24172. Store that value as `priceFrom`, store the new trade's unit price as
2418 `lastTradePrice`, and store `now` as `lastTradeAt`.
2419
2420Shopkeepers and item tooltips both read this record. They do not tick it;
2421they evaluate it from timestamps when a shop is opened, a purchase is
2422attempted, or a tooltip refresh is requested.
2423
2424# 26. Combat
2425
2426## 26.1 Every combatant can attack
2427
2428Players, enemies, animals and any other mobile with a `Combat` component can
2429attack. Shopkeepers and other non-fighting NPCs simply omit `Combat`, or
2430never issue attack commands.
2431
2432Attacking is an intention. The client (or AI, or a future script) sends
2433`ATTACK(targetEntityId)`. The owning worker validates range, line-of-use,
2434the current attack profile and cooldown, then resolves hit and damage
2435authoritatively. The client never supplies a hit result or a damage number.
2436
2437Cross-worker attacks already use `REMOTE_ACTION(attack intent)`: the worker
2438that owns the target applies the authoritative result.
2439
2440## 26.2 Attack profiles
2441
2442The current attack comes from the wielder's selected profile: a wielded
2443weapon's `AttackProfile`, a selected spell, or a default unarmed melee
2444profile when nothing is wielded.
2445
2446```text
2447AttackProfile
2448- attackId
2449- mode: melee | ranged | magic
2450- rangeTiles // melee is always 1; ranged/magic from the item or spell
2451- hitSkillId
2452- damageSkillId
2453```
2454
2455```text
2456SpellDefinition
2457- spellId
2458- displayName
2459- AttackProfile // mode = magic, hitSkillId = Magic, damageSkillId = Mind
2460- other costs/effects // later content
2461```
2462
2463Typical weapon mappings:
2464
2465```text
2466Sword -> melee, range 1, hit Swordfighting, damage Strength
2467Axe -> melee, range 1, hit Axefighting, damage Strength
2468Bow -> ranged, range from item, hit Archery, damage Dexterity
2469Spell -> magic, range from spell, hit Magic, damage Mind
2470Unarmed -> melee, range 1, hit Unarmed, damage Strength
2471```
2472
2473The exact weapon and spell catalogue is content. The pairing rule is not:
2474melee weapons use a weapon skill plus **Strength**, ranged weapons use a
2475weapon skill plus **Dexterity**, and spells use **Magic** plus **Mind**.
2476
2477`EquipItem(slotIndex)` moves a legal item from inventory into the matching
2478equipment slot (section 21.6). The **weapon** slot supplies the current
2479`AttackProfile`. `SelectSpell(spellId)` selects a spell the actor is
2480allowed to use. The selected profile determines range and both skills.
2481
2482## 26.3 Melee range
2483
2484A melee attack is legal only when the attacker stands on **one of the eight
2485tiles surrounding** the target's tile: orthogonal or diagonal, Chebyshev
2486distance exactly 1. The attacker cannot melee from the target's own tile.
2487
2488```text
2489. . .
2490. T . attacker must occupy one of the eight `.` tiles
2491. . .
2492```
2493
2494This adjacency rule is independent of whether ordinary walking is four- or
2495eight-directional.
2496
2497## 26.4 Ranged attacks and spells
2498
2499Ranged weapons and spells may fire from further away. Maximum Chebyshev
2500distance is `rangeTiles` on that item or spell. Distance 0 (same tile) is
2501not a legal ranged/spell attack unless a later exception is defined.
2502
2503The attacker must still occupy a simulating chunk and satisfy any later
2504line-of-sight rule. Exact obstruction rules are an open content decision;
2505range itself is not.
2506
2507## 26.5 Hit roll
2508
2509Whether the attack lands is a server-side roll driven by the **hit skill**
2510of the current profile (Swordfighting, Axefighting, Archery, Magic, Unarmed,
2511and so on). The client does not roll.
2512
2513The exact hit curve, any defender contribution from Defence, and the RNG
2514are later tuning. The invariant is that the hit chance is a function of the
2515attacker's hit-skill level, not of Strength, Dexterity or Mind.
2516
2517A miss deals no damage.
2518
2519## 26.6 Damage
2520
2521On a hit, damage is determined by the **damage skill**:
2522
2523- Melee → Strength
2524- Ranged → Dexterity
2525- Magic → Mind
2526
2527Weapon or spell base damage and the defender's mitigation (including whether
2528Defence reduces damage) are later tuning. The governing damage skill is not.
2529
2530## 26.7 Experience split
2531
2532When a **player** successfully hits, the attack's XP award is split equally
2533between the hit skill and the damage skill:
2534
2535```text
2536totalXp = attack xp formula for this successful hit
2537hitSkill += totalXp / 2
2538damageSkill += totalXp / 2
2539```
2540
2541Example: a sword hit awards half its XP to Swordfighting and half to
2542Strength. A bow hit splits Archery and Dexterity. A spell hit splits Magic
2543and Mind.
2544
2545If an unusual profile ever named the same skill twice, XP is awarded once,
2546not doubled. Misses award no combat XP. Ordinary mobs do not earn XP; their
2547`Skills` component is filled from the mob archetype and stays at those
2548levels.
2549
2550Non-combat actions remain single-skill as in section 27.4.
2551
2552## 26.8 Mob combat stats
2553
2554```text
2555MobDefinition
2556- ...
2557- skillLevels: { skillId → level }
2558- defaultAttack: attackId | unarmed
2559```
2560
2561A wolf might have Unarmed and Strength. An archer guard might have Archery
2562and Dexterity. Those levels feed the same hit and damage resolution as
2563players.
2564
2565# 27. Player-driven economy and skill progression
2566
2567## 27.1 Item-source philosophy
2568
2569The economy is intentionally player-driven.
2570
2571Normal NPC shops should sell only basic ingredients. The vast majority of
2572materials are gathered directly from the world by players. Finished goods are
2573normally produced by player crafting/professions.
2574
2575The only normal non-player source of finished items is enemy or boss loot.
2576
2577This gives four broad source paths, with ground-item spawners as an additional
2578early world source once content defines them:
2579
2580```text
2581World gathering / harvesting -> ingredients
2582Ground-item spawners --------> some world items, later specified
2583Basic NPC shops -------------> limited basic ingredients
2584Player production -----------> intermediate/final products
2585Enemies and bosses ----------> loot, including possible finished items
2586```
2587
2588Stacking, unique instances, letters and cheques are defined in section 22.
2589Economy-facing fields remain on the same `ItemDefinition`:
2590
2591```text
2592ItemDefinition
2593- itemId
2594- displayName / description / seedValue
2595- stackable / maxStackSize / uniqueInstance
2596- category: ingredient | intermediate | finished | document | other
2597- npcShopAllowed
2598- gatherSources
2599- craftingRecipe(s)
2600- dropTableSources
2601- attack?: AttackProfile
2602- equipment?: slot / overlaySpriteId / recolourableChannels / materialId
2603```
2604
2605Content validation can then reject an ordinary shop inventory that accidentally
2606contains a finished product unless explicitly permitted by a future exception.
2607
2608## 27.2 No player classes
2609
2610Players do not choose a class. Capabilities and progression come from independent
2611skills.
2612
2613Examples include:
2614
2615- Swordfighting, Axefighting, Archery, Magic, Unarmed
2616- Strength, Dexterity, Mind
2617- Defence
2618- Lumbering
2619- Fishing
2620- Smithing
2621
2622The final skill list is game content and is not limited to skills found in any
2623particular inspiration game.
2624
2625## 27.3 Skill state
2626
2627Skill progression is persistent player state.
2628
2629```text
2630SkillProgress
2631- skillId
2632- xp
2633```
2634
2635Level should preferably be derived from XP and the skill's level curve rather
2636than stored as an independent source of truth, although it may be cached.
2637
2638```text
2639SkillDefinition
2640- skillId
2641- displayName
2642- levelCurve
2643- maxLevel (if any)
2644```
2645
2646## 27.4 Actions are governed by skills
2647
2648Every gameplay action that participates in progression is associated with a
2649governing skill. Combat attacks are the explicit exception: they have a hit
2650skill and a damage skill, and split XP equally between them (section 26.7).
2651
2652```text
2653ActionDefinition
2654- actionId
2655- governingSkillId
2656- requiredLevel
2657- xpAward / xpFormula
2658- other requirements
2659```
2660
2661Examples:
2662
2663```text
2664Cut tree -> Lumbering
2665Catch fish -> Fishing
2666Forge sword -> Smithing
2667Sword hit -> Swordfighting + Strength (equal split)
2668Bow hit -> Archery + Dexterity (equal split)
2669Spell hit -> Magic + Mind (equal split)
2670Defensive act -> Defence
2671```
2672
2673The server validates the action, performs the authoritative outcome, and then
2674awards XP according to the action result. A client cannot claim XP independently.
2675
2676## 27.5 Skills replace class restrictions
2677
2678Equipment, recipes, actions, gathering nodes and other content may require skill
2679levels, but there is no permanent class gate. A player can train any combination
2680of skills over time.
2681
2682This also fits the future scripting model: scripts issue normal actions, and
2683successful scripted actions use exactly the same skill checks and XP rules as
2684manual player actions.
2685
2686## 27.6 NPC shops and market-adapted prices
2687
2688Named shop NPCs can sell items to players. They are not the player marketplace
2689and they do not expose live sell orders. A shop interaction requires being at
2690that NPC.
2691
2692Stock remains constrained by `npcShopAllowed` and the ingredient-only rule in
269327.1. Each shop NPC has a hidden discount that players never see:
2694
2695```text
2696ShopNpc
2697- npcId
2698- hiddenDiscount // multiplier, e.g. 0.9; not shown to clients
2699- stock[] // itemIds this NPC sells
2700```
2701
2702Until an `itemId` has a player-market last-sale record, the undiscounted
2703value is `seedValue` from the item definition.
2704
2705When a last-sale record exists, both tooltips and shops evaluate a timestamp
2706lerp that does not require a per-tick update:
2707
2708```text
2709t = min(1, (now - lastTradeAt) / WorldSettings.shopPriceLerpDuration)
2710undiscounted = lerp(priceFrom, lastTradePrice, t)
2711shopPrice = undiscounted * thatNpc.hiddenDiscount
2712```
2713
2714`lerp(a, b, t) = a + (b - a) * t`. After the configured lerp duration
2715(default one hour), `t` is capped at 100% and the value rests on the last
2716player-market unit price (times discount, for shops) until another
2717player-market sale occurs.
2718
2719A new player-market sale captures the then-current `undiscounted` value as
2720`priceFrom` (section 25.7), so the lerp restarts toward the new last price
2721without jumping back to seed.
2722
2723Integer currency must be rounded deterministically at evaluation time. Shop
2724purchase price is computed on the server at the instant of `BuyFromShop`.
2725Displayed tooltip value is the undiscounted figure and may be refreshed at
2726most once per minute (section 22.6).
2727
2728Buying from a shop removes the listed price from the player's carried
2729currency, puts the stack in inventory subject to the 32-slot rules, and
2730stamps `ItemOrigin.kind = shop` with that NPC. Shops in this model sell to
2731players; they do not buy player goods unless a later iteration adds that.
2732
2733# 28. Suggested implementation phases
2734
2735## Phase 1 — Single-worker playable core
2736
2737- World coordinate helpers, 16×16 chunks and 4×4-chunk regions.
2738
2739- Ground/block tile model and chunk spatial occupancy.
2740
2741- Basic ECS and fixed simulation tick.
2742
2743- ChunkLoader reference counting and sleeping/unloading.
2744
2745- Single simulation worker behind the same worker interface planned for
2746 later scaling.
2747
2748- world.sqlite read path and state.sqlite persistence service.
2749
2750- Admin world editor: chunk navigation, open/closed flag, default grass for
2751 unsaved chunks, ground/block paint, light-emitting blocks, baked
2752 cross-chunk light maps, night-to-day preview slider, world settings modal,
2753 per-chunk changelog, save to pending revision.
2754
2755- SpawnerSystem for at least one non-persistent mob archetype.
2756
2757- WebSocket gateway, stub `admin-<n>` auth until auth.timfalken.com,
2758 character create/select/delete, authoritative command queue and 3×3 chunk
2759 replication.
2760
2761- Click-to-move with server-side A\*, global walk/run cadence (default 2
2762 tiles/s walk, run every movement tick, walk every other), and `SetGait`.
2763
2764- FrameworkV3 git submodule at `client/frameworkv3`, built first, then a
2765 game-specific client on top of it with 16×16 sprites, load-time and CI
2766 rejection of wrong-sized art (including equipment overlays and recolour
2767 masks), layered worn equipment with material recolouring, a
2768 player-centered viewport with bounded zoom, client-only lerp of
2769 tile-to-tile movement, and night shading from baked light maps.
2770
2771- 32-slot player inventory, stack merging, drop/pickup, and 10-minute
2772 non-blocking ground items.
2773
2774- Paper items that can be written into unique letter items.
2775
2776- Basic proximity chat with server-side distance degradation.
2777
2778- Persistent player skill state, including Strength, Dexterity and Mind, and
2779 at least a small initial set of skill-governed actions.
2780
2781- Melee and ranged/spell attack validation (8-tile melee adjacency, item/spell
2782 range), server-side hit rolls, damage from the matching damage skill, and
2783 equal XP split on a successful player hit.
2784
2785- Graceful forced-unload shutdown.
2786
2787## Phase 2 — Operations and live deployment
2788
2789- RestartScheduler and player-visible scheduled restart state.
2790
2791- origin/master change detection.
2792
2793- `systemd` service supervision and conditional deployment hook.
2794
2795- World-revision activation on restart.
2796
2797- Admin immediate restart.
2798
2799- Migration, backup and startup readiness checks.
2800
2801## Phase 3 — Multi-worker world
2802
2803- Multiple worker_threads simulation workers.
2804
2805- Region coordinator and dynamic region ownership.
2806
2807- Cross-worker entity transfers.
2808
2809- Border ghosts and remote actions.
2810
2811- Gateway subscriptions spanning multiple workers.
2812
2813- Load metrics and neighbour-aware region balancing.
2814
2815## Phase 4 — World depth, social systems and economy
2816
2817- Persistent named NPCs and other persistent mob archetypes.
2818
2819- Spawner persistent-instance index and duplicate prevention.
2820
2821- Optional durable gameplay chunk overrides, written only on unload.
2822
2823- Hierarchical pathfinding if long-distance autonomous travel needs it.
2824
2825- Persistent player groups and invitations.
2826
2827- Carrier-pigeon cargo transit: free dispatch, money or one item stack,
2828 player or nearest-bank destinations, including offline/full-inventory
2829 fallback to the recipient vault.
2830
2831- Shared unlimited **character** bank near the marketplace, account
2832 inheritance tab on character delete, blank cheques filled to 99, reserved
2833 filled cheques, in-person redemption and pigeon-to-bank cheque transfers.
2834
2835- Central marketplace, escrow, deterministic order matching, pigeon-to-bank
2836 settlement for the older counterparty, and a per-item last-sale record for
2837 shop/tooltip adaptation.
2838
2839- NPC shops that sell `npcShopAllowed` stock at seed value lerped toward the
2840 last player-market price over `shopPriceLerpDuration`, with a hidden per-shop discount.
2841
2842- Item inspection: name, description, origin (crafter or shop NPC) and
2843 undiscounted current value, refreshed at most once per minute.
2844
2845- Player crafting/gathering economy rules and shop-content validation.
2846
2847- Broader skill catalogue, progression curves and skill-gated content.
2848
2849## Phase 5 — Player scripting
2850
2851- Custom language grammar/compiler/interpreter.
2852
2853- ScriptController and event API.
2854
2855- CPU/memory/query quotas and sandboxing.
2856
2857- Online scripted control mode.
2858
2859- Offline retained player entities with expiry and ChunkLoader
2860 behaviour.
2861
2862- Persisted/restart-safe script state.
2863
2864# 29. Core invariants
2865
2866| **Invariant** | **Rule** |
2867|------------------------|--------------------------------------------------------------------------------------------------------|
2868| Server authority | Clients send intent; the server computes and owns outcomes. |
2869| Region ownership | Exactly one simulation worker authoritatively owns a region. |
2870| Entity ownership | Exactly one worker authoritatively owns an entity. |
2871| Remote mutation | Workers never directly mutate remote authoritative state. |
2872| Spatial separation | Region residency, chunk simulation and client visibility remain distinct. |
2873| Persistence separation | Persistent and ChunkLoader are independent entity traits. |
2874| Chunk persistence | Normal dirty chunk state is written on unload, not periodically. |
2875| World authoring | Editor changes create pending authored state; the running server stays pinned to its startup revision. Each chunk save appends an admin-attributed diff changelog. |
2876| Restart path | Planned restart force-unloads the world and reuses the ordinary unload save path. |
2877| Control | Human and future scripted control both emit validated action commands. |
2878| Deployment | The game exits gracefully; systemd relaunches it and only pulls/builds when an intentional deployment manifest requests it. |
2879| Client architecture | FrameworkV3 is a git submodule under `client/frameworkv3`, built before game client code; backend ECS internals do not become the client object model. |
2880| Sprites | All world sprites are exactly 16×16 pixels; any other size is rejected on load and fails CI. Equipment overlays and recolour masks are included. |
2881| Appearance | Visible gear is layered 16×16 overlays on the mob; recolourable channels (such as metal) use material colour without duplicate art sets. Nearby clients receive appearance layers, not another player's inventory. |
2882| Play camera | The play viewport is centered on the local player. Only the admin world editor uses a free chunk camera. |
2883| Movement | All ground mobiles share a global walk/run cadence from world settings; the server commits integer tiles; clients lerp for presentation only. |
2884| World time | World calendar time is server time minus 1200 years. Night darkens tiles the baked light map cannot reach. |
2885| World settings | Tick timers and global constants are authored in the editor modal, pinned to the world revision, and not hot-patched into a live process. |
2886| Baked light | Static light reach is raycast through passable tiles on chunk save, may cross chunks, and is not recomputed every tick. |
2887| Ground items | Player drops last `groundItemDespawnDuration` (default 10 minutes), block nobody, and are picked up only by a player standing on that tile. |
2888| Shop prices | NPC shop prices lerp from the captured pre-sale value toward the last player-market unit price over `shopPriceLerpDuration` (default one hour), times a hidden per-shop discount. |
2889| Proximity speech | Distant clients never receive unobscured plaintext that game rules say they cannot understand. |
2890| Courier cargo | Pigeons carry money or one item stack, never a chat packet; cargo is durable in transit and remains delayed. |
2891| Inventory | A player has 32 slots; a stack occupies one slot; the client never asserts inventory, wallet or vault results. |
2892| Shared bank | Every bank reads the same **character** vault; pigeon deposits become available only after arrival at the nearest bank. |
2893| Closed chunks | Closed or never-edited chunks are visible but not enterable; never-edited terrain is default grass with no blocks. |
2894| Accounts | Login is auth.timfalken.com (or `admin-<n>` stub). Characters belong to an account; one may be in the world at a time. |
2895| Names | Surnames are globally unique per account; first+last is unique per account; names free only after permanent delete. |
2896| Inheritance | Deleted characters dump inventory, equipment, wallet and vault into an account inheritance tab other characters can claim. |
2897| Cheques | Filling a cheque reserves vault goods; the bearer item is the claim; destruction without redemption releases the reservation. |
2898| Marketplace escrow | Every open order is fully backed by escrow and matching/settlement is atomic and deterministic. |
2899| Combat | Melee requires an 8-neighbour tile; ranged/spell range comes from the item or spell; hit uses the weapon skill; damage uses Strength, Dexterity or Mind. |
2900| Progression | Players have no classes; non-combat actions award XP to one governing skill; a successful attack splits XP equally between hit and damage skills. |
2901
2902# 30. Important edge cases to preserve during implementation
2903
2904- A ChunkLoader crossing a region boundary can change
2905 residency/simulation references and worker ownership in the same tick;
2906 ordering must avoid temporary double ownership.
2907
2908- A player at a worker boundary may receive visible chunks from multiple
2909 workers without moving ownership solely for rendering.
2910
2911- A planned restart must ignore normal ChunkLoader retention when
2912 forcing the world to unload.
2913
2914- A world-editor save must never cause newly loaded chunks in the
2915 current process to use the pending revision. It must append a changelog
2916 record naming the admin, timestamp and tile diffs.
2917
2918- Pathfinding and player movement must reject tiles in closed or
2919 never-edited chunks even when those chunks are in the 3×3 view.
2920
2921- Two accounts must not claim the same surname. One account may reuse its
2922 surname; first+last must stay unique on that account until permanent
2923 delete.
2924
2925- Marking a character for deletion must not free the name or move items
2926 until the delay elapses. Cancelling must restore playability.
2927
2928- Character deletion must notify the account email (or log, on stub auth).
2929 Permanent delete must void that character's issued cheques, then move
2930 inventory, equipment, wallet and vault into the account inheritance tab.
2931
2932- Saving a chunk must rebake that chunk's light map and any neighbour
2933 chunks within max light range, using passable-tile raycasts. Light from
2934 a source in chunk A may appear in chunk B.
2935
2936- A mob definition must not carry its own walk/run speed; gait only
2937 selects every-other vs every movement tick on the global cadence.
2938
2939- World-settings saves must not apply to the live process; they wait for
2940 the same pending-revision restart as chunk edits.
2941
2942- Night shading must not light a tile the baked mask marks unreachable,
2943 even if a torch is nearby through a wall.
2944
2945- A sprite whose pixel size is not 16×16 must be rejected at load and must
2946 fail the sprite-dimension unit test. Equipment overlays and recolour
2947 masks are included.
2948
2949- Equipping must not leave two items in the same equipment slot. Unequip
2950 into a full inventory must fail and leave the item worn.
2951
2952- Nearby clients must not receive another player's inventory in order to
2953 draw their armour; appearance layers and material ids are sufficient.
2954
2955- A client build without `client/frameworkv3` initialized must fail rather
2956 than silently using some other FrameworkV3 install.
2957
2958- Client interpolation of movement must not be treated as authority. Combat
2959 range and pickup use the server tile, not the lerped draw position.
2960
2961- The play camera must remain centered on the local player. Zoom must not
2962 expand the subscribed chunk set.
2963
2964- A persistent mob spawned by a spawner must not be duplicated merely
2965 because it moved out of the spawner’s loaded area.
2966
2967- A non-persistent mob disappears when its chunk is actually unloaded,
2968 not merely when it becomes dormant.
2969
2970- If a persistent ChunkLoader or offline scripted player exists after
2971 restart, startup must discover it from an index without loading the
2972 entire world.
2973
2974- A pending code update followed by an unrelated Node.js crash must
2975 restart the currently deployed commit rather than deploying early.
2976
2977- Negative coordinates, daylight-saving midnight calculation, duplicate
2978 transfer messages and failed deployment migrations should all have
2979 explicit tests.
2980
2981- Proximity chat degradation must happen before plaintext reaches an unauthorised
2982 distant client; rendering-only obfuscation is not sufficient.
2983
2984- Carrier-pigeon deliveries must survive restarts and recipient logout without
2985 requiring every traversed chunk to remain stimulated.
2986
2987- A pigeon carrying an item to a player whose inventory cannot accept it must
2988 not destroy the cargo; it deposits into that player's vault via the nearest
2989 bank.
2990
2991- Two concurrent bank withdrawals, cheque fills or pigeon-arrival deposits must
2992 not spend the same vault goods twice.
2993
2994- Filling two cheques against the same vault stack must reserve disjoint
2995 quantities or reject the second fill.
2996
2997- A filled cheque that expires on the ground must release its reservation and
2998 must not remain redeemable.
2999
3000- A player-dropped ground item must not block movement, must not keep its chunk
3001 loaded, and must still be present after a chunk unload/reload if `expiresAt`
3002 has not passed.
3003
3004- Pickup of a ground item from a tile the player is not standing on must fail.
3005
3006- Requesting blank cheques must never raise the player's carried blank-cheque
3007 count above 99.
3008
3009- A marketplace match must atomically consume both escrows exactly once, even if
3010 two compatible orders arrive concurrently.
3011
3012- A matching market order from an online player may settle immediately for that
3013 player while the older/offline counterparty's delivery remains durable.
3014
3015- Skill XP is awarded only after authoritative action resolution, never directly
3016 from a client-reported result. A successful player attack splits that XP;
3017 a miss awards none.
3018
3019- A melee attack from the target's own tile, or from Chebyshev distance greater
3020 than 1, must fail. A ranged or spell attack beyond that item or spell's
3021 `rangeTiles` must fail.
3022
3023- A new player-market sale must capture the then-current undiscounted lerp
3024 value as `priceFrom` so shop and tooltip prices do not jump back to seed.
3025
3026- Two shop NPCs may charge different prices for the same item at the same
3027 instant because each applies its own hidden discount to the same lerp.
3028
3029- Item tooltip value must not be recomputed every tick; a one-minute refresh
3030 is sufficient. Purchase price is still evaluated at the moment of buy.
3031
3032# 31. Decisions through version 0.12
3033
3034- Chunk persistence is unload-driven rather than periodic.
3035
3036- The authored tile model has separate visual ground and functional
3037 block layers.
3038
3039- Mobile actors remain ECS entities and are not authored as painted tile
3040 contents.
3041
3042- Spawner blocks are editor-placeable and configurable per instance;
3043 persistence belongs to the spawned mob type.
3044
3045- world.sqlite is an authored, revisioned world source; state.sqlite
3046 holds runtime durable state.
3047
3048- Editor changes are staged for activation on restart instead of
3049 hot-patching the running world.
3050
3051- Code/world changes schedule a player-visible midnight restart; admins
3052 can trigger the same graceful pipeline immediately.
3053
3054- Git pull/build/relaunch belongs to `systemd` supervision after the
3055 game process has safely exited.
3056
3057- Deployment is manifest-driven: crash recovery restarts the currently
3058 checked-out commit, while only an intentional deployment restart may
3059 fast-forward `master`.
3060
3061- Future player scripting is modelled as an alternative controller
3062 producing normal server action commands.
3063
3064- Offline scripted players may remain in-world as ChunkLoaders until
3065 death or expiry and must survive planned restarts through persistence.
3066
3067- The player client is built on FrameworkV3, included as the git submodule
3068 `client/frameworkv3` and built first so this game's client code can layer on
3069 top. The client does not need an ECS and consumes protocol state
3070 independently of backend ECS storage. The Node.js server does not import
3071 FrameworkV3.
3072
3073- All world sprites (tiles, blocks, mobs, items) are exactly 16×16 pixels.
3074 Other sizes are rejected at load. A unit test lists offenders and fails if
3075 any exist. Sprites are not individually resized; the player may zoom the
3076 whole viewport within configured bounds.
3077
3078- Visible equipment is drawn as extra 16×16 layers on the mob, including
3079 players. Worn items occupy equipment slots, not the 32 inventory slots.
3080 Nearby clients replicate appearance layers only, never another player's
3081 inventory.
3082
3083- Recolourable gear (metal armour) shares one overlay sprite and a 16×16
3084 channel mask. Material definitions supply the metal colour; luminance of
3085 the overlay is preserved. Iron and steel plate are different items with
3086 the same art and different `materialId`.
3087
3088- The play camera is always centered on the local player. The admin world
3089 editor is the only exception, and it frames one chunk at a time.
3090
3091- Authoritative movement is a tile-to-tile jump on a **global** cadence:
3092 default walk 2 tiles/s, run double. Walk steps every other movement tick;
3093 run steps every movement tick. Mobs do not set their own speed. Clients
3094 lerp for visuals only and never send interpolated positions.
3095
3096- Admins edit global tick timers and constants in a world-settings modal.
3097 Those values live in the pending world revision and apply on the next
3098 process start, like other editor saves.
3099
3100- World calendar time is server time minus 1200 years, same IANA zone as
3101 midnight restarts. At night the client darkens tiles the baked light map
3102 cannot reach.
3103
3104- Static light is baked on chunk save by raycast through passable tiles,
3105 including across chunk borders. The editor has a night-to-day slider for
3106 preview only.
3107
3108- Each world-editor chunk save stores who edited it, when, and a bullet
3109 diff of ground changes, block placements, block replacements and block
3110 removals at world tile coordinates.
3111
3112- Default speech is proximity-based and becomes less legible with distance.
3113 Long-distance exchange is physical: a pigeon carries money or one item stack.
3114 A letter is paper with player-written text, not a separate mail record.
3115
3116- Permanent player groups are social/addressing structures and do not create an
3117 instant global chat channel.
3118
3119- Carrier-pigeon transit is persistent but does not automatically keep every
3120 traversed chunk simulated. Whenever a pigeon passes through a chunk that is
3121 already simulating, it materialises as an ECS `Mob` and is visible to any
3122 nearby client whose normal chunk subscription includes it, even if that client
3123 is unrelated to the delivery. Unrelated clients do not receive cargo contents.
3124
3125- A player has a 32-slot inventory. Stackable items occupy one slot. Currency is
3126 a numeric wallet/vault balance, not an inventory item.
3127
3128- Player-dropped items lie on the tile for `groundItemDespawnDuration`
3129 (default 10 minutes), block nobody, and may be picked up by anyone standing
3130 on that tile. They survive unload until expiry via timestamps.
3131
3132- The bank near the marketplace holds an unlimited **character** vault.
3133 Later banks are linked to the same vault. Pigeons may deposit money or one
3134 stack into the sender's vault after arriving at the nearest bank. An
3135 account-level inheritance tab receives a deleted character's goods.
3136
3137- Blank cheques are issued at a bank up to a carried total of 99. Filling a
3138 cheque reserves a vault item quantity. The filled cheque is a bearer item.
3139 In-person redemption withdraws into the bearer's inventory. Sending the cheque
3140 to the bank by pigeon transfers the reserved goods into the pigeon's sender's
3141 vault.
3142
3143- The central marketplace hides individual live sell listings and matches durable
3144 escrowed buy/sell orders at the midpoint of compatible bid/ask limits.
3145 Quantities are item stacks.
3146
3147- The newest matching market participant receives the trade result locally; the
3148 older counterparty receives theirs by pigeon into their bank.
3149
3150- NPC shops remain restricted to `npcShopAllowed` basic ingredients. They sell
3151 to players at
3152 `lerp(priceFrom, lastTradePrice, min(1, (now - lastTradeAt) / shopPriceLerpDuration))`
3153 times a hidden per-shop discount. With no player-market sale yet, the
3154 undiscounted value is `seedValue`. Tooltips use the same lerp without the
3155 discount and refresh at most once per minute.
3156
3157- Hovering an item shows name, description, origin (crafter, or shop NPC name
3158 if bought there) and current undiscounted value.
3159
3160- All combatants can attack. Melee requires standing on one of the eight
3161 neighbouring tiles. Ranged attacks and spells use the item's or spell's
3162 range. The hit roll uses the weapon skill; damage uses Strength (melee),
3163 Dexterity (ranged) or Mind (magic). Successful player-attack XP is split
3164 equally between those two skills.
3165
3166- Player progression is skill-based rather than class-based. Non-combat
3167 actions award XP to one governing skill; combat hits split XP as above.
3168
3169- Never-edited chunks are default grass, no blocks, and **closed**. The
3170 editor opens or closes each chunk. Closed chunks are visible but not
3171 enterable.
3172
3173- Accounts authenticate at auth.timfalken.com. Until that service is up,
3174 each connection is stub `admin-<n>` (n = connected client count including
3175 this one) and is treated as admin.
3176
3177- An account has unlimited characters and plays one at a time. Creation
3178 takes first name (not globally unique), last name (globally unique to the
3179 account, reusable on that account's other characters), and male/female.
3180 first+last must be unique for that account. This setup may change later.
3181
3182- Character deletion is a 24-hour (configurable) delay with email notify
3183 and cancel. Permanent delete frees names and moves inventory, equipment,
3184 wallet and vault to the account inheritance tab, which any of that
3185 player's characters can claim into their own vault.
3186
3187# 32. Open design decisions for later iterations
3188
3189These do not block the initial implementation, but should eventually be
3190specified explicitly:
3191
3192- Whether multiple mobile entities may occupy one tile and, if so, which
3193 categories can overlap.
3194
3195- Whether player movement is four-direction only or also supports
3196 diagonals. Combat melee adjacency already includes diagonals.
3197
3198- Exact hit-chance and damage curves, attack intervals/cooldowns, whether
3199 Defence modifies incoming hit chance or damage, and ranged/spell
3200 line-of-sight or obstruction rules.
3201
3202- Deterministic rounding when shop discount or lerp produces a fractional
3203 currency amount.
3204
3205- Exact equipment slot list, per-slot draw order exceptions (cloaks,
3206 two-handed weapons), and whether worn overlays have facing frames to
3207 match the mob.
3208
3209- Additional recolour channels beyond metal (for example cloth dyes) and
3210 the exact luminance-preserving remap function.
3211
3212- Exact camera zoom minimum, maximum and whether zoom is restricted to
3213 integer steps.
3214
3215- Exact night ambient curve (how dark, dusk length) and whether baked light
3216 stores a boolean reach mask or a distance/falloff value per tile.
3217
3218- Whether opening a door at runtime should rebake or ignore static light.
3219
3220- Exact simulation tick rate stays a world setting; lower-frequency AI and
3221 spawner cadences can still be tuned independently.
3222
3223- Exact world/chunk binary serialisation format and schema/version
3224 migration strategy.
3225
3226- Whether gameplay can permanently modify ground/block tiles in the
3227 initial release.
3228
3229- Spawner timing rules, spawn-point restrictions and behaviour when
3230 persistent spawned mobs travel very far away.
3231
3232- World-editor undo/redo and rollback UI. The per-chunk changelog is an audit
3233 log, not by itself an undo stack.
3234
3235- Exact restart warning intervals and whether admins can
3236 cancel/reschedule a planned restart.
3237
3238- Worker rebalance thresholds and whether regions may migrate while
3239 players are actively crossing their boundaries.
3240
3241- Future scripting language syntax, event model and resource quotas.
3242
3243- Exact proximity-chat distance curve, maximum range and character degradation
3244 algorithm.
3245
3246- Group naming/roles, membership limits and whether group-wide letter sending
3247 is offered as an addressing convenience that still dispatches one pigeon and
3248 consumes one paper/letter per recipient.
3249
3250- Whether pigeons can eventually be intercepted, killed or redirected in transit.
3251
3252- Marketplace partial fills, cancellation rules, fees/taxes (if any),
3253 tie-breaking details and midpoint rounding for indivisible currency.
3254
3255- Whether market price history or aggregate statistics are visible despite live
3256 order listings remaining hidden.
3257
3258- Initial skill catalogue, XP curves, level caps, action XP formulas and the
3259 remaining interpretation of skills such as Defence.
3260
3261- Maximum letter body length and whether writing paper requires a desk or can be
3262 done from inventory anywhere.
3263
3264- Exact item catalogue, which items stack, per-item `maxStackSize` exceptions,
3265 harvest interactions and ground-item spawner parameters.
3266
3267- Whether death drops inventory, and whether dropped unique items other than
3268 cheques have destruction side-effects.
3269
3270- Whether the issuer can void a filled cheque without the bearer item being
3271 destroyed, and whether cheques can ever represent currency rather than items.
3272
3273- Whether a short dispatch interval is needed so many pigeons cannot leave in a
3274 single tick, even though sending remains free.
3275
3276- New-character spawn location (must be an open chunk) and name length /
3277 allowed-character rules.
3278
3279- Later changes to character creation beyond first name, last name and sex.
3280
3281# 33. Architectural summary
3282
3283ECS → what an entity is and what systems can act on it
3284Chunk → tile data, spatial lookup, simulation and client subscription
3285Region → residency and simulation-worker ownership
3286Coordinator→ where regions execute
3287Gateway → stable client connections, auth, character select, and command/update routing
3288world.sqlite→ authored versioned ground/block/spawner/light/settings world; unedited chunks are closed grass
3289state.sqlite→ accounts, characters, vaults, inheritance, and other durable live-game state
3290systemd → process supervision and relaunch
3291Deployment hook → conditional Git update/build only for intentional deployment restarts
3292Controller → manual client input today; sandboxed player scripts later
3293FrameworkV3 → git submodule at `client/frameworkv3`; built first; game client code layers on top
3294Sprites → all world art is 16×16; reject and CI-fail any other size
3295Equipment → layered 16×16 overlays on mobs; metal armour shares art and recolours by material
3296Camera → play view centered on the local player; bounded zoom; editor is chunk-framed
3297Movement → global walk/run cadence (default 2 tiles/s walk, run double); server tile steps; client visual lerp
3298World time → server clock minus 1200 years; night darkens unlit tiles
3299Light → baked passable-tile raycast on editor save; shines across chunks
3300World settings → admin modal for tick timers and global constants; pending revision
3301Inventory → 32 slots; stacks occupy one slot; letters are written paper items
3302Bank → per-character vault; account inheritance tab on character delete
3303Auth → auth.timfalken.com, stub admin-<n> until live; unlimited characters, one in world
3304Chunks → editor open/closed; default grass and closed until painted
3305Ground items → non-blocking, 10-minute player drops, pickup only while standing on the tile
3306Communication service → proximity speech
3307CourierService → pigeons carrying money or one item stack through durable transit
3308BankService → shared unlimited vaults, cheque reservations and redemption
3309MarketService → durable escrowed order book, matching, last-sale index and pigeon-to-bank settlement
3310Shop NPCs → sell allowed stock; price lerps toward last player-market sale over shopPriceLerpDuration, times a hidden discount
3311Combat → 8-tile melee, item/spell ranged range; hit skill roll; Strength / Dexterity / Mind damage; equal XP split
3312Skills → classless progression; non-combat XP to one skill; attack XP split hit/damage
3313
3314
3315# 34. Version history
3316
3317## 0.12
3318
3319- Chunks are open or closed in the world editor. Closed chunks stay visible
3320 but cannot be entered. Never-edited chunks are default grass with no
3321 blocks and are closed.
3322- Login uses auth.timfalken.com; until that is live, connections are stub
3323 `admin-<n>` (connected-client count including this one) and are admins.
3324- Accounts have unlimited characters, one in the world at a time. Creation
3325 is first name, unique account-owned last name, and male/female.
3326- Character deletion waits 24 hours with email and cancel. Permanent delete
3327 frees names and moves goods to an account inheritance bank tab.
3328
3329## 0.11
3330
3331- Made walk/run a global cadence from world settings (default 2 tiles/s
3332 walk, run double): walk steps every other movement tick, run every tick.
3333 Mob definitions do not set move speed.
3334- Added an admin world-settings modal for tick timers and global constants
3335 (shop lerp duration, drop lifetime, simulation tick, and the same class
3336 of values). Settings ride the pending world revision.
3337- World calendar time is server time minus 1200 years.
3338- Baked static lighting by passable-tile raycast on chunk save, including
3339 across chunk borders. Clients darken unreachable tiles at night. The
3340 editor has a night-to-day preview slider.
3341
3342## 0.10
3343
3344- Drew visible equipment as 16×16 overlay layers on mobs (including players),
3345 with worn items in equipment slots rather than the 32-slot inventory.
3346- Replicated compact appearance layers to nearby clients instead of another
3347 player's inventory.
3348- Recolourable metal armour shares one overlay plus a 16×16 channel mask;
3349 material definitions supply the metal colour while preserving shading.
3350
3351## 0.9
3352
3353- Vendored FrameworkV3 as the git submodule `client/frameworkv3`. The game
3354 client builds that library first and implements game-specific code on top
3355 of it. The Node.js server does not import the submodule.
3356
3357## 0.8
3358
3359- Required all world sprites (tiles, blocks, mobs, items) to be 16×16 pixels,
3360 rejected at load, with a CI unit test that reports and fails on any other
3361 size. Sprites are not individually scaled; the player may zoom the viewport
3362 within configured bounds.
3363- Locked the play camera to the local player. The admin world editor remains
3364 the only non-player-centered view.
3365- Made authoritative movement integer tile-to-tile steps. Clients lerp
3366 mobiles for presentation only.
3367- Added a per-chunk world-editor changelog: admin, timestamp, and bullet
3368 diffs for ground changes, block place/change/remove.
3369
3370## 0.7
3371
3372- Added combat for all mobs including players: melee from any of the eight
3373 neighbouring tiles, ranged and spells from the item or spell range.
3374- Hit rolls use the weapon skill (Swordfighting, Axefighting, Archery, Magic,
3375 and so on). Damage uses Strength, Dexterity or Mind according to melee,
3376 ranged or magic.
3377- Successful player-attack XP is split equally between the hit skill and the
3378 damage skill. Ordinary mobs use archetype skill levels and do not earn XP.
3379- Shop NPCs sell items at seed value adapted to the last player-market unit
3380 price, lerping over one hour, multiplied by a hidden per-shop discount.
3381- Only the latest player-market sale per item is stored (price, timestamp, and
3382 lerp origin). No historical series.
3383- Item hover shows name, description, origin (crafter or shop NPC) and the
3384 undiscounted current value, refreshed at most once per minute.
3385
3386## 0.6
3387
3388- Added a 32-slot player inventory, stackable items, carried currency as a
3389 numeric wallet, and unique-instance items for letters and filled cheques.
3390- Redefined letters as paper items with player-written text rather than a
3391 separate mail record.
3392- Redefined carrier pigeons as free couriers that carry money or one item
3393 stack to a player or to the nearest bank.
3394- Added a shared unlimited bank near the marketplace, blank cheques filled to
3395 99, vault reservations on fill, in-person redemption and pigeon-to-bank
3396 cheque transfers between vaults.
3397- Added player-dropped ground items: 10-minute lifetime, non-blocking, pickup
3398 only while standing on the tile, timestamp persistence across unload.
3399- Specified later ground-item spawners and harvesting as content that reuses
3400 this item model.
3401- Routed offline/full-inventory pigeon delivery and older-side market
3402 settlement into the recipient's shared bank vault.
3403
3404## 0.5
3405
3406- Made carrier pigeons shared world-visible entities whenever their route crosses an already-simulating chunk.
3407- Unrelated nearby players can see pigeons in their normal 3x3 chunk view; pigeons do not keep chunks loaded themselves.
3408- Added deterministic materialisation/dematerialisation between durable abstract transit and worker-owned ECS pigeon entities.
3409
3410## 0.4
3411
3412- Added FrameworkV3 as the shared player-client foundation while keeping backend ECS internal to the server.
3413- Added server-side proximity chat degradation, persistent player groups and durable carrier-pigeon letters.
3414- Added scalable courier transit that can cross dormant world space without forcing normal chunk simulation.
3415- Added the central marketplace, escrowed hidden order book, midpoint pricing and pigeon-based remote settlement.
3416- Added the player-driven item-source philosophy and restrictions on NPC shop inventories.
3417- Added classless, skill-based player progression and authoritative skill XP.
3418
3419## 0.3
3420
3421- Converted the living design document to Markdown as the canonical format.
3422- Defined `systemd` as the production process supervisor.
3423- Added a conditional, manifest-driven deployment path so crashes do not deploy pending code early.
3424- Added a concrete example systemd service shape and clarified privilege separation.
3425
3426## 0.2
3427
3428- Added unload-driven chunk persistence, authored world revisions, the admin world editor, spawner blocks, graceful scheduled restarts and future player scripting hooks.