Current Version Number is the same as previous version number.

[Rivernoodl]

Players Updating from the .NET4 Version will have trouble because the .NET7 version number is the same.

Currently the remedy is to delete the old version from the mod folder before attempting to install the latest version.

I recommend posting this fix on the main page, or changing the version number to be different so Vintage Story recognizes it as a different version.

[l33tmaan]

I don't understand what the actual problem is. What trouble will people have?

[Rivernoodl]

Just based on my own experience, I went to update to the newest version and Vintage Story says "This is the same version number, mod enabled instead of downloaded!"

This seems well and all, but this means Vintage Story erroneously sees v1.0.12 as being the same as v1.0.12-pre.2 and refuses to update to the newer version. This means that after updating Expanded Foods from v1.6.6 to v1.6.7 (with A Culinary Artillery still on v1.0.12) the game will break and the player will have no idea why, as what happened to me this afternoon.

I think in order for vintage story to allow changing of the files to the .NET7 update organically, the version will have to be v1.0.13 (or some equivalent.)

Normally, I don't think this would have been worth reporting, but with the new stable update of Vintage Story making .NET7 available to everyone there will be a mass exodus of players moving from version v1.0.12 to v1.0.12-pre.2 and will have the same issue as I am having, making this problem annoy a lot more people than it normally would have.

[l33tmaan]

I see, I believe other people have mentioned this to me before. I'll do that, thank you for the heads up!

[l33tmaan]

This should be fixed in the latest releases!