> For the complete documentation index, see [llms.txt](https://gregorigin.gitbook.io/safesave/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gregorigin.gitbook.io/safesave/overview/introduction.md).

# Introduction

### Welcome to SafeSave!

{% embed url="<https://youtu.be/GvxXqw3H9oo>" %}

**SafeSave** is a workflow tool designed to remove the anxiety from working in Unreal Engine teams. It replaces complex Source Control menus with a simple **Traffic Light** system that lives directly in your main toolbar.

It acts as your "Air Traffic Controller," constantly monitoring your project to answer three questions:

1. Is it safe to save?
2. Did a teammate just push code?
3. Are you about to overwrite someone's work?

***

#### **Core Features**

* **🟢 Visual Status:** Know instantly if you are Synced, Dirty, or in Conflict.
* **🔵 Update Detection:** The "Blue Light" warns you if a teammate has pushed code before you start working.
* **🔴 Conflict Prevention:** The "Safe Update" protocol helps you merge changes without breaking the build.
* **🔒 Billy Lock:** Instant, non-blocking notification when you open a file locked by another user.
* **⚡ Zero Latency:** Runs on a background thread (ActiveTimer); does not consume game-thread tick cycles.

#### **Supported Providers**

| Provider          | Status       | Notes                                             |
| ----------------- | ------------ | ------------------------------------------------- |
| **Perforce (P4)** | ⭐ Best       | Instant lock detection & status updates.          |
| **Git (Beta)**    | ✅ Verified   | Requires remote repo for Blue Light features.     |
| **PlasticSCM**    | ✅ Verified   | Works natively.                                   |
| **Diversion**     | ✅ Compatible | Works via the standard Unreal Source Control API. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gregorigin.gitbook.io/safesave/overview/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.