Expertise 03 / Multiplayer & Reliability

Networked gameplay that survives real production

I design multiplayer as a set of explicit simulation, ownership, communication, recovery, and presentation responsibilities—not as networking added around gameplay after the fact.

01 / Scope

More than packets
The complete online game flow

Simulation authority

Define server-only, client-only, and shared logic; separate tick simulation from presentation; make authoritative outcomes and replay responsibilities explicit.

Responsive interaction

Work with movement prediction, input latency and precision, synchronization, local feedback, and consistency under real network conditions.

Recovery and continuity

Design initialization, reload, reconnect, offline behavior, and failure boundaries as lifecycle concerns rather than exceptional patches.

02 / Evidence

Network architecture
across different game models

Pixel Gun 2 / Photon Fusion

Authoritative voxel FPS

  • Designed controllable CoreGame tick and presentation-frame pipelines.
  • Made server-only, client-only, and shared-simulation boundaries explicit.
  • Optimized general gameplay and voxel-destruction synchronization.
  • Refined movement prediction and corrected input-latency and input-precision issues.
  • Designed load, reload, reconnect, host, and client startup flows around the whole game lifecycle.

Combat Master / Photon Bolt

Battle Royale gameplay systems

  • Developed gameplay and networking systems for an online multiplayer FPS.
  • Implemented networked moving platforms and a train, alongside vehicle systems.
  • Built player-facing systems including rebindable gamepad input and perks within an existing live-product architecture.
  • Later supported architecture and scalable-backend decisions through periodic consulting.

D.A.W.Studio / Unity Transport

Two online sniper games

  • Designed a custom networking layer over Unity Transport.
  • Connected ASP.NET Core metagame services over HTTP with UDP battle servers.
  • Built the CoreGame foundation around movement, weapon fire, ballistics, controllable bullet-sprites, and network synchronization.
  • Supported online and offline operation with seamless reconnect.

Wargaming / REVOLT

Fault-tolerant simultaneous turns

  • Built a universal client/server command-processing flow.
  • Players submitted actions independently; the server resolved unit priority, buffs, and debuffs.
  • Both clients replayed the same authoritative result simultaneously.
  • Eliminated recurring integration and reliability failures that had consumed weeks of development.

Earlier client/server work

Protocol, racing, and hidden object

  • At GoGames, designed the communication protocol, developed the C# server, and supported the Flash client for World of Fishing.
  • At West-Games, built Seaker's client/server functionality using Unity Legacy Networking.
  • At Plarium, implemented synchronization for the mobile racing game Motorplanet.

Reliability outcome

Failure can be a normal state

The metagame and battle architecture created at D.A.W.Studio supported offline work and seamless reconnect. The same resilience model was later adopted independently by Combat Master.

During a prolonged backend outage, players were able to continue playing without noticing that the services were unavailable—a strong demonstration that recovery behavior had become part of the product flow.

03 / Design model

Make responsibilities
visible in the code

  • Lifecycle first: startup, connection, authentication, session entry, gameplay, reload, reconnect, exit, and shutdown are one design problem.
  • Simulation and presentation: authoritative state progression should be controllable and independent from the visual frame.
  • Explicit ownership: code should state whether it belongs to the server, client, or shared deterministic/simulation path.
  • Fault containment: a service or subsystem failure should not automatically corrupt unrelated game state.
  • Fast local iteration: developers should be able to start a host and client directly from a map, not reproduce the entire production navigation path.

04 / Technology

Networking technologies
used in production work

The choice of library is secondary to the structure around it. My work has covered several generations of Unity networking and multiple product models; the durable expertise is in simulation boundaries, lifecycle, responsiveness, and failure behavior.