Troubleshooting and Feedback

Turboism does not start

• Confirm you are using the intended Preview directory and Turboism home.
• Check the Java Agent and Runtime logs in Preview-owned or home-owned log directories.
• Verify that the active Cubism installation matches the supported Preview envelope.
• Do not replace Cubism JARs, DLLs, BAT files, or licensing components to bypass an identity failure.

A plugin does not appear

Check that:

• the managed JAR installation completed after restart, or the manual JAR is directly in the root of <turboism.home>/plugins/ (not in a subdirectory);
• the same Turboism home is used on both launches;
• no older JAR with the same plugin ID remains (a duplicate ID fails with DUPLICATE_PLUGIN_ID);
• the JAR has exactly one META-INF/turboism/plugin.json;
• the manifest uses schema version 2;
• the entrypoint class exists, is public, implements TurboismPlugin, and has a public no-argument constructor;
• the Turboism API range and required dependencies resolve;
• the plugin ID is not disabled or duplicated;
• environment.requiresCubism matches the current environment.

A JAR is rejected

A managed JAR can be rejected for a symbolic link or non-regular source, size over the 16 MiB cap, malformed paths, duplicate entries, special files, or a missing or duplicate META-INF/turboism/plugin.json.

Descriptor ID/version/API inconsistencies, copied SDK/Runtime/Live2D classes, native or installer payloads, nested JARs, missing entrypoints, and undeclared resources are also rejected.

Rebuild the JAR from the current plugin source. Do not edit the archive manually or disable inspection. The reasons above describe managed preflight; manual copying skips it, and only violations enforced by startup validation appear in Runtime startup diagnostics.

An operation remains pending

Plugin install, replacement, enable, disable, and uninstall operations apply after Cubism restarts.

• Confirm Cubism exited fully and was restarted.
• Confirm the same turboism.home is used on both launches.
• Inspect Runtime state and logs.
• Do not edit plugin, config, and pending-state files while Turboism is running.

A host capability is unavailable

This is often a deliberate fail-closed result caused by host version, Cubism file identity, mapping verification, Provider availability, safe mode, or stale object generation.

Record the exact Cubism version, Cubism file identity, operation, and diagnostic code. Do not bypass the failure with reflection or direct host access.

Feedback

Use Feedback and Requests to report bugs or request framework and plugin features through Discord, GitHub, or email.