The system problem
A strategy game has to feel simple at the surface while keeping turn state, economy, movement, combat, timeouts and multiplayer ownership internally exact. Online play cannot trust the client to decide what is legal.
Independent game project · Unity + backend
Vorgar: Fields of War
Accessible strategy, backed by serious systems engineering.
A mobile turn-based strategy game built around hex territory control, readable combat, light economy and online play shaped by backend authority.
Visit Vorgames ↗Unity 6client
Hexterritory system
PvPonline priority
3time presets
Clarity through structure
Vorgar separates visual presentation from deterministic rules and authoritative orchestration. Unity owns the tactile map and interaction layer, shared libraries own portable contracts and rules, and the backend validates every online action.
What this work demonstrates
Product depth across the stack.
01Unity scene and responsive UI systems
02Hex map and territory rules
03Deterministic gameplay logic
04Authoritative multiplayer backend
05Save, timing and inactive-player flows
06Build and mobile release discipline
Engineering shape
Deliberate boundaries.
One coherent product.
Unity client
Scenes, prefabs, input, rendering, local orchestration and landscape-first mobile UI live in a focused client surface.
Shared contracts
Portable DTOs and enums cross the Unity/API boundary without leaking engine, database or web dependencies.
Shared game logic
Movement, economy, combat and validation rules stay deterministic so local previews and server decisions can align.
Authoritative backend
ASP.NET Core, persistence and online orchestration own identity, lobby state, turns, timeouts and command legality.
Vorgar: Fields of War is under active development. The portfolio presents current project direction and real project assets without suggesting that unfinished systems are already released.