Skip to content

v0.3.89 — License probe stops blocking itself; a request journal you can trust; smaller logs and payloads

Choose a tag to compare

@FoxsterDev FoxsterDev released this 10 Nov 11:23
· 14 commits to main since this release

Why this matters

license-capabilities given the Unity executable path counted its own probe as a running editor and refused with licensing_busy, so batch validation could not start on a machine with no editor open. A scenario run that Unity had already started could come back as "not submitted", a Play Mode test run interrupted by its own domain reload looked abandoned and invited a replay, and a player build looked like a hung editor. Logs and payloads cost more than they had to: a console grep returned stack frames as matches, an offline unity_status_summary was about 23 KB, and a fully qualified component type made a whole prefab edit roll back.

What changed

Unity process detection and rollout tooling

  • A process counts as a Unity editor, worker or Hub launcher only when its executable is one. A Unity path in an argument, or a shell wrapper such as zsh -c <Unity path>, no longer matches. license-capabilities with the executable path now works when no editor is open.
  • The consumer rollout helper uses the same rule for its global process check. It ignores its own run directory inside a consumer workspace. It closes the VBCSCompiler servers its batch compiles leave behind. It accepts --expected-churn <glob> for files a batch import rewrites deterministically.
  • Launchers find a supported Python (3.10+) even when a GUI-spawned client puts an old system python3 first on PATH.
  • xuunity_setup_plan no longer blocks a session that already runs the requested release. It reads .mcp.json files in parent directories.

Request journal and dispatch

  • unity_scenario_run_and_wait separates dispatch from the wait. A failure while waiting returns scenario_wait_failed_after_dispatch (or scenario_wait_timeout) with scenario_run_submitted: true, the run_id and poll_scenario_result_do_not_rerun.
  • A Play Mode test run that its own domain reload interrupts, and that resumes, is journaled with resumes_after_domain_reload and retryable: false. Every request the host refuses before submission writes exactly one request_refused. A completed run past its time budget reports completed_after_runtime_budget and keeps its own verdict.
  • A raw -batchmode -runTests run writes Library/XUUnityLightMcp/state/cli_test_progress.json, and unity_status_summary reports it as cli_test_progress. It shows running, running_without_progress or process_exited_before_completion.
  • During a player build the bridge state says busy_reason: build_player. The host reports editor_busy_in_build with wait_for_build_player_to_finish instead of escalating to anr. unity_scenario_result answers from the persisted result while the editor is busy.
  • Batch runs end with one terminal record on every path, including a failed GUI fallback.

Scenario verdicts

  • A scenario whose first failure is a required UI step that found no node after a complete search is now a clean failed, with failure_class: precondition, instead of inconclusive.

Prefab authoring

  • unity_prefab_mutate and unity_prefab_create resolve componentType by full or assembly-qualified name, then by a unique short name. An ambiguous short name is refused as prefab_mutation_component_type_ambiguous, with the candidates.
  • A path miss names the prefab root and up to five nearest paths. A path without the root segment is accepted when it resolves to exactly one object.

Logs and payloads

  • unity_console_grep takes beforeLines / afterLines (0–20) for source: editor_log, inside the byte budget. Stack-frame lines are no longer matches unless includeStackTraces: true. messagesOnly: true returns just the messages. With an editorLogPath, the result reports explicit_path_requested: true.
  • The compact offline unity_status_summary dropped from about 23 KB to 7 KB on a real project. Compact unity_ui_query nodes dropped from 12.6 KB to 4.0 KB for ten matches. A prefab refusal before any change is 570 bytes instead of about 5 KB. includeFullPayload: true still returns everything.
  • Transport and lifecycle-reset errors honour includeFullPayload and name the MCP recovery tool. In a test's final status, elapsed_runtime_seconds now counts from the run start. A run that is still running never gets a Play Mode exit as a cleanup suggestion.

What this gives developers

  • Batch compiles, test runs and version matrices start on a machine with no editor open, without a workaround for the license probe.
  • Fewer false "not submitted", "abandoned" and "hung" readings, so agents stop replaying long suites or killing a busy editor.
  • Raw batch test runs and player builds are visible while they run.
  • Prefab edits accept the type names developers actually write.
  • Smaller console, status and UI results on the default path, so less context is spent on logs.

Validation

  • Host Python suite: 1475 tests passed, 14 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 237/237 and PlayMode core 6/6;
    • on 2021.3.58f1 also TextMeshPro 6/6, uGUI 79/79, and PlayMode uGUI with 22 passed and 6 skipped.
  • The matrix ran with the Unity executable path for the license probe, the case that returned licensing_busy before this release.

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 Windows .cmd and .ps1 launcher changes are covered by host tests and the Windows CI job, not by a live Windows editor run.
  • cli_test_progress and the build_player busy reason need this package version in the project.
  • A batch-mode Unity process killed hard (crash, SIGKILL) still leaves a healthy bridge state; only a normal quit writes process_exited.
  • Prefab snapshots do not carry full component type names; the validator's reference type check does.
  • run_unity_version_matrix.sh installs the server from the checkout it runs in, so running it from a branch replaces the shared install until you reinstall from the release checkout.