Editor configuration
The All settings page — the asset inspector, the configuration report grouped by section, and this machine's measured capabilities.
The window, and the menu#
Everything lives under NexusForge → Persistence:
| Menu item | Opens |
|---|---|
| Setup | The guided setup — where a new project should start |
| Configuration | The same window on All settings: asset inspector, configuration report, capabilities, checks |
| Validate Configuration | The Validation page, run immediately against the configuration |
| Validate Everything | The Validation page, including package, dependencies, platform, identity and a real write |
| Log Configuration Report | Writes the whole report to the Console without opening a window |
| Run Smoke Test | Saves and loads a small model through the real pipeline |
| Verify Platform | Reports the active target, scripting backend and measured crypto/compression capabilities |
| Open Save Folder | Reveals the folder your configuration writes to |
| Validate Persistent Identities | Scans prefabs and open scenes for missing, duplicate or unstable ids |
What the All settings page shows#
- The asset inspector — every field of
PersistenceSettingsAsset, with tooltips. - The configuration report — the same settings grouped by section, but in consequences: what your configuration enables, what it costs, and what it forbids. It is generated by
PersistenceConfigurationReport, which is engine-free and unit-tested, so the words on screen cannot drift from the behaviour. - This machine's capabilities —
SecurityCapabilityProberuns the primitives and reports what actually works here rather than assuming. - An explicit list of what the window cannot configure — storage root folder name, path ceiling, migration registrations (they are code), per-slot request options, and encryption keys.
Why the report exists#
Configuration mistakes are usually silent: a ceiling nothing can fit under, encryption on with no key provider, a save folder that a platform will not allow. The report names each one in terms of what it means for the player, which is the difference between a setting and a decision.
Next#
- Validation — the checks that come with a remedy.
- Settings and configuration reference — every setting's meaning and cost.
- Support — what a useful report contains.
Something wrong on this page? Every page here describes behaviour that is checked in the repository. If a page and the package disagree, the package wins.
Report a documentation problem · Frequently asked questions · Troubleshooting