Creator Project Setup 0.3.7

Creator Plugins catalogue and import reliability update.

• Refresh and validate the shared community catalogue before downloading or sending a package to Unity.
• Keep pending-import status visible when returning from Unity, and clear obsolete warnings when starting a new action.
• An unchanged package is no longer rejected just because an approval took longer than the catalogue cache timeout. Changed or withdrawn listings still require fresh approval.
• Unity catalogue helper 0.1.3 correctly handles listings without downloadable archives, including OptiC's Warehouse Loft. All apps and the Unity window use the same community catalogue.
• Exact known older Unity helpers can be upgraded with backups. User-modified helpers are not overwritten.

Existing Unity projects need their catalogue helper updated through Add Unity menu to receive the Unity-side changes. Updating the desktop app alone does not overwrite project files.

Validation included real native Unity package cancellation and retry on Unity 2022.3 and Unity 6 using disposable text-asset fixtures. This does not guarantee every community package is safe or compatible with every project. Back up your project before importing.

Windows, macOS Apple silicon, macOS Intel and Linux packages are provided. macOS packages use ad-hoc signing, not Apple notarization; platform security prompts may still appear.

Creator Project Setup 0.3.6

Creator Project Setup 0.3.6. Includes the updated terms acknowledgement, contextual help, and packaging fixes. Windows x64 installation and upgrade from 0.3.4 passed disposable-machine tests with user data preserved. macOS Apple silicon and Intel DMGs passed architecture and ad-hoc signature checks. Linux packages were built in CI. macOS and Linux Unity project workflows still need native user acceptance; these builds are not Apple-notarized. See SHA256SUMS.txt for asset checksums.

Creator Project Setup 0.3.4

Portable Creator SDK Unity project setup. Windows is the first physically tested platform; macOS and Linux are preview packages until their Unity workflows receive native acceptance testing.

Creator Project Setup 0.3.1

Windows update: fixes Add Unity menu remaining blocked by a stale Unity lock file. Plugins gains preview galleries, streamed large-package downloads, progress and cancellation. Hub integration requires Creator Hub 0.1.7 or newer. Standalone use remains available.

Installed upgrade and native lifecycle checks. Package integrity checks do not establish code safety.

Creator Project Setup 0.3.0

Creator Project Setup 0.3.0

The coordinated Windows release with Creator Hub 0.1.0 and Creator Works MCP 2.7.0.
Use Project Setup inside Hub or independently with the installer or portable ZIP.

Setup And Recovery

• Set up and create project checks requirements, previews the downloads and
  installs missing supported tools after your licence and installation approval.
• Pinned recipe: Unity 6000.3.21f1, Creator SDK 4.0.14, URP 17.3.0 and Input 1.20.0.
  Android SDK/NDK/OpenJDK and Windows build support are required.
• Package import/compilation, Visual Scripting configuration and a second Unity
  validation session are separate visible progress stages.
• Download size, received bytes and speed are shown when measurable. Installed
  requirements are refreshed instead of retaining a stale Missing label.
• Failures show the actual error, recovery guidance and local report paths.
  Failed project folders are preserved; logs are never uploaded automatically.
• Existing-project inspection and reviewed, backed-up repairs remain available.

Creator Plugins

The built-in catalogue includes images, descriptions, credit and category filters.
Add its Editor-only menu to a selected project, or queue eligible packages for
Unity's import selection. The menu supports thumbnail cards, direct Import and
Cancel/retry without reopening. Known old helpers update with a retained backup;
unknown edits are preserved. MCP tools and AI skills have their own categories,
without automatic AI-client configuration.

Important Limits

Windows x64. Unity sign-in/licence activation and administrator prompts still need
the user; this app cannot bypass them. An old Unity Hub is not silently upgraded.
Automatic Hub project registration requires Hub 3.21.1 or newer and may need an
approved restart. macOS/Linux automatic prerequisite installation is not available.

Windows binaries are not Authenticode signed. Signed Hub download metadata is a
separate integrity check. Attached acceptance reports identify the exact release
artifacts and tested upgrades; they do not prove every previous installation,
every project, player builds, hosted spaces or headset behavior. Review package
file selections and logs before importing or sharing them.

Reporting: https://github.com/BOBWORKS-XR/CREATOR-PROJECT-SETUP/blob/master/docs/REPORTING.md

Release Evidence

• Final Windows build and source checks.
• Installed upgrades from 0.2.2, alpha.1, alpha.2 and alpha.6, preserving synthetic settings and refusing replacement while active.
• The actual installed app refused close while its folder chooser was active,
  returned safely on Cancel and exited normally when idle. Its approved Plugins
  icon was verified inside the packaged frontend.

