History and Activity
Two panels float over the bottom left of the 3D view. Each starts as a small square with an icon and a count. Click the header to open or close it. Drag the header to move the panel, and drag its right edge to make it wider. The editor remembers where you put them.
History
History is in the Terrain and Objects modules. Each module has its own list, because each has its own undo.
- Entries are listed newest first, with a name such as Painted 12 tiles with Grass, Raised 8 tiles, Edit health of Footman or Delete Footman.
- Click an entry to jump the map to that point. You can go back or forward.
- Entries newer than the one you jumped to are dimmed. They stay available until you make a new change, which drops them.
- A search field filters the list by name.
- The count on the collapsed icon is the number of entries.
Undo and Redo in the top bar walk through the same list one step at a time.
What History covers:
- In Terrain, every brush stroke. The list keeps the last 500. At the bottom, Opened is the map as you found it.
- In Objects, placing, moving and deleting objects, owner and facing changes, edits of definitions (typing in one field is merged into one entry), and a model rename done in Imports.
What it does not cover: players, scripts, shaders, and the files in Imports. Those change files directly. The history is also not saved with the map. It starts empty each time you open it.
Activity
Whenever the editor shows you a toast, it also writes the message to Activity. Toasts disappear after five seconds. Activity keeps them.
- Each entry has a tick or a cross, the time it happened (in UTC) and the message.
- Some entries have detail lines, shown as a count and an arrow. Click the entry to unfold them. A migration lists what it filled in. An import lists each texture that came along and each file that was renamed. A failed script build lists the compiler output, with the line numbers. A shader that does not compile gets the compiler's message.
- The header counts the entries, and the problems among them.
- Clear empties the panel. It does not touch the log file.
- The panel holds the last 500 entries.
When something goes wrong, look here first.
The log file
Each entry is also appended to activity.log in the editor's data folder (see Files of a map for where that is). The file is shared by all maps. It stores the time in UTC, then info or error, then the message, with the detail lines indented under it. When it grows past 1 MB, the editor moves it to activity.log.old and starts a new one.
Not built yet
Local versions of a map, meaning checkpoints you could restore an hour later, exist in the map library but the editor does not make or show them yet. There is no timer, no list of versions and no Restore button.