Dezdemona Released v1.2.0. I've disabled pre-release versions by default (only updates if already on dev branch). Can be enabled by creating a shortcut or running in cmd with:

Hmmm... I would say if on a dev branch, it would be best to just continue it with the assumption of approval. But otherwise, perhaps have it have a forced confirmation even if you selected to just update all? That way there is still the convience, but somewhat less risk of accidental save shenanigans.

Dezdemona No problem 😁. Fixed the Error 400 in v1.1.4.
I didn't thought about dev/rc builds. Should I disable them by default and add flag to allow downloads? Or maybe detect if downloaded version is a dev build then allow updating to lastest version?

Sorry to pop back in again, but I seem to be getting some strange error 400 'bad request's, it doesn't seem to like cullinary artillery's dev builds, but I assumed that might have been intentional, but it also seems to struggle with the forgotten armories? It's not that much of a trouble to just manually do it, but figured, again, I should proooobably say something. Regardless, thanks so much for this! It still manages to save me such a damn headache managing updates haha

Dezdemona Thanks for pointing that out. Fixed in v1.1.3.

seems to be having an issue of not seeing updates for certain mods, the one I caught was Butchering where it was stuck on 1.10.9 whilst 1.10.11 was out. Not entirely sure why, but figured I'd throw a message about it.

Awesome, tysm!

Rui333, I've added option to update all. It will ask on first mod update found.
If you would like to update every mod without asking, you can create a shortcut and edit target to have this at the end:

hell yeah. any chance you could add an option at the beginning that's effectively a "Yes to All" command?

Thanks Master_Story. Should be now fixed in v1.1.1

I found this odd line while running your mod. Not sure if it's relevent, but figured I'd share:

Hi Nermit, the version v1.0.9 should now handle mods with non-compliant JSON.

Thanks for your response! Sorry for being slow to follow up.

It looks like 1.0.8 solved the issue. There are indeed a couple of mods that seem to cause the error:

Any interest in putting this on a package manager? I'd love to be able to `choco install` or `brew install` this 😁

Nermit Could you share what mods you have?
Looks like one of the mods could have something in JSON that crashes the updater.

Also, in v1.0.8, the mod updater continues even if reading the zip file fails.

This updater is exactly what I was looking for. However, currently when running in Linux I get the following error:

Can you write, how it works?))

RunYouCleverBoy I've added the interactive mode and made default on Windows

can u please describe all launch parameters and make programm started with exe do not close after all
we wanna be able to read the log or choose -do i wanna update special mod or not
pls)

Maltiez single executable, some people don't like the messing around with python app, including me. Python apps always come with a lot of dependencies, heavy appimages. So it's a preference thing.

Maltiez None at the moment. Maybe only that it's smaller download :D

What are the advantages compared to https://news.kalataka.ru/modsupdaterforlinux ?

Sorry lmperfect. I haven't tested the program on Windows yet.

It's supposed to be run from Windows Terminal or cmd exe

Not sure how its supposed to work. Ran the program, it said it might be malware, it did nothing, added it as a mod itself, it did nothing, ran the exe from the mod folder, it did nothing. Changed my password though on my accounts. 👍