Skip to content

Help

How a commission runs from the first click to the finished jar.

01

Configure

Choose a tier, loader, Minecraft version and any extras. The total updates as you go.

02

Brief

Describe the mod in plain language. Screenshots, references and half-formed ideas all help.

03

Pay

Stripe Checkout. The order enters the queue the moment payment clears.

04

Build

You get progress updates in your dashboard and a build to test before final delivery.

Questions

How is the price decided?

The configurator is the quote. A tier sets the base, options scale it, extras add to it. The server recalculates the same numbers before payment, so the total you see is the total you are charged.

What if my idea does not fit a tier?

Pick the closest one and describe the rest in the brief. If the scope turns out to be off, we say so before starting and adjust — we do not start work and invoice the difference later.

Do I get the source code?

The full Gradle project is an add-on on every tier, MIT-licensed to you. Without it you still get the built .jar and the config files.

How many revisions are included?

Two rounds of changes within the agreed scope, plus 30 days of bug fixes after delivery. New features are a new commission.

Which loaders and versions do you support?

Forge, Fabric and NeoForge on current versions. Legacy targets like 1.12.2 are available at a surcharge because the APIs are slower to work with.

What happens if you cannot finish it?

You get a full refund for anything undelivered. If we have shipped part of the scope, we refund the rest and hand over what exists.

How do I pay?

Card, via Stripe. We never see or store your card number. A receipt goes to the email on the order.

Still unsure about scope?

Start a configuration — nothing is charged until you confirm.

Configure a mod