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

# Getting help

Reporting a problem, and what to include.

## Before reporting

Run `nxc_versions` and confirm every resource comes from one [compatibility set](/reference/compatibility-sets.md). A mismatch explains most confusing behaviour and is worth ruling out first.

## What to include

A report without these usually needs a round trip before anyone can start:

* The output of `nxc_versions`
* Your Cfx Server build (`fx: b106-ea/Win` on the last line of startup)
* The **whole** Lua stack trace, not the first line
* What you were doing
* Whether it happens every time

## Where

| What                              | Where                                             |
| --------------------------------- | ------------------------------------------------- |
| A defect in a resource            | An issue on that resource's repository            |
| A question about running a server | The community discussion                          |
| A security issue                  | Privately — see `SECURITY.md`. Not a public issue |

## What is known already

[Current status](/start-here/status.md) lists what does not work yet. Three things fail closed on purpose and are not defects:

* Item-gated interactions are always refused — there is no inventory yet
* Capability-gated interactions are always refused — nothing grants capabilities yet
* Zone-attached interactions are refused server-side — that check is not implemented yet

Each makes a feature look broken. Failing the other way would leave real actions ungated with nothing saying so.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nxcframework.net/reference/help.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.