Quod Soler · Unreal Engine consultant · 11 shipped games in 10 years

An Unreal Engine code review where I read your code before we ever get on a call.

Blueprint and C++, reviewed by a lead who has shipped 11 games: a 90-minute recorded walkthrough of what I found, plus a findings document ranked by what it costs you to leave alone, within 48 hours.

$35090 minuteswritten findings within 48 hours
Book a 20-minute scoping call · free

Not every project is a fit. Twenty minutes finds out.

11 shipped games · 10 years, AAA and indie · 1,050+ Unreal devs read my weekly newsletter

Is this your project right now?

If you nodded at any of these, this call was built for exactly that.

How it works ( the diagnosis happens before the call )

You are not booking 90 minutes of me thinking out loud. The diagnosis is already done by the time we talk; the call is where you get it and argue with it.

Scoping call ( 20 minutes, free )

Twenty minutes for me to understand the project and the problem, and to tell you honestly whether the diagnostic is the right tool. Not every project is a fit; if yours is not, I say so on the call and point you somewhere better.

Repo access and review ( 2-3 hours of mine, before we meet )

If it is a fit, you book the diagnostic and send me access to what I need: a repo, a build, a trace capture, whatever fits the problem. Then I spend two to three hours inside your material before we ever meet. ( This is the part you are actually paying for. ) By the time the call starts I have a ranked list of findings, not a list of questions.

The walkthrough ( 90 minutes, screen-shared, recorded )

Ninety minutes, screen-shared and recorded. We do not spend them on setup, we spend them walking through what I found, in order of what it costs you to leave alone. Bring your team if you want.

Written findings ( within 48 hours )

Within 48 hours you get the findings in writing: every issue, why it matters, and the recommended fix.

What you walk away with

Book a 20-minute scoping call · free

Who this is for ( and who it is not for )

This is for you if:

  • You are mid-production in Unreal, with a real build and a real problem.
  • You are a solo dev or a small team, and there is nobody senior around to check your thinking.
  • You are a lead about to make an expensive decision and you want a second opinion that has shipped before.

This is not for you if:

  • You are in pre-production and there is no code or content to look at yet. ( Come back when there is something to diagnose. )
  • You are looking for a full-time hire or an outsourcing team.
  • You want the code written for you rather than diagnosed. That can come later, but it is not what this is.
Quod Soler

Who you would be talking to

I have shipped 11 games in ten years, on AAA and indie budgets, with teams from two people to two hundred. My home ground is combat systems, the Gameplay Ability System ( GAS ), C++ architecture and performance.

I have given lectures at Ramon Llull and Pompeu Fabra universities, and 1,050+ Unreal developers read my weekly newsletter on GAS, combat and performance. The diagnostic is that same material, applied to your game instead of the general case.

If you want to audit my judgment before paying for it, read the blog.

Read the blog·LinkedIn

Track record

Key art from a shipped AAA action RPG
Lead Gameplay Programmer · AAA action RPG
Key art from a shipped AAA action RPG sequel
Lead Gameplay Programmer · AAA action RPG ( sequel )
Key art from a shipped co-op shooter
Lead Gameplay Programmer · co-op shooter
Key art from a shipped licensed action game
Lead Gameplay Programmer · licensed action game
+ 7 more shipped titles

The alternatives, honestly

A marketplace reviewA forum threadThis diagnostic
Price$35 per 15 minutesFree$350 flat
Who reads your projectWhoever accepts the gigStrangers with 90 secondsA lead with 11 shipped games
PreparationReads what you pasteReads your screenshot2-3 hours inside your repo, before the call
What you keepA chat logA threadRecording plus ranked findings in writing
AccountabilityNoneNoneUnder 3 findings worth fixing? Refunded
When it is rightOne function, one bugLearning, general questionsA real build with a real problem

The price, and what happens after

