cyberia 3.2.22 → 3.2.70

package/src/client/components/cyberia-portal/TranslateCyberiaPortal.js

@@ -22,6 +22,14 @@ class TranslateCyberiaPortal {
       en: 'Cyberia Instance Engine',
       es: 'Cyberia Instance Engine',
     };
+    Translate.Data['cyberia-action-engine'] = {
+      en: 'Cyberia Action Engine',
+      es: 'Cyberia Action Engine',
+    };
+    Translate.Data['cyberia-entity-engine'] = {
+      en: 'Cyberia Entity Engine',
+      es: 'Cyberia Entity Engine',
+    };
   }
 }
 

package/src/client/public/cyberia-docs/ACTION-SYSTEM.md

@@ -27,11 +27,12 @@ CyberiaAction {
   sourceCellX:   Number
   sourceCellY:   Number
 
-  // Identity — used to match quest objectives of type 'talk'
-  provideItemId: String  // entity's active skin ObjectLayer item ID (e.g. 'wason', 'alex')
+  // Identity — the NPC skin is derived from the `default-<skin>` dialogue code
+  // (no stored field); 'talk' objectives match the talked-to bot's active skin.
 
-  // Quest grant — first interaction with this NPC starts the linked quest chain
-  grantQuestCode: String  // empty = no quest granted
+  // Quest award — NOT stored on the action. The quest(s) this action awards are
+  // the CyberiaQuest documents whose (sourceMapCode, sourceCellX, sourceCellY)
+  // match this action's cell; the runtime offers the next acceptable one.
 
   // Dialogue
   dialogCode:        String    // greeting dialogue shown on tap
@@ -73,7 +74,7 @@ A single `code` groups many ordered dialogue lines. The C client fetches all lin
 
 | Type         | Description                                                    | Active Payload                                       |
 | ------------ | -------------------------------------------------------------- | ---------------------------------------------------- |
-| `quest-talk` | Grants a quest on first interaction, then shows dialogue       | `grantQuestCode`, `dialogCode`, `questDialogueCodes` |
+| `quest-talk` | Awards the quest bound to its cell (via Take Quest), shows dialogue | quests bound by cell, `dialogCode`, `questDialogueCodes` |
 | `talk`       | NPC dialogue only — satisfies `talk` quest objectives          | `dialogCode`, `questDialogueCodes`                   |
 | `shop`       | Item shop — player buys items with in-game currency            | `shopItems[]`                                        |
 | `craft`      | Crafting station — consume ingredients to produce output items | `craftRecipes[]`                                     |
@@ -83,25 +84,26 @@ A single `code` groups many ordered dialogue lines. The C client fetches all lin
 
 ## Action–Quest Integration
 
-The Action System and Quest System are linked through `provideItemId` and `questDialogueCodes`:
+The Action System and Quest System are linked by **cell** (the action and the
+quest it awards share `sourceMapCode/sourceCellX/sourceCellY`) and by the NPC's
+active **skin** (which `talk` objectives match):
 
 ```mermaid
 graph LR
-    Quest["CyberiaQuest\nstep.objective:\n{ type: 'talk', itemId: 'wason' }"]
-    Action["CyberiaAction\nprovideItemId: 'wason'\ngrantQuestCode: 'wason-intro'\nquestDialogueCodes: ['wason-intro']"]
+    Quest["CyberiaQuest\nsource cell: (12,10)\nstep.objective: { type: 'talk', itemId: 'wason' }"]
+    Action["CyberiaAction\nsource cell: (12,10)\nquestDialogueCodes: ['default-wason']"]
     Progress["CyberiaQuestProgress\nstep.objectiveProgress[i].current++"]
 
-    Quest -->|matched by provideItemId| Action
+    Quest -->|same source cell| Action
     Action -->|player completes dialogue| Progress
 ```
 
 **Talk objective satisfaction flow:**
 
 1. Player taps NPC → interaction bubble shown.
-2. Player taps interaction bubble → Action is fetched by spatial coordinates.
-3. Client displays `dialogCode` dialogue sequence.
-4. On first tap, if `grantQuestCode` is set → server grants the quest.
-5. After viewing all `questDialogueCodes` dialogue lines → server increments the matching `talk` objective's `current` counter.
+2. Player taps interaction bubble → `modal_interact` opens; the offered quest is the one bound to the NPC's cell.
+3. Accepting is explicit: the **Take Quest** button sends `quest_accept` and the server grants the acceptable quest bound to that cell (prerequisites met, not active/completed).
+4. Talk objectives advance only after the player reads **all** `questDialogueCodes` lines (`dlg_complete`), validated server-side; never by a button.
 
 ---
 
@@ -157,9 +159,11 @@ sequenceDiagram
 ## Dialogue Interaction Protocol (talk / quest-talk)
 
 Tapping an interaction bubble opens the Raylib-native **`modal_interact`** modal
-first — the general-purpose entry point. Its `[Talk]` tab (shown only when the
-entity has dialogue) opens `modal_dialogue`; its `[Chat / Profile]` tab opens the
-JS overlay with no freeze.
+(top half of the screen). It has a tab strip — **stack** (active item slots),
+**stats** (six-stat stack totals), and **action** (mission interface, shown only
+for action-provider entities, ESI 8) — over a fixed bottom bar of right-aligned
+integration buttons (**Chat**, **Integration**) that open the JS overlay. The
+action tab's **Talk / Take mission** opens `modal_dialogue` (bottom half).
 
 The client is identical for `talk` and `quest-talk`; the **server** branches after
 `dlg_complete`. The client never declares the action type, quest code, or quest
@@ -187,11 +191,13 @@ simulation state.
 1. Validate `player.activeDialogueEntityID == msg.entityId`; drop otherwise.
 2. Clear the dialogue context and thaw the player (modal protection off).
 3. Resolve the action from `actionCache[entityId]`. `talk` → ack only.
-4. `quest-talk`: on first contact grant `grantQuestCode`; then for every active
-   quest whose **current step** has a `{ type: 'talk', itemId == provideItemId }`
-   objective, increment it — **only** when `msg.dialogCode` is in the action's
-   `questDialogueCodes`. On quest completion, deliver rewards (FCT) and unlock
-   successors.
+4. `quest-talk`: `dlg_complete` NEVER grants — it advances every active quest
+   whose **current step** has a `{ type: 'talk', itemId == bot active skin }`
+   objective, **only** when `msg.dialogCode` is in the action's
+   `questDialogueCodes`. Granting is a separate explicit `quest_accept`, which
+   grants the acceptable quest bound to the NPC's cell. On quest completion,
+   deliver rewards (FCT); successors are NOT auto-granted (the player accepts
+   each from its NPC).
 
 > **Dialogue-code contract.** The C client fetches dialogue groups at
 > `/api/cyberia-dialogue/code/default-<itemId>`, so the code it reports on
@@ -208,6 +214,22 @@ simulation state.
 
 ---
 
+## Fallback World mission instantiation
+
+The default mission system is playable in the procedural **Fallback World**.
+`DefaultCyberiaActions` carry `sourceMapCode` / `sourceCellX` / `sourceCellY`
+(all on `fallback-map-0`), and the world generator's
+`generateActionProviderBots()` places one passive NPC bot per action at those
+exact cells (skin = `provideItemId`, zero spawn/aggro radius). The fallback map
+builder reserves those cells (dropping any overlapping obstacle) so the NPCs
+always stand on walkable ground. The Go server then binds each bot back to its
+action by `sourceMapCode + sourceCellX + sourceCellY` at instance init and keeps
+an **ephemeral** per-session `CyberiaQuestProgress` (no persistence) — matching
+the ROADMAP Road-to-Alpha-Open contract. `scp-2040` kill targets spawn from the
+random bot pool, so the intro quest's talk → collect → kill loop is reachable.
+
+---
+
 ## Spatial Binding and Instance Init
 
 `sourceMapCode + sourceCellX + sourceCellY` links an Action to a specific entity cell in a specific map. During instance initialization:
@@ -257,8 +279,6 @@ The C client fetches the full `code` group sorted by `order`, then renders lines
 ```javascript
 // CyberiaAction
 { code: 1 }           // unique
-{ provideItemId: 1 }
-{ grantQuestCode: 1 } // sparse
 { sourceMapCode: 1, sourceCellX: 1, sourceCellY: 1 }
 
 // CyberiaDialogue
@@ -278,10 +298,8 @@ The C client fetches the full `code` group sorted by `order`, then renders lines
   "sourceMapCode": "cyberia-village",
   "sourceCellX": 12,
   "sourceCellY": 8,
-  "provideItemId": "wason",
-  "grantQuestCode": "wason-intro",
-  "dialogCode": "wason-intro",
-  "questDialogueCodes": ["wason-intro"],
+  "dialogCode": "default-wason",
+  "questDialogueCodes": ["default-wason"],
   "shopItems": [],
   "craftRecipes": [],
   "storageSlots": 0

package/src/client/public/cyberia-docs/CYBERIA-CLI.md

@@ -178,8 +178,8 @@ Named scripts from the `scripts/` directory for seeding and build maintenance.
 
 | Subcommand                   | Description                                                                         |
 | ---------------------------- | ----------------------------------------------------------------------------------- |
-| `import-default-items`       | Import default object layers, skill config, dialogues, client-hints to Mongo        |
-| `seed-skill-config`          | Upsert `DefaultSkillConfig` into a `CyberiaInstance` (`--instance-code`)            |
+| `import-default-items`       | Import default object layers, skills, dialogues, actions/quests, client-hints to Mongo |
+| `seed-skills`                | Upsert `DefaultSkillConfig` into the `cyberia-skill` collection (full records)       |
 | `seed-dialogues`             | Upsert `DefaultCyberiaDialogues` into the `cyberia-dialogue` collection             |
 | `generate-semantic-examples` | Generate one procedural example per registered semantic prefix                      |
 | `build-manifest`             | Build K8s Deployment + Service manifests for mmo-client / mmo-server                |
@@ -187,7 +187,7 @@ Named scripts from the `scripts/` directory for seeding and build maintenance.
 
 ```bash
 cyberia run-workflow import-default-items --env-path ./engine-private/conf/dd-cyberia/.env.development
-cyberia run-workflow seed-skill-config --instance-code default
+cyberia run-workflow seed-skills
 cyberia run-workflow generate-semantic-examples
 cyberia run-workflow build-manifest
 cyberia run-workflow build-server-dashboard

package/src/client/public/cyberia-docs/CYBERIA-CLIENT.md

@@ -235,16 +235,22 @@ All requests are CORS-simple GETs (no preflight) and cacheable. None require cre
 ```bash
 cd cyberia-client
 
-# Development build
-make -f Web.mk clean && make -f Web.mk web
+# Development build (defaults: BUILD_MODE=DEBUG, localhost URLs)
+make -f Web.mk clean && make -f Web.mk all
 
-# Release build
-make -f Web.mk clean && make -f Web.mk web BUILD_MODE=RELEASE
+# Release build — pass the production URLs explicitly (see note below)
+make -f Web.mk clean && make -f Web.mk all BUILD_MODE=RELEASE \
+    WS_URL=wss://server.cyberiaonline.com/ws \
+    API_BASE=https://www.cyberiaonline.com
 
-# Build + serve on dev port :8082
-make -f Web.mk serve-development
+# Build + serve locally on dev port :8082 (DEBUG, localhost)
+./dev-server.sh            # or: ./dev-server.sh <port>
 ```
 
+`WS_URL` and `API_BASE` are passed straight through to the compiler — see
+[Compile-time configuration](#compile-time-configuration). When omitted they
+default to `localhost`, so **production build pipelines must pass real URLs**.
+
 The build is part of the Underpost Platform static + PWA pipeline; production deploys go through `underpost client` and `underpost deploy`.
 
 ### Output
@@ -261,22 +267,33 @@ bin/
 
 ## Compile-time configuration
 
-`src/config.h`:
-
-| Constant                    | Default                             | Description                                                                                                      |
-| --------------------------- | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
-| `WS_URL`                    | `wss://server.cyberiaonline.com/ws` | WebSocket endpoint of cyberia-server                                                                             |
-| `API_BASE_URL`              | `https://www.cyberiaonline.com`     | engine-cyberia REST base URL                                                                                     |
-| `CYBERIA_CLIENT_HINTS_CODE` | `cyberia-main`                      | Lookup key for the optional client-hints fetch (presentation override key — never an instance/server identifier) |
-| `HTTP_TIMEOUT_SECONDS`      | `10`                                | HTTP request timeout                                                                                             |
-| `MAX_TEXTURE_CACHE_SIZE`    | `512`                               | Atlas texture LRU cap                                                                                            |
-| `MAX_LAYER_CACHE_SIZE`      | `256`                               | ObjectLayer metadata LRU cap                                                                                     |
-| `MAX_ATLAS_CACHE_SIZE`      | `256`                               | Atlas metadata LRU cap                                                                                           |
-| `DEFAULT_FRAME_DURATION_MS` | `100`                               | Default animation frame duration                                                                                 |
-| `ENABLE_DEV_UI`             | `false`                             | Force dev overlay regardless of presentation hints                                                               |
-| `APP_VERSION`               | `"1.0.0"`                           | Application version string                                                                                       |
-
-For local development, point `WS_URL` and `API_BASE_URL` at `localhost` before rebuilding.
+### Server URLs (build arguments)
+
+`WS_URL` and `API_BASE` are `make` arguments baked into the WASM as
+`-DWS_URL_OVERRIDE` / `-DAPI_BASE_URL_OVERRIDE`. There is **no** RELEASE/DEBUG URL
+switch — both default to `localhost` regardless of `BUILD_MODE`:
+
+| make argument | Default                  | Baked macro             |
+| ------------- | ------------------------ | ----------------------- |
+| `WS_URL`      | `ws://localhost:8081/ws` | `WS_URL_OVERRIDE`       |
+| `API_BASE`    | `http://localhost:4005`  | `API_BASE_URL_OVERRIDE` |
+
+> **Production pipelines must pass the URLs.** `BUILD_MODE=RELEASE` alone still
+> yields `localhost`. Any release build — the Docker image build, CI, manual
+> release — must pass `WS_URL=wss://… API_BASE=https://…` as make arguments
+> (or Docker build-args wired through to `make`), or the client ships pointing
+> at localhost. If unset, `src/config.h` falls back to bare `"ws://"` /
+> `"https://"` stubs.
+
+### Constants (`src/config.h`)
+
+| Constant                    | Default        | Description                                                                                                      |
+| --------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------- |
+| `CYBERIA_CLIENT_HINTS_CODE` | `cyberia-main` | Lookup key for the optional client-hints fetch (presentation override key — never an instance/server identifier) |
+| `MAX_TEXTURE_CACHE_SIZE`    | `512`          | Atlas texture LRU cap                                                                                            |
+| `MAX_LAYER_CACHE_SIZE`      | `256`          | ObjectLayer metadata LRU cap                                                                                     |
+| `MAX_ATLAS_CACHE_SIZE`      | `256`          | Atlas metadata LRU cap                                                                                           |
+| `DEFAULT_FRAME_DURATION_MS` | `100`          | Default animation frame duration                                                                                 |
 
 ---
 

package/src/client/public/cyberia-docs/CYBERIA-LORE.md

@@ -0,0 +1,88 @@
+# **Cyberia Lore — The Frontier of Hyperspace**
+
+### **Setting: Year 2520+**
+
+Earth is a ruined monument to humanity’s first age. Civilization now spans broken continents, orbital fortresses, lunar citadels, asteroid enclaves, and distant colonies. From the ashes of collapse emerged **Cyberia**: a living frontier where the physical world and **hyperspace** (persistent, immersive Instances) have fused into one unstable civilization.
+
+The boundary between reality and hyperspace is porous. Relics, wars, identities, and events bleed between layers, creating opportunity, conflict, and myth.
+
+---
+
+### **The Historical Fracture**
+
+The **Pacific Cataclysm** (2045) shattered the old world through nuclear disaster, environmental collapse, plagues, and uncontrolled experiments. As Earth became hostile, humanity expanded into space while building advanced **Instances** — enduring digital worlds that evolved from tools into homes, markets, religions, and battlefields.
+
+Two new groups emerged:
+
+- **Mutagens**: Radiation- and bio-altered humans, resilient but often marginalized.
+- **Synthetics**: Artificial beings who gained autonomy and identity.
+
+These groups, along with baseline humans, now navigate the layered reality of Cyberia.
+
+---
+
+### **The Dual Nature of Cyberia**
+
+Cyberia exists on two overlapping layers:
+
+- **Physical Layer**: Harsh, resource-driven reality of fleets, colonies, infrastructure, territory, and direct force. Slow, unforgiving, dominated by logistics and raw power.
+- **Hyperspace Layer**: Vast network of persistent Instances — living archives, simulated empires, memory-cities, and evolving digital ecosystems where time, geography, and identity are fluid.
+
+The two layers constantly influence each other through neural links, relics, breaches, and megastructures. What happens in one can reshape the other.
+
+---
+
+### **The Three Great Confederations**
+
+#### **Zenith Empire (Red)**
+
+Militaristic, hierarchical, expansionist. Masters of the **physical layer** — fleets, fortresses, industry, and territorial control.  
+**Core belief**: Civilization requires imposed order through strength.  
+**Strength**: Force, discipline, infrastructure dominance.  
+**Weakness**: Rigidity, anti-Mutagen prejudice, ecological destruction, over-reliance on Nova’s systems.  
+**Internal split**: Iron Legion (conquest) vs. Aether Council (technocratic stability).  
+**Relations**: Views Atlas as chaotic and degenerate; depends on Nova for intelligence and administration while resenting the dependency.
+
+#### **Atlas Confederation (Yellow)**
+
+Decentralized web of frontier settlements, Mutagen clans, Synthetics, traders, scavengers, hackers, and nomads. Excels in the unstable spaces **between** layers.  
+**Core strength**: Adaptation, asymmetric warfare, improvisation, infiltration, and survival in chaos.  
+**Weakness**: Fragmentation and internal division.  
+**Internal split**: Harmony Enclaves (diplomacy & coexistence) vs. Void Nomads (radical independence).  
+**Relations**: Opposes Zenith’s rigidity and environmental harm; undermines Nova through hacking and sabotage. Thrives on black-market networks and flexible alliances.
+
+#### **Nova Republic (Blue)**
+
+Technocratic, intelligence-driven civilization that dominates **hyperspace**. Obsessed with optimization, prediction, cognitive architecture, and transcendence.  
+**Core strength**: Information control, surveillance, predictive systems, and deep integration into digital realms.  
+**Weakness**: Emotional detachment, underestimation of irrational human elements (faith, loyalty, culture).  
+**Internal split**: Singularity Directive (machine supremacy) vs. Transcendent Conclave (hybrid flesh-machine future).  
+**Relations**: Provides critical systems to Zenith; faces constant subversion from Atlas hackers. Sees itself as the guiding intelligence of civilization.
+
+---
+
+### **The Balance of Power**
+
+The three confederations exist in tense, interdependent equilibrium:
+
+- Zenith controls physical force and territory.
+- Nova controls hyperspace information and architecture.
+- Atlas thrives in the gaps, through mobility, sabotage, and adaptation.
+
+They compete publicly, collaborate secretly, and betray each other routinely. None can fully dominate Cyberia — the frontier is too unstable, layered, and resistant to total control.
+
+---
+
+### **Your Role as Player**
+
+You are not a destined hero. You are a survivor who has lived long enough to matter.
+
+You can be:
+
+- A soldier, scout, smuggler, hacker, relic hunter, Instance diver, mercenary, diplomat, or rogue Synthetic/Mutagen.
+- Aligned with one faction, multiple, or none.
+- A wanderer who moves between physical ruins and hyperspace realms.
+
+Your power comes from what you **carry, recover, build, protect, steal, or remember**. In Cyberia, the true battle is over meaning, memory, and access across layers of reality. Your choices can shift alliances, awaken relics, destabilize systems, or forge new legends.
+
+**Welcome to Cyberia** — the Hyper-Reality Frontier. A broken future where physical and digital realities collide, ancient scars shape new empires, and your story is still unwritten.