Getting Started with Build Doctor

Unreal Engine build failures are notoriously difficult to debug. UBT and UHT output buries the actual issue under engine-specific noise, module dependency chains, and compiler output that generic tooling cannot interpret. Build Doctor exists to close that gap — it takes a failed build and returns structured, ranked findings with enough context for an operator to decide what to do next.

Build Doctor is a diagnosis workflow, not a code generator. It reads build output, classifies the failure, and packages the result as ranked findings with file, line, and module context. The output is designed for human review — it does not silently edit code or skip the operator decision.

• Classifies build failures into structured error families
• Packages ranked findings with file, line, and module ownership context
• Suggests reviewable next steps without mutating your code
• Works the same across CLI, MCP, VSCode, and CI surfaces

After installing Gamibase, point Build Doctor at a failed build log or let it capture a live build. The command is the same whether you are diagnosing locally or in CI.

# Diagnose a failed build from a log file
gamibase doctor --log BuildOutput.txt

# Or capture a live build and diagnose inline
gamibase doctor --target MyGame --platform Win64

Build Doctor reads the output, identifies the error family, and returns a structured diagnosis. Each finding includes the likely cause, the file and module scope, and a suggested next step that is easier to review than the raw log.

A Build Doctor diagnosis is not a wall of text. It is a structured evidence package with clear sections designed for fast operator triage.

Ranked findings

Findings are ranked by confidence and impact. The top finding is the most likely root cause. Each finding includes the error classification, the affected file and line, module ownership, and a description of why this matters.

Next steps

Every finding includes a reviewable next step. This might be a specific file to inspect, a configuration to check, or a patch to review. The key word is review — Build Doctor does not apply changes by default. The operator decides.

Build Doctor classifies failures into error families that map to real Unreal build issues. Understanding these families helps you anticipate what Build Doctor will surface and how to act on it.

• Include order errors — missing or misordered headers that cause cascading failures
• Module dependency breaks — circular or missing module references in .Build.cs files
• UHT reflection failures — incorrect UCLASS, UPROPERTY, or UFUNCTION macros
• Linker errors — unresolved symbols from mismatched module imports or missing libraries
• Config mismatches — target or platform settings that contradict the build request
• Plugin binding failures — engine or project plugins that fail to load or compile

Build Doctor is the entry point for most Gamibase workflows. A diagnosis grounds the operator in what actually went wrong before they decide on a follow-up action. This is why Project Intelligence, Code Review, and Feature Pipeline all benefit from running a diagnosis first — they inherit the structured context.

1. A build fails locally or in CI
2. Build Doctor diagnoses the failure and packages ranked findings
3. The operator reviews the findings and decides on a next step
4. If deeper context is needed, Project Intelligence provides module and symbol grounding
5. If a fix is needed, the operator reviews the suggested patch before applying

Build Doctor is available in the free Community edition. Core diagnosis, structured findings, and reviewable next steps work out of the box. Pro adds deeper execution capabilities — patch generation, symbol-level context, and crash analysis — for teams that need the full operator toolkit.