Locks
Most game assets (.uasset, .umap, textures, audio) can't be merged: if two people change the same one, one person's work is lost. LodeBase prevents that with exclusive locks: you check a file out, everyone sees that you have it, and nobody else can submit it until you're done.
Which files need a lock
A .lodeattributes file at the root of the repo (it's versioned like everything else) decides:
*.uasset *.umap lock binary
*.wav *.png *.fbx lock binary
Content/Sandbox/** -lockFiles marked lock must be locked before you submit a change to them; binary tells LodeBase not to try line-by-line merges. -lock turns locking off for a folder (scratch areas). Later lines win.
Taking and releasing locks
sh
lode lock Content/Maps/L_Arena.umap # updates the file to the latest version first if needed
lode unlock Content/Maps/L_Arena.umap
lode unlock # every lock this workspace holdsIn the Unreal Editor, Check Out takes the lock, and the editor asks when you start editing a file that needs one. Submitting releases the locks on what you submitted.
Locking first brings the file up to date, so you never start editing an old version.
Who has what
sh
lode locks # everything locked on this branch
lode who Content/Maps/L_Arena.umap # who has it locked, and who has it openThe editor shows badges on assets, and the tray lists your own locks. Locks held by a workspace that hasn't been seen for a while (72 hours by default) are marked stale.
Breaking a lock
If someone left for the weekend holding a file you need, a maintainer can break it:
sh
lode unlock --force Content/Maps/L_Arena.umapThey're notified in the tray, and it's recorded. Their local edits stay on their computer; they'll need to redo them on the new version or hand them over.
Locks and branches
Locks are per branch: a lock on main doesn't stop someone changing the same asset on a task branch. The merge then shows it as a conflict. For assets, prefer working on the same branch with locks.