> 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/start-here/status.md).

# Current status

What works today, and what does not.

This page is kept accurate rather than encouraging. Last updated **2026-08-03**.

## In one line

**Not ready for a public server.** All eight foundation resources exist and run on a development server. There is no gameplay — no jobs, no inventory, no vehicles, no property.

What there now is: a demonstration site you can walk to, with zones, interactions, and a timed action. It exists to prove the foundation works, not to be played.

## What exists

| Resource       | Version | State                                                       |
| -------------- | ------- | ----------------------------------------------------------- |
| `nxc_lib`      | 0.4.0   | Shared primitives. Used by everything                       |
| `nxc_core`     | 0.3.0   | Identity, sessions, lifecycle, service discovery            |
| `nxc_config`   | 0.1.1   | In-game configuration with history and rollback             |
| `nxc_ui`       | 0.2.2   | The interface layer                                         |
| `nxc_zones`    | 0.1.1   | Spatial zones with enter and exit events                    |
| `nxc_target`   | 0.1.1   | Look-at-it interaction                                      |
| `nxc_interact` | 0.1.1   | Timed actions: animation, progress, cancellation, cooldowns |
| `nxc_devtools` | 0.1.0   | Diagnostics, and demonstration zones, options and workflows |

## What has actually been run on a server

Verified on a development server running Enhanced, build 106:

* The framework starts, connects to MariaDB, and applies its migrations
* A player connects; one account is created and reused across reconnections
* Configuration registers, and settings survive a restart
* The interface opens, takes focus, and gives it back on every close path
* A resource restarting with an interface open releases focus rather than stranding the player

## What has not

* **Anything under load.** One player, never more
* **Any gameplay.** There is nothing to do on a Nexus Core server yet
* **Zones, targeting, and workflows in a game client.** All three are built and tested. Nothing has been walked into, chosen, or completed by a person
* **A public server.** No deployment has ever faced players who did not build it

## What that means for you

If you are evaluating frameworks for a server you intend to open soon, this is not it yet.

If you want to follow along, run a development server, and have opinions early, the foundation is solid enough to build against and the contracts are settling.

## Versions before 1.0.0

Contracts are **unstable**. A minor version increment may carry breaking changes. Pin exact versions, install a whole [compatibility set](/reference/compatibility-sets.md), and read the changelog before upgrading.


---

# 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/start-here/status.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.