FilmstripStudio

Play Mode, Saves, and Diagnostics · Version 0.5

Structured Diagnostics and Failure Reports

Read editor and runtime messages, locate persistent JSONL logs, and use atomic failure reports for saves, packaging, migration, and validation problems.

Filmstrip records structured diagnostics for editor, runtime, storage, interaction, validation, preflight, export, recovery, and packaging events. Messages include a subsystem and useful source context when available.

Where feedback appears

  • Editor status and operation messages.
  • Runtime success or failure notifications.
  • Development console output during source runs.
  • User-local filmstrip.jsonl logs.
  • Atomic JSON failure reports for supported save, packaging, and migration failures.
  • Build preflight and reproducibility reports.

User-local log location

Persistent project logs are stored beneath the user’s local application-data directory using the project publisher and project ID. Logs are not written into authored project content or the installed game bundle.

Respond to a failure

  1. Read the first actionable editor or runtime message.
  2. Identify the subsystem, source object, document, or path involved.
  3. Open the relevant authoring window or Project Asset Browser.
  4. Repair the reference, value, path, or project setting.
  5. Rerun the failed save, load, preflight, build, or migration.
  6. Use the structured log or report when the short UI message is not enough.