Installer SHA-256: 1cb72e2ea31345a4679aabf2b0756e847b10b68bc2043988147c2449584e02f2.
App source: f8d5423df9a477ceb65ec62a00358c7900703b66.
Later acceptance/history commits do not alter the application source or artifact.

Creator Project Setup 0.3.0-alpha.6

Creator Project Setup 0.3.0-alpha.6

Windows prerequisite-installation prerelease. Stable 0.2.2 and earlier
prerelease assets remain unchanged.

What Changed Since Alpha.2

• Set up and create project can install missing Windows requirements before
  creating a Creator SDK project. It previews the pinned Editor, required tools,
  locations and storage reserve, then asks for installation and licence approval.
• Downloads the pinned official Unity Hub installer when needed, verifies its
  hash and Windows signature, and uses the verified official Unity CLI to install
  the Editor and missing supported modules. Existing unrelated Editors remain intact.
• Checks the actual installation and active licence before creating a project.
  Missing sign-in or activation hands off to Unity Hub; no project is created
  until that check passes, and already installed requirements are retained.
• Download progress shows file size, received bytes and recent speed when
  measurable. Unity rates are labelled estimates from installer-file growth;
  unavailable measurements are not invented. This improves visibility, not speed.
• Refreshes the Requirements panel from native checks as project creation starts,
  so an installed Editor does not keep its startup Missing label during import.
• The Creator Hub menu entry opens the Hub releases page, not an old plan document.
• Retains detailed failure messages, versioned local receipts and reporting
  guidance. Logs stay local; nothing is automatically uploaded.

The recipe remains Unity 6000.3.21f1, Creator SDK 4.0.14, URP 17.3.0 and Input
System 1.20.0. Android SDK/NDK/OpenJDK and Windows support remain mandatory.
New projects are compiled, Visual Scripting is initialized, and configuration
is validated in a second Unity session. Existing-project repair remains preview.

Install And Test

Use the Windows installer or portable ZIP; keep the included licenses folder.
Close Setup normally before upgrading. Both forms work standalone without Hub
or MCP. Windows binaries are not Authenticode signed; signed Hub download
metadata is a separate verification mechanism.
The footer retains 0.3.0-alpha.6 candidate: these are the exact tested files,
not a cosmetically rebuilt installer.

For hosted use, the coordinated version is Creator Hub 0.1.0-alpha.6. Update
Hub first. Creator Works MCP 2.7.0-alpha.1 remains the matching unchanged
release; no MCP reinstall is needed just for this Setup update.

Use a new test project and review local logs before sharing them. Unity sign-in,
licence acceptance/activation and OS administrator prompts cannot be bypassed.
An old Unity Hub is not silently upgraded; automatic project registration needs
Hub 3.21.1 or newer. A running Hub may need the offered, approved restart before
its project list refreshes.

Verification And Limits

Clean candidate checks
passed from source a025a112519994670af8f48d848e408ec9dfa492: 63 Rust unit tests,
two executable-identity tests, 57 browser tests, strict Clippy, complete original
notices, portable ZIP and installer guard checks. Six explicit live tests are
separate from that candidate run.

Installed upgrade acceptance
passed on three disposable Windows runners, from public stable 0.2.2, alpha.1
and alpha.2. All used the same exact candidate installer: active owned-process
refusal, unchanged refusal snapshots, cooperative exit, successful update,
installed executable/notices, synthetic preservation data, real GUI startup and
normal close passed. This does not prove arbitrary user-settings migration.

Earlier local alpha.6 testing is not evidence for a different CI executable:
it covered a real alpha.1 upgrade/refusal with restoration,
project compilation/Visual Scripting/reopen validation, and a matched hosted run
with normal close. The hosted retry required observer assistance with the test
harness. Fully unattended testing of that final harness remains separate.

Fresh disposable Windows prerequisite acceptance
passed on the same alpha.6 source. It installed and checked the real Hub, Editor
and Android tools, reused the install, repaired isolated OpenJDK damage, executed
Java/javac, ADB and NDK clang, and required the activation handoff without using
a Unity account. The native test took 1,437.87 seconds, excluding CI preparation.
Actual Hub HTTP transfers and Unity Editor/Android module downloads produced
byte and recent-rate measurements. Quick/cache-hit components can still have
no speed reading. These are observations, not an independent speed benchmark.
This test did not create a project or activate a licence. It and the separate
licensed-PC project tests do not prove the complete fresh-user flow.

Paired Hub staged native acceptance
passed clean-install, older-app upgrade and MCP-only routes with the exact files.
It verified signed staged Setup metadata, approved installs, hosted views,
retained state and busy-close refusal. The MCP-only route leaves Setup uninstalled.
Hub's release records the separate public-feed retest; staged-cache acceptance
does not itself prove public discovery, Unity creation or Hub self-update.

