search

ModOrganizer2 / modorganizer

Mod manager for various PC games. Discord Server: https://discord.gg/ewUVAqyrQX if you would like to be more involved
http://www.nexusmods.com/skyrimspecialedition/mods/6194
GNU General Public License v3.0
2.16k stars 160 forks source link

MO flags issue with mod version when two revisions are released on Nexus on the same day #2003

Closed hikingmetalpunk closed 6 months ago

hikingmetalpunk commented 6 months ago

The problem:

MO flags version 1.17.1 of this mod as being newer than the newest reported version despite validating that the version number is correct on the nexus page. https://www.nexusmods.com/stardewvalley/mods/3231?tab=files You can see here that v 1.17.0 released March 19 9:30AM and 1.17.1 released March 19 2:43 PM.

To Reproduce:

Download the above linked mod manually Install via MO Manually update 'version' from datestamp to 1.17.1 Once MO interface checks for updates, it will flag the mod and note that 1.17.0 is the newest version

Environment:

Windows 10, MO v 2.5.0

Details:

n/a

Link to Mod Organizer logs:

USVFS:

Following setting the MO log level to debug, restarting, and validating the issue still exists, this file is empty

MO Interface:

Following setting the MO log level to debug, restarting, and validating the issue still exists, this file is empty

Holt59 commented 6 months ago

This is not an MO2 issue, the mod on Nexus is still on version 1.17.0, which is why you get the warning in MO2 - It's the difference between file and mod version on Nexus.

image

The mod author simply forgot to update the mod version when updating the file.

hikingmetalpunk commented 5 months ago

Thanks @Holt59 , so the version comes from the nexus API rather than the mod filename or mod content? Is that why manually installed mods simply have the current date for a version?