@Welsey

Full release! I had hoped to wait until my fork of ModpackUtils was approved for proper Modrinth distribution before making the push for full release but it has been under review for a full month now and I am out of time. Although the modpack does still have quite a few mods, am happy with where it is right now. It can achieve 60+ FPS consistently on my minimum spec test machine and everything seems to be tuned to my liking and working well, although I’m sure there will be plenty of little things to catch. I’m excited to continue developing this modpack, especially with 26.4 fast approaching, but here’s hoping I get some time before that comes to full release.

As this will be my last Stardance devlog, thank you for this! It has given me that little push to keep putting in a little time to keep this project running and I am happier for it. :)

I’ve made six more commits and released three more alpha versions for 26.3. I additionally updated and submitted my fork of a utility mod for the modpack. In order to update this mod I had to figure out gradle and mod development, and had to update the mod’s mixins (hooks into Minecraft’s code) for changing the window title and icon. For Sherbert, I added some new resource packs for utilities and more information for the player. I also went through and rewrote all of the mod configuration files and Minecraft’s options.txt to clean up and improve them. I’m in the process of releasing my first beta version and am getting ever closer to a full release!

I’ve continued work on this project, making 11 commits since my last devlog. I’ve continued to iterate on the mod selection and update my toolkit, which I also gave a seperate name from Sherbert for distinction and to denote it as an independent tool. Speaking of my toolkit, I used it for another project (still under wraps for now) and developed a solution for an issue I found there: Pre-build commands! When adding mods to the pack, STK adds all library mods by default, which hasn’t been a problem and keeps everything working. However, in one case a library mod was incompatible with certain other mods. The solution was to remove the library mod and replace it with a better alternative, but because it was a library mod it couldn’t be managed through STK at this point. My solution, probably the most simple way to do it, was to add a configuration option to give the modpack the ability to run packwiz commands right before the build process starts. This allows the modpack to be configured to automatically remove the problem causing mod and preserves the automatic build process, so that the issue can be dealt with even if building with the included CI system. In order to keep track of all the features I add to the packinfo configuration file, I have also been updating a template packinfo.toml which is heavily annotated for ease of use. A new Minecraft version, 26.3, has also just been released, so I’m starting work on Sherbert 6.0.0.

Just implemented a new feature in STManager, update checking. This helps mitigate the weirdness of the architecture I built and helps modpack authors stay on top of mod updates. This function includes my first direct work with the Modrinth API!

I made some improvements to STManager, with a new command and some fixes. I also made some small modlist changes and updates, and released version 5.2.0

I just shipped version 5.1.1, ending a very productive day of work! I added several new mods, backend tool improvements, and config changes.