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

# How to Get Support for FA Scripts FiveM Resources

> Contact FA Scripts for help with installation, configuration, and errors. Learn what to include so support can resolve your issue quickly.

FA Scripts support runs through Discord. This page explains where to ask for help, what information to include, and how to reach the team for purchase or licensing issues.

## Where to Get Help

<CardGroup cols={2}>
  <Card title="Discord Support" icon="discord" href="https://discord.gg/ePYv5V5b8w">
    The fastest way to get help. Open a ticket in the support channel after verifying your purchase.
  </Card>

  <Card title="Tebex Store" icon="cart-shopping" href="https://fa-scripts.tebex.io">
    For refunds, missing purchases, or billing questions, contact Tebex through your order.
  </Card>
</CardGroup>

## What to Include in a Support Request

The more detail you provide up front, the faster support can diagnose the issue. Include the following whenever you open a ticket:

<Steps>
  <Step title="Script name and version">
    The exact resource name and the version you downloaded. You can find the version in the resource's `fxmanifest.lua` or on the Cfx.re [Granted Assets](https://portal.cfx.re/assets/granted-assets) page.
  </Step>

  <Step title="Framework and server details">
    Which framework you use (ESX, QBCore, QBox, standalone), the framework version, and any relevant server info such as artifact version and OS.
  </Step>

  <Step title="Full console error">
    Copy the complete server console output around the error, not just the last line. Screenshots are fine, but pasted text is easier to search.
  </Step>

  <Step title="Reproduction steps">
    A short description of what you did before the error occurred, and whether it happens every time or intermittently.
  </Step>

  <Step title="Recent changes">
    Any config edits, dependency updates, or other resources you installed shortly before the issue appeared.
  </Step>
</Steps>

## Before You Open a Ticket

<Steps>
  <Step title="Check the troubleshooting page">
    Every script ships with a troubleshooting page covering the most common first-launch issues. Check it before opening a ticket.
  </Step>

  <Step title="Confirm Asset Escrow is set up">
    Most "resource won't start" issues come from a license key mismatch. Review [Asset Escrow](/basic-knowledge/asset-escrow) to confirm your server key belongs to the account that purchased the script.
  </Step>

  <Step title="Verify dependencies">
    Make sure every dependency listed on the script's requirements page is installed and started before the FA Scripts resource in `server.cfg`.
  </Step>
</Steps>

<Note>
  Support is provided for the current version of each script. If you are running an outdated release, redownload the latest version from the [Cfx.re portal](https://portal.cfx.re/assets/granted-assets) before opening a ticket.
</Note>