The diagnostic is $350. That is the whole price: the preparation, the 90 minutes, the recording and the written findings. No hourly billing, no quote at the end.

The scoping call before it costs nothing, and the diagnostic gets booked only when we both think it fits.

For calibration: the optimization pass that takes two weeks and buys 3 FPS costs a team more than twenty of these calls.

Most teams stop there, and that is fine. The findings are yours to act on with or without me.

If you want me to stay involved, the next step is my advisory retainer: $2,800 per month. I join your Slack or Discord, you get unlimited questions with answers within one working day, one call a month, cancel monthly. Three seats total, on purpose, so answers stay fast.

If you move to the retainer, the $350 comes off your first month. So the diagnostic ends up costing nothing.

What $350 includes

  • The 2-3 hours of preparation inside your project
  • The 90 minutes, screen-shared and recorded
  • The ranked findings document, within 48 hours
  • My preparation notes, dead ends included
  • The evidence behind each finding

Your side's total effort: a 20-minute call, then about fifteen minutes of intake.

The guarantee ( a falsifiable one )

If the diagnostic does not surface at least three issues you agree are worth fixing, I refund it. Not three observations, three findings worth your team's time.

I can offer this because in ten years I have not yet opened a production Unreal project that did not have at least three ( including the ones I wrote ).

Book a 20-minute scoping call · free

Questions people ask before booking

I can get a code review on a marketplace for a fraction of $350. Why pay this?

You can, and for one function or one bug those reviews are fine. What they can not give you is a senior lead spending hours inside your actual codebase before the call. A marketplace review is "looks fine to me" on the file you pasted. This is a ranked list of what will cost you money, with evidence next to each item. Fewer than three issues worth fixing, and you get a refund.

What if you look at my project and can not help?

If I open your material and see that I am not the right person for it ( wrong engine area, wrong kind of problem ), I cancel the call and refund you in full before we ever meet. You lose a few days, not $350.

Will you sign an NDA?

Yes, before you send me anything. Discretion runs both ways: nothing from one project ever crosses into another. If your project conflicts with work I am already committed to, I will tell you at booking, not after you have paid.

We can not share our repo. Can you still do this?

Usually yes. The repo is the best input, but a packaged build, a trace capture, or screen-sharing the project live during the call all work, they just move some of the diagnosis into the call itself. Tell me what you can share and I will tell you honestly what depth to expect.

What about timezone and language?

I am in Barcelona ( CET / CEST ). Afternoon slots here line up fine with mornings in the US. The call can be in English, Spanish or Catalan; the written findings are in English unless you ask otherwise.

How does the invoice work?

You pay at booking and you get a proper invoice from a registered business in Spain. For clients outside the EU ( including the US ) there is no European VAT on top: $350 is the whole price. EU businesses with a VAT number usually fall under reverse charge, and Spanish clients have IVA added on the invoice. ( I am not your tax advisor, but your accountant will recognize the invoice. )

What if I want ongoing help afterwards?

That is the retainer: $2,800 per month, unlimited questions in your Slack or Discord with answers within one working day, one call a month, cancel monthly. The $350 you paid for the diagnostic comes off your first month.

Which engine versions do you cover?

Most of my current work is UE5, and I have shipped on UE4. Most of what a diagnostic surfaces ( architecture, GAS usage, tick discipline, reference chains, frame cost ) reads the same in both. On a heavily modified engine or something older, say so in the booking form and I will tell you honestly before we start.

One problem. Ninety minutes. Findings in writing.

You already know which problem you would bring. Tell me enough to make the call useful, pick a time, and in twenty minutes we will know whether the diagnostic is the right tool for it.

About a minute. The scheduling link opens right after.

Prefer email? Write to quodsoler@gmail.com and describe the problem.

Not ready to book? I write Combat Architecture, one email a week on how combat systems get built in Unreal Engine. 1,050+ Unreal devs read it.Join Combat Architecture →

Book a 20-minute scoping call · free