Client Server Build Compatibility
Define and verify the release contract that allows a game client and server build to operate together.
Guides and how-tos
These guides start with failure modes, ownership, and recovery. Tool choices follow from the studio’s actual constraints rather than becoming the goal.
Browse the library
Showing 8 of 8 resources
Define and verify the release contract that allows a game client and server build to operate together.
Establish deterministic export, validation, source-integration, and recovery boundaries for game-content pipelines.
Build a repeatable path for packaging, validating, promoting, and recovering dedicated server releases.
Choose between Horde, an improved existing CI path, or a narrow custom build system by defining operational boundaries first.
Define safe stream intent, integration ownership, policy gates, and recovery paths for Perforce automation with RoboMerge.
Map the source, builder, cache, artifact, and promotion boundaries behind a repeatable Unreal Engine delivery path.
Separate Unreal Engine Derived Data Cache from release artifacts with explicit keys, invalidation, provenance, and recovery behavior.
Create replaceable Unreal Engine build workers across Windows and Linux with explicit state, identity, and recovery boundaries.