WorldEdit

WorldEdit

45M Downloads

litematic files don't load

spring-dependency-management opened this issue ยท 3 comments

commented

WorldEdit Version

7.3.10-beta01

Platform Version

1.21.4 paper

Confirmations

  • I am using the most recent Minecraft release.
  • I am using a version of WorldEdit compatible with my Minecraft version.
  • I am using the latest or recommended version of my platform software.
  • I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
  • I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)

Bug Description

Worldedit refuses to load litematic files, saying they don't exist, despite being in the directory

Expected Behavior

Worldedit should load litematic files the same as .schem or .schematic, its a very common format

Reproduction Steps

Place litematic file into schematics directory, try to load it, will say "schematic does not exist!"

Anything Else?

As a workaround does anyone know an easy way to convert litematic to schematic?

commented

There's no written objective specification for the Litematic schematic format, so it's not something we can currently support.

We're open to supporting it, but we'd need a spec first so we can actually support it properly.

commented

Just tried lite2edit and it works perfectly, all block data, tile entities etc copy
https://github.com/GoldenDelicios/Lite2Edit

the conversion code is very simple also, depending on how worldedit's code is structured it should be pretty simple to add, I will make a PR if so (we can have a disclaimer message when loading the litematic that it is being converted to schematic and stuff may break)

https://github.com/GoldenDelicios/Lite2Edit/blob/main/src/main/java/goldendelicios/lite2edit/Converter.java#L30

commented

It's not about how simple it is, it's about conformance to the format. There have been numerous different "flavours" of litematic schematic files output by various programs, it's important to objectively outline what the format is when adding support for it.

It's easy to reverse engineer the files and add hacky support, but doing it correctly requires a proper specification.