Repository navigation
Bug: unsupported litematica version 5,6,7 #307
Description
Activity
yeah the build command system uses its own schematic-style structure system, which also happens to have support for some litematic versions. Its not something i plan to work on in the near future, so i'd just recommend using the printer module with litematica
What do you mean "schematic-style structure system"? Does this mean no litematica files work or I should use schematic files instead? What has to be different/specific, also litematica printer is detected by AC's on servers
Would pasting it into a different world, selecting it then re-saving it as a schematic fix this?
im not sure tbh; i didnt write the specific litematic versions support we have currently. By schematic-style structure system, i mean that the build command, specifically, actually uses the minecraft structure storage system rather than litematics and we only have translation support for certain litematic types. Its a very underdeveloped way of building with lambda, which is why i recommend using the printer module. I dont mean litematica printer, lambda has its own printer module. This works directly with litematica, and doesnt have to deal with storing schematics, etc. Also, another thing to know about the build command: As it is underdeveloped, it simulates the entire schematic every tick, rather than just the area around you like the printer module does. It can be incredibly laggy, if not freezing your game entirely with big structures
Reacted by rwonkensv2Alr, thanks man, appreciate it a bunch and good work. Also unrelated question, but when you mention built with GrimAC in mind does this apply for all modules? Eg killaura etc
Reacted by beanbag44its not a guarantee with every module. There are ncp modes in speed i think, and others might be there just in case something gets unpatched in the future, or happens to work on other servers aside from 2b. But generally, all configs default to 2b2t's grim setup afaik
Reacted by rwonkensv2This is working as intended. Schemas 1 to 4 were simple enough to parse. However, newer versions uses a more complex approach that I was unable to replicate even by reading the source code of litematica (classic java oop hell). At first, when I wrote the code a year and a half ago, lambda was supposed to read and automatically converted all sponge and litematica files into nbt.
lambda/src/main/kotlin/com/lambda/util/extension/Structures.kt
Lines 179 to 182 in 178f399
There are two subsystems for structures. One which was abandoned in favor of using a soft dependency on litematica. The oldest one supports some sponge and litematica while the other supports all structure files
I'm so high chat
What happened?
Can't use ;build to build my litematica structure, but litematica printer and litematica parses them just fine
https://abfielder.com/Products/ProductDetails.php?id=2411
What should have happened?
shoulda built i guess
Version
1.21.11
Log Output
No response