Building the Mesh: M1 Air to Shadow PC Pipeline

TL;DR: I’m currently based out of Kuala Lumpur, but the heavy lifting happens elsewhere. I’ve established a Zero-Trust, transcontinental routing mesh: M1 Air fswatch + rsync -> Shadow PC -> Aura headless P4D (SSL Port 1666) -> UE5.

When you’re building a massive procedural horror game like All Hallows, you cannot rely on local storage or fragmented environments. My primary hardware array is highly distributed: an M1 Air acts as my lightweight command center (driving Cursor, Gemini, and Veo), a Shadow PC handles the Unreal Engine 5.7.4 heavy lifting, and an M2 Max sitting elsewhere acts as my dedicated Audio/FCP rig.

The linchpin holding this together is Tailscale and strict Perforce (P4V) discipline. There are absolutely zero local roots allowed in this project (FPaths::ProjectDir() only).

If you map an absolute C:/ drive path, the mesh breaks. If you forget to check out a binary from the Singapore VPC, the mesh overwrites you. It is a harsh, military-grade pipeline, but it ensures that the “Single Source of Truth” remains entirely insulated from hardware failures or location changes.