Combat Architecture · Weekly newsletter
Every Saturday I take one system from my combat framework ( hitboxes, i-frames, input buffering… ) and explain how it works, with the code. I'm a lead gameplay programmer with 11 shipped games.
1,150+Unreal devs get it every week
Free · One email a week · Four minutes to read · Unsubscribe anytime
The newsletter follows my Quod Combat Framework, the melee combat I build on top of the Gameplay Ability System ( GAS ). 8 of 8 are out.

The hitbox: a capsule on a bone
The windows: i-frames, walk cancel, branch on hit
The numbers: hitstop, damage, knockback
Subscribers get each one the week it comes out.
Eleven shipped games, AAA and indie, most of them action games.
It's the short version of that week's post, always in the same order. Take the input buffering one.
A press that went nowhere because the player was a few frames early, and the playtest note that says the combat feels unresponsive.
The pieces, and why each one is there. For the buffer that is a struct, a gate tag, two anim notify windows and one drain function.
What changes once real players get it. In this case, hitstop stretching how long a buffered press stays valid.
On the blog, with all the code, linked at the end. Read the email on the phone and the post with the editor open.
It's for people building melee or action combat in UE5, mostly with GAS.
I'm the Lead Gameplay Programmer for Lords of the Fallen at Hexworks. I love action games and combat design, and I specialize in Unreal's Gameplay Ability System ( GAS ).
I've spent a decade shipping games with teams from two people to two hundred, and I have given lectures at Ramon Llull and Pompeu Fabra universities. In the newsletter I write down what I learn in AAA production.
Free · One email a week · Four minutes to read · Unsubscribe anytime
It helps, but it isn't required. Everything in the framework assumes the Gameplay Ability System, because that's how I build combat on shipped games, and the first issue explains the six pieces it is made of. If you've never touched GAS, start there and the rest will make sense.
Read: Introduction to GAS (opens in a new tab)Both. Every system is explained in prose first, and the code is C++ written for the post, with Blueprint where Blueprint is the right tool ( anim notifies, montages, behavior trees… ). If you only use Blueprint you still get the architecture, and that is the part that's hard to find.
Both, the systems don't care. Some readers build alone, others work in small teams and studios. I write for whoever has to make the combat work.
No. I never publish studio internals. The newsletter follows my own Quod Combat Framework, and the code in every issue is written for the post. What carries over is the experience, mostly the bugs that only show up once real players get their hands on the game.
One email a week, about four minutes to read, free. Every email has an unsubscribe link at the bottom.
You get one email to confirm your address ( the newsletter runs on beehiiv ), one click and you're in. That click takes you to the issues I'd start with, and the next system comes with the next issue, Saturday morning for now.
Yes, same list, same author. I renamed it Combat Architecture in August 2026 because almost every issue was a combat system anyway. If you were already subscribed you still are, no need to sign up again.
One system a week, with the code and the gotcha that tends to show up later in a bug report.
Free · One email a week · Four minutes to read · Unsubscribe anytime
1,150+Unreal devs get it every week