Known limitations:

• Abnormal hosted-session termination left a completed Setup backend running
  in one local test. Normal close passed; abnormal-disconnect cleanup is unresolved.
• A reported missing-Hub label after completion was not reproduced in current
  tests. Custom Hub install paths may be undetected; capture the exact path and
  version if this occurs rather than reinstalling Unity blindly.
• Fresh-PC sign-in/UAC and the combined account-to-finished-project flow still
  need user testing. Actual download rates on other PCs are not benchmarked.
• Failed project folders are preserved, not automatically resumed or overwritten.
  Existing-project recovery is manual and backups are selective.
• No claim of every historical upgrade, real user-settings migration, Android
  APK/Windows player builds, hosted-space or headset behavior. macOS/Linux
  automatic prerequisite installation is not implemented.

See the reporting guide
for receipts, logs and privacy checks.

Creator Project Setup 0.3.0-alpha.2 - Setup Diagnostics

Creator Project Setup 0.3.0-alpha.2

Windows diagnostics hotfix prerelease. Stable 0.2.2 and the earlier prerelease
remain unchanged. This release keeps the same Unity/Creator SDK recipe.

What Changed

• A recognized final Unity package-download failure now shows the failed package,
  host, connection error, exit code and connection-check guidance, instead of only
  "Unity setup failed". Earlier recovered warnings are not treated as the cause.
• Creation receipts now record the Setup version, timestamp, platform and paths
  of existing Unity logs, so optional user reports can be tied to the right build.
• Failed creation explicitly explains that the retained folder cannot be resumed
  or overwritten by Create. A fresh attempt needs a different project name.
• Reporting instructions
  explain which files to keep and what to redact before sharing.

Logs remain local. No telemetry, automatic upload, automatic retry, security-policy
changes or project deletion was added. This improves diagnosis; it does not claim
to fix a user's network or Unity's package server.

Install

Use the Windows installer or the portable ZIP from this release. Keep licenses/
with the portable EXE. Close Setup normally before upgrading. Both forms work
standalone; Creator Hub is optional. Windows binaries are not Authenticode signed.

For hosted use, update to the matching
Creator Hub 0.1.0-alpha.5
first. Signed metadata tells older Hubs to update Hub before installing this
Setup version. Standalone Setup remains independent. No MCP update is required.

Validation

Clean Windows candidate checks
passed for source a8878c49a4c4cb57268c45484baa9e889b79bac2: 41 Rust tests,
34 browser tests, strict Clippy, packaged notices, exact executable identity,
portable ZIP and installer guard checks. Four explicit live Unity/Hub tests were
not run. The release contains these exact accepted binaries, not a rebuild.

Installed upgrade acceptance
passed on two separate disposable Windows runners: public 0.2.2 to alpha.2 and
public alpha.1 to alpha.2. Each tested early refusal with a same-name owned test
process alive, unchanged refusal snapshots, cooperative exit, successful update,
installed executable/license hashes, synthetic preservation sentinels, real GUI
startup and normal close. See release-verification.json for exact hashes/scope.

These tests do not establish real user-settings migration, every historical
uninstaller, a busy Unity creation/repair, reporter-side network recovery or
successful project completion. Native macOS/Linux workflows, full project
recovery and headset behavior are outside this Windows diagnostics acceptance.

Creator Project Setup 0.3.0-alpha.1 - Windows Testing

Creator Project Setup 0.3.0-alpha.1

Windows testing prerelease for the Creator Hub suite. Stable 0.2.2 remains available;
this release is not marked as the stable/latest release.

Changes

• Compact layout and shared Creator app navigation.
• Read-only Creator Hub identity and the backend for a build-pinned hosted preview.
• Early refusal when an installer detects Setup running. It does not force-close
  active work or continue into a potentially destructive legacy uninstall path.
• App MIT licence and original third-party notices accompany the Windows packages.
• The existing project creation, Visual Scripting initialization and reviewed
  repair flows remain available. Android and Windows support are both required.

Installation and Testing

Use the Windows installer, or extract the portable ZIP and run its EXE. Keep the
included licenses folder with the portable app. The installer places notices
in its own licenses folder.

Close Setup normally before updating from 0.2.2. Updates require approval.
Stable-to-newer-prerelease and prerelease-to-newer-stable are forward upgrades;
disabling prereleases must not trigger a downgrade to an older stable version.
General rollback and automatic Unity/SDK version migration are not offered.

Test the suite with the matching Creator Hub prerelease
and Creator Works MCP prerelease.
Start with a disposable Unity project, then check project creation/validation,
MCP connection and one small saved scene edit. Follow the
testing guide
and report exact versions, steps and relevant errors/logs.

