Source control

Check file status and history, revert files and mark new files for add.

What it’s for

Ask your assistant about the version-control state of your content. It uses whatever provider the editor is already connected to, such as Perforce, Git or Subversion. It can tell you which assets are checked out, added or modified, show an asset’s history, discard local changes, and mark new files for add.

The most common use is a safety check around edits. Before your assistant changes a Blueprint or a material, it can check the file’s status. Afterward it can revert the changes you do not want, or mark new assets so they are tracked. You can also ask questions like “when did this asset last change?” without leaving the editor.

It goes through the editor’s own source-control connection, so it sees exactly what the editor sees. If no provider is connected, these requests have nothing to act on.

Things you can ask

Check what changed, then revert the rest

Your assistant checks a set of assets and discards the ones you did not mean to touch.

You: I only meant to edit BP_Player. Revert anything else that got dirtied.

BP_Player, BP_Enemy and M_Floor were all checked out. I reverted BP_Enemy and M_Floor and left BP_Player checked out.

Track a new asset

A newly created asset is marked for add so source control tracks it.

You: Add the new material I just made to source control.

Marked /Game/Materials/M_Water for add in Perforce.

Look up an asset’s recent history

You get the last few revisions of one asset, with who changed it and when.

You: When was BP_Door last changed, and by whom?

The latest change is revision 14 by amy on 2026-06-30. Before that: revision 11 by sam on 2026-06-18 and revision 9 by amy on 2026-06-02.