History, Scatter Brush & Project Health

Three smaller editor tools that the other guides assume you know about. Search the Command Palette for any of them.

History

History lists every edit you have made in the open scene, in order, with Now marking where you are. It is the visible form of Undo / Redo (Ctrl/⌘ + Z, Ctrl/⌘ + Shift + Z): click an earlier row to step back to that state.

A run of the built-in Agent folds into one row, named after the prompt (Agent · …). That row has a Revert button which takes the whole run back — the scene edits and the project files it wrote. Because files are involved, going back past a run asks first and says how many runs and files it will undo. This one cannot be redone. Anything too large to hold a copy of is listed and left as it is.

After a run, History can offer Keep this check: a verification the run passed — the scene has nothing flagged, or the scripts compile — that you can pin to the project. Every later run is measured against it, and no run can weaken or remove it.

Scatter Brush

The Scatter Brush dresses a scene — rocks, trees, grass tufts — by dragging in the viewport instead of placing each copy by hand. Arm it from the Command Palette (Scatter Brush); its panel opens on the left. Arming it again, or pressing Esc, puts it away.

1. Select the entity to scatter and press Use Selected (Source shows what is armed). Without a source the panel says Select an entity to scatter.

2. Set the Brush:

   Setting	What it does
   Radius	How wide a disc one stroke dabs.
   Density	How many copies fall inside the disc.
   Spacing	The minimum gap between copies, so they never pile up.
   Scale Variation	Random size spread per copy.
   Random Turn	Random facing per copy.

   The preview shows one sample: the disc, the copies it would drop, and the spacing each keeps.

3. Drag in the viewport. Each stroke is one undo step and reports Scattered N.

The Scatter Around command fills the spot the selection stands on without a stroke — “more of this, here”.

Project Health

Project Health is the checklist the editor runs over the project before you build, and the same one Build → Package Project… runs first — a blocker stops the build. It covers things like asset references that resolve to nothing, an empty required field on a component, a missing entry scene, scripts that do not compile, unsaved changes that would not be in the build, a target that cannot be built on this machine, and viewport fallbacks (HDR, MSAA). It sits in the bottom dock and groups what it found:

• Blocks the build — fix before packaging.
• Warnings and Notes — worth a look, not fatal.
• Could not be checked — the editor lacked what it needed (a connected device, a toolchain); this is not a pass.

Some entries carry a Fix button that applies the repair for you; if it cannot, the panel says why. Re-check runs it again, and the panel tells you when the project changed since the last check. A clean result reads Nothing is standing in the way of a build. The same list is available to automation as get_project_health in the editor MCP.