Skip to content

Troubleshooting

Follow the diagnostic and fix the specific obstacle to preview, paste or paid construction.

Check the active launcher instance, not another Minecraft folder. Place the file in schematics/, press V, use Open Folder to confirm the location and press Refresh. Check the selected subfolder and search filter.

Read the reported format, registry or DataVersion problem. Supported extensions do not guarantee supported contents. Install missing mods where appropriate, choose replacements/manual omissions, or use a converter that understands the original data. See Formats.

Check Preview opacity and the visible layer in Settings. Confirm that the anchor and dimension are correct. A detail-limit message calls for moving closer or selecting a layer. Pink outlines indicate unsupported rendering rather than a missing-file problem. See Preview & settings for shader visibility details.

With Iris, check for an old K menu binding that also toggles shaders. Rebind the menu to V or another unused key. The shader guide lists compatible addon/pack versions and OptiFine’s compatibility status.

Hold Shift + use to bypass the preview tool, or disable In-world editing in Settings. Check key conflicts and bindings in Minecraft Controls. G cycles tools; V opens the menu by default.

Check the Containers, Inventory or All sources selection. Containers must be within 10 blocks of the transformed schematic’s edges, including vertical distance. Inspect protected slots, exclusions and extraction faces. Armor/offhand, unopened loot and stores that would be replaced are excluded.

Decorated or displayed items may need exact matching data. A generic banner or head may not satisfy a decorated requirement. Check Needed, Missing and the Problems tab.

An operator can open Materials → Problems → Add rule. Review the prefilled target and fields, classify all stored resources correctly, then Save. Start with the complete beginner guide. A rule with an unknown field or invalid item does not apply.

Required chunks may have unloaded; work resumes when they are available unless manually paused. Moving your preview does not move the existing job. A relevant rule change stops the job and offers Restart with new rules. Permission/provider or obstruction diagnostics need attention at the original site.

For a printer, the controller chunk must also be actively ticking. Loaded or cached alone is insufficient. After a clean cold reload or server boot, the owner must explicitly Resume; a job reporting Recovery after an unclean shutdown needs inspection first. See Printer ticking requirements.

Later world or container edits are protected. Inspect conflicts and consider the explicit unchanged-groups undo option. Supporting blocks may remain when an edited hanging decoration needs them. Expired history cannot be restored through the ordinary undo entry.

Inspect the recorded operation rather than assuming every held item should be refunded. Ambiguous operations retain evidence and require fresh validation. Server owners should review the server log and recovery behavior.

If this appeared after changing mod versions, review the upgrade guidance. Finish/cancel and settle returns before updating, rather than using an update to bypass an unfinished job.

Use Copy recovery on the Survival build screen when you need to share its recovery details with the server owner.

Include your Minecraft version, loader, Simple Schematics version, relevant addon/provider mods, exact diagnostic and steps to reproduce. Preserve the source schematic and server log where useful. Check logs for private server details before sharing them.

Open the project’s issue tracker.