Terms

How commissioned work runs.

These terms cover commissioned scripting work. They apply from the day a job is agreed, and anything that changes them is agreed in writing first.

Hiring me means agreeing to everything on this page. Booking a job, paying an upfront, or asking me to start work is acceptance of these terms in full.

Last updated 2026-08-28

Scope and quotes

Every job starts with a written scope: what ships, what it does, and what it does not cover.
Quotes are fixed against that scope. Anything outside it is quoted as new work before it is built.
Estimates are given in good faith. If a date is going to slip, you hear it from me early.

Payment

50% upfront before work starts, 50% on delivery.
100 USD minimum on any payment, including a single small task and the closing half of a larger job.
Wise is preferred and carries no added fee. PayPal is accepted with a small add-on that covers their cut.
Invoices are in USD and due within 7 days. Robux is not accepted as payment.
Revenue share is not a substitute for a rate. I am open to it on top of an agreed rate, never in place of one.
Work pauses while an invoice sits more than 7 days overdue.
A chargeback or payment reversal raised after delivery suspends your licence to the code until it is settled.

Refunds

The upfront is not refundable. It secures your slot in my schedule and lets the work run without the payment question hanging over it, which serves both sides.
Any refund of an upfront is at my discretion. I am not obligated to return it.
Negligence on my side is where that discretion gets used: if I fail to deliver the agreed scope, or cannot put materially broken work right within an agreed window, I will look at returning part or all of the upfront against what was actually delivered.
If you end the job partway, completed work is billed and the rest is not.
A change of mind, a change of direction, or a project shelved on your side is not grounds for a refund.

Revisions

Revisions that bring the work in line with the agreed scope are included.
Requests that add to or change the scope are quoted as new work.

Delivery and acceptance

Delivery runs against the agreed scope on an agreed date.
Work counts as delivered when it is handed over and running in your place or repository.
You have 7 days from delivery to raise anything that misses the agreed scope. After that the work is accepted and the closing payment is due.
Time spent waiting on you for assets, access, decisions or feedback moves the delivery date by the same amount.

Existing code and backups

I am responsible for the code I write, not for code that was already in the project.
Fixing pre-existing bugs, or untangling systems I did not build, is quoted as its own job.
Keeping backups of your place and data is yours to handle. I work on a staging place wherever the project allows one.

Access and ownership

You provide the access a job needs: a place, a repository, a test server, and any assets involved.
On final payment the code written for the job is yours to use: in the game it was built for, in your own projects, and in any project you own or hold a major stake in.
Reselling, redistributing or licensing that code to anyone else is not part of the deal. It needs my explicit written permission, agreed case by case.
Handing the code to developers working on your own project is fine. Passing it to a project you do not own is not.
Before final payment the code stays mine and is licensed for testing only, not for release.
My existing libraries and tooling stay mine, licensed to you for use inside the delivered work under the same limits.
Assets, models, animation and VFX from third parties stay with their owners under their own licenses.

Credit and portfolio

Showing delivered work in my portfolio is part of every job. It is not something a commission opts out of.
The timing is yours to protect. If the game or feature is not out yet, the showcase waits until it is public, so nothing about it leaks ahead of your release.
Once it is public I may show the work, the game name and its public numbers.
If a job needs to stay quiet past its release, say so before it starts and we set the date in writing.
Scripting is what I claim. Art, models, animation and VFX are credited to whoever made them.

Confidentiality

Anything you share about an unreleased project stays between us: builds, plans, numbers, and the code itself.
That holds whether or not a separate agreement is signed, and it outlasts the job.
It does not cover anything already public, or anything I have to disclose by law.

Support after delivery

Bugs inside the delivered scope, reported within 14 days of delivery, are fixed at no cost.
Breakage caused by later edits from other developers, or by changes outside the delivered scope, is new work.

Liability

My total liability for a job is capped at what you paid for that job.
I am not liable for lost revenue, lost players, lost data, or moderation action taken against your game.
Nothing here limits liability that cannot be limited by law.

Ending an engagement

Either of us can end an engagement in writing at any time.
Work already completed is billed and handed over. Work not started is not billed.
If a project goes quiet on your side for 30 days, I treat the engagement as ended: completed work is invoiced, and picking it back up is quoted as a new job.
I decline or stop work that breaks Roblox's Terms of Use, uses stolen assets, or puts a game's moderation standing at risk.

Communication

Day to day contact runs over Discord or email.
Anything that changes scope, price or dates is confirmed in writing before work continues.

Changes to these terms

The version of these terms in effect on the day a job is agreed is the version that governs it.
Later changes apply to new jobs, never backwards to one already running.

Questions on any of this before booking? Ask on Discord or by email.