Issues with OneDrive and new mods folder?

[Mechsrus]

Noob question. Now that the official mod loader is in the Documents\My Games folder, is anyone having any issues with the mod loader where OneDrive Sync is enabled in WIN10 and the mod files seem like they are actually on OneDrive than on local? Ex. path is actually C:\Users\User\OneDrive\Documents\My Games\BattleTech\mods.

It seems like mods are not appearing in the loader, or disappearing after enabling and then restarting the client. I am just trying to enable a simple mod like BTMLColorLOSMod following the instructions PDF. Thanks.

 

[tainted loki]

thats because the modloader in looking here --> C:\Users\User\Documents\My Games\BattleTech\mods

 

[Mechsrus]

thats because the modloader in looking here --> C:\Users\User\Documents\My Games\BattleTech\mods

And when I go to "C:\Users\User\Documents\" there are no folders there so again is it an issue with OneDrive moving stuff up to the cloud...

 

[tainted loki]

you should be able to exclude it from onedrive, you'll have to google it since no links.

 

[Mechsrus]

I wound up having to exclude the entire Documents library from OneDrive since, Microsoft being Microsoft, apparently you can't exclude at folder level. Had to copy data back down to local drive as well. So the files are in the right place on the local but the mod loader is still not working. It sees the BTMLColorLOSMod on startup but after enabling, saving, and "restarting the client" the mod disappears from the list of available mods. The mod files are still in the mods folder and have not been deleted. It's listed in the load order but doesn't look like the cache and database were updated at all. No error log. I think I'm giving up on this thing and using the updated Modtek.

 

[ronhatch]

I wound up having to exclude the entire Documents library from OneDrive since, Microsoft being Microsoft, apparently you can't exclude at folder level. Had to copy data back down to local drive as well. So the files are in the right place on the local but the mod loader is still not working. It sees the BTMLColorLOSMod on startup but after enabling, saving, and "restarting the client" the mod disappears from the list of available mods. The mod files are still in the mods folder and have not been deleted. It's listed in the load order but doesn't look like the cache and database were updated at all. No error log. I think I'm giving up on this thing and using the updated Modtek.

Oh, hey... that sounds very familiar all of a sudden. Turns out that user Red1812 forked off a newer version of BTMLColorLOSMod... search for it on GitHub or follow the forks link on the original GitHub page. It's working just fine for me, and the older version was doing exactly what you're seeing.

(Though I did end up using ModTek for other mods, I've got the version that doesn't disable the built-in loader and LOS is one of the mods I've got running from the built-in.)

 

[Mechsrus]

Thank you! I will try that one!

 

[Mechsrus]

@ronhatch BTMLColorLOSMod still isn't working for me even with the latest files by Red1812 from Github. The mod loader just doesn't recognize it. I did try the latest Panic System and it shows up and works fine.

 

[ronhatch]

@ronhatch BTMLColorLOSMod still isn't working for me even with the latest files by Red1812 from Github. The mod loader just doesn't recognize it. I did try the latest Panic System and it shows up and works fine.

Well, that's too bad. Strange also... I wonder what the difference between our systems is. I played around with the settings/colors a bit, but didn't make any other edits to the mod.

Edit: Oh, but maybe try clearing the cache? In the mod/HBS folder, there are two folders that store intermediate files used while loading mods. If the version number is the same as the prior incarnation of the mod, the loader may see that and think it doesn't need to rebuild those files. Deleting those folders will force it to re-create them the next time the game is started. That could be why we're seeing different behavior.