Why WorldEdit needs a schematic, not an .obj
WorldEdit and FastAsyncWorldEdit work with blocks: the clipboard holds a region of block states, and //paste writes it into the world. An .obj holds a polygon mesh with UV coordinates and a material file, which WorldEdit does not import on its own.
The missing step is voxelization, turning that mesh into blocks. Our free converter handles it online and writes a Sponge v3 .schem, the format //schem load expects. Block states are stored by name, so stairs and slabs keep the orientation the converter gave them.
