Build History and Restore

InstanceForge stores build history so generated instances can be inspected and restored.

Build history is also the safety layer behind delete-after-backup workflows.

Instances overview

Open the Instances tab after building.

Use it to inspect:

• active build records;
• history and rolled-back records;
• selected build details;
• generated component counts;
• source actor/component counts;
• restore availability.

Restore flow

Select a build or generated component, inspect restore availability, then choose the matching restore action.

Main actions

What build records store

Each build appends a record to the map build history actor.

A record can include:

• build id;
• map package name;
• UTC build date;
• settings snapshot;
• build status;
• source actor/component restore records;
• generated actor/component records.

Source backup strategy

Build history stores data needed for restore or recreate workflows.

Source records can include:

• source actor path and class path;
• actor label and tags;
• component name/path;
• Static Mesh reference;
• material slot assignments;
• world transform;
• visibility and hidden-in-game state;
• mobility;
• collision profile;
• cast shadow;
• component tags.

Changed actor/component property overrides may be captured when they differ from their archetype/default.

What restore does

Restore Selected Build performs best-effort recovery for the selected active build:

1. Removes generated actors/components for that build.
2. Restores hidden source components/actors.
3. Recreates deleted simple AStaticMeshActor originals when enough backup data exists.
4. Updates the build record status.

If no manual selection is available, InstanceForge can fall back to the latest active build record.

Delete and restore safety

Use Delete safe originals after backup only after you have verified restore.

Safe rule:

1. Build with Hide originals after build first.
2. Confirm generated instances look correct.
3. Confirm build history exists.
4. Test restore on a safe sample.
5. Use deletion only after validation.

Warning: Deleted custom actor behavior cannot always be reconstructed unless enough data was captured in build history.

Next steps

• Plan and Build
• Troubleshooting
• Known Limitations