For the complete documentation index, see llms.txt. This page is also available as Markdown.

Using SafeSave

SafeSave adds a single, context-aware button to your Main Toolbar. Here is how to read the signals.

🟢 Green: Synced

"You are Safe."

  • Status: Your file matches the server perfectly. You have no local changes.

  • Action: You are free to edit.

  • Pro Tip: Clicking the Green button performs a Force Refresh, querying the server to double-check for updates.

🟠 Orange: Push Changes

"You have unsaved work."

  • Status: You have modified an asset (Dirty), but it has not been sent to the team yet.

  • Action: Click the button to Save & Submit.

  • Behavior:

    1. SafeSave saves all dirty assets to disk.

    2. Safesave opens the native "Submit Files" window.

    3. Enter your changelist comment and commit.

🔵 Blue: Get Updates

"Your teammate updated this file."

  • Status: SafeSave detected that the server has a newer version of the map or asset you are currently viewing. You are looking at old data.

  • Action: Click the button to Download & Sync.

  • Behavior: Unreal performs a Sync operation, pulling the latest files and reloading the asset in your viewport.

i Info: The Blue Light relies on your Source Control plugin's ability to check IsCurrent(). For Git Users, SafeSave polls the network every 3-5 seconds to enforce this check.

🔴 Red: Safe Update

"STOP. Conflict Imminent."

  • Status: You have unsaved local changes AND the server has a newer version of the same file.

  • The Risk: If you Pull now, you lose work. If you Push now, you create a conflict/error.

  • Action: Click the button to run the Safe Update Protocol.

  • The Protocol:

    1. Force Save: Your local changes are saved to disk.

    2. Sync: SafeSave commands Unreal to pull the latest changes.

    3. Merge: Unreal detects the collision and opens the Visual Merge Tool, allowing you to merge the two versions safely.

Last updated