> 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/configuring/in-game.md).

# Changing settings in game

Changing a setting without restarting.

> **Not available yet.** The configuration interface arrives with `nxc_devtools`, which is not built. This page describes what it will do so you can tell whether it is missing or broken.
>
> Today: `nxc_config_status` on the console shows what is registered, and every setting runs on its declared default.

## What it will look like

Settings are grouped by the resource that owns them. Each shows its description, its current value, where that value came from, and what it would be if you cleared it.

## Draft, preview, publish

A change is not applied as you type it. You build a **draft** of one or more changes, see an impact preview — which resources are affected and which players would notice — and then **publish**.

Publishing is atomic. Either every change in the draft takes effect or none does, so a half-applied set of settings is not a state your server can reach.

## Rolling back

Every publication is recorded and can be reverted. Values are versioned rather than overwritten, so rollback is a first-class operation rather than remembering the old number.

## Who can change what

Editing configuration requires a capability. **Capability grants are not populated yet**, so this is currently ungated in the sense that nothing can grant it either — another reason the interface is not released.


---

# 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/configuring/in-game.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.
