Gold Village
My role: 3D web frontend and game backend
A browser game where players build and upgrade buildings on a hex-tile 3D map, collect resources, complete tasks, visit friends and advance through video lessons and quizzes. It is designed to run embedded in a partner app. I worked on the 3D web frontend and the game backend; the content admin panel was built separately.
- React
- React Three Fiber
- three.js
- Zustand
- NestJS
- TypeORM
- PostgreSQL
- Redis
Highlights
- StagePilot, built at Findie Studios (Fame Yazılım games brand)
- FrontendReact 19 + React Three Fiber 9, ~18k lines of JSX/JS in 161 files
- BackendNestJS 10 · 9 modules · 15 PostgreSQL tables · Redis sessions
- Tests8 service-level Jest spec files on the backend
3D Frontend
The client renders the village with React Three Fiber and drei inside a single Canvas, with a rapier physics provider at the root. The map is a hex grid generated row by row (radius 7) from lot data, and the same world component renders either the player's own village or a friend's during a visit. Buildings (farm, mine, sawmill, foundry, market) are separate components, with worker characters animated per building.
Terrain textures can switch by season through a persisted settings store. The 2D layer on top (HUD, drawers, modals, education and task pages) is Tailwind-styled React.
Client State and API Layer
State lives in Zustand stores, split into slices for buildings, economy and navigation plus separate stores for auth, tasks, education, social and tutorial; the auth store is persisted. An axios client adds the bearer token to each request and reacts to 401 and connection errors, and a service module per domain (village, building, economy, task, education, social) keeps components away from raw HTTP.
Code is organised by feature (buildings, education, social, tasks, tutorial, village) rather than by file type.
Game Backend
The NestJS API is split into nine modules: auth, user, village, building, economy, task, education, social and health. Entities are mapped with TypeORM onto a PostgreSQL schema of 15 tables, and requests are validated with a whitelisting ValidationPipe. JWT sessions are mirrored in Redis with a 30-minute TTL.
Production is computed on the server from building level and per-type curves (rate = base × gamma^level, plus a capacity curve). Harvesting and upgrades run inside a database transaction and write to an append-only transactions table that stores the balance after each change.
Skills Demonstrated
| Skill Area | Evidence in Project |
|---|---|
| React Three Fiber / three.js | Hex-tile village scene, camera rig, terrain, animated workers |
| React state design | Zustand slices and stores, feature-based folders, service layer |
| NestJS | Nine modules, guards, JWT strategy, DTO validation |
| PostgreSQL / TypeORM / Redis | 15-table schema, transactional harvest and upgrade, Redis sessions |
| Backend testing | Jest specs for eight services (auth, building, economy, task and more) |
Want to discuss this project or work together?
Get in touch