brendan/brendan-ch.github.io
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Publish: Resonance

Browse Source
This commit is contained in:
Brendan Chen
2026-08-31 15:19:00 -07:00
parent b95406e2d2
commit 24bf54e273
1 changed files with 2 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
_notes/resonance.md
View File

@@ -1,6 +1,4 @@
--- ---
categories: "- '[[Projects]]'"
related: ""
title: Resonance title: Resonance
--- ---
@@ -14,8 +12,6 @@ My core role was to implement the game’s networking logic using [[PurrNet]], a
My first project was to implement networking for **Arena**, a free-for-all PVP game mode, where the player with the most eliminations wins. I learned how to isolate game logic on the server and synchronize state on each client. My first project was to implement networking for **Arena**, a free-for-all PVP game mode, where the player with the most eliminations wins. I learned how to isolate game logic on the server and synchronize state on each client.
Another project was the **build system**. Having a server dependency and Steam integration meant that the environment differed from development to production. We found it painful to prepare a build for each class-mandated playtest. I used Claude to create a two-step system including an editor script and a GitHub Actions pipeline. Another project was the **build system**. Having a server dependency and Steam integration meant that the environment differed from development to production. We found it painful to prepare a build for each class-mandated playtest. I used Claude to create a two-step build process using GitHub Actions.
I’m currently working on a client-side prediction model to match other FPS games on the market. I’m currently working on a client-side prediction model to match other FPS games on the market. I'm also working on some [[Game server orchestration]] to help manage dedicated server instances for a future game launch on Steam.
Even with our team size, the most important thing I learned was how to manage scope and scale. Each one of us pushed ourselves to the limits of our knowledge, going from bare theoretical understanding to practical working implementations. The goal was never to get things right on the first try; it was to learn and realize new ideas in multiple passes.