How ill-inc/biomes-game works
Project type and purpose
• Biomes is a full-stack, web-based sandbox MMORPG. It combines a Next.js/React frontend, WebAssembly game engine modules (C++/Rust → WASM via Bazel), and a polyglot, distributed backend written in TypeScript/Node.js (dozens of microservices) plus shared C++ libraries (“voxeloo”).
• It’s deployed on Kubernetes (see deploy/k8/) and uses Redis, Firestore, SQL and Cloud Storage for persistence.
File structure
• Top‐level “src/client” and “src/pages” → Next.js React frontend (SPA + SSR + API routes).
• “src/server/web” → standalone Node.js/Express app backing web UI and admin REST endpoints.
• “src/server/…” (anima, chat, gaia_v2, logic, map, sync, spawn, etc.) → ~16 specialized backend services, each compiled from TS, tied together via zrpc/gRPC, Redis pub/sub and service discovery (“server/shared/discovery”).
• “server/shared” → cross‐cutting libraries (auth, config, cache, storage, zrpc, pubsub, tasks).
• “src/shared” → client + server shared TypeScript libraries (data models, ECS, game logic, C++→WASM bindings).
• “voxeloo” → core C++ modules for terrain, biomes, galois, WebAssembly extensions.
• “deploy/k8” → Kubernetes manifests for each component.
README
• Confirms Next.js/TypeScript/WebAssembly/React stack.
• Mentions distributed architecture that can also run locally.
• Documentation points to running dozens of services locally via Bazel and devcontainer.