Milestones are clearly defined deliverables or outcomes as part of a project. A “project” can be anything - for example, a custom AI system, a gameplay feature, or a technical tool. This “project” will then be split into multiple milestones, each representing a concrete step toward completion.

I take full responsibility for each milestone’s implementation, including planning, coding, and testing, so you don’t need to provide technical direction – the work is fully handled on my end.

Each milestone has a fixed scope and a fixed price. While a milestone is typically equivalent to roughly one focused development day (8 hours), it is not billed as a daily rate and not tied to a calendar schedule. This is backed by a formal work contract (Werkvertrag), so the price is tied to the deliverable, not the hours worked. Milestones are scheduled flexibly based on scope, availability, and project needs. Workshops operate the same way, with the schedule being flexible and not tied to consecutive days.

Once a milestone is agreed upon, the price stays the same – even if it ends up taking more time or effort than expected on my end.

For more information, see the Terms & Conditions for full contractual details.

It’s important to come prepared – but don’t worry, you don’t need a finished design document or a polished project plan. At minimum, it helps if you have a rough outline or notes about what you want to achieve. Think of it like homework: a starting point for our discussion.

Bring energy and an open mind, because I’m going to ask a lot of questions – and I mean a lot, down to the tiniest details. This ensures we’re on the same page and we know exactly what we want to create. The more prepared you are, the smoother the workshop will go and the more accurate the resulting project plan and pricing will be.

The workshop happens in writing, so every discussion and thought is documented. This ensures nothing is forgotten, provides a clear record for both of us, and makes it easier for me to review our conversation and plan the project accurately.

Remember: everything we discuss in the workshop directly impacts how I execute your project and how much it will cost. Taking a bit of time beforehand to think things through will save us both time and make the final outcome much stronger.

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 server. By minimizing their use, I help reduce technical debt, which is the potential future cost and extra work caused by choosing a quick, easy, or less robust solution now instead of a better, more sustainable approach, and avoid future headaches. It also means I can fully stand behind everything I build.

Another important factor is that most third-party tools and assets are designed for general use, not for the specific needs of your project. To support many different scenarios, they often include a large number of features you may never need. Those unused features still add complexity and can become a maintenance burden over time.

Engine updates and deprecated features can further complicate things. If a third-party tool relies on functionality that changes or is removed, you may be forced to update or replace it. Removing such tools is rarely trivial and can lead to cascading issues across your codebase. Even updating them can reintroduce features or behaviors you previously had to work around or remove.

By building focused, project-specific solutions, I keep systems lean, predictable, and easier to maintain over the long term.

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

A C++ extension is basically a more powerful type of plugin for SourceMod, written in C++ instead of SourcePawn. SourcePawn is the standard scripting language, but it has limitations. With a C++ extension, I can build things at the same level as the game’s developers, directly interfacing with the engine to add or modify functionality that SourcePawn simply can’t handle.

This enables more advanced, optimized features and better performance. It’s more complex to develop, but it can be the best solution depending on what your project needs.

You’ll find more details about risks related to modding in my Terms & Conditions. I’ll also inform you in advance if any potential risks apply to your specific project.

The price for updating the gamedata file is usually €100, provided it is a plugin I developed myself.

If the plugin comes from a third party, the price may vary. This depends, among other things, on the complexity. In some cases, updating can be significantly more time-consuming, especially if it is not just a plugin but an extension.

Beyond the voluntary warranty period I offer on top of the statutory 2-year warranty, I’ll be available at no extra charge for any questions or clarifications you have. I’m here to ensure everything works smoothly and that you feel confident using what I delivered. Support does not end when the project ends, and your project’s success matters to me.

I process payments securely through Stripe and currently support:

• Credit & debit cards

• PayPal (EEA countries only)

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

• Klarna (available in most EEA countries)

• Alipay

• Link

• iDEAL

• Bancontact

• EPS

• TWINT

• Bank transfer

Payments are generally always made upfront. In cases where budget or cash flow is limited, it is possible to split a milestone into two installments. A one-time 3% fee, based on that milestone’s total price, is added to the first installment for each milestone that is split.

I also accept PayPal and Klarna which allow you to pay in installments or defer payment.