Development Status

What the current Turboism codebase implements, what remains version-limited, and what is not yet a product promise.

Turboism is a Java 17 runtime enhancement tool and plugin framework for Live2D Cubism Editor. Development is organized around usable framework and product capabilities rather than the retired M1–M16 migration sequence.

This page is a source-backed snapshot of the current Stable release, 0.67.4 (tag v0.67.4, published 2026-10-24). It is not a release announcement; use the release feeds for published versions.

Current architecture

Plugin -> SDK -> Runtime policy -> versioned Adapter/Provider -> Cubism/Editor

Plugins depend on the Turboism SDK only. Runtime owns host access, lifecycle, safety, threading, transactions, diagnostics, compatibility, and version routing.

Supported host versions

  • Windows x64 is the supported Cubism host platform.
  • The current Stable release, 0.67.4, like every 0.67.x Stable, supports all 20 reviewed Cubism Editor versions from 5.0.00 to 5.3.04, each with version-routed adapters and Providers (see Compatibility). The previous Stable, 0.44.0, admitted only 5.2.03, 5.3.02, and 5.3.03.
  • Version support is not feature parity: 129 of 143 capabilities are admitted on every version, and coverage is 100% on 5.3.x, 97.9% on 5.2.x, up to 95.1% on 5.1.x, and 90.2% on 5.0.x. Every exclusion is an evidence-backed version boundary.
  • Unlisted Editor versions are not claimed compatible, and unsupported or unverified capabilities fail closed.
  • macOS packaging is preview-only with no verified host support; Linux covers runtime behavior only and is not a supported Cubism host.

Release and delivery

  • One product identity with three channels: stable, beta, and nightly.
  • Stable releases in the 0.67 line are 0.67.0 (2026-10-19), 0.67.1 (2026-10-20), 0.67.2 (2026-10-23), and 0.67.4 (2026-10-24); there is no 0.67.3 release. The previous Stable was 0.44.0 (2026-09-11).
  • Each release publishes two product downloads, TurboismInstaller-<version>.exe and turboism-<version>.zip, plus the developer assets turboism-sdk-<version>.jar and turboism-event-processor-<version>.jar, each with a .sha256 file.
  • Product releases are split into read-only candidate builds and an explicitly protected GitHub promotion step. A failed candidate reuses the intended version; only promotion creates the annotated tag and publishes the verified bytes without rebuilding.
  • Every build embeds a global build identity: version, channel, build number, source revision, and dirty flag (FrameworkBuildInfo).
  • A release API at api.turboism.dev mirrors every channel with per-asset SHA-256 and checksum files, resolves the official mirror and GitHub sources, and reports per-release download requests.
  • Reviewed release notes carry Simplified Chinese, Japanese, and Korean translations with English as the fallback; a translation whose digest no longer matches the exact English section is rejected rather than reused.
  • Installers ship in English, Simplified Chinese, Japanese, and Korean. Installer language is installer-scoped; runtime language comes from the runtime locale setting, and plugin interface language follows the Cubism Environment Settings language.

Framework foundations

  • Java Agent bootstrap, Runtime, SDK, first-party plugin, test-framework, and integration-test modules.
  • Plugin SDK API ranges start at 0.67.0 and end before 1.0.0. The lower bound is the minimum framework base version (beta, nightly, and SNAPSHOT suffixes are ignored), and legacy [0.1.0,0.2.0) plugins are rejected.
  • Plugin metadata schema versions 2, 3 (adds required category and bounded tags), and 4 (adds declared event imports and exports), with strict validation per version.
  • Local plugin JAR discovery, manifest and API-range validation, dependency resolution, one ClassLoader per plugin, lifecycle execution, reverse shutdown, and scope/ClassLoader cleanup.
  • Ordered multiple entrypoints per JAR with whole-JAR startup rollback.
  • PluginContext services for logging, paths, localization, tasks, configuration, storage, user files, events, actions, UI contributions, Cubism access, and diagnostics.
  • Managed local JAR install, replacement, enable, disable, and uninstall. Changes are staged in a journal and applied after Cubism restarts; the built-in framework shell (dev.turboism.shell, which replaced the separate core plugin in 0.67.0) is runtime-owned framework code, not a plugin, and cannot be disabled or uninstalled.
  • Startup preflight revalidates the staged payload identity (SHA-256, size, descriptor hash) before apply, and a private backup/restore protects failed replacement applies.
  • Framework message catalogs are held to the same locale matrix as the first-party plugins, so a missing catalog fails a build gate instead of silently degrading to English.

Installer and delivery

Since 0.67.0, each release ships exactly two product downloads:

  • the Windows-native NSIS installer TurboismInstaller-<version>.exe, offering an optional managed GraalVM component and safe upgrades;
  • the portable turboism-<version>.zip archive.

