Planetary Assault

Overview

Planetary Assault is a planned 1v1 PvP “versus tower-defense” prototype designed to demonstrate authoritative netcode and a full-stack backend. Two players attack each other’s planets using units and defenses, with matches orchestrated by a Nakama backend and simulated on an authoritative FishNet server instance. The project exists to show end-to-end multiplayer and backend skills rather than to ship as a commercial title.

My Role

Solo developer (design, Unity client, authoritative server, and backend integration).

Key Contributions

(Planned / in progress)

  • Design an authoritative FishNet-based server responsible for the full match simulation (units, projectiles, planet health) while clients send only inputs/commands.
  • Implement a Unity client that connects to dedicated match servers, handles prediction where needed, and renders a clean, readable battlefield for 1v1 play.
  • Integrate with a Nakama + Postgres backend for authentication, matchmaking, player profiles, and basic stats (MMR, wins/losses).
  • Build an end-to-end flow: login → queue → match assignment → connect to match server → play → report result back to Nakama → update profile.
  • Provide dockerized backend infrastructure (Nakama + Postgres) and clear local dev environment for running the full stack.

Tech Stack

  • Unity
  • C#
  • FishNet (authoritative netcode)
  • Nakama backend
  • Postgres (player data and match stats)
  • Docker / docker-compose for backend dev environment

Why This Example Matters

  • Designed to demonstrate practical experience with authoritative multiplayer networking for real-time PvP.
  • Shows ability to integrate a game client with a modern backend stack (auth, matchmaking, persistence) rather than relying on ad-hoc services.
  • Reinforces full-stack thinking: data model, protocols, match lifecycle, dev environment, and operations.

How to Play

Planetary Assault is currently in the design/prototype phase. Once a stable prototype exists, I will provide a downloadable build and technical writeup showing the client–server–backend interaction.

Links

  • Design and technical details will be added here as the prototype progresses.