When part of an Unreal Engine team sits in India and the rest sits in London, Austin or Toronto, the nightly build stops being a convenience and becomes the main way the two halves talk to each other. If the build that lands at 9:30 am IST is broken, the Bengaluru or Pune side loses its morning; if the one that lands for the US or UK morning is broken, the other side does.
The time-zone gap can genuinely be an advantage, because work keeps moving around the clock. But only if the handoff is boring and predictable. This is the checklist we would want a split team to agree on before relying on a follow-the-sun build.
1. Agree on one cut-off time, written in both time zones
Pick the moment the nightly build takes its changelist and write it down as both, for example "18:30 IST / 13:00 GMT / 08:00 EST". Put it in the channel topic and in the build job description. Most "your change wasn't in the build" arguments come from people assuming a different cut-off.
Remember that the UK and US shift their clocks twice a year and India does not, so the gap moves by an hour. Review the cut-off on those dates instead of discovering the change from a missing build.
2. Make the build machine the only source of truth
Every artefact the other side uses (packaged builds, cooked content, symbols) should come from the CI machine, not from someone's workstation. That means:
- A clean sync to the cut-off changelist in Perforce (or a tagged commit in Git LFS).
- The same engine version for everyone. If the team uses a source build of Unreal, the build machine compiles that exact engine revision too, and the version string goes into the build name.
- Derived Data Cache settings that the build machine and both offices understand, so a shared DDC in one region does not make the other region's editor crawl.
3. Split the pipeline into stages that fail loudly
A single "BuildAll" step that runs for three hours and fails at the end is the worst possible handoff. Break it up:
- Compile editor and game targets.
- Run automated tests (even a small smoke set using the Automation framework or Gauntlet).
- Cook content for each target platform.
- Package, archive and upload symbols.
Each stage posts its result to the shared channel. When stage 2 fails at 19:00 IST, someone in India can still fix it before leaving, rather than the UK team finding a red build in their morning.
4. Attach a short, human-written handoff note
Automation tells you whether the build passed; it does not tell you what changed that matters. Ask whichever side closes the day to write five lines:
- What landed today that the other side should test first.
- Anything known to be broken, with the ticket link.
- Any asset or map that is checked out or locked overnight.
- Who to ping if something blocks them, and when that person is back online.
- Any change to the cut-off or to engine/plugin versions.
Five lines in a predictable place beat a 40-message thread.
5. Lock binary assets deliberately
Unreal .uasset and .umap files cannot be merged. If a level designer in Manchester and an environment artist in Hyderabad both edit the same map overnight, one of them loses work. Use exclusive checkout for binary files, use One File Per Actor (World Partition) where it fits so people can work on the same level without colliding, and make "release your locks before you log off" part of the end-of-day routine.
6. Plan for the network you actually have
Large syncs and build uploads that are fine on an office fibre line can be painful over a home connection during a monsoon outage or a power cut. A few cheap safeguards:
- An edge server or proxy close to each office so syncs do not all cross continents.
- Resumable uploads for packaged builds.
- A smaller "playable" package for quick checks, separate from the full archive.
7. Write down who owns a red build
Decide in advance: if the build breaks after the India day ends, does the UK or US side revert the offending change, fix forward, or wait? There is no universally right answer, but there must be an answer. Otherwise a broken build sits untouched for a whole cycle while each side waits politely for the other.
8. Keep platform builds on the same rhythm
If the game targets consoles as well as PC or mobile, do not let platform packages drift to "whenever someone remembers". Certification-style problems (save data, suspend/resume, controller disconnects) are much cheaper to catch in a nightly than in the final month. We wrote up the console side of this separately in a pre-cert checklist for porting a PC or mobile game to console.
Closing thought
A split Unreal team works best when nobody has to be awake at an odd hour to unblock someone else. That comes down to a fixed cut-off, a build that fails early and loudly, and a short note that travels with it.
If you are planning to extend your team with dedicated Unreal Engine developers in another time zone, agree on these eight points in the first week, before the first nightly build goes out.
Written by the team at Juego Studios, a game development studio.