Hey! I downloaded version 4.0 of the mod and I seem to not be able to use your Unholy Smite mod that goes in tandem with this one. I reclaimed my oath, which let me use divine smite, but as soon as I broke my oath and went back to being an oathbreaker, I lost access to both.
Hello. Yes, I apologize. There was a small bug when combining both mods since I updated this one but forgot to update the Unholy Smite too. The fix to that bug is on the latest update (version 3.0) of the Unholy Smite mod, so please make sure to update that mod and try again.
There are two ways to make changes to progression (the features you unlock as you level up):
Overrides: literally overwrite the existing content with your entry. Usually you copy what's there and then add yours. The problem with this is that if multiple mods use this method, only the mod loaded last will actually apply (because they copy the content of vanilla/unmodded base game, and then add theirs, they don't include other mods).
Merging: created by Larian for Patch 7, using this method you only create a new ''empty'' entry and then add your new content. Then, using Larian's automated system, this entry will be merged into the base-game entries. This, assumming it works as it should, is the perfect way of doing it. But right now it doesn't work that way. Sometimes, the merging process gets bugged and only applies to progression for single-classes, while ignoring multi-classes. Even worse, when that bug happens, the game checks if the base game has an exclusive multiclass progression or a shared one; if it only has shared one the game merges your changes into the single-class progression and deletes the WHOLE multi-class progression (base-game AND modded), creating situations in which if you multiclass with that mod installed, you will get a level-up with NOTHING on it, losing all features of that level permanently. This is all on Larian and their buggy progression merging system that doesn't merge properly without breaking other things. To work around this, most modders either use overrides (not ideal because of what was said in point 1 but in some situations in can be harmless as you are not supposed to have two different mods touching that same thing) or use Compatibility Framework (requires Script Extender which is a third-party tool and it doesn't support all platforms; this tool literally does merging the way it should and also can do much more like surgically removing entries from anywhere without affecting the rest).
Thanks for bothering to explain. I actually faced that issue with modded Warlock class, multiclassing showed me no new skills!
So there are 3 methods: 1_ Override everything, resulting in only the latest mod working 2_ Merge by Larian, allows features from several mods but too often bugs many things 3_ Merge by Compatibility Framework, works well but has to be maintained by a 3rd party and only works on Windows
To be clear, Compatibility Framework works flawlessly even without being updated for a long time. I don't think it even needs to ever be updated. The only ''drawback'' (if you can call it that) is that it requires ScriptExtender and external integration: you can't do it inside the official toolkit; usually I finish my mods with normal progression for mod.io, then I unpack my own mod with third-party tools, delete normal progression and add Compatibiliy Framework merging, and rename this version of my mod to ''NexusMods ver.''.
ScriptExtender is updated super regularly and works great so I don't think itself is a problem. So the real problems are: you need to do a very small amount of extra (external) work to make it work with Compatibility Framework and that people that can't/won't use ScriptExtender won't benefit. These problems are small in the grand scheme of things in my opinion.
I assume you mean the 3rd-party BG3ModManager. Not exactly, but it has a built-in menu option that downloads and installs it for you automatically if you use it. And regardless of whether you installed ScriptExtender manually or via BG3ModManager, by default it auto-updates itself everytime you run the game (what you actually install when you install ScriptExtender is an auto-downloader that downloads the latest version of the addon when you open the game).
8 comments
So there are 3 methods:
1_ Override everything, resulting in only the latest mod working
2_ Merge by Larian, allows features from several mods but too often bugs many things
3_ Merge by Compatibility Framework, works well but has to be maintained by a 3rd party and only works on Windows
To be clear, Compatibility Framework works flawlessly even without being updated for a long time. I don't think it even needs to ever be updated. The only ''drawback'' (if you can call it that) is that it requires ScriptExtender and external integration: you can't do it inside the official toolkit; usually I finish my mods with normal progression for mod.io, then I unpack my own mod with third-party tools, delete normal progression and add Compatibiliy Framework merging, and rename this version of my mod to ''NexusMods ver.''.
ScriptExtender is updated super regularly and works great so I don't think itself is a problem. So the real problems are: you need to do a very small amount of extra (external) work to make it work with Compatibility Framework and that people that can't/won't use ScriptExtender won't benefit. These problems are small in the grand scheme of things in my opinion.