Skip to content

v2.6.9 - real vrc_upload fix, exact project selection

Latest

Choose a tag to compare

@TunaSync-Studio TunaSync-Studio released this 02 Nov 15:12
· 2 commits to main since this release
128898b

Unity plugin + npm server release. Update both: a real vrc_upload needs the server (npm) and the Unity package (VCC) from this release.

Fixed

  • Real vrc_upload through MCP was always refused in 2.6.7–2.6.8 ("arm file not found"): the server consumed the human arm file before submitting the job while the plugin also required it. The Unity plugin is now the single consumer: it claims the arm under an exclusive lock once the VRChat SDK builder is ready, before anything is changed or built. One arm = one attempt, also across racing attempts and editors.
  • The server submits real uploads only to plugins that advertise vrcUploadArmClaim (PLUGIN_UPDATE_REQUIRED otherwise), checked on the connection that carries the submit.
  • Project selection could switch projects while an editor restarted (.../Avatar -> .../Avatar2): absolute paths are exact-only, relative paths match whole folder names, bare names prefer the exact project, and a selector keeps its meaning for the server session.
  • Creator Console and the upload gate use the same arm file and lifetime (UNITY_MCP_ARM_FILE / UNITY_MCP_ARM_TTL_MIN, capped at 1440 min); leftover claim locks are shown and cleared by Arm/Disarm.
  • macOS/Linux: server and plugin share the default registry/arm folder ($XDG_DATA_HOME or ~/.local/share).

Full details: CHANGELOG.md. Install: https://tunasync-studio.github.io/UnityMCP-VCC/