> 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/what-you-get/overview.md).

# Overview

What Nexus Core gives you, and what it deliberately does not.

Nexus Core is a **foundation**, not a finished server. It gives you the parts that every roleplay server needs and that are painful to build well, and it stays out of the way of the parts that make your server yours.

## What it gives you

|                   |                                                                      |
| ----------------- | -------------------------------------------------------------------- |
| **Identity**      | One account per person, surviving reconnections                      |
| **Configuration** | Settings in the database, changed in game, with history and rollback |
| **Interface**     | One in-game browser, shared by every resource                        |
| **Places**        | Zones with enter and exit events, interior and bucket aware          |
| **Interaction**   | Look at something, see what you can do, and have the server check it |

See [The foundation](/what-you-get/foundation.md) for what each resource actually does.

## What it does not give you

**Any gameplay.** There are no jobs, no inventory, no vehicles, no property, no banking. Those are later phases, and until they exist there is nothing to do on a Nexus Core server.

**Any content.** No maps, no MLOs, no clothing, no vehicles. The framework assumes nothing about what you run on top of it — that is deliberate, and it is what lets it work on a server that shares none of its original author's assets.

**Anything you already have.** It replaces a framework, not your content.

## The shape of it

Each resource owns one domain and nothing else. Identity does not know about money; configuration does not know about jobs; the interface does not know what it is displaying.

That costs more resources than a single monolithic one, and buys two things: a restart that affects one thing rather than everything, and a defect that stays where it started. Every framework that became difficult to work on did so one reasonable exception at a time.

## Where it is

Early. See [Current status](/start-here/status.md), which is kept honest about what has and has not actually run.


---

# 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/what-you-get/overview.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.
