API for saving/loading?

[fatboychummy]

Hi, I'm developing a mod that generates plots of land players can claim. I'd like players to be able to save their plots server-side (with ability to transfer to the client), preview their saves in their plots, and reload saved plots. Using schematics seems to be a simple way to deal with that, and that's how I came here to Litematica. However, I have a question:

Is there a dedicated API in Litematica that would allow saving/loading schematics? Or would I need to work directly with the internals for this? If the latter, where should I start?

I'm targeting Fabric 1.20.1.

Thanks!

[sakura-ryoko]

Research the Syncmatica mod; would be your best bet; IMO:
https://github.com/End-Tech/syncmatica
https://modrinth.com/mod/syncmatica

[sakura-ryoko]

And to answer; there really isn't a specific "API" it would just be a flat Litematica dependency that would use Litematica functions to do the above.

[maruohon]

Yeah there isn't currently any proper API, and Litematica is written as a client-side mod, so I can't say off the top of my head how many of the schematic saving related methods might need changes to not reference any client-only classes, which would lead to crashes when used on a server. And the entire mod is not designed to be loaded on a server, that again would probably crash in a million places if it were let to try to load there.

Long-term I would like to rewrite and better separate the schematic, placement, area selection and other similar areas of code, possibly to a separate library mod (that would then get embedded inside Litematica), which would make it a lot easier to re-use the code in other mods. I would also need that in some of my other mods, if I ever resurrect them and start updating them again. But I have no timeline or ETA for when, if ever, this might actually happen.

Some of the schematic, placement and area selection code rewrites have already been done in the main development branch (ornithe_1.12.2), but there is still more cleanup and changes needed, some of which I have in a separate old branch where I was working on cross-MC-version conversion support. So the 1.12.2 code is better, but still WIP/not complete for what it should do.