Expertise 06 / Build, Content & Tools

Infrastructure should shorten the feedback loop

I design build, content, editor, and test workflows so developers can reproduce production behavior locally instead of waiting for external machinery to tell them whether the game works.

01 / Principles

Delivery without sacrificing
developer iteration

Reproducible locally

A developer can select a configured asset and run the same Unity-owned build pipeline that CI invokes with command-line parameters.

Composable steps

Independent tasks replace a growing hardcoded script, making individual pipeline stages understandable, reusable, and testable.

Content as architecture

Asset layout, references, versioning, assembly, content updates, delivery, and runtime loading are designed as one system.

02 / Evidence

Pipelines and tools
used in production

D.A.W.Studio / Studio-wide delivery

Reproducible Unity-owned CI/CD

  • Built the first complete version of the local/CI approach used in later work.
  • Kept project build logic inside Unity rather than making the product dependent on a CI server.
  • Used the same configured parameters for developer and build-machine output.
  • Owned asset organization, content build workflows, and delivery across studio projects.

Combat Master / Content Update

Asset build and delivery architecture

  • Designed asset layout, bundle versioning, assembly, and content delivery.
  • Integrated the content system with Google Play Asset Delivery, including Android Play Asset Delivery support.
  • Kept the main build script, but moved content-bundle assembly out of it.
  • Replaced that part with a modular pipeline of independent tasks shared by local and CI builds.

Pixel Gun 2 / On-demand content

Addressables-based migration

  • Migrated the project's on-demand asset build and loading flow onto an Addressables-based pipeline.
  • Modernized surrounding project systems while preserving production continuity.
  • Kept map and game-mode structure independently replaceable, reducing the cost of testing content combinations.

Flexy.Fun / Reusable packages

Tools extracted from recurring needs

  • Flexy.AssetRefs provides explicit asset-reference workflows and its public version now works with Unity ContentDirectory.
  • The first Flexy.Bundles architecture was adopted by Combat Master and remains in use there; newer independent work is not yet publicly released.
  • Flexy.GameFlow and Flexy.UI package parts of the wider architecture and production approach.
  • Project templates include CI-independent versioning that behaves consistently locally and on build machines.
  • Unity ContentDirectory was selected for a current partner workflow where it was simpler and more appropriate than extending older bundle infrastructure.

Cubic and D.A.W.Studio / Direct startup

Iteration is also tooling

  • At D.A.W.Studio, projects could start directly in a required gameplay or test state in roughly one to two seconds.
  • At Cubic Games, enabled Play Mode, local host, and client startup directly from gameplay maps with synchronous frame-0 initialization.
  • The earlier direct-start approach began on Cyberstrike and Animals Happy Run; a partial adaptation in Pixel Gun still reduced navigation, even though unrelated startup paths kept total time closer to ten seconds.

Plarium and GSC / Editor productivity

Purpose-built production tools

  • Motorplanet's track builder let designers drive any greybox section before handing a track to art.
  • For S.T.A.L.K.E.R. 2, built an editor framework with a property grid, curve editor, and foundational node editor.
  • At Sonelly, created a JSON scene description with hierarchy, components, loading, and persistence for a custom C#/XNA engine.

Serious Cake / Age of Phoenix

Faster UI production and smaller builds

  • Streamlined the Unity UI production pipeline to accelerate feature implementation and iteration.
  • Reduced build size while also improving runtime performance.
  • Kept primary ownership of the Unity client while contributing selected Akka.NET backend work.

03 / Feedback loop

The build is only one part
of production speed

I treat setup time, direct game-state entry, local server access, content rebuilds, test scenes, editor tools, versioning, and CI reproducibility as one developer-experience problem. A technically correct pipeline that requires a remote build for every useful check still damages production.

  • Local builds must exercise the same code path as CI.
  • Content and CDN behavior must be testable without turning every iteration into a release operation.
  • Client/server projects need local launch paths for both sides.
  • Individual architectural units need dedicated development and test scenes.
  • Versioning must remain consistent without relying on a CI-specific build number.

04 / Outcomes

What better tooling changes

1–2 sec

Direct entry into a useful state in the most streamlined projects.

Local = CI

The same Unity-owned process and parameters build the product.

Frame 0

Synchronous map startup establishes the required state immediately for Pixel Gun 2 development.

Modular tasks

Content assembly evolves without expanding one monolithic build script.

05 / Relevant stack

Build, content, and editor systems