We're not supporting GOG at this time, but if someone approaches us needing these features we can look at adding it in. The other issue is people can have this in a totally custom directory, unlike with Steam where it has the same workshop and item structure no matter what drive it's on (unless you did some really weird stuff). We have yet to find anyone who actively plays on GOG anyway.

RequireFix is to be included with any relevant mods, and currently it can be used without Steam dependencies. It can either point to the Extra Utilities mod requiring a dependency, or point to itself if you hardcode the steam ID of your own mod.

You should probably add support for GOG since it's so easy to do (as I noted with my scratch function above, dumb adding both the steam workshop and gog path would be an acceptable work around).

The truth about GOG is it's the best platform for developing advanced mods, though IDK if you guys have graduated to the methods that most benefit from using the GOG version for dev yet.

Thanks for the opinion.

The other issue I found when I looked into this...there is no rhyme or reason to what name the mod may have. The only reason RequireFix works is because you can point it to a steam workshop ID. I guess we could assume the mod downloaded would keep the same ID as the folder name, but that is no guarantee at all. Especially if someone puts the mod on GOG/Moddb or whatever.

I don't see a clear way of doing this that wouldn't result in multiple issues.

I have bought a copy of GOG version so I can see what cpath actually returns, and if I can find a solution.

I am pretty sure mod folders need to match between GOG and Steam to work properly. It should be safe to assume if a mod is workshop ID 12345 on Steam it will be in a folder called 12345 in the GOG mods folder. If it is not the user should not expect things to work properly. The code I was investigating while working on automatic mod downloading for GOG (proved the concept out but haven't solved the CRC needing to recalculate yet) showed that the folder name does matter in MP joining.

Edit: Non-numeric mod folders work too, in fact I strongly suggest that anything not on the workshop ensure it has at least one non-numeric character in its folder name when placed in the GOG mods folder or steam workshop folder to ensure it is not improperly thought of as a workshop mod.

Mods don't belong in the packaged mods folder but might work there. I still strongly advise against putting anything in that folder as it is intended purely for mods that are packed into the base game and the code around it is... interesting.

Originally posted by Nielk1:

I am pretty sure mod folders need to match between GOG and Steam to work properly. It should be safe to assume if a mod is workshop ID 12345 on Steam it will be in a folder called 12345 in the GOG mods folder. If it is not the user should not expect things to work properly. The code I was investigating while working on automatic mod downloading for GOG (proved the concept out but haven't solved the CRC needing to recalculate yet) showed that the folder name does matter in MP joining.

Edit: Non-numeric mod folders work too, in fact I strongly suggest that anything not on the workshop ensure it has at least one non-numeric character in its folder name when placed in the GOG mods folder or steam workshop folder to ensure it is not improperly thought of as a workshop mod.

Mods don't belong in the packaged mods folder but might work there. I still strongly advise against putting anything in that folder as it is intended purely for mods that are packed into the base game and the code around it is... interesting.

I've provided my in progress mod to several GOG users and they threw it into packaged mods and it ran fine...I don't know how or why it wouldn't work correctly but that has just been my experience. I'll just check against both folders (mods and packaged_mods).

Good to know about the folder ID...if I can "assume" it has the same folder name as the steam workshop item then this should be pretty simple to add.

Originally posted by GrizzlyOne95:

...

packaged_mods and mods are both scanned for mods, but packaged_mods appears in other places in the code too for reasons I have not yet determined.

Very well, thanks for bringing this to our attention.