> ## Documentation Index > Fetch the complete documentation index at: https://arclux-os.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # πŸŒπŸ’Ύ ARCLUX β€” Persistent World (Tanpa Reset Naratif) > Blueprint detail β€” ARCLUX Repository War Universe # πŸŒπŸ’Ύ ARCLUX β€” Persistent World (Tanpa Reset Naratif) > **A server restart should not have to mean a world reset.** Bagian dari blueprint ARCLUX (Repository War Universe). Extension V6 β€” Persistent World. > **Aturan inti:** > > * **SERVER RESTART β‰  WORLD RESET** β€” state dunia yang tervalidasi dipulihkan > setelah maintenance/restart/crash/recovery. > * **NO PLAYER-INITIATED WORLD PAUSE** β€” pemain tidak bisa menghentikan dunia. > * **Respawn / logout-location policy = keputusan ruleset terpisah** (belum > diputuskan di sini; dibawa ke `docs/blueprint/progres/decisions-mmo.md`). *** ## 1. Yang Sudah Ada (cross-reference) | Topik | Sudah di | | - | - | | Persistence region (save/load `RegionSnapshot`, recovery) | `packages/gameserver/persistence.ts` + `world.ts` (`snapshot`/`regionFromState`) | | Provenance / history vessel/component | `packages/provenance` + [04-wreckage-history.md](https://github.com/GSF-001/ARCLUX/blob/main/04-wreckage-history.md) | | Replay / event log (server authoritative) | [03-combat.md](https://github.com/GSF-001/ARCLUX/blob/main/03-combat.md) I.8 | | World Validator / client β‰  source of truth | [03-combat.md](https://github.com/GSF-001/ARCLUX/blob/main/03-combat.md) I.4/I.7 | | Persistence via `packages/db` + RecoveryManager | [arsitektur.md](https://github.com/GSF-001/ARCLUX/blob/main/progres/arsitektur.md) | *** ## 2. Persistent World State World state diperlakukan sebagai data persisten: ``` WORLD β”œβ”€β”€ Regions β”œβ”€β”€ Communities β”œβ”€β”€ Stations β”œβ”€β”€ Vessels β”œβ”€β”€ Components β”œβ”€β”€ Wreckage β”œβ”€β”€ Ownership β”œβ”€β”€ Provenance └── Events ``` Saat server aktif kembali: ``` PERSISTED WORLD STATE β†’ RECOVERY β†’ VALIDATION β†’ WORLD RESTORED β†’ SIMULATION CONTINUES ``` Restart teknis tidak boleh menghapus keadaan dunia. *** ## 3. No Auto History Reset Pergantian versi, maintenance, atau restart tidak otomatis menghapus: sejarah perang, provenance, ownership history, component lineage, community history, vessel history, recovery/governance/destruction/diplomatic events. Data historis hanya berubah melalui **mekanisme dunia yang sah**. *** ## 4. Perang sebagai Event Persisten Pertempuran bukan match terpisah yang di-reset: ``` WAR DECLARED β†’ ENGAGEMENT β†’ DAMAGE β†’ RETREAT β†’ RECOVERY β†’ SECOND ENGAGEMENT β†’ VESSEL LOSS β†’ AFTERMATH ``` Setiap event jadi bagian persistent world history. Konflik berkembang dari tindakan pemain, bukan diatur-paksa. *** ## 5. No Match Reset Hasil pertempuran tidak dikembalikan ke kondisi awal setelah engagement/server restart: ``` VESSEL A HP 100% β†’ BATTLE β†’ 63% β†’ SERVER RESTART β†’ WORLD RECOVERY β†’ 63% ``` State mengikuti hasil simulasi terakhir yang tervalidasi. *** ## 6. Ship Veteran & Service History Satu kapal bisa bertahan melewati banyak konflik: ``` VESSEL ALPHA β”œβ”€β”€ Created β€” Year 1 β”œβ”€β”€ Battle #03 β†’ Damaged β”œβ”€β”€ Repaired β”œβ”€β”€ Battle #11 β†’ Component replaced β”œβ”€β”€ Battle #24 β†’ Recovered β”œβ”€β”€ Ownership transferred └── Active ``` Kapal punya service/battle history = identitas teknis, bukan hanya statistik. ### 6.1 Incident Model Kegagalan signifikan bukan sekadar status akhir ("ENGINE HP: 0"). Dunia mempertahankan **rantai sebab-akibat** bagaimana kegagalan terjadi (Vessel Failure Intelligence): ``` WORLD EVENT ↓ ENVIRONMENTAL / COMBAT EXPOSURE ↓ COMPONENT RESPONSE ↓ DEPENDENCY FAILURE ↓ SUBSYSTEM DEGRADATION ↓ VESSEL CONSEQUENCE ``` **Incident** = event signifikan yang tercatat dengan metadata: ``` INCIDENT β”œβ”€β”€ Incident ID β”œβ”€β”€ World Tick β”œβ”€β”€ Region β”œβ”€β”€ Vessel β”œβ”€β”€ Triggering Event β”œβ”€β”€ Involved Components β”œβ”€β”€ State Before β”œβ”€β”€ State After β”œβ”€β”€ Causal Links └── Consequences ``` Contoh: ``` INCIDENT #8291 VESSEL: Capital Vessel Aurora TRIGGER: Solar Event Exposure PRIMARY: Propulsion Degradation RELATED: Thermal System β†’ Power Distribution β†’ Main Propulsion RESULT: Emergency retreat required ``` ### 6.2 Failure Timeline Engineer dapat melihat kegagalan sebagai urutan peristiwa (bukan cuma status akhir): ``` TICK 18420 Solar event detected TICK 18460 Thermal load increased TICK 18502 Cooling efficiency degraded TICK 18531 Power redistribution triggered TICK 18577 Propulsion output reduced TICK 18610 Vessel mobility compromised ``` ### 6.3 Guardrail: Causal β‰  Halusinasi Causal chain HARUS turun dari dependency graph yang benar-benar ada β€” bukan diinfer dari imajinasi. Data tervalidasi dunia β‰  interpretasi engineering. ARCLUX membedakan: ``` AUTHORITATIVE: ENGINEERING CONTEXT: Tick 18492 "Thermal subsystem was involved Component: degraded in the failure sequence leading Thermal load: increased to propulsion degradation." Propulsion: reduced ``` Authoritative facts dijaga integritasnya. Interpretasi engineering dibangun di atas data tersebut, bukan mengubahnya (cross-ref 05 Β§3.1). *** ## 7. Repair Tidak Menghapus Sejarah `DAMAGED β†’ REPAIR β†’ OPERATIONAL`, namun event damage/repair tetap tersimpan. Vessel veteran memiliki sejarah panjang yang dapat diverifikasi. Repair memperbaiki **state**. History mempertahankan **masa lalu**. Engineer dapat melihat bahwa vessel pernah mengalami: component failure, major damage, environmental exposure, battle loss, emergency repair. Tidak ada incident yang dihapus hanya karena vessel sudah kembali operational. *** ## 8. Kerusakan Punya Konsekuensi `COMBAT β†’ DAMAGE β†’ SYSTEM DEGRADATION β†’ REPAIR REQUIRED`. Repair dapat butuh: komponen, resource, engineering capability, akses station, waktu, recovery op (per ruleset). *** ## 9. No Retcon Tanpa Mekanisme Resmi Event tersahkan tidak dianggap tak pernah terjadi karena: pemain menyesal, komunitas kalah, kapal hancur, server restart, versi berubah. Koreksi/migration jika ada = event yang dapat diaudit. *** ## 10. World History > Match History History bukan hanya match result: ``` WORLD HISTORY β”œβ”€β”€ Battles Β· Vessel creation/destruction Β· Repairs β”œβ”€β”€ Recovery Β· Component transfers Β· Ownership changes β”œβ”€β”€ Governance Β· Community splits Β· Alliances └── Technology lineage ``` Dunia memiliki kontinuitas. *** ## 11. Veteran Dihitung dari History Label informal "veteran vessel" dihitung dari history (bukan scripted title): `Battles survived Β· Major repairs Β· Recovery events Β· Ownership transfers Β· Age`. Veteran β‰  otomatis lebih kuat; veteran berarti sejarah lebih panjang. *** ## 12. Persistence sebagai Sumber Kebenaran ``` PLAYER INTENT β†’ WORLD VALIDATOR β†’ SIMULATION β†’ WORLD STATE β†’ EVENT LOG β†’ PERSISTENCE ``` Client tidak menentukan: serangan berhasil, kapal rusak, pemilik, komponen ditemukan, recovery valid, kemampuan tersedia, event terjadi. Client hanya menampilkan state tervalidasi. *** ## 13. Recovery Setelah Server Restart ``` PERSISTED REGION STATE β†’ LOAD β†’ RECONSTRUCT WORLD REGION β†’ VALIDATE STATE β†’ RESUME SIMULATION ``` Entity tercatat sebelum restart dapat dipulihkan. (Reuse `regionFromState` / `packages/gameserver/persistence.ts`.) Incident/failure history juga persisten β€” server restart β‰  world reset (D-013). Semua incident yang tervalidasi tetap tersedia setelah restart untuk engineering context (Vessel Failure Intelligence). *** ## 14. NO PLAYER-INITIATED WORLD PAUSE > Keluar game β‰  keluar dari dunia. Model yang TEPAT: ``` PLAYER LOGIN β†’ WORLD STATE β†’ PLAYER/KAPAL DI POSISI X β†’ LOG OUT β†’ WORLD TETAP BERJALAN β†’ LOGIN LAGI β†’ KEMBALI KE STATE TERAKHIR ``` Bukan "resume dari save terakhir", melainkan "lanjut dari keadaan dunia yang benar-benar terjadi saat pergi". Jika sebelum logout kapal di station, state itu yang dipulihkan; perubahan dunia yang sah selama offline tidak di-undo. **Pengecualian teknis:** server tetap butuh maintenance/restart. Yang persisten adalah **state dunianya**, bukan servernya harus hidup selamanya. *** ## 15. Respawn / Logout-Location Policy (KEPUTUSAN RULESET β€” OPEN) Blueprint ini **tidak menetapkan** apakah pemain selalu respawn tepat di lokasi logout, maupun ada/tidaknya mekanisme respawn/teleport. Ini adalah **keputusan ruleset terpisah**; dicatat sebagai **D-number** di `docs/blueprint/progres/decisions-mmo.md` dan belum diputuskan. (Referensi navigasi jump/teleport tetap ada β€” lihat Β§14 Jump/Teleport System di [01-spatial-ux.md](https://github.com/GSF-001/ARCLUX/blob/main/01-spatial-ux.md) β€” tapi kebijakan respawn pemain dirumuskan terpisah.) *** ## 16. Persistent Consequence Loop ``` PLAYER ACTION β†’ VALIDATION β†’ SIMULATION β†’ STATE CHANGE β†’ DAMAGE/LOSS/RECOVERY β†’ EVENT β†’ PERSISTENCE β†’ HISTORY β†’ FUTURE WORLD STATE β†’ NEW PLAYER ACTION ``` Dunia tidak kembali ke keadaan awal hanya karena engagement selesai. ### 16.1 Failure Intelligence Loop Dari consequence loop, **failure history** menghasilkan **engineering context** yang membantu generasi vessel berikutnya: ``` FAILURE / SURVIVAL ↓ INCIDENT HISTORY ↓ ENGINEERING INTELLIGENCE ↓ ENGINEER / COMMUNITY REVIEW ↓ REDESIGN ↓ NEXT GENERATION VESSEL ``` ARCLUX tidak mendesain ulang kapal secara otomatis. ARCLUX mempertahankan bukti, hubungan sebab-akibat, dan konteks kegagalan agar engineer dapat membuat keputusan berikutnya (cross-ref 06 Β§18 community technology evolution & 05 Β§25 Design Evolution). *** ## 17. Hubungan dengan V4 & V3 * **V4 (07)**: `SPECIAL CAPABILITY β†’ ACTIVATION #1-3 β†’ DEPLETED β†’ VESSEL DAMAGED β†’ REPAIR β†’ VESSEL RETURNS`. Kemampuan terkuras tetap jadi sejarah kapal (provenance). * **V3 (06)**: `MEMBER β†’ TRUST β†’ ACCESS β†’ SPECIAL VESSEL β†’ BETRAYAL β†’ ACCESS REVOKED β†’ GOVERNANCE β†’ RECOVERY β†’ HISTORY`. Keputusan governance/teknologi menjadi bagian sejarah komunitas, bukan hanya sesi. *** ## 18. Final Persistence Model ``` ARCLUX WORLD β†’ PERSISTENT STATE (COMMUNITIESβ†’GOVERNANCEβ†’TRUSTβ†’ACCESS) (VESSELSβ†’DAMAGEβ†’REPAIRβ†’DESTRUCTION) (TECHNOLOGYβ†’COMPONENTSβ†’RECOVERYβ†’CUSTODY) β†’ EVENTS β†’ PROVENANCE β†’ HISTORY β†’ COMMUNITY MEMORY β†’ FUTURE WORLD STATE ``` *** ## 19. Prinsip Sentral > Code creates the vessel. Vessel creates gameplay. Gameplay creates > relationships. Relationships create trust. Trust creates access. Access > creates responsibility. Actions create consequences. Consequences create > damage, recovery, and governance. Recovery preserves technical lineage. > Governance preserves social history. History influences the future world. > Players create the events. ARCLUX preserves the consequences. > > **A server restart should not have to mean a world reset.** This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.