Not sure why this happens but been getting this report on a few of my mod pages so wanted to give a heads up.
I tested it myself and it does indeed cause issue for other mods when people try installing it via a mod manager or installing via editing the modsettings.lsx which I realise is against your installation instructions on your mod page description but I wanted to confirm the issues people were getting.
I have a solution that will hopefully help. The solution though would be updating the mod so it can't be installed by mod managers or editing modsettings. You can achieve this by removing your Mods folder that contains the meta.lsx and then repacking into a .pak
By doing this it then works still via dropping into the mods folder as per your instructions which causes no conflicts with other mods. And ensures less people accidentally installing it wrong.
Just thought I would share what has been happening and a possible solution. Thank you for your time, happy modding.
Thank you for the heads-up; this has worked for me: "extracting the .pak and placing it as loose file in AppData\Local\Larian Studios\Baldur's Gate 3\Mods" :)
I installed it as described, manually dragging it to the Larian Studios\Baldur's Gate 3\Mods folder, uninstalled it, reinstalled it again, and repeated the process, because the minimap is in the place of my chat on the stream, and after 2 hours of testing I reached the conclusion that it is the mod that is causing the problem :/ It may not have been a problem for you, but it certainly was for me, but just in a previous existent save I know that several mods can cause problems with existing saves, but this was the only incorrigible one for me happy modding to all!
66 comments
Thank you anyway.
I tested it myself and it does indeed cause issue for other mods when people try installing it via a mod manager or installing via editing the modsettings.lsx which I realise is against your installation instructions on your mod page description but I wanted to confirm the issues people were getting.
I have a solution that will hopefully help. The solution though would be updating the mod so it can't be installed by mod managers or editing modsettings. You can achieve this by removing your Mods folder that contains the meta.lsx and then repacking into a .pak
By doing this it then works still via dropping into the mods folder as per your instructions which causes no conflicts with other mods. And ensures less people accidentally installing it wrong.
Just thought I would share what has been happening and a possible solution. Thank you for your time, happy modding.
Good game to all^^
It may not have been a problem for you, but it certainly was for me, but just in a previous existent save
I know that several mods can cause problems with existing saves, but this was the only incorrigible one for me
happy modding to all!
I wish there was a way to indicate a zone is hostile..but still.. love this soo much!