Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If the mod puts something into the game that didn't exist before, and you save the game ... then you disable the mod ... and try to re load the save, this can OFTEN cause a crash because the game no longer "knows" what the nonexistent item does. This can be a big problem with mods that add new equipment, though not necessarily with those that change the properties of existing equipment. I have found with class mods, respec any one you have out of the modded class, then remove the class mod, and everything proceeds fine.
Or as we can put it more simply, many mods create save dependencies.
Ones without save dependencies can usually be disabled without issue. A good mod author will often put in the description of the mod whether it creates dependencies.
Unfortunately, there are all kinds of mod authors. And THAT has led to some of my irritating frustrations with SOME few mods I've run across. They don't bother to tell you.
As I've said - a good author of a cosmetic mod should tell you in the description whether it creates dependencies or not. But you can't count on them to do so.
AFAIK, the only cosmetic mods creating Hotfix 16 issues have BG3 Mod Fixer embedded.
I do not understand your initial premisse.
Nonetheless I consider seeker1's comment very helpful.
Why do you want to get rid of mods that badly? If you are no longer satisfied with them there is no way but to start a new playthrough.
If you are experiencing issues with the current game version but it worked with a previous game version, consider a rollback of the game.
If you are afraid a future patch might bug out the modded playthrough, freeze your game version.
What is your initial intention here?
Ah. Now I see.
Anyway, besides regressing patches and updates, most good mod authors, once they know their mods are creating problems with a patch, will release updates. For example, the guy who does Party Limit Begone -- Legacy, did that (updated 1.7.3 to 1.7.4 to make it compatible with Hotfix 16.)
By now it is like an old song... like "Last Christmas", if you will, that I recommend strongly when using mods to freeze the game version. I emphasised that strong in my guides.
I cannot help you with the decision how to go on from here. I probably would, if 50 hours feels much to you, rollback the game version if I were you. But then I am having so much fun replaying the game... plus such issues can also happen without mods.
By the end of the day the decision is yours and I wish you good luck when contacting the mods authors for assistance.