Campaign settings govern the fundamental operating parameters of a campaign — its designation, operational type, and data acquisition protocols. These parameters determine how sectors are populated and what capabilities are available to the crew.
- Name
- The campaign's operational designation. Displayed throughout the interface and used to identify the campaign in mission briefings and reports.
- Campaign Type
- Determines the campaign's operational context and how sectors are initialised.
- Sector Data Source
- Visible only for Deepnight Revelation campaigns. Controls where build configurations are sourced when populating sectors.
- Track Survey Index
- When enabled, the jump log form includes a Survey Index field. On saving a jump log, the survey index value is written to the destination star system — or to the destination parsec directly if no system exists at that location.
Charted Space
The standard operational mode. Sectors are imported from TravellerMap and the crew explores the known reaches of Charted Space. Build configurations are assigned manually or pulled from TravellerMap data.
Deepnight Revelation
Configured for the Deepnight Revelation campaign. On creation, all Deepnight Revelation sectors are pre-populated with build configurations derived from the sourcebook. Survey index tracking is enabled by default.
Homebrew
The universe is constructed from scratch. No sectors are imported automatically. All sectors, subsectors, and build configurations are defined by the referee.
TravellerMap
Build configurations are imported from TravellerMap data. Use this when you want sector data that reflects the published universe as catalogued by TravellerMap.
Deepnight Books
Build configurations are sourced from the Deepnight Revelation sourcebook. Use this for a faithful rendering of the sectors as described in the published adventure materials.
The default value when logging a jump is 10. Valid range is 0–12, corresponding to the survey index scale used in the Deepnight Revelation sourcebook. This setting is enabled automatically for Deepnight Revelation campaigns.
System Generation
- Sophont Check
- Controls the procedure used when determining whether a world has a native sophont species.
- Max Tech Level
- Sets a campaign-wide ceiling on the tech level assigned to any generated world. The generator will not produce worlds with a tech level above this value. The default is 16, corresponding to the standard upper bound in Traveller. Valid range is 0–33.
- Use Native Sophont Tech Level Rules
- When enabled, the tech level of worlds with a native sophont population is determined using native sophont rules rather than the standard procedure.
- Allow Captive Government
- When disabled, the generator will not assign government code 6 (Captive Government) to any world during subsector generation. A captive government implies the system is politically controlled by another system — in exploration campaigns this relationship should be a referee decision rather than a generated result.
Standard
Default sophont check procedure.
Rare Earth Universe Variant
Applies the Rare Earth variant (World Builder's Handbook, p.130). Applies a DM −2 to biocomplexity rolls. Significantly reduces the probability of complex life.
Very Rare Earth Variant
House rule — not a standard Traveller rule. Applies a DM −3 to biocomplexity rolls, more severe than the Rare Earth variant (DM −2). Severely reduces the probability of complex life.
None
Sophont check is skipped entirely. No sophont worlds will be generated. This is the default for Charted Space campaigns.
Individual build configurations may specify their own maxTechLevel, which takes precedence over this campaign setting for that subsector generation run.
Standard rules (default)
Tech level is generated using the standard Traveller procedure.
Native sophont rules
Tech level is rolled as 3D3 − 2 + DMs, where the DMs are determined as follows:
| Condition | DM |
|---|---|
| Star age < 1 | −1 |
| Star age 2–3 | +1 |
| Star age ≥ 4 | +2 |
| Government code 1, 5, or 7 | +1 |
| Population code > 7 | +1 |
Defaults to disabled for Deepnight Revelation campaigns and enabled for Charted Space and Homebrew campaigns.
Individual build configurations may specify allowCaptiveGovernment, which takes precedence over this campaign setting for that subsector generation run.
Display Preferences
- Distance Display
- Controls which distance measurement is shown in star system tables and orbital data sections throughout the interface.
- Date Format
- Controls how Imperial dates are displayed throughout the interface.
AU (default)
Distance from the primary star is displayed in Astronomical Units.
Orbit #
Distance is displayed as the Traveller orbit number (0–19 scale).
Traveller Standard (default)
Dates are displayed in day-year format, e.g. 001-1105.
ISO 8601
Dates are displayed in year-day format, e.g. 1105-001.
Map Colours
- Native Sophont Colour / Extinct Sophont Colour
- Hex colour codes used to highlight worlds with a native or extinct sophont population on generated maps. The default colours are powder blue (#B0E0E6) for native sophonts and pale goldenrod (#EEE8AA) for extinct sophonts.
- Show Native / Extinct Sophont Colours on SVG Maps
- Controls whether sophont highlight colours are applied to SVG maps generated by the server (subsector exports and the all-sectors map). When disabled, sophont worlds are not visually distinguished on those maps regardless of the configured colour.
This setting does not affect the interactive starmap. In the starmap, sophont colours are always visible in referee mode and always hidden in player mode.
API Access
- Campaign Slug
- The campaign's unique identifier as it appears in all URLs — the :campaign_slug segment of /c/:campaign_slug/…. Enter this value in the Foundry module's MTU Campaign Slug setting.
- API Token
- A shared secret used to authorise write operations from external tools such as the Foundry VTT module. The token is transmitted as a Bearer credential in the Authorization header of each request. Enter this value in the Foundry module's MTU API Token setting.
The token is generated automatically when a campaign is created and is not transmitted or stored anywhere other than this page. Use the Copy button to transfer it to the Foundry module settings.
Use Regenerate to issue a new token — for example if the token is compromised. The previous token is invalidated immediately. Any external tool using the old token will receive a 401 Unauthorised response and must be updated with the new value.
Bulk Operations
- Populate All Sectors
- Enqueues generation jobs for every subsector in the campaign that has a build configuration assigned, regardless of whether the sector already contains star systems. Existing systems are replaced.
- Populate Empty Sectors
- Enqueues generation jobs only for subsectors belonging to sectors that contain no star systems. Sectors that have already been generated are left untouched. The confirmation prompt displays the number of empty sectors and subsectors that will be affected.