订阅以下载
模组配置文件管理器 [Mod Profile Manager]

the version number displayed in the mod menu is often wrong in such cases, it might display the "latest" number, but the mod file itself got replaced with an old version

The game will sometimes bug out and download an older version of a mod.
In such cases, mod updater will refetch the last version

the main problem seems to stem from some weird entirely unexpected cases that either the game or updater thinks it needs to update a given mod, but said mod actually hasn't been updated in as much as a couple years, and of course the versions in both the game and workshop are the same as they were beforehand, which is just weird and nonsensical as to why this would be triggered...

this was primarily why i was pointing to some form of steam api change, which the broken behaviour was also very well timed with the latest steam client and website updates, however so far it appears that the potential change on valve's side was unintended and they may have fixed it

the only way to prevent this issue is to manually install mods outside of the game.

or wait until Klei fixes their buggy extraction process.

"restart loops" are a bug in the game, not the mod, and caused by the game failing to handle extraction errors.
that process cannot be done by mods, so mods cannot fix it.
it happens more often with mod updater, because without it, the game wouldnt even try to install an update

ony's version does seem to be slightly affected but it handles it in a different way, in this case it just suggests there may be an out of date mod, but it doesn't actually show any as being out of date, probably because the mod screen does check the version numbers

unfortunately 'mod updater is not broken' is incorrect, its still broken in that it has been causing update-restart loops and often doesnt re-enable the mods its trying to update, partly because the mods its trying to do so with are already their latest versions and have not been updated in the workshop.
as to why exactly any of this is happening, is unclear, but it did begin with the recent updates and changes to the steam interface, store and workshop pages.

blatant misinformation gets removal.
mod updater is not broken, there has not been a change in the steam api.

ony also stole the updating code from mod updater (and still managed to fuck up so it remains buggy) in mod manager, both mods access the same endpoints (that are still in game code, not the actual api), just that mod updater does it properly and onys implementation is broken

use mod updater to force update the mod.
your local installation got most likely broken by bugs in the updating system

the mod is not working now it shows an error when starting