Both include every bundled first-party plugin and the complete offline GraalJS engine; GraalVM runtime installation remains separate. The four-download Full/Thin layout (-full and -thin installers and ZIPs) existed only in the 0.67.0 Beta releases and is retired. Releases up to 0.44.0 used the legacy assets (TurboismInstaller-<version>.exe, the Java 17 IzPack installer TurboismInstaller-<version>.jar, and turboism-<version>-full.zip / turboism-<version>-lite.zip). The Java installer is no longer published.

Installers have no mode or plugin-selection pages. Since 0.67.4, Windows installers use Turboism branding and hide the elevated configuration console. Inside Cubism Editor, the top menu is named Turboism (previously "插件"/Plugins), offering the in-Cubism Plugin Market…, Manage Plugins…, Plugin Settings… (a dedicated two-pane window), Check for Updates, and background auto-updates for verified first-party plugins.

The installer gates installation behind four required acknowledgements and a full localized runtime declaration. config.json has explicit update ownership: on an existing valid document the installer preserves user configuration. The Windows configurator lists only exact supported Cubism installations and keeps Turboism-owned shortcuts separate from official BAT integration. Since 0.67.0 the installer pre-selects official Cubism BAT integration: it backs up and modifies the selected CubismEditor5.bat launchers so existing Cubism shortcuts and file associations load Turboism. The option can be unchecked on the launch-options page, is hash-guarded and idempotent, is restored on uninstall, also applies to silent installs, and is the only step that elevates through UAC.

Cubism and Editor API progress

  • A unified object graph covers Canvas, Parameters, Parameter Groups, Parts, Drawables, Deformers, Warp and Rotation Deformers, Glue, parameter bindings, and texture atlases.
  • Core-backed reads use immutable copied data, version normalization, generation-bound stale-reference rejection, and digest-pinned resolver evidence.
  • The parameter authoring path connects Parameter.setValue to Editor operations, permission checks, Undo, dirty-state handling, refresh, and stale-target rejection.
  • Part display-name writes have real-host evidence on 5.2.03 and 5.3.02. Part opacity authoring writes require 5.3.00–5.3.04 (real-host verified on 5.3.02) and are unavailable on 5.0.00–5.2.03 because part-form opacity accessors were introduced in Cubism 5.3.00.
  • Exact-version verification records, selector contracts, and profiles now cover all 20 reviewed builds from 5.0.00 to 5.3.04; per-plugin and per-capability version boundaries are generated on Compatibility.
  • Parameter lifecycle hooks support ordered synchronous before rewriting, changed-only on, normal-completion after, recursion rejection, bounded observation work, and unload cleanup.
  • History now projects immutable semantic detail: HistoryEntry, HistoryChange, HistoryEditContext, HistoryGroup, HistoryOrigin, HistoryTarget, and bounded validation of targets, coordinates, and grouping. These values grant no host write authority.
  • The animation workspace SDK (documents, timelines, tracks, keyframes, scenes, and playback) is available on Cubism 5.2.00–5.3.04.
  • Texture-atlas SDK support covers per-page sizes, packing failure diagnostics, and planner negotiation (0.67.2), plus source outlines and polygon output pages (0.67.4), with linkage gates for retained constructors.

SDK compatibility baseline

  • The reviewed binary API baseline v23 is the live release gate for 0.67.4; v2–v22 are kept as historical audits (v21 was the 0.67.0 baseline and v22 the 0.67.2 baseline).
  • v22 added TextureAtlasPageSize, a per-page TextureAtlasLayoutPlan constructor, TextureAtlasLayoutPlanner.supportsCompleteAtlas(), TextureAtlasPackingException with Reason, PsdEditFile.openInApplication(String), and the SettingsControl.FilePath variant. Exhaustive switches over SettingsControl must add a case when recompiling.
  • v23 added an optional source outline on TextureAtlasLayoutItem, TextureAtlasLayoutPlan.polygonPages, value equality for TextureAtlasOutline, and TurboismProgressDialog. Existing constructor signatures remain, but records that gained components change reflection, equality, hashCode, and toString, and the retained former canonical constructors no longer expose parameter-name metadata. No existing public type or callable JVM descriptor was removed.
  • @Incubating marks experimental API, such as TextureAtlasPolygonLayoutPlanner, that may change or disappear and is excluded from the exact baselines. The SDK remains under a pre-stable policy, so an unannotated API is not by itself a frozen-SDK guarantee.

