I’m specialized in gameplay programming – meaning I focus specifically on the core mechanics of your game. This includes things like game systems, player interactions, NPCs, basic or complex AI (such as bots), and other elements that shape the actual gameplay experience.

This is the only area I offer on purpose, because it's where my expertise lies – not in graphics, level design, or animation. So if you’re looking for someone to bring your game’s mechanics to life through code, you’re in the right place.

That depends a bit on the project. In most cases, I prefer working with Unreal Engine, because it comes with a lot of built-in systems that would otherwise need to be developed manually in other engines – for example, a solid character controller, a robust movement system, networking support, or visual scripting via Blueprints.

This significantly speeds up development and helps reduce costs, since I don’t have to start from scratch or reinvent the wheel. Much like the Source Engine (which Valve used for games like Team Fortress 2 and CS:GO), Unreal already provides a strong foundation – and that makes it easier and more efficient to develop your project with less overhead and more focus on gameplay.

If your project has specific requirements, I’ll take a close look and advise you on the best technical base for your needs.

The main reason is long-term reliability and support. I don’t own or control third-party tools, so I can’t guarantee they’ll stay compatible or supported throughout your project — especially by the time you launch your game. By minimizing their use, I help reduce technical debt and avoid future headaches. It also means I can fully stand behind everything I build.

For more detailed information on liability and third-party dependencies, you can review my Terms & Conditions.

Not by default. I avoid using experimental or beta features unless you specifically agree to it. Just like with third-party tools and dependencies, these features aren’t guaranteed to be stable, supported long-term, or even available in future engine versions.

If your project really needs something that’s experimental, I’ll discuss the risks with you first so you can make an informed decision. As always with such potentially risky elements, I elaborate further on this in my Terms & Conditions.

Code work is priced based on its complexity. I start with my base day rate (for an 8-hour day) and adjust the price according to the scope and technical demands of the project.

If a milestone is estimated to take more than 8 hours — for example, 12 hours — I calculate the hourly rate by dividing the day rate by 8, then multiply by the actual estimated hours. This total becomes the fixed price for the milestone.

The final quote is always a fixed price, not hourly. It includes all work necessary to deliver results: session time, research, planning, and buffer time for unexpected challenges.

The license lets you use the work exclusively for one specific game project. That means only you get this license—no one else will be granted the same rights—and it covers the main game plus any DLCs, expansions, or updates tied to it. You’re free to modify and monetize the work within that project.

The license is perpetual (it doesn’t expire) and royalty-free—there are no renewals or ongoing payments required.

If you want to use the work in other projects—like sequels, ports, remasters, or new games—you’ll need to get a separate license and pay a reuse fee. This fee is about 10% of what you originally paid for the licensed work.

Yes, milestone payments can be split. A portion is paid upfront, and the rest is invoiced later. There’s a small surcharge to cover the extra admin and cash flow handling—usually 3%, capped at 50.00€.

Yes, I’m totally fine with working on a monthly schedule—like doing one milestone per month—if that works better for your cash flow or planning. It’s actually a pretty common setup with consumer clients.

I process payments securely through Stripe and currently support:

• Credit & debit cards

• PayPal (EU/EEA countries only; Pay Now, Buy Now, Pay Later, and installment options available)

• Digital wallets (Apple Pay, Google Pay, MobilePay)

• Klarna (Pay Now or Buy Now, Pay Later options with flexible installments)

• Alipay

• Link

• iDEAL

• Bancontact

• EPS

• TWINT

• Billie (Buy Now, Pay Later for B2B)

• Bank transfers (for invoice payments)

Upfront payment is required before any work begins. Once we've established a working relationship, I'm open to discussing invoice-based or alternative payment terms.