Terms and Conditions of Work, Mastedore Dev

This document applies to any programming commission you take on with me: standalone systems, bug fixes, specific features, or similar work on the software area or Roblox development. By confirming a commission (through a message, paying the deposit, or any written agreement) you accept these terms in full.

Scope of work

Each commission is quoted on a specific scope, which we define before starting: what system or bug is being worked on, what behavior it should have once finished, and what’s not included.

If something outside that scope comes up during development (a new feature, an additional system, a redesign of something that wasn’t broken), that’s quoted separately. I don’t take on extra work just “because I’m already in the code”: if you want it included, we talk it through and adjust price and timeline before I touch it.

Payment

I work with 50% upfront and 50% on delivery.

The deposit confirms the commission and locks in your spot in the work queue. I don’t start writing code without it. The second 50% is paid once the system is working as agreed in the scope, before I hand over the final code.

If you cancel the commission after paying the deposit and I’ve already started working, the deposit isn’t refunded, since it covers time already spent. If you cancel before I start, we talk through a refund case by case.

Revisions and changes

The agreed price includes reasonable adjustments while the system is in active development: things like fixing behavior that doesn’t match what we asked for, or polishing minor details.

Once I deliver the final product and you confirm it works as agreed, that delivery is closed. Changes after that point (new functions, design changes, “now that I see it I also want it to do X”) count as a new commission, even a short one. This isn’t about putting up walls, it’s the only way the original price makes sense for both of us.

Code ownership and license to use

The code I deliver remains my authorship. What you receive is a perpetual, non-exclusive license to use that code, limited to the project it was made for.

In practice this means you can use the system in your game forever, and I can’t take it away or charge you again just for continuing to use it. But you can’t resell it as a standalone asset, or license it to third parties, without talking to me first. On my end, I keep the right to reuse my own logic and patterns in other projects. What I never reuse is anything specific to you: names, data, lore, assets that belong to your game (like models, animations, sounds, etc.).

We can still agree on a paid assignment of rights if you want no limits on using my code.

Modifications after delivery

The warranty and support I provide apply to the version I deliver, as delivered. If you or someone else touches that code afterward (edits it, integrates it poorly with another system, “improves” it) and something breaks, that responsibility is no longer mine.

If you want me to maintain the system later on, I’m happy to, but as a separate commission.

Right to decline commissions

I reserve the right to decline any commission, without needing to justify it in detail. In particular, I don’t take on work for games or systems with NSFW content, or anything that carries a legal or moderation risk I’m not willing to take on.

Confidentiality

If during the work I get access to code, data, or project information of yours that isn’t public, I don’t share it or use it outside that commission.