Skip to content
Development
Command

/unity-build

Configures and triggers Unity builds via MCP — handles platform settings, scenes, player settings, and monitors build progress.

From plugin
everything-claude-unity
2427 skills20 agents27 commands
Install
> /plugin marketplace add XeldarAlz/everything-claude-unity

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/unity-build

Context preview

What this command does when you run it.

Configures and triggers Unity builds via MCP — handles platform settings, scenes, player settings, and monitors build progress.

Command definition

unity-build.md
name: unity-build
description: "Configures and triggers Unity builds via MCP — handles platform settings, scenes, player settings, and monitors build progress."
user-invocable: true
args: platform

/unity-build — Build the Project

Configure and trigger a build for the specified platform.

Target

If the user specified a platform: build for **$ARGUMENTS** If no platform: ask the user which platform to build for.

Workflow

Use the `unity-build-runner` agent to:

Step 1: Pre-Build Checks

1. **Check console** via `read_console` — abort if compilation errors exist 2. **Check project info** via `project_info` resource — current platform and Unity version 3. **Validate build scenes** — ensure all scenes in build list exist 4. **Run code quality check** — look for `UnityEditor` namespace leaks

Step 2: Configure Platform

Switch platform if needed via `manage_build`:

  • Set player settings (company, product name, version, bundle ID)
  • Configure platform-specific settings:
  • **Android**: API level, IL2CPP, ARM64, keystore, AAB format
  • **iOS**: signing, bundle ID, minimum version, target devices

Step 3: Build

manage_build action:"build" → trigger the build
read_console → monitor progress and catch errors

Step 4: Report

  • Build result: SUCCESS or FAILURE
  • Build size (if available from log)
  • Warnings from build log
  • If failed: error details and suggested fixes
  • Next steps: where to find the build output

Common Build Fixes

| Error | Fix | |-------|-----| | `UnityEditor` namespace | Add `#if UNITY_EDITOR` guard | | Missing type/assembly | Check `.asmdef` references | | Stripping removes code | Add entries to `link.xml` | | Build too large | Run `/unity-optimize` or `analyze-build-size.sh` |

Read more
Ships witheverything-claude-unity

The ultimate Claude Code toolkit for Unity game development. A production-ready, plug-and-play system that gives Claude Code deep Unity expertise — from writing performant C# to building scenes, profiling performance, and triggering iOS/Android builds — all

Get the whole plugin

Other commands on everything-claude-unity.