> For the complete documentation index, see [llms.txt](https://studioworks.gitbook.io/studioworks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studioworks.gitbook.io/studioworks-docs/support/preparing-a-ticket.md).

# My issue is still unresolved

Give support the details needed to reproduce your issue.

## Include these details

| Detail              | What to provide                                              |
| ------------------- | ------------------------------------------------------------ |
| Product and version | Purchased package and installed version                      |
| Resource/model name | Actual folder name and spawn identifier if relevant          |
| Environment         | FXServer artifacts, game build, and relevant system versions |
| Expected behavior   | What should happen?                                          |
| Actual behavior     | What happens instead?                                        |
| Reproduction        | Exact steps from startup to failure                          |
| Scope               | One player, everyone, or the server process?                 |
| Changes             | Configuration, integrations, model or texture edits          |
| Tests               | Each test and its result                                     |

## Copy this template

```
Product / version:
Resource name:
Model or weapon identifier, if relevant:
FXServer artifacts / game build:
Framework / inventory / other dependencies:

Expected behavior:
Actual behavior:
First error message:

Steps to reproduce:
1.
2.
3.

When it started / last change:
Who is affected:
Custom changes:
Tests already completed and their results:

Attachments: relevant log excerpt, screenshot, or short video
Order reference: private support ticket only, if required
```

## Useful attachments

For startup failures, include the server log from the resource start. For UI/client issues, include F8 errors and any related server log. For model issues, show the model, distance, extras, and action in a short video. Include the first error and its context rather than only the last line.

[Finding and redacting logs](/studioworks-docs/support/finding-logs.md).

{% hint style="danger" %}
Remove license keys, tokens, passwords, webhook URLs, and database credentials. Do not share complete paid product packages in public channels.
{% endhint %}

## Submit your ticket

Open the [StudioWorks Discord](https://discord.gg/UmqU67rp4v) and follow its support process. Add further test results to the same ticket.

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

# 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://studioworks.gitbook.io/studioworks-docs/support/preparing-a-ticket.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.