Skip to content

Troubleshooting and support diagnostics

For the new fluent API, first verify the preview.3 SDK and ShutterBug Renderer 1.1.0 platform JAR with its embedded native library. NoSuchMethodError, missing autocomplete classes or UNSUPPORTED_CAPABILITY often mean the compile and runtime versions differ. Use setup to refresh IDE sources and compatibility to choose the correct pair. Photo-saving and map-binding recovery are described in operator storage guidance.

The commercial installation checks below apply to Renderer 1.1.0. SDK publication does not establish personalized buyer activation.

Start at the first failing boundary:

  1. Confirm Java 25, Paper 26.2, Minecraft 26.2, and a supported platform. Java 21 is the SDK compilation baseline, not this server's runtime requirement. Supported platform archives are macOS ARM64, Linux x86-64 and Windows x86-64.
  2. Verify ShutterBugRenderer.jar came from your personalized MCModels Renderer 1.1.0 download for this platform. Personalization changes the JAR and may change its enclosing ZIP, so a published checksum for the vendor's unpersonalized archive or native payload is not a byte-for-byte checksum for your download. If provenance is uncertain, retain the original purchase download, calculate its SHA-256 locally, and ask MCModels product support to check it through a private ticket; do not post the JAR or purchase identifiers publicly. The native is embedded and checksum-verified by the provider before extraction; do not copy, rename, or install a separate native file. A generic or incomplete JAR is not an activation substitute.
  3. Read the provider startup result. license-key stays blank only for a separately verified and enabled personalized-download activation flow; that production buyer gate is currently pending. An explicitly configured support-supplied manual value takes precedence for fresh activation. A valid signed cache may cover a restart only until its six-hour lease expires. The purchase permits three active hardware installations. For activation, lease, seat, trust, hardware-change, or product-mismatch errors, stop retries and follow the supported operator/admin process in operator activation.
  4. Confirm RendererService appears. Optional consumers should remain usable and attach when the service registers; hard dependencies should fail clearly.
  5. Inspect rendererVersion, platform, nativeAvailable, packagedForProduction, supported profiles, and supported attachments. Do not dump object internals or environment variables.
  6. Reproduce with the sample plugin, one small Classic render, no optional attachments, and no custom assets. Add one feature at a time.
  7. Use the typed failure recovery table. After reload, discard old clients, scenes, asset handles, and tasks.

A support bundle may contain UTC timestamp, product and SDK versions, Paper/Minecraft versions, platform key, sanitized provider startup code, capability snapshot, failure code, task phase/status, artifact SHA-256 values, and the smallest reproduction. Remove player data, world paths, network addresses, environment dumps, license values, bearer tokens, purchase identifiers, and private plugin source. Preserve the original logs locally.