History panel

The History panel combines viewport edit history and modifier actions. Viewport history tracks terrain edits, vector geometry edits, and raster paint diffs. The panel shows the current cursor, saved cursor, and unsaved count.

Use history for recent editing mistakes. Use reimport only when you intentionally want to rebuild layers from source assets, because reimport can remove saved layers, modifiers, and generated placement metadata.

What saves to the project

Layer records are saved through project layer API calls. Creating terrain, vector, raster, and marker layers changes project layer data.

Manual raster paint saves by updating the manual raster asset content. Vector feature geometry saves back to project vector data. Marker and placed building transforms save through their editor data paths.

Editor metadata autosaves after a short debounce. This includes modifiers, terrain height overrides, terrain override grids, tree placement recipes and placements, building placements, electricity placements, road assignments, bounds, road junction settings, and Editor project settings.

What stays local

Some state is intentionally local to your browser: editor settings, hotkeys, camera state, hidden layer visibility, raster overlay display settings, raster paint labels, road builder preferences, and modifier dialog preferences.

Local state changes how your Editor feels and displays data. It does not change the project for teammates and should not be expected to affect exports.

Status messages and errors

The status strip reports save success, skipped operations, import progress, and failures. If a save fails, wait for the error to clear or retry the operation before exporting.

The refresh control reloads project data from the API. Use it when a background task has produced new assets or when another collaborator changed the project while your Editor was open.