I would like to start looking at porting to 1.21.5. I considered raising this issue, but didn't want to be an entitled complainer; however, at the start of the development section under CONTRIBUTING.md it does recommend opening an issue, and this is probably a good way to track what actually needs to be done because I have no idea. (I haven't done java since 2010).

My strategy for now will be "hit play then try to fix whatever bugs appear".

After having looked at this for a few hours, and getting my head around libs.versions.toml it looks like there are a number of mods published to maven manually? The versions on modrinth don't match the ones I can find. I've started trying to just comment these out, but they'll obviously need publishing to maven somehow.

Thanks for getting in touch! I have started work on the 1.21.5 update, so definitely wouldn't recommend doing too much work on this yourself! The main challenges here are around models and rendering — Minecraft has done some major refactors in both 1.21.4 and 1.21.5.

I'm currently waiting on a NeoForge PR of mine to be merged. I don't strictly speaking need this, so if that takes too long I can work around it (my last PR to NF took 10 months to be merged, so here's hoping lol), but waiting to see for now.

Would you recommend against using the artifact from the latest build? https://github.com/cc-tweaked/CC-Tweaked/actions/runs/14800678173

And just as an aside to let you know why I appreciate the work you're doing, I have two nephews who recently joined our server, they're 8 and 10 (I got them both java accounts a few months ago). I told them I'd teach them programming in Minecraft and the older one is keen as; we had a look at the 1.21.1 version and he can't wait to start running excavate 16 all over our town.

I've been looking through the commits you've made and can appreciate the hard work you're putting in, lots of love coming from our direction.

I'm afraid it depends what you mean "recommend" :p. The 1.21.5 version should be mostly bug flee (well, there's no new bugs), so if you want to fiddle around with it, you should be fine!

However, it's not something I'd actively promote. There's not been an official release yet, so there's a risk of your save breaking between commits (to explain, if I change the save format, I have to do that as part of a Minecraft release — I can migrate 1.21.1 saves to a new format, but not existing 1.21.5 saves).

If you're planning to use this with your nephews, I'd recommend sticking with 1.21.1 for now!

Do you let me know how you guys get on — I want CC:T to be accessible as possible (though it's no Scratch, I admit) but getting feedback on this is always hard. Hope they have fun at least!

I'm not sure exactly what you mean about changing the save format. We've got a vanilla 1.21.5 world at the moment. It sounds like you're saying there's no guarantee that world saves from this artefact version will load in later versions because the migration hook doesn't run unless porting the world from an older version of mc? If that does happen I would think that the CC:T blocks and items would just disappear? I suppose it would be hard to say without knowing what kind of changes might be made.

you're saying there's no guarantee that world saves from this artefact version will load in later versions because the migration hook doesn't run unless porting the world from an older version of mc

Correct, yep! Sorry, probably could have phrased that better.

If that does happen I would think that the CC:T blocks and items would just disappear?

Yes, or will lose their data. It should never result in full-scale save corruption.