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
Mod fixer does not contain any other overriders, nor does it contain any story definition or references. You can test this yourself by enabling story compilation debugging and logging using Script Extender and you'll see some "hardcore" (internal name for honor mode) references being loaded which did not exist at the time Mod Fixer was created, as Honor Mode is a recent game addition.
Recompilation of the story on character creation is a necessity to make mods work that alter core game logic (i.e. character creation, in-game UI, dialogue changes, etc.).
This topic is best posted on the forum of your modding site of choice.
Same goes for topics where people report mods related issues. And yet we have them over here plenty.
Now let's get back to BG3 Mod Fixer. You might want to go to the Nexus Bug Reports section for it.
18 Pages of Bugs! Most mods there have maybe 1 page of Bug Reports.
https://www.nexusmods.com/baldursgate3/mods/141?tab=bugs&BH=1
You can view at least two people saying directly it prevents them from turning in "mission related" or quest items post Hotfix 16. Plus a whole bunch of others in the forums.
Go a little further back and you will see several bug reports about it blocking the Epilogue from being viewed. (I think embedded mods containing it are causing me this problem.)
Bug reports on it blocking kiss and other animations from occurring. Bug reports on it interfering with "getting" Minthara. Problems, problems, problems ...
I can probably track down the three people here on these forums who said they did nothing else but disable BG3 Mod Fixer, and then they were able to turn in quest items.
I don't know how much additional evidence one needs.
Again, I'm not on Windows so some of these things I can know only from reading, rather than direct experience, but it seems what BG3 Mod Fixer does, can be done better, more safely, and less "dangerously" with Script Extender, and if you have v12 of Script Extender, patch 5 of the game, and any mod made after release of the game, you.do.not.need.it. It is "solving" a problem with how mods interact with the game that no longer exists.
If you're wondering why I keep blathering on this, it's because mods containing the "mod fixer" are blocking me from seeing the Epilogue, and POSSIBLY one other issue. And unfortunately, because I can't use Script Extender, I also have no solution.
Other than purging ALL mods from my saves, which I really can't feasibly do.
18 pages... that tab is supposed to be empty / only having posts with marked as resolved
That sure does not give a good impression of the mod author. Holy... 18 pages... by the looks of it, it is basically abandonware - exactly as you wrote before.
Are you serious? Remove the mods.
Personally, I have never used it, and never seen this bug, and I can't even USE SE, but then, I think it is embedded in other mods I have. If I was on Windows, I could know for sure which ones. But anyhoo.
Mod Fixer is necessary to actually force a recompilation of the story. That is all that Mod Fixer does and why it never needed an update since August 2023.
Mod Fixer is NOT at fault for the Hotfix 16 bugs.
To avoid further side effects, BG3 Script Extender is required.
I recommend you extract the Mod Fixer pak file and see for yourself what it contains.
Again, Mod Fixer is NOT at fault for the HF16 issues.
No matter how often you claim that: others have proven with their tests it is related to the issues seen with hotfix#16.