Validation Limits

The exact final artifact and CI evidence are recorded in the release's verification
receipt. Native installed tests cover public 0.2.2 upgrading to this prerelease,
active-app refusal, unchanged refusal snapshots, cooperative exit, installed hashes,
synthetic preservation sentinels, and real main-window startup and normal close.

Candidate checks
and installed upgrade acceptance
passed for these exact files. Native regression tests: 35 passed, with four
explicit live Unity/Hub tests not run. Browser interface tests: 32 passed.

These checks do not establish migration of real user settings or project receipts,
historical uninstaller safety, busy Unity creation/repair, full Hub adoption,
headset behavior, published multiplayer spaces, or native macOS/Linux acceptance.
Hosted development previews retain their preview status. Setup remains usable
standalone; persistent shortcut takeover is not advertised.

Download Verification

SHA-256 checksums accompany the files. Hub also requires signed release metadata
for supported verified download/install actions. These signatures are separate
from Windows Authenticode signing: Windows executables are still unsigned and
may show an Unknown Publisher or SmartScreen warning.

Creator-owned application code is MIT-licensed. Dependency and brand-asset terms
are retained in the included notices; they are not all relicensed as MIT.

Creator Project Setup 0.2.2 - Windows

Creator Project Setup 0.2.2 - Windows Release

A portable setup tool for creating and validating a SideQuest Creator SDK Unity
project without editing package manifests, dragging package files, or using Git
or a terminal.

Promoted from prerelease after automated checks, native packaged-app testing,
and user confirmation that Restart Unity Hub made the project visible. The
original tested downloads and checksums are unchanged; the app footer still
says Preview. Existing-project repair remains experimental.

New In This Build

• Restart Unity Hub from the completion screen. A project can be registered
  successfully but missing from a running Hub's cached Projects list. The new
  confirmed restart fully closes and reopens Hub, including when it is hidden in
  the tray. Unity Editors remain open. Nothing is force-terminated.
• Separate registration from refresh. Saving a registry entry no longer
  appears as a completed Hub refresh. Cancel and retry retain the ready project.
• Hub version check. Automatic registration requires Hub 3.21.1 or newer,
  opened at least once. Older/unknown versions get explicit update or Add from
  disk instructions rather than a false success.

Included

• Detect installed Unity, Android SDK/NDK/OpenJDK, Windows build support and URP.
• Create a new project with the tested recipe: Unity 6000.3.21f1, Creator SDK
  4.0.14, URP 17.3.0 and Input System 1.20.0. Android and Windows are required.
• Resolve packages, initialize Creator Visual Scripting nodes, and reopen Unity
  in a second validation pass before marking the project ready.
• Show setup stages, import activity, elapsed time and local validation receipts.
• Inspect existing projects without changing files, then offer reviewed,
  opt-in settings backup and targeted repair/validation for the tested recipe.

Downloads

• Creator-Project-Setup-0.2.2-Windows.exe: portable app; run directly if WebView2
  is already installed.
• Creator-Project-Setup-0.2.2-Windows-portable.zip: the same app with instructions.
• Creator-Project-Setup-0.2.2-Windows-setup.exe: optional installer, including
  WebView2 prerequisite handling.
• SHA256SUMS-0.2.2.txt: checksums for the three downloads.

Tested And Limited

The missing-project case was reproduced in Hub 3.21.1. The final portable EXE
created a fresh project, initialized Visual Scripting, and passed the separate
Unity reopen check with no C# compilation errors. The native Cancel action left
Hub running unchanged; confirming Restart made that new project visible in the
native Hub window while all existing Unity Editor process IDs stayed unchanged.
22 Rust tests and 21 frontend tests pass, plus a separate live restart check and
Clippy with warnings treated as errors.

Finish Hub downloads/installations before confirming a restart. A refused
shutdown stops without forcing it. The app does not inspect every user's Hub UI.

This is a Windows release for the tested recipe, not a guarantee for arbitrary
SDK versions, existing projects, player builds, hosted spaces or headset behavior. Existing
repair backs up settings/manifests/generated Visual Scripting data, not the whole
project; retain your own full backup. macOS/Linux automatic restart is not
implemented; their native workflows remain unverified. Unity sign-in, licensing
and missing Editor/module installation remain Unity Hub handoffs.

Ensure the project and package-cache drives have enough free space. Disk-space
preflight is not yet implemented; a disk-full test stopped with Unity's log
retained, but the UI currently reports a generic setup failure.

The Windows files are unsigned. Only run trusted copies and compare the
published checksums. Optional Creator Hub support for installing, opening, and
updating the independent tools is next-version work. This release does not
install or reconfigure the MCP and does not contain Hub integration.