Most co-development hand-offs go wrong in a boring place: version control. Code merges are a solved problem, but game projects are mostly binary files - scenes, prefabs, Blueprints, textures, audio banks - and two people editing the same binary file at the same time means one of them loses a day of work.
It gets sharper when the new team sits in a different time zone. A partner pod in Bengaluru or Pune working India hours overlaps with a UK studio for a few hours in the afternoon and with a US West Coast studio barely at all, so "just ping them before you open the level" stops working. The rules have to live in the tooling.
This is the checklist we run through in the first week whenever an outside team is added to a project that is already in production.
1. Decide which file types are exclusive-checkout
Write the list down rather than assuming everyone knows it. A typical starting point:
- Unity:
.unity,.prefab,.asset,.controller,.anim, lighting data - Unreal:
.umap,.uasset(all of them, unless you use One File Per Actor for levels) - Source art:
.psd,.blend,.fbx,.ma,.spp - Audio middleware banks and project files
Anything on this list gets locked before it is edited. Text files (scripts, config, shaders) stay mergeable.
2. Make the tool enforce it
Perforce: set the +l (exclusive open) filetype modifier in the typemap so locking is automatic, not a habit:
TypeMap:
binary+l //depot/....uasset
binary+l //depot/....umap
binary+l //depot/....psd
Git with LFS: mark the patterns lockable in .gitattributes:
*.uasset filter=lfs diff=lfs merge=lfs -text lockable
*.umap filter=lfs diff=lfs merge=lfs -text lockable
*.prefab filter=lfs diff=lfs merge=lfs -text lockable
Lockable files check out read-only, so people have to run git lfs lock <path> before the editor lets them save. Check that your host supports the LFS locking API before you rely on it.
If you use Unity's YAML scenes and prefabs, decide explicitly whether you are locking them or merging them with UnityYAMLMerge. Mixing both approaches across two teams is how scenes get corrupted.
3. Agree a lock etiquette that survives the time difference
Tooling stops collisions; etiquette stops a lock from blocking the other team overnight.
- Never leave a lock open at the end of your day unless the file is genuinely mid-change. Release or submit before you log off.
- Put a reason in the lock or changelist description ("lighting pass on Level_03, until 18:00 IST").
- Decide who can break a stale lock, and that they message the owner first. A lock held by someone asleep eight time zones away should not stop a milestone.
- Run a daily report of locks older than 24 hours and post it in the shared channel.
4. Split the content so teams rarely need the same file
The best lock is the one nobody needs. Before work starts, carve the project so each team owns its own files:
- Use sub-levels / streaming levels (Unreal World Partition with One File Per Actor, or additive scenes in Unity) so environment art, lighting and gameplay scripting are in different files.
- Give the partner team its own folders for new content and a clear rule for touching shared folders.
- Prefer nested prefabs or child Blueprints over editing shared master assets.
5. Give the new team the right access, not all access
- Branch or stream permissions so the partner works in a development stream and integrates through review.
- Read-only access to areas they do not own (shared core systems, release branches).
- A named reviewer on the home team for every integration, with review windows inside the overlap hours.
6. Make the build tell you when something slipped through
- CI that fails on missing references and unresolved redirectors after every submit.
- A nightly build both teams look at first thing in their morning, so a broken asset is caught by whoever wakes up first rather than at the next standup.
- A short, written rollback procedure for a bad binary submit.
7. Write it all into the definition of done
"Done" for a content task should include: lock released, changelist described, references validated, and the nightly build green. When this is part of the definition of done, nobody needs to remember the rules - they are just part of finishing the ticket.
A note on briefs
Version control rules cover the files; the brief covers what goes into them. If you are handing art to an outside team as well, we wrote up what a usable art brief should contain here: How to write a game art brief an outside team can deliver on.
At Juego Studios we join existing productions as an embedded pod for a specific milestone, so this checklist is usually the first thing we agree with a client team. If you are weighing up a game co-development partner for an in-flight project, sorting out locking and ownership before day one saves more time than any other single step.
What rules does your team use for binary assets across time zones? I would like to hear what has worked for you in the comments.
Top comments (0)