Found this by reproducing locally (installed a Go toolchain + helm earlier in this session; this time added Chromium anti-throttling flags and instrumented walkTo/pendingAction/keys onto window.__aeternalis to watch it live) rather than guessing from CI logs again: the "Target Harbinger" button sets pendingAction/walkTo directly, bypassing action() entirely -- so the give-up budget from the last commit, which only got initialized inside action(), read Date.now() against its initial value of 0 on the very first tick after clicking. That's always "expired" by billions of milliseconds, so it gave up on "boss" immediately, blacklisted it, and reselected the nearest sentinel mob instead -- explaining every "boss out of reach" / zero-progress boss failure we've chased across the last several rounds. Confirmed via a throwaway diagnostic test logging position/target every second: the character walked calmly away from the boss it started standing on top of, chasing first one sentinel then another. Fixed the immediate bug (also set the budget's clock in the button's handler), then found a second one the same repro immediately exposed: attack against a live target is *mostly* cooldown rejections between the hits that land, so "no progress since the initial click" was still wrong -- it gave up mid-fight after ~10 successful hits during a lull. Replaced the give-up condition with an actual progress signal (target HP for attack, held-item count for gather/loot); it now only gives up once that has genuinely stopped moving, confirmed via the same diagnostic: 10 clean hits (1200 -> 1020 HP) holding position, matching the server's own attack cooldown. Also added the standard Chromium flags (--disable-background-timer-throttling etc.) to the test browser launch: the CI logs' 2-11s gaps between retries (instead of the intended ~0.3s) are the classic signature of requestAnimationFrame throttling down to ~1Hz for a backgrounded/occluded headless tab, which independently made every frame-driven client action crawl. Left walkTo/pendingAction/keys exposed on window.__aeternalis since they were useful for this and will be again. Verified: tsc/build clean, and three full local e2e runs (7/7 each) all show the boss test landing clean periodic hits via "attack cooldown" rejections between them, never wandering to a mob. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Aeternalis
A playable browser survival RPG foundation: an authoritative Go world server, Three.js terrain and GLB models, persistent one-life characters, and weekly worlds.
Status: local prototype, not a production MMO or a verified 2,000-player server.
The review, architecture, deployment instructions, and remaining work are in
docs/ARCHITECTURE.md, docs/DEPLOYMENT.md, and docs/ROADMAP.md.
Run locally
Requirements: Node.js 24 and Go 1.26+ (tested with Go 1.27.1).
On Windows without Go, powershell -File tools/bootstrap-go.ps1 downloads a
checksum-verified, project-local toolchain.
npm ci
npm run build
node tools/dev-server.mjs
Open http://127.0.0.1:18080. Guest authentication is available only in development, on an explicit loopback listen address. Production fails closed without PostgreSQL and an HTTPS OIDC configuration.
The delivered Windows build can also be started without installing Go:
powershell -File tools/start-local.ps1 -UseExisting
That command starts a hidden background process and prints its PID. Stop your
specific local process with Stop-Process -Id <printed-pid>. Local state lives in
.local/aeternalis.db; restarting preserves characters, world age, and death.
Deleting this development database is an explicit reset, not part of startup.
Play
- Move with WASD/arrows, click the terrain, or use touch direction controls.
- Click resources/enemies to approach and gather/attack. The toolbar also chooses the nearest suitable target. E gathers, Space attacks, I opens inventory.
- Gather wood, ore, and herbs. Craft a spear or bandages in inventory.
- The Harbinger appears after seven days. In loopback development, Display settings includes Awaken Harbinger for testing the event immediately.
- During the boss event the safe world radius shrinks toward the center. The boundary deals damage; complete collapse kills remaining characters, including offline and daily-capped characters. Killing the boss freezes survivor eligibility.
- Survivors sign into a different configured world with the same identity, then choose Continue as .... An atomic passage redemption preserves identity, inventory, skills, kills, and daily play-time usage.
PvP, damage-priority corpse looting, body-part damage, full skills/stats, leaderboards, and an admin center are not implemented. Corpse looting currently has no priority lock because PvP is not enabled.
Multiple local worlds
Start independent worlds against the same SQLite database. Every process needs a unique world ID and port. A completed world ID must never be recycled for a new season. Seeds and balance are stored when a world is first created.
$env:WORLD_DIRECTORY = '[{"id":"world-001","url":"http://127.0.0.1:18080"},{"id":"world-002","url":"http://127.0.0.1:18081"}]'
powershell -File tools/start-local.ps1 -WorldId world-001 -Port 18080
powershell -File tools/start-local.ps1 -WorldId world-002 -Port 18081 -Seed 829312
Loopback cookies are shared across these two ports, so the same local guest can redeem a passage. Production worlds use OIDC issuer + subject for stable identity and separate secure host cookies. Never use dev identity for public servers.
Validate
npm run test:contracts
npm run check
npm run build
# In server/:
go test ./...
go vet ./...
# At the repository root:
npx playwright install chromium
npm run test:e2e
helm lint deploy/chart
helm template aeternalis deploy/chart
When Go is local, use .tools/go/bin/go.exe from the root or
../.tools/go/bin/go.exe from server/. Go tests use a temporary SQLite database.
Set TEST_DATABASE_URL to an expendable PostgreSQL test database to run the same
storage suite on PostgreSQL; CI provides one. Linux CI also runs go test -race.
The browser suite starts and stops its own server on port 18089 with a fresh DB.
On Windows, PLAYWRIGHT_CHANNEL=msedge can use installed Edge without downloading
Chromium. Screenshots and traces are written to test-results/.
For client hot reload, run the server with PUBLIC_URL=http://127.0.0.1:5175,
then run npm run dev and open port 5175. Origin checking intentionally rejects
requests from other origins.
Layout
| Path | Responsibility |
|---|---|
planning/VISION.md |
Original user vision; new boss rule in IMPLEMENTATION-NOTES.md |
server/internal/game |
Terrain, authoritative simulation, lifecycle |
server/internal/store |
World ownership, snapshots, sessions, atomic passages |
server/internal/transport |
HTTP, OIDC, origin checks, WebSocket intent validation |
schemas/protocol.json |
Generated Go/TypeScript wire contracts |
server/content/balance.yaml |
Validated balance and recipe data |
client/ |
Full-screen browser game and mobile controls |
tools/create-models.py |
Original temporary Blender models |
deploy/chart/ |
Five independent world deployments, services, TLS ingress |
.gitea/workflows/build.yaml |
Tests, Harbor image publication, optional GitOps promotion |