Updating a CUTWIRE World

A World cloned from CUTWIRE is independent. A later CUTWIRE release does not update it automatically. Treat system upgrades as migrations.

Start with craft import <workspace-cdf.zip> --dry-run. Review the proposed schema, content, and settings changes before applying them. Use --include-types and --include-settings only when you want those parts of the migration. Resolve conflicts instead of overwriting customized World content.

Afterward run craft check, verify GM triggers, confirm CUTWIRE Core is pinned, and test one Operation.