Core details

Name

The sector’s designation. Use to generate a random name. Use to choose the language used for name generation.

Abbreviation

A short code used on maps and in references. Typically two to four characters.

Imperial Coordinates

The sector’s position in the Imperial grid. X increases coreward; Y increases spinward. Each sector occupies a unique X/Y position.

Observations

Free-text notes in CommonMark (Markdown) format. Displayed on the sector survey record.

Default subsector build

Settled space

When enabled, each of the 16 subsectors is pre-configured with a populated build plan so that generated star systems will have populations, governments, and tech levels. The survey index is set to 10.

When disabled, subsectors are seeded with a minimal build plan and a survey index of 3. Use this for exploration or frontier sectors where population data should be sparse or absent.

Defaults to on for Charted Space and Homebrew campaigns, and off for Deepnight Revelation campaigns.

Survey index

The survey index (defaultSI) controls what data is visible on player-facing maps. Systems with a survey index below the map’s threshold are hidden or shown with reduced detail.

A value of 10 marks a system as fully surveyed and visible on all maps. A value of 3 marks it as lightly surveyed — it will appear on the starmap but without detailed world data, reflecting an exploration-era record.

T5 Tab Delimited File

Homebrew campaigns only. Optionally upload a whole-sector T5 Tab Delimited file to seed each of the 16 subsectors with its own build plan, derived from the systems that fall within its hexes.

While a file is attached, it takes precedence over the Build plan field below for system placement — the field becomes read-only to reflect this. Survey index still applies from Settled space above, to every subsector, regardless of the uploaded file. Subsectors with no matching rows in the file fall back to the build plan below.

Build plan

YAML configuration applied to every subsector when the sector is created. You can customise it here before committing, unless a T5 Tab Delimited file is attached above, in which case it is locked and the uploaded file’s data is used instead. See the build specification reference for the full schema.