History, Saving, Refresh, and Recovery

The Editor · 11 min read

Know what is shared, what stays in your browser, how Undo and Redo differ from project versions, and what to do after a save or collaboration problem.

Use History, Undo, and Redo

Open Windows -> History to see supported edits from the current work session. Use Undo and Redo in the header for the previous or next available step. Read the action name before applying it when a large operation or multi-selection was involved.

History is not a permanent project backup. Closing or refreshing the Editor can end the current undo chain, and some one-shot processing operations have their own completion behavior. Use project versions for a durable checkpoint before risky reimport or broad terrain and raster changes.

What saves to the project

Shared project data includes imported layers, vector geometry and attributes, working terrain edits, editable raster content, markers and gameplay objects, bounds, persistent modifiers, road profiles and junction choices, islands, collection assignments, and saved model or object placements.

Many small metadata changes save automatically after a short delay. Geometry, raster, and terrain operations can take longer. Watch the status message and wait for saving or processing to finish before closing, refreshing, reimporting, or exporting.

What stays local to the browser

Local preferences include the active tool, tool settings, view toggles, hotkey choices, camera preferences, viewport preset, appearance, panel arrangement, and checklist progress. Saved cloud layouts can follow the account where the tier supports them, but choosing a layout still does not edit map content.

A collaborator can therefore see the same roads and terrain through different lighting, visibility, draw-distance, and window settings. Ask them to check the actual project state, not to match your exact screen arrangement.

Refresh and collaboration

Refresh reloads current project data and newly available assets. Use it after another collaborator finishes a change or after a background task creates a source you expect to import. Save or finish your own work first so a reload does not discard an in-progress gesture or dialog.

Avoid two people editing the same feature, terrain area, raster, road profile, or assignment at the same time. Divide work by layer or area, communicate handoffs, and refresh between them.

Recover from a save or connection error

Stop editing when the connection indicator or status message reports a save failure. Keep the tab open, restore network access, open the connection control for details, and use Retry when offered. Confirm that the error clears before making more changes.

If recovery does not succeed, record the project name, action, time, visible error, affected layer or feature, and a screenshot. Do not assume a change reached the project merely because it remains visible in the current tab. Refresh only after deciding that any unsaved local view may be lost.