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-09 23:53:53 -04:00
parent 3435c69c88
commit faaef0a7d5
1 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
_notes/resonance.md
View File

@@ -1,6 +1,5 @@
--- ---
categories: "- '[[Projects]]'" categories: "- '[[Projects]]'\n- '[[Website pages]]'"
related: ""
title: Resonance title: Resonance
--- ---
@@ -12,10 +11,8 @@ The project was also part of the [[Chapman University]] game development capston
My core role was to implement the game’s networking logic using PurrNet, an open-source library for Unity. My core role was to implement the game’s networking logic using PurrNet, an open-source library for Unity.
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. The networked API for Arena is used by every aspect of the game, including the scoreboard UI and spotlight mechanic. Following a pivot in the game’s core direction, I successfully handed this system to another engineer, who implemented a rating system for style points. 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. With the help of Claude, I created a two-step system: an editor script to build and configure dependencies in one step, and a nightly GitHub Actions pipeline. Besides simplifying the build process, this created another positive side effect by ensuring we fixed compiler issues proactively. 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.
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.