> ## Documentation Index
> Fetch the complete documentation index at: https://docs.virusstudio.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Script Delivery: What Is Included and How to Use It

> Find out how Virus Studio delivers finished scripts, what each delivery includes, how to install your script, and what to do if something doesn't run.

When your script is finished and has passed our internal review, we send it directly to you through the same channel you used to communicate with us — typically as a file attachment, a formatted code snippet, or both. You do not need to chase us down for your delivery; we reach out to you as soon as it is ready.

## What Your Delivery Includes

Every delivery from Virus Studio is more than just raw code. Here is what you can expect to receive with your finished script:

* **Commented code** — inline comments throughout the script explain what each section does, making it easier to read, maintain, and modify later.
* **Usage instructions** — a short written summary covering how to install the script, what inputs it expects, and any configuration variables you may want to adjust.
* **Dependency notes** — if your script relies on external libraries, modules, or Roblox services, those are listed clearly so you know exactly what needs to be in place before running it.

## How to Install Your Script

### Roblox Studio

<Steps>
  <Step title="Open your experience in Roblox Studio">
    Launch Roblox Studio and open the place file where you want to use the script.
  </Step>

  <Step title="Place the script in the correct location">
    Depending on whether the script is a LocalScript, Script, or ModuleScript, drag it into the appropriate container — ServerScriptService, StarterPlayerScripts, or ReplicatedStorage. The usage instructions in your delivery will specify the correct location.
  </Step>

  <Step title="Set any configuration variables">
    Open the script and locate the configuration block near the top. Adjust any variables — such as team names, damage values, or asset IDs — to match your experience.
  </Step>

  <Step title="Playtest and verify">
    Run a playtest in Studio and confirm the script behaves as expected before publishing.
  </Step>
</Steps>

### Python Scripts

<Steps>
  <Step title="Save the file to your project directory">
    Place the delivered `.py` file in the root of your project or in whatever subfolder your project structure requires.
  </Step>

  <Step title="Install any listed dependencies">
    Check the dependency notes in your delivery and install any required packages using `pip install package-name` before running the script.
  </Step>

  <Step title="Run the script">
    Execute the script from your terminal with `python script_name.py`, or import it as a module into your existing codebase as described in the usage instructions.
  </Step>
</Steps>

<Tip>
  Save a backup copy of your delivered files before making any modifications. If your edits introduce a bug, having the original clean version on hand means you can restore it instantly rather than requesting another delivery.
</Tip>

## If Your Script Doesn't Run

If the delivered script throws an error or behaves unexpectedly right out of the box, work through these checks before reaching out:

* **Check your dependencies** — make sure every library or module listed in the dependency notes is installed and accessible.
* **Verify your Lua version** — some scripts require a specific Luau feature set. Confirm you are using the expected environment (e.g., the script is in a `Script` rather than a `LocalScript` if server-side execution is required).
* **Read the full error message** — error output usually includes a line number and a description. Match that line to the comments in your script to understand what is failing.
* **Review the usage instructions** — double-check that the script is placed in the location specified in your delivery notes.

If none of those steps resolve the issue, contact us with the full error message and a description of what you tried. That information helps us diagnose and resolve the problem quickly. You can also visit [/support/troubleshooting](/support/troubleshooting) for additional guidance.

## Code Ownership

Once your project is delivered and payment is complete, the script is yours. You have full ownership of the code and are free to use, modify, and distribute it however you like within the terms of your platform. We do not retain rights to resell or reuse your custom script.

## Related Pages

<CardGroup cols={2}>
  <Card title="Revisions" icon="rotate" href="/working-with-us/revisions">
    Need a tweak after delivery? Learn how the revision process works and how to write effective feedback.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/support/troubleshooting">
    Find solutions to common script issues and error messages.
  </Card>
</CardGroup>