Shukhrat N.

Most Unreal projects don't fail on the fun part. They fail when the multiplayer desyncs, the save file breaks after a patch, or the build drops to 22 FPS two weeks before a deadline. That's the work I do. I'm a C++ gameplay engineer on Unreal Engine. Most of my contracts have started the same way: an existing codebase, thin documentation, and a system that needs to be understood before it can be extended without breaking what already ships. What I'm strongest at: Multiplayer — replication, client-server authority, prediction and reconciliation, dedicated servers, Steam/EOS. Desyncs are my favorite kind of bug. Gameplay systems — GAS, inventory, progression, save/load that survives a version bump. Written in C++ with clean Blueprint-facing APIs, so your designers can iterate without pulling a programmer in every time. AI — behavior trees, perception, EQS, decision logic that holds up when the player does something the designer never planned for. Performance — Unreal Insights profiling, mobile and console optimization, Lumen and Nanite in shipping builds rather than tech demos. I also handle cinematics and MetaHuman work (Sequencer, procedural animation) when a project needs it, but the code is the main thing. How I work: I ask questions before I give an estimate. If the scope is wrong, or the approach will cause problems three months from now, you'll hear it at the start instead of finding out together later. I don't need daily check-ins, and I'd rather send you a build than a status update. Based in Uzbekistan, with solid overlap on US and EU hours. Open to long-term contracts and to one-off systems work where something specific is broken.