Every engagement is under mutual NDA — names redacted, outcomes verifiable. Four representative files below.
Problem. A 3-person team built combat on character classes — no GAS, no replication strategy. Worked solo, broke at 2+ players. 10 weeks to Early Access.
Solution. Full GAS migration: ASC setup, 20+ abilities, attribute sets, multiplayer replication with prediction. Documentation and live test environment included.
20+ abilities live · zero ability desync post-QA
Problem. Stuck in prototype hell for four months. No clear data model. No working save pipeline.
Solution. Modular inventory with equipment slots, loot tables, and a progression pipeline integrated with GAS attribute sets. Delivered foundation in 6 weeks.
Project unblocked · MVP shipped on schedule
Problem. Critical publisher demo in 3 weeks. No server authority — abilities fired client-side, damage unvalidated, desyncs every few minutes.
Solution. Rebuilt GAS pipeline as server-authoritative with client prediction. Latency compensation, rollback handling, clean separation. Demo shipped on time.
Zero gameplay-critical desyncs · publisher demo successful
Problem. Unmaintainable codebase. 30+ hrs/week lost to bug chasing. Heavy tick functions, Blueprint spaghetti calling C++ out of order. Performance degrading per feature.
Solution. Full Unreal Insights profiling pass, architectural review doc, prioritized refactor plan, and hotfix implementation. 3,000+ lines of dead code removed.
~40% tick perf improvement · team back to shipping
Delivered early, flagged issues before I even noticed them. Easily the best contractor I've hired for UE5 work.
GAS was a black box to us. He built the whole system and made sure our team actually understood it. Saved us months.
Private contract engagements only. All work NDA-protected, fully documented, handed off clean. No public portfolio, no shared codebases, no exceptions.
Full architecture of the Gameplay Ability System — built right the first time. Attribute sets, gameplay effects, ability blueprints, cues, and tag taxonomies designed around your game.
Melee, ranged, and ability-based combat frameworks built on GAS. Feels good to play, holds up in production. Hit detection, damage pipelines, team management, and visual feedback via Cues — all properly replicated.
End-to-end gameplay features: inventory, questing, dialogue, crafting, progression. Modular C++ core, fully documented and Blueprint-friendly for your team to extend without touching internals.
Strategy, not just code. Architect scalable systems before a line is written — or audit what you already have. Prevents costly refactors that kill momentum six months in. Deliverable: a prioritized fix plan your team can act on.
Production-ready Gameplay Ability System foundation — attribute sets, default abilities, gameplay effects, cues, and replication wired correctly from day one. The boilerplate done right, so your team builds on solid ground.
Modular weapon framework on GAS — hitscan, projectile, and melee from one base. Fire modes, ammo, reload, recoil, and damage pipelines fully replicated with prediction. Drop-in new weapons via data assets, no engineer required.
This is a deliberate focus — not a gap. It's why the code work is fast, clean, and shipped on schedule. If you need art-side talent, tell me or bring your own team.
A clear, low-friction sequence designed around busy studios and fast-moving projects.
Talk through scope, technical requirements, timeline, and budget. I ask the right questions and give a straight answer on whether it's a fit. No sales pitch.
If the call surfaces open questions, send the project over — I spend a day in it and come back with the issues I found and concrete optimization tips. No cost, no obligation.
A written proposal with deliverables, milestones, timeline, and fixed or hourly rate. No vague estimates. You know exactly what you're getting and when.
Async-first, with progress updates at each milestone. You get working builds to test, not just commits. Blockers flagged early, scope changes handled cleanly.
Full documentation, code walkthrough, and a 2-week post-handoff window for questions and minor adjustments. Your team inherits clean systems — not a black box.
Public technical write-ups from real production audits — the clearest signal of how I think about UE5 systems, with nothing under NDA.
Three real audit findings — per-tick ASC tag queries, replication spam, redundant traces — and the targeted helpers that fixed them.
Read the audit →How redundant attribute captures compound across simultaneous effects — and the frame-scoped pattern that pulls the overhead back down.
Read the audit →Moving off the default driver onto a spatialized Replication Graph — grid nodes, dormancy, and a per-connection always-relevant split.
Read the audit →Five ways to engage — anchors below, final scope and rate set on the discovery call. Mutual NDA available before any detail is shared.
Right fit: private studios needing a system owned end-to-end · publishers pre-milestone · indie teams stuck on GAS or multiplayer · senior sub-contract partners.
A private call to discuss scope, timeline, and fit. NDA can be signed before the call if needed. No recordings, no third parties.
Book a call →Outline scope, timeline, and budget range. All incoming briefs treated as confidential. NDA available on request before details are shared.
Email the studio →Hourly and fixed-project pricing both available. Final rate depends on scope and complexity — discussed during the discovery call. No surprises.
Yes, always. Most of my work is confidential by default. Client IP handled with full discretion — zero IP disputes to date.
IST (UTC+5:30), with overlap calls scheduled for US, EU, and AU teams. Communication is never a bottleneck.
Yes. I ramp into existing projects quickly — a short codebase review call sets the baseline. Usually productive within the first few days.
Milestone-based for fixed projects: deposit upfront, then payments tied to defined deliverables. Hourly work billed weekly. Full transparency.
Yes. Hands-on experience with Lyra — GAS integration, weapon systems, input configs, modular gameplay features built on top.
A 2-week support window is included post-delivery for bug fixes and minor adjustments. Larger scope changes are scoped and priced separately.
Absolutely — some of my best work has been with 1–3 person teams. Light comms, documented everything, your team continues independently.
