Troubleshooting

Most paste problems come from a missing flag or a game rule. Find what you're seeing below. Where the fix is to paste again, //undo first, while nothing else has changed since the paste.

Leaves are disappearing

Random ticks are on and the leaves aren't marked as permanent.

1. Set /gamerule random_tick_speed 0 (randomTickSpeed before 1.21.11) to stop any more decaying.
2. Leaves that have already decayed are gone, and //undo won't bring them back on its own. If you haven't changed anything since the paste, //undo and paste again.
3. Run //replace ##leaves ^[persistent=true] on the build. See Make the leaves permanent.

If you pasted with plain WorldEdit, also turn off block updates before you paste again. See Using plain WorldEdit.

A cube of terrain vanished around the build

The build was pasted without -a, so the schematic's air replaced everything in its box. Run //undo, then paste again with //paste -a -e -s.

Terrain or old blocks are inside the build

The build was pasted with -a, which leaves existing blocks where the schematic has air. Either dig them out, or //undo and paste again without -a so the build's air clears its box. Bear in mind that this also clears the terrain around the build inside that box. See With or without air.

The build is in the wrong place or underground

The paste is placed relative to where you were standing, so the builder's origin landed at your feet. If the build went underground, the origin was above it, so stand higher by the same amount. Run //undo, move, and check with //paste -n before pasting again. See Know where it will land.

The top or bottom of the build is missing

Part of the build was outside the world's height limit, Y -64 to Y 319 in the Overworld, and was cut off. Run //undo, move up or down, and check with //paste -n.

Armour stands, item frames or paintings are missing

They're entities, and entities are only pasted with -e. Run //undo and paste again with -e.

Holograms made with a hologram plugin aren't saved in schematics at all. Set those up again in the plugin.

Sand or gravel fell, or water and lava are flowing

Block updates were on during the paste, which is the default on plain WorldEdit. Run //undo, then //perf neighbors off and //perf update off, and paste again.

FAWE doesn't update blocks while pasting, but a player placing or breaking a block next to floating sand later can still make it fall.

Dark patches or black shadows

Select the build and run //fixlighting on FAWE. On plain WorldEdit, leave and rejoin. See Fix dark patches.

Grass, leaves or water are the wrong colour

Those colours come from the biome. If the schematic was saved with its biomes, //undo and paste again with -b. Otherwise, select the build and set a biome yourself, for example //setbiome plains. Rejoin to see the change.

The schematic won't load

• "Doesn't exist". The file is in the wrong folder, still inside a .zip, or the name is mistyped. Run //schem list and copy the name exactly. If FAWE has per-player schematics turned on, the file must be in schematics/<your-uuid>/. See Upload the schematic.
• Unknown format, or blocks missing after loading. The build was saved on a newer Minecraft version than your server, or your FAWE or WorldEdit is out of date. Update the plugin, and run the Minecraft version listed for the build or newer.

FAWE asks you to confirm, or says "Too many blocks changed"

• A confirm prompt appears for large selections. Run //confirm to go ahead.
• "Too many blocks changed" means you've hit FAWE's edit limit. Paste as an operator, or give yourself fawe.limit.unlimited.

The server froze or lagged during the paste

Plain WorldEdit places the whole build in one go, which can freeze the server on big builds. Use FAWE for anything large. Pasting into land that hasn't been generated yet also slows things down, because every chunk has to be generated first. See Choose where the build goes.