Caites' Mods Compatibility Page

FAQ (including patch 7 questions)

Q (Patch 7): Do I still need to put mods to Override/mark them as replacer?

A: Strictly saying there is no more "Override" thing, all my mods will be active and should be in the list (be it main list of in-game MM or whatever happen to

Active Mods of BG3MM), unfortunately. Either this or loose files - that is an option for SOME mods, but I would try to avoid it altogether.

Q (Patch 7): Was meta data change?

A: All mods ported to patch 7 have UUID different from those in old versions. This shouldn't be an issue, since normally my mods were in Overrides and your modsettings didn't have them, with UUID, in the list.

Q (Patch 7): Which of your mods are official?

A: All my mods except three are official - that means you won't see additional warnings and popups from the game. But there will be official mods on mods.io (MM will provide full access to them from the game, you will see thumbnails, screenshots and short desc) and official from Nexus (you won't see details about them in in-game MM and need to manually put their paks to Mods), otherwise they are equal. Only one version of the given mod will be presented on mods.io (for casual players and potentially console players), Nexus as previously will have all of them.

Q (Patch 7): What about those unofficial mods?

A: 3 mods which are not official are No Intro, Better Hints and New Loading screens and Better Map Icons. They technically can't be made official right now. You will see warning triangle near them (as for all 3rd party mods) and game will be asking if you are sure about enabling them when loading your save. They work properly, its just how in-game MM treat them rn.

Q (Patch 7): Were requirements changed?

A: Good part of mods (Better Inv UI, Better Hotbar, Dynamic Sidebar, Better Tooltips, Better Map, Damager Preview 2, Better Combat Log, Better Topbar, Better Target Info, CDPR) have Improved UI as a dependency. Since toolkit doesn't provide ways to release official mods under the same ls:state of statemachine, we were needed to split them manually and since ImpUI already does similar things we moved that part to ImpUI. Shouldn't be a problem since