1
Register and sign in
Use TGS ID when it is configured for the server. Local email/password remains available as a fallback for isolated deployments.
TimeGit v1
One place to register, download the client and work safely with Unreal Blueprints in Git.
TimeGit keeps `.uasset` and `.umap` files exclusive across the team. The UE 5.4 plugin notifies the local Windows client, the client updates the server, and everyone else sees which Blueprint is busy before they lose work.
2
Download the Windows client
The site gives every authenticated user the Windows bundle. The client clones from the hosted TimeGit remote repository and keeps Git/LFS auth aligned with your account session.
3
Accept a project invite
Project access comes through invite-links. Once accepted, you see the project page, clone URL and the matching UE 5.4 plugin package.
4
Edit Blueprint safely
When you edit a Blueprint, the plugin requests a lock. Other users can inspect the asset, but save is blocked until the owner submits and everyone else syncs.
Projects visible
0
Invite-based access keeps projects private.
Active locks
0
Repo-wide exclusive locks for Unreal binary assets.
Open assets
0
Presence heartbeats from UE tell the team what is being used right now.
Save rule
Sync first
If another user already submitted a new Blueprint version, local save stays blocked until sync.
Blueprint flow
What happens in a conflict
User A
Opens `BP_Door.uasset` for edit, plugin requests a lock and sends edit presence through the local client.
Server
Stores the lock, broadcasts presence and remembers the current asset revision so everyone else sees the Blueprint as busy.
User B
Can inspect the asset, but when save is attempted the plugin asks TimeGit to validate save and shows a blocking modal instead of writing a conflicting binary revision.