Files
aeternalis/planning/IMPLEMENTATION-NOTES.md
T

1.6 KiB

September 2026 implementation notes

The original VISION.md remains the user-authored planning source. This addendum records the new explicit requirement and the boundary of the first implementation.

Confirmed addition

After one real-world week, a boss spawns and slowly destroys the world. When the boss dies, living characters may move to a new server/world. A dead character is permanently finished. Production deployment should run on Kubernetes and use a Gitea workflow compatible with Harbor and ArgoCD. The client is browser-first, with platform changes considered only after real performance measurements.

Implemented interpretation for playtesting

The deadline is seven days by default. A shrinking circular hazard represents world destruction over a configurable period. Victory grants persistent passage to eligible survivors; complete collapse kills everyone still assigned to the world. A character and its inventory/skills retain identity across successful passages. A passage is bound to its account and can be redeemed only once per successful world. Daily play usage carries forward with the character.

These choices remain provisional: 30-minute destruction duration, hazard damage, offline exposure, safe-zone behavior during the event, finite world radius, 48-unit spawn separation, and mob scaling. The current generated chunks are heightfields; volumetric terrain and terrain deformation are not implemented.

The full assessment, delivered scope, and follow-up work are documented under docs/. No 2,000-player, security-audit, or live Kubernetes deployment claim is made.