Request for new feature to block mod version rather than just pin to a given version

[Riffz]

It would be nice to have the ability to block or blacklist a given version of a mod so it is never downloaded or suggested for updates in the list command. Specifically this is coming up because https://mods.vintagestory.at/canjewelryxskill#tab-files released a newer version that requires another mod be present in order for the game to load. I would like to block that version but if a newer version is available be alerted to that so I can evaluate if it is a good addition to the server I'm hosting for friends.

Proposed functionality would be set as a config like the pinned version. Something like this to mimic the pin command
./rustique config set -w canjewelryxskill -B 0.1.5 and it would not flag as an available version when running ./rustique list -u. Presumably we would still want this to flag when running ./rustique info canjewelryxskill but that would be a user specifically asking about a mod rather than the program informing about an update being available.

[Tekunogosu]

Hiya, so this functionality is already possible with version pinning. If you pin the version to 0.1.4 it wont show an update for anything newer until you unpin it. To pin a version ./rustique config set -w canjewelryxskill -P 0.1.4 That would keep it an 0.1.4 until you decide to unpin it.

The next major version, which is in the works, will have much more sophisticated version pinning like ./rustique config set -w canjewelryxskill -P <0.1.5 so it would allow updates for anything below 0.1.5. If you find out that 0.1.6 is fine, then you can remove the pin and update like normal or even set the pin to be >0.1.5.

Basically it opens more advanced forms of pinning. You can even do ranges, something like <0.1.5, >0.1.5 which would effectively block 0.1.5 completely and still allow you to update straight to 0.1.6 when it is released.

I appreciate your suggestion, version pinning already does this so I wouldn't be adding a new flag for blocking specific version.

[Riffz]

The existing behavior to pin to a single version doesn't really match the blacklist behavior I was thinking about. I'm fine being alerted about newer version using sync and list -u but the current latest version isn't something I want. Glad to hear about the planned changes for version range definitions that sounds a bit like what I was hoping for to avoid a version I know I don't want.