Settings Backup & Transfer

Calendaria writes its world settings, calendar data, and notes to a JSON file, and reads the same file back into another world.

Open the Settings Panel, go to the Module tab, and find the Backup & Transfer section. The section is GM-only.

Exporting

1. Click Export.
2. Leave Include active calendar: {name} checked to embed the active calendar’s full definition, or clear it to leave the calendar and its notes out of the file.
3. Save the JSON file.

The file is named calendaria-settings-{timestamp}.json and covers:

Category	Examples
Display Formats	Date and time formats for HUD, MiniCal, BigCal, Time Keeper, Stop Watch, Chat
Time Settings	Clock speed multiplier, speed increment unit, clock pause sync
Weather	Current weather, history, forecast plans, intraday settings, inertia, custom presets
Fog of War	Enabled state, revealed ranges, start date, nav mode, reveal settings
Cinematic	Enabled, threshold, panel duration, per-element toggles, event weighting
Chronicle	Depth mode, view mode, visibility toggles, button visibility, combat mode
UI Visibility	Force settings for all seven widgets; show settings for BigCal, HUD, MiniCal, Time Keeper, toolbar button, journal footer
Permissions	All role-based permissions
Categories	Custom note presets: exported in full when calendar data is not included, or limited to presets referenced by the exported notes when it is
Custom Time Jumps	HUD, Time Keeper, MiniCal jump configurations
Macro Triggers	Season and moon phase trigger assignments
Scene Integration	Ambience sync, darkness sync, color shift sync, brightness multiplier
Equivalent Dates	Multi-calendar sync calendar list

Calendar data and notes

With Include active calendar: {name} checked, the calendar’s full definition is embedded along with the current date. Its notes are bundled, except for festival notes, which ride along inside the calendar definition as festival seeds. The custom presets the bundled notes’ categories point at travel too. Importing the file creates a new custom calendar in the target world.

Checking the box also takes three things out of the settings block: your other custom calendars, your edits to bundled calendars, and your custom note presets. An export with the box checked carries the active calendar and nothing else calendar-shaped, while one with the box cleared carries every custom calendar and every bundled-calendar edit, but no notes.

Notes are serialized into the file. On import they are recreated and cross-references between them are re-linked. Scene, macro, and playlist references are cleared, since they do not resolve in the target world.

Bundled custom presets are restored before the notes are processed. A preset whose ID already exists in the target world is skipped rather than overwritten.

What is not exported

Scope is not what decides this. Some per-user settings travel and some world settings do not. These are left out:

• Window positions for the HUD, MiniCal, BigCal, Time Keeper, Stop Watch, Sun Dial, and Chronicle.
• Sun Dial sticky states. Sticky states for the HUD, MiniCal, Stop Watch, and Time Keeper are included.
• Lock position states.
• Combat behavior for the BigCal, MiniCal, Time Keeper, Stop Watch, and Sun Dial. HUD and Chronicle combat behavior are exported.
• FXMaster integration. Every setting in that section stays behind, including whether the integration is on at all.
• Rest and bastion advancement amounts. Whether time advances on rest is exported; how far it advances is not.
• Real-time tick interval and whether the clock runs during combat.
• Weather seed, ambience intensity, and audio muffling.
• Weekly almanac publishing, secret-note visibility, dual temperature display, enricher click target, and developer mode.
• Theme settings. Theming is handled by 3DS:ATLAS, not Calendaria.

Set these by hand in the target world after importing.

Importing

1. Click Import.
2. Select a previously exported JSON file.
3. Review the confirmation dialog. It reports how many settings the file holds and which version wrote them, and offers checkboxes for the calendar data, the notes, and Set as Active Calendar when the file carries them.
4. Click Import.

Importing overwrites the world settings the file carries. Settings the file does not contain are left untouched, so they keep whatever the target world already has.

Importing a calendar always adds a calendar, never replaces one. Importing the same calendar into a world that already has it produces a second copy under a numbered id.

A note is skipped when the target world already holds a note with the same name on the same date, so importing the same file twice does not duplicate notes. A skipped note is also missing from the re-linking pass, and cross-references pointing at it are dropped.

A file exported by an older release imports without extra steps. Weather sound references and festival icons are rewritten to the shapes the current release stores.

Transferring between worlds

1. Export from the source world with the calendar checked.
2. Open the target world and enable Calendaria.
3. Import the file.
4. Leave Set as Active Calendar checked to switch to the imported calendar.

Version compatibility

Settings files carry version metadata. When the file came from another version:

• Settings that exist in both versions are imported.
• Settings the file does not contain keep whatever the target world already has.
• Settings removed from older versions are ignored.
• Values stored in an older shape are brought up to the current shape as they are imported.
• One-shot repairs that delete data are never replayed against an imported file.

A value the current release cannot accept is skipped rather than aborting the import. The count in the confirmation dialog is what the file offered; the count in the success message is what applied.

Troubleshooting

Import fails with an error

• The file must be a valid Calendaria export, containing a settings object.
• Check that the file is not corrupted.
• Export fresh settings and compare the file structure.

Calendar or notes did not import

Settings, the calendar, and the notes are applied in that order, and each stage reports its own result. A calendar or note failure leaves the settings that already applied in place. Re-running the import writes those settings again and skips notes that already exist, but it adds a second copy of the calendar.

A file whose calendar block has no name is rejected up front with the same generic format error as a malformed file.

Settings do not apply after import

• Refresh the page after importing.
• Check that all players have refreshed their browsers.