> 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/nexus-core-docs/for-players/interface.md).

# The interface

What the on-screen interface is telling you.

> Written to be handed to your players.

## Notifications

Brief messages in the corner. They never take your cursor and never stop you moving — you can keep driving, running, or talking while one is up.

The colour is the whole message: green worked, amber is a warning, red failed, blue is information.

## Dialogs

A confirmation, a form, or a menu. These **do** take your cursor, and you cannot move while one is open.

Close with the button, or press **Escape**. Either releases the cursor.

**Only one at a time.** If something tries to open while another is up, it is refused rather than taking over — otherwise the first would still be there, invisible and waiting for input.

## Progress

A bar for something that takes time. You can usually cancel with **Escape**; whether an action can be cancelled depends on what it is.

## Accessibility

If your system is set to reduce motion, animations are disabled automatically. You do not have to find a setting for it.

Text contrast meets AA at body size throughout.

## If your cursor gets stuck

You cannot move and no dialog is visible. In order:

1. Press **Escape**
2. Ask a staff member to run `/nxcui close` — it force-releases the cursor
3. Reconnect. This always works

**This is a bug, not something you did.** Please report it with what you were doing.


---

# 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/nexus-core-docs/for-players/interface.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.