Commission Guidelines

Payment

1.1 We will agree the total price before any work begins.
1.2 50% upfront is required to reserve the slot and confirm the start date.
1.3 While I work, I will usually share progress updates so you can give feedback early. These updates are a courtesy and are not guaranteed.
1.4 Once the work is complete, I will provide a demo via a private game link or a video. After you approve the demo, the remaining 50% is due before final files are delivered.
1.5 If I need to cancel the commission for any reason, including personal circumstances, I will refund the upfront payment in full. This is an allowed outcome under HiddenDevs rule 2.2.1 and similar guidelines.

2.1 Final delivery is provided as RBXM or RBXL.
2.2 I can help with installation into an existing game where feasible, but installation and integration into existing systems is not included by default unless we agree it in writing.

3.1 I may choose to use reputable libraries such as ProfileService and Requirement.lua, unless you raise an objection.
3.2 I may use LLM-based tools to speed up parts of development, for example brainstorming, refactoring, or generating a first draft, but I do not use them as a substitute for understanding.
3.3 I remain fully responsible for the code. Every line is reviewed, understood, and intentionally written into the final deliverable by me. I maintain complete control over structure, quality, and correctness throughout.

4.1 We will agree a deadline in days, weeks, or months.
4.2 The deadline starts once the upfront payment has been received and I am cleared to begin development.
4.3 If I miss the agreed deadline, you may request a full refund of the upfront payment. In that case, you will not owe the remaining 50%, and the commission will be treated as cancelled.
4.4 If you do not request a full refund and continue working with me, you cannot later randomly change your mind and enforce the prior deadline unless I exceed a reasonable amount of time since our last communication.
4.5 Missing a deadline is not a violation of HiddenDevs rule 2.2.1 or similar guidelines.

5.1 It is your responsibility to provide a clear and accurate description of your requirements. The specification should be detailed enough to avoid ambiguity.
5.2 I am not required to develop features beyond a reasonable interpretation of your written description.
5.3 I am not obligated to request clarification where a reasonable interpretation can be made. If a dispute arises regarding interpretation, a marketplace moderator may be asked to review and decide.

6.1 I do not accept game links, product files, reference images, videos, or similar materials as a substitute for a written specification.
6.2 If such materials are shared, they will be treated as supplementary only and will not override or replace your written description.
6.3 Requirements must not be omitted on the basis that they appear obvious within shared materials. Only explicitly described requirements will be considered binding.

7.1 Unless otherwise specified, I provide a programming service only.
7.2 Any assets, resources, or materials I create or source outside of programming are provided on a voluntary and demonstrative basis.
7.3 Concerns or complaints regarding the quality, suitability, or inclusion of such non-programming assets are not considered valid unless explicitly agreed as part of the commission.

Before work begins, the price, deadline, scope, and delivery format should be clearly agreed in writing.