Back to the cards

A community game server

Live ops: a game that was shut down

My part
Systems and operations lead
When
Sep 2026 to now
Made with
C# (ASP.NET Core), Photon, PostgreSQL, Docker Compose
A cartoon raccoon peeks over the top of a grey server that has a plaster stuck on one corner and green lights on. A cable runs from the server to a phone showing a red heart.

What it is

A mobile game was shut down, and a community of its players brought it back. I’m the systems and operations lead, so I run the servers day to day.

In one week the servers handled 76 players, 1,435 sessions and 831 matches, with no server errors.

Fixing a client without its source code

The community doesn’t have the source code for the original game client, so when the client crashes I can’t fix it directly. I debug the crash from the outside to work out what the client was doing, and in many cases I can fix it from the server side by changing what the server sends.

What else I look after

  • A server-side update gate, which keeps broken client builds away from players.
  • Balance changes. I lead a volunteer balance team, and I sign off every change before it goes live.

The servers are written in C# on ASP.NET Core with Photon and PostgreSQL, and they run on Docker Compose.