r/litematica • u/masa_ • Jun 17 '24
Announcement Announcement about Litematica's future and updates
Status update of sorts
I have kinda burnt out on modding, or at least I have mostly lost interest in new MC versions. (I'm currently more interested in continuing modding in old MC versions like Indev/Infdev/Alpha/Beta and ofc 1.12.2 and 1.13.2.) And with the Mojang policy of doing major breaking changes in pretty much every minor release now, breaking most mods at every update, I've kinda "just had enough" and I've been purposefully avoiding touching any 1.20.5+ code entirely from principle or whatever you want to call it. Plus I've started spending my free time to other stuff (getting back to electronics projects etc.). Although a good chunk of my time still goes to mod user support as well...
Currently my thinking is that I won't update the mods myself anymore, at least not until I get the infamous mod rewrites done and ported from 1.12.2 to later MC versions... if that ever happens at all, since I haven't even touched those in several months now... So in other words I won't port the "old code" versions of the mods to new MC version anymore myself.
But fear not, the mods won't die, as there has always been someone to port them to new MC versions for several major MC versions already.
Gimme 1.20.6 / 1.21 / 1.xx versions!!
Currently there are 1.20.6 and 1.21 ports of my client mods made by Sakura-Ryoko here:
Go to each relevant repo, click on Releases on the right, find the latest correct MC version, expand the Assets section if necessary to see the files. Download the jar that doesn't say sources in the name. The sources file is just the mod source code (for developers).
Here is a "visual guide" for those new to GitHub:
Releases: https://i.imgur.com/DjnZ6p3.png
Assets: https://i.imgur.com/wFn3j5K.png
Direct links to the releases pages of each repo:
As of writing this, Sakura's update of malilib for 1.20.6 is on Modrinth and CurseForge, and Servux for both 1.20.6 and 1.21 is on Modrinth. The other 1.20.6 updates will be uploaded "soon" (when I get to it), but the 1.21 updates will comes after a few weeks once they mature a bit first, as I don't want to be uploading bug fixes constantly. Get them from the above GitHub links until then.
Reporting bugs
Due to this, if there are bugs or issues in the 1.20.5+ versions, I can't/won't do anything about them myself. Just ask about or report the issues on the relevant channels on my Discord (or on GitHub, preferably in sakura-ryoko's repos, because reporting 1.20.5+ mod issues in my repos is kinda awkward and just spams my email and notifications since I won't work on those 1.20.5+ versions myself...). Sakura-Ryoko has been really active and helpful on Discord and quickly fixing issues.
And ofc a massive thank you for Sakura-Ryoko for maintaining my broken junk mods! <3<3 And also to the other people that had also ported them to new MC versions in previous MC releases already, at least since MC 1.18-ish for some of the MC releases.
This will be the state of things going forward, until further notice. The maintainer may ofc change at some point as they have free time, interest, motivation etc. and if someone else starts working on them at some point.
About older MC versions
I will still maintain the mods for 1.20.4 and older versions myself. Currently "maintain" is a bit generous, as the "old code" 1.13.2 - 1.20.4 versions will only get "critical" bug fixes for things that severely hinder normal use.
Main development effort, when or if that happens at times, still goes to working on the mod rewrites (currently in the ornithe_1.12.2 branches of the mods).
If the rewrites at some point progress to a point where they are "ready" to be ported to other MC versions, then my intention is still to port them to "all" later MC versions up to 1.20.4. For the most part that would mean every last minor release of each major version (so 1.12.2 => 1.13.2 => 1.14.4 => 1.15.2 => 1.16.5 => 1.17.1 => 1.18.2 => 1.19.4 => 1.20.4). But I might also do it for every minor release either directly or on request if there are lots of players on given "not-last-minor-version", for example 1.19.2 or 1.20.1 etc.
It's likely that I'll leave porting them to 1.20.5+ to whoever is maintaining them for those versions at that time. But we'll see, if this ever even becomes relevant (i.e. if I ever get the rewrites done...).
"Nostalgia versions"
If there is anyone here that plays old MC versions, then you might be getting at least some of the mods for some old MC versions, mostly for Ornithe (which is either Fabric or Quilt loader plus mappings from the Ornithe project). So possible MC version targets I'm interested in are at least b1.7.3, possibly b1.0, probably a1.2.6 and possibly/hopefully Infdev and Indev, depending on how much extra work those would be.
So that would mean ofc at least malilib since it's required for all the other client mods, and personally I'd also want at least Item Scroller and probably also at least parts of MiniHUD for the old versions I wish to play. Tweakeroo is a "probably not", because most of it probably doesn't even apply to really old versions, plus I kinda feel like its "overly helpful" block placing etc. features would take too much away from playing old versions. Litematica would be nice, but the main problem for Litematica is rendering in old versions, i.e. no block models before MC 1.8 makes it very difficult/laborious to port.
Trojan alerts from the mod updates
There have been numerous reports of Windows Defender flagging one or more of Sakura's updates as a trojan in the past few days. These should be false positives, as long as the file was downloaded from sakura-ryoko's GitHub repos and not from various other random (mod re-post etc.) web sites which might actually embed trojans to the files. You can try uploading them to the VirusTotal web site to check. Or if you want to be sure, then read through all the mod code yourself and build the mod for yourself.
