Skip to main content
Getting your script exactly right is important to us. Every project includes a set number of revision rounds so you can request adjustments after reviewing the delivered code. Understanding how revisions work — and what qualifies as one — helps you make the most of that included support and keeps your project moving smoothly.

​
What Is a Revision?

A revision is a change to functionality that already exists within the original agreed scope. If the delivered script does not behave the way it was described in your request, or if a small detail needs tuning, that is a revision. A new request is anything that adds functionality not described in the original brief — a new feature, a different system, or a significant change in direction. These are scoped and quoted separately.
  • The script runs but the output format is slightly different from what you described.
  • A condition triggers at the wrong threshold and you want it adjusted.
  • A loop runs one too many times and needs a minor fix.
  • The variable naming or code comments need to be cleaned up for readability.
  • A Roblox RemoteEvent is firing on the wrong side (client vs. server) relative to what was requested.
  • Adding a leaderboard to a script that was originally scoped as a basic reward system.
  • Integrating a third-party API that was not mentioned in the original brief.
  • Rewriting the script in a different language or framework than originally agreed.
  • Adding a UI layer to a back-end system that was scoped without one.
  • Extending a 50-line utility into a full game system.
Revisions are designed for adjustments to the original scope. If your feedback describes changes that go beyond what was agreed at the start, we will let you know and provide a separate quote for the additional work — no surprises.

​
How to Submit Revision Feedback

When you are ready to request a revision, send your feedback through the same channel you used to receive your delivery. Clear, specific feedback leads to faster turnarounds and fewer back-and-forth messages.

​
Tips for Writing Good Feedback

1

Be specific about what needs to change

Instead of “this doesn’t work,” describe exactly which behavior is wrong. For example: “The damage function applies the value twice on the first hit.”
2

Reference line numbers or function names

If you can point to the exact location in the code, do so. This helps us find and fix the issue immediately without having to reproduce it first.
3

Explain expected vs. actual behavior

Tell us what you expected the script to do and what it actually did. For example: “Expected: the timer resets to 30 when a player joins. Actual: the timer does not reset at all.”
4

Include any error messages

If the script is throwing an error, copy the full error text. Error messages point directly to the problem and speed up the fix significantly.

Submit a Request

Starting a new project? Here is how to put together a strong initial request.

Delivery

Learn what your delivered script includes and how to get it up and running.