Quod Soler

Combat Architecture · Weekly newsletter

How combat systems get built in Unreal Engine.

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

Shipped withHexworksNovaramaSonyTencentCI GamesAdult Swim

The series so far.

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 Quod Data Editor with a dragon mid breath attack: the attack hitbox drawn as a red capsule at its mouth, timeline lanes for i-frames, walk cancel and branch on hit under the viewport, and the attack's data fields on the right.

The hitbox: a capsule on a bone

The windows: i-frames, walk cancel, branch on hit

The numbers: hitstop, damage, knockback

A breath attack open in my data editor: the hitbox shape, its windows and its numbers.
GASThe six pieces of GASThe map first: ASC, abilities, effects, attributes, tags and cues, and one attack going through all of them.Out · Jul 17
HitboxesHitbox rank and group: sweetspots without scriptingCapsules between two sockets, plus a rank and a group ID on every hit.Out · Jul 25
DodgeDodge i-frames: anim notify windows and perfect dodgesWhere the invulnerability window lives, and the perfect dodge that comes with it.Out · Jul 31
DamageMMCs or executions: which one your damage needsWhen one MMC is enough, and when a hit has to write several attributes at once.Out · Aug 8
InputSouls-style input buffering on top of GASThe press that came a few frames early, kept until the next window opens.Out · Aug 15
Enemy AIHow enemies decide to dodgeA dodge chance attribute, a pressure effect on top and a dice roll in the behavior tree.Out · Aug 22
ReplicationPlaying montages through the ASC in coopWhy Montage_Play only plays on your own screen, and what the ASC does about it.Out · Aug 29
MovementDashes and knockbacks with Root Motion SourcesMovement built from plain numbers, with no root motion in the clip.Out · Sep 5

Subscribers get each one the week it comes out.

You've probably played something I helped build.

Eleven shipped games, AAA and indie, most of them action games.

Four parts, about four minutes.

It's the short version of that week's post, always in the same order. Take the input buffering one.

It starts with the player

A press that went nowhere because the player was a few frames early, and the playtest note that says the combat feels unresponsive.

Then the pattern I use

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.

Then production

What changes once real players get it. In this case, hitstop stretching how long a buffered press stays valid.

Then the full post

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.

Quod Soler

Hi, I'm Quod.

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.

Join 1,150+ Unreal devs.

Free · One email a week · Four minutes to read · Unsubscribe anytime

Read the past issues.

Questions

Do I need to know GAS already?

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)

Blueprint or C++?

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.

Is this for solo developers or for studios?

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.

Is this the code from the games you shipped?

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.

How often, how long, and how do I leave?

One email a week, about four minutes to read, free. Every email has an unsubscribe link at the bottom.

What happens when I subscribe?

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.

Is this the same newsletter as Unreal Solo Game Developer?

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.

See you on Saturday?

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