> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/help/readme.md).

# Getting support

How to ask for support and what to include so the first answer is the useful one.

Most problems are solved in one reply when the report has the right details. This page lists them.

## Before you ask

{% stepper %}
{% step %}

## Check the script's Troubleshooting page

Each script has its own Troubleshooting page. Start there.
{% endstep %}

{% step %}

## Check the shared pages

[FAQ](/help/faq.md) and [Common errors](/help/common-errors.md) cover what applies to every script: licensing, start order, missing dependencies, interfaces that do not show.
{% endstep %}

{% step %}

## Reproduce it on a clean start

Restart the server, join, and trigger the problem once. Errors from that single run are much easier to read than a console that has been open for hours.
{% endstep %}
{% endstepper %}

## What to include

| Detail                   | Where to find it                                                                                                |
| ------------------------ | --------------------------------------------------------------------------------------------------------------- |
| Script and version       | The `version` line in the script's `fxmanifest.lua`.                                                            |
| Cuxial Bridge version    | The `version` line in `cuxial_bridge/fxmanifest.lua`.                                                           |
| What the bridge detected | The line starting with `[cuxial_bridge] listo` in the server console. It shows framework, inventory and target. |
| Server artifact          | The build number shown by txAdmin, or by the `version` command in the server console.                           |
| Server console           | A screenshot or copy of the console from server start until the error.                                          |
| F8 console               | A screenshot of the in-game console (press F8) right after the problem happens.                                 |
| Steps                    | What you did, what you expected and what happened instead.                                                      |
| Your changes             | Anything you edited in `shared/config.lua`, `data/` or `locales/`.                                              |

{% hint style="warning" %}
Hide your license key, database password, tokens and webhooks before sharing a screenshot or a file.
{% endhint %}

{% hint style="info" %}
Send the two consoles even if they look clean. A problem that leaves no error is also a clue.
{% endhint %}

## Where to ask

Use the support channel that came with your purchase. If you cannot find it, start at [cuxial.com](https://cuxial.com).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cuxial.com/help/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.