Skip to content

v0.3.90 — Dead batch processes stop looking alive; the version matrix keeps your MCP install and runs uGUI everywhere

Latest

Choose a tag to compare

@FoxsterDev FoxsterDev released this 10 Nov 15:45

Why this matters

A batch-mode Unity process killed hard (SIGKILL, crash) left a healthy bridge state behind, and the host read that file as a live non-main owner: requests to the real editor were refused with bridge_owned_by_non_main_process until someone deleted the file. The readiness timeout for an editor whose bridge never attached told agents to restart, while setup said to poll first. Running the Unity version matrix from a branch silently replaced the host's shared MCP install, so every MCP session started afterwards ran that branch. On Unity 6000.x the matrix never compiled the uGUI self-tests, and prefab snapshots gave only short component type names, so two components that share a name could not be told apart before an edit.

What changed

Dead batch processes

  • A bridge state written by a batch process that is gone no longer reads as a live non-main owner. Discovery sets bridge_state_writer_exited and treats the file as stale, so a live main editor is routed normally and an empty project reads stale_bridge_state.
  • Health views report process_exited for a dead batch writer and editor_not_running for any other dead writer; the file's own value stays visible as recorded_health_status.
  • A batch writer pid that is alive but now belongs to another process counts as exited too (bridge_state_writer_pid_reused). Without process visibility the host does not claim either way.

Readiness guidance

  • The editor_not_ready_bridge_not_attached timeout now says to poll first and restart only once import has settled without attachment, with the same restart_criterion as setup. It sets attachment_pending_predates_install (with attachment_pending_basis) when the editor was opened before the manifest change, and adds the focus or Assets > Refresh hint.

Prefab snapshots

  • unity_prefab_snapshot with includeFullPayload: true returns component_type_full_names: one row per node with the namespace-qualified type of each component, in components order. The default snapshot is byte-for-byte unchanged.

Version matrix and self-tests

  • run_unity_version_matrix.sh installs the checkout into a per-run sandbox (<run>/host-install) instead of the host's neutral and Claude/Codex installs. --use-host-install opts back in.
  • The matrix adds the uGUI lane packages to every created project, so the EditModeUgui self-tests now compile and run on 6000.x. --no-ugui skips it.
  • The blank-prefab render self-test checks pixels only when a graphics device is present, so it no longer fails under -nographics.
  • The recovered Play Mode completion path has EditMode tests, including an end-to-end one that runs under a thread-local project-root override and never touches the live test-run file.

What this gives developers

  • A crashed or killed batch run no longer blocks the next request to the real editor.
  • One consistent answer on whether to wait or restart when the bridge has not attached yet.
  • Matrix runs from a branch no longer change which MCP code your other sessions use.
  • uGUI behaviour is tested on every supported Unity line, not only 2021.3.
  • Component types can be disambiguated before a componentType prefab edit.

Validation

  • Host Python suite: 1508 tests ran, 1490 passed, 18 platform skips.
  • Package self-tests in clean generated projects, package from local source, macOS, on Unity 2021.3.58f1, 2022.3.62f3, 6000.0.58f2, 6000.1.13f1, 6000.2.14f1, 6000.3.23f1, 6000.4.4f1, 6000.5.10f1 and 6000.6.0b3: EditMode core 240/240, TextMeshPro 6/6, uGUI 79/79, PlayMode uGUI 22 passed and 6 skipped, PlayMode core 6/6 on every version.
  • The matrix ran in its new per-run install sandbox; the host's shared MCP install was identical before and after.
  • A live kill -9 of a batch Play Mode run on Unity 6000.0: the state file still said healthy, and the host reported process_exited and stale_state.
  • CI now also runs the launcher interpreter discovery with an old Python 3.9 first on PATH, on Windows and Linux.

Known limitations

  • Unity Package CI remains waived (no runner Unity license); the local licensed runs above are the package evidence.
  • Live Unity runs were on macOS only.
  • The reused-pid rule needs process visibility; where the host cannot list processes, a reused batch writer pid is not reclassified.
  • Prefab snapshot nodes themselves still carry short type names; the full names are in the separate component_type_full_names rows.