Update checker

  • Turboism checks for stable updates against the deployed release API. The comparison uses the authoritative build number embedded in the installed package.
  • An available update is presented as a native Cubism hint over the drawing area. Clicking it opens the fixed first-party download page; no installer is downloaded or executed automatically.
  • The update checker is non-blocking and runs at most once per 24 hours, with a manual check always available. Automatic checks have their own persistent toggle in the Startup settings tab.
  • Plugins can show native Cubism hints over the drawing area through the canvas-hint UI capability (turboism.ui.canvas.hint permission), version-routed through verified host routes (see Compatibility for the versions on which it is available).

First-party plugins

The reviewed 0.67.4 bundle contains twenty-nine plugins: folder texture-atlas layout with the MaxRects-BSSF, Bitmask nesting, and Dalsoo polygon packing algorithms, texture-atlas statistics, 3D model import, frame animation import, PSD clip-mask import, external PSD editing, mesh mirror-axis editing, BoundingBox warp mirror, Warp Deformer Alt symmetry, selection brush, parameter batch transfer, parameter lock, physics editing, history panel, recent preview thumbnails, command palette, palette tab filters, palette label styling, scene palette enhancer, UI themes, clip-mask viewer, performance statistics, protected export, WebDAV auto-backup sync, the loopback MCP server, and the ACP agent bridge. The built-in Turboism menu, settings, plugin management, and update hints are provided by the runtime-owned framework shell, not by a plugin. See First-Party Plugins.

Shared plugin services and UI

The SDK includes contracts for:

  • actions and menus;
  • main and palette toolbars;
  • typed context menus;
  • toolkit-neutral embedded panels;
  • overlays, status notifications, canvas hints, dialogs, and file selection;
  • typed plugin configuration and migrations;
  • plugin-owned data, state, and cache storage;
  • bounded tasks and cancellation;
  • asynchronous host reads;
  • localization and diagnostics;
  • appearance, scene-table, and selected Editor feature families.

Host and UI families fail closed when a matching Provider or verified host capability is unavailable. Fake or static tests do not automatically establish real-host readiness.

Verification model

Verification is layered by cost and risk rather than run as one undifferentiated gate:

focused verification      smallest affected compile or test selection
devCheck                  production compilation plus structural boundaries
checkIntegration          packaged runtime, plugin, bundle, and cross-module behavior
checkCompletedCommit      full automated repository gate for a coherent change
checkRelease              completed-commit plus supply-chain, historical, and installer-artifact checks
host validation           explicit exact-version Cubism execution for the affected feature

Host validation runs through a supervised local queue: build and prepare work may run in parallel, but a single host-admission lock serializes real Cubism sessions, completion requires matching structured lifecycle and cleanup evidence, and unknown ownership quarantines the host for inspection instead of killing unrelated sessions.

Official Directory and Plugin Market status

The in-Cubism Plugin Market client and UI are active for browsing and installing verified first-party and catalog plugins directly from the live signed directory at turboism.dev/plugins. First-party plugins support background automatic updates with signature verification and hot-reload, and the updates can be turned off in settings. Since 0.67.2, plugin management labels each plugin's SDK API range and its declared exact Cubism versions for available, full, and partial functionality; since 0.67.4 it also shows installed and marketplace plugin counts.

In progress or version-limited

  • Many unified-object write methods still depend on a specific version Provider. A method in the interface does not mean every supported Cubism version can execute it.
  • The full Editor-authoring matrix remains incomplete for several operation families, and per-family readiness is recorded in the SDK API Guide.
  • Drawable, Deformer, Glue, mesh, PSD, and additional texture-atlas workflows require consumer-driven implementation and exact validation.
  • Host UI attachment, high-frequency hooks, and real-host readiness remain high-risk boundaries with exact-version gates.
  • SDK HTML Javadoc can be generated and is hosted on this site, but many public declarations still need better explanatory comments.

Not currently promised

Turboism does not currently promise:

  • a signed or notarized public release channel for installer packages;
  • verified macOS Cubism host support;
  • automatic download and silent execution of framework installer packages (update checks and background plugin updates are available; automatic framework installer updates are not);
  • publisher signing or revocation for Plugin Directory entries;
  • a complete user-facing install, repair, rollback, recovery, and purge UI;
  • global modification of Cubism launchers;
  • uniform feature readiness across every Cubism version;
  • production readiness based only on fake, static, or single-version evidence.

Near-term order

  1. Finish the unified object and reference model.
  2. Complete Core reads and version-routed Providers.
  3. Expand Editor-owned writes with Undo from verified consumers.
  4. Standardize operation lifecycle semantics.
  5. Complete project, selection, and model-tree APIs.
  6. Restore remaining first-party workflows through SDK-only plugins.
  7. Add hooks only when explicit APIs, refresh, polling, or callbacks are insufficient.
  8. Harden third-party SDK, packaging, and release evidence.

For source-level context, see the Turboism repository and its ARCHITECTURE.md and ROADMAP.md files.