Big worlds.
Small changes.
Version control for game makers. Large assets, shared history, and your team in sync.
Built for big assets
Transfer the chunks that change.
One source of truth
An authoritative server. A shared history.
Your work, protected
Recovery comes before replacement.
BIG ASSETS. CONSIDERED TRANSFERS.
Move your world.
Transfer the change.
Upload only missing chunks. Reuse local data on sync. Verify every reconstructed file.
THE WHOLE TEAM. THE WHOLE PROJECT.
It all comes together.
Branches without asset duplication.
Branch the metadata, share the assets. Merge only the paths that diverge.
Just your part of the world.
Sync the characters, audio, or code you need with selective workspace views.
Lock the assets that need it.
Repository-wide locks protect shared assets. You decide how binary conflicts resolve.
Your servers. Your permissions.
Shared identities, clear repository roles, and revocable tokens over TLS 1.3.
Storage and transfer, your call.
Independent LZ4 compression for storage and transfers. Incompressible data stays raw.
Built for your pipeline.
Revision exports, JSON output, integrity checks, and verified backup and restore.
One project. Every possibility.
- Worlds & scenes
- Textures & materials
- Code & everything else
A SHORT PATH FROM IDEA TO SHARED HISTORY.
Change. Submit. Sync.
Make it yours
Open a tracked file for editing.
scribe edit Assets/world.sceneMake it history
Publish the change to the server.
scribe submit -m "Build a new world"Bring everyone along
Bring a teammate's working copy up to date.
scribe syncTHE NEXT CHAPTER