How does the Launcher tie local mods to mods on the workshop?

[Ryika]

Okay, sooooo I'm trying to update my mods, but some of the updated mods just don't want to do what I want them to do. The proper remote_file_id is present in both, the .mod file as well as the descriptor file, yet the new version is not recognized by the launcher as being the same mod as the one on the workshop.

For testing purposes, I uploaded the mod as a new mod, and that worked:
The mod was uploaded, it got its own id, both files were automatically updated with the new ID by the launcher.

So I changed them back to the ID I actually want the mod to have.
To my surprise, it didn't actually do anything. Despite the new ID having been replaced with the old ID, the launcher still treated it as the mod that I had just uploaded to the workshop.

Sooo... this means that the launcher isn't actually using the remote_file_id in the files in this case, right? I reset the launcher, and now the mod is not being recognized as either the new nor the old mod, so that assumption seems correct.

But how do I get that piece of junk to acknowledge the updated version of my mod as the mod that's already on the workshop?

 

[Ryika]

Alright, got it to work.

All I had to do was to...
...Subscribe to the mod in question.
...reload Installed Mods in the Launcher so the local mod shows in the list while I'm subscribed to the the online version of the mod.
...revert the changes that this caused the Launcher to make in the .mod file.
...and finally I was able to update the Mod.
Well, at least I think those are the steps that caused the launcher to stop being stubborn, but who really knows.

Totally reasonable, and not at all random if you think about it.

 

[gigau]

to the User Mods subforum.

 

[gedsaro]

Alright, got it to work.

All I had to do was to...
...Subscribe to the mod in question.
...reload Installed Mods in the Launcher so the local mod shows in the list while I'm subscribed to the the online version of the mod.
...revert the changes that this caused the Launcher to make in the .mod file.
...and finally I was able to update the Mod.
Well, at least I think those are the steps that caused the launcher to stop being stubborn, but who really knows.

Totally reasonable, and not at all random if you think about it.

Are you using the Paradox launcher? Because it really sucks (when it even works)
So far i've had a much better time using "Irony Mod Manager)

 

[Ryika]

Are you using the Paradox launcher? Because it really sucks (when it even works)
So far i've had a much better time using "Irony Mod Manager)

Irony can't upload mods, unless I've somehow missed that feature.

 

[gedsaro]

Ah you could be right, I havn't ever done any mod uploading, if i make any mods they are just my own personal slight adjustments to exisitng mods usually.