TERAGO ONLINE

A real-time multiplayer 2D fantasy MMORPG that runs in a desktop web browser. Full design: SPEC.md. Current build status: docs/PROGRESS.md. Build log/decisions: docs/DECISIONS.md. Module layout and protocol: docs/ARCHITECTURE.md.

Setup

npm install

Note for this dev sandbox: if npm install fails with ENOTFOUND registry.npmjs.org, the environment's proxy config is excluding the registry from the proxy it actually needs. Run instead:

npm_config_noproxy="" NO_PROXY="" no_proxy="" npm install

Running

npm run dev

Starts the game server (WebSocket, fixed 20 Hz tick) and the client (Vite + Phaser) together. The client opens on http://localhost:5173; the server listens on ws://localhost:8080.

Dev commands

• npm test — Vitest unit tests (shared formulas, server systems)
• npm run test:e2e — Playwright smoke tests: e2e/two-player.spec.ts (two browser contexts register, see each other, move via both click-to-move and WASD, and see a live equipment change) and e2e/system-menu.spec.ts (Esc opens the system menu, Replay Intro actually hides the HUD and shows the intro, skipping it returns cleanly to World). Starts npm run dev itself if it isn't already running. Needs npx playwright install chromium once if no compatible browser build is present locally.
• npm run typecheck — TypeScript, no emit, across all three workspaces
• npm run build — production build of server + client

In dev mode (TERAGO_DEV_TOOLS=1), the server accepts dev:command messages like /level 50, /give potion_hp_small 10, /tp map2, /spawn slime, /boss gatekeeper (see SPEC.md §2, server/src/devtools/commands.ts). The client does not yet translate a /-prefixed chat message into one of these (a known gap - chat:send is always sent and treated as literal chat, never sniffed for a leading /; see docs/DECISIONS.md), so for now these are reachable only by sending the raw WebSocket message yourself (e.g. from devtools' console, or a small script) - not by typing into the in-game chat box.

Replacing placeholder art

No final art exists yet. Every sprite, tile, and sound is generated procedurally and referenced through client/src/assets/manifest.json. To swap in real art: drop the file in client/src/assets/, point the matching manifest entry at it, and the generator is skipped for that key automatically. No code changes needed.

Project structure

shared/   Types, zod schemas, formulas, data config — consumed as TS source by both apps
server/   Node + ws game server, SQLite persistence, server-authoritative simulation
client/   Vite + Phaser game client, DOM overlay UI
docs/     Architecture, progress, decisions