Not really a bug per say but Vortex is getting this one confused with https://www.nexusmods.com/baldursgate3/mods/902 (More Surrur tree bark) and keeps noting these mods as redundant. (Posted on both mod pages).
Had some look and there is no reason why that should happen. Probably a Vortex bug, so maybe report it to them. Our mods have nothing to do with each other and are completely unrelated, they don't even do similar things. That aside, most people use BG3ModManager instead of Vortex because it is actually built to handle BG3 mods specifically.
Would it be possible to get a version that also restricts the aura to only effecting ALLIED undead?
As it stands with vanilla this aura strangely applies to the enemy undead also, which is very weird since no other Paladin aura applies to enemies AND the only undead that actually use weapons in vanilla are enemies that players themselves are unable to use as summons.
Can I make a suggestion, change the feature of this aura, to whenever damage type, you do add necrotic to your damage type weapon or spell or unarmed for undead or fiend only allies
Thats the fix I've been waiting for. Would it be possible to deliver it in a version with two files: info.json and .pak so I can use it with the Mac Mod Manager?
I recently asked the same question for the Arrow Trajectory Mod made by @xDennis83x and in the comments @robogena pointetd out that there ist a tool (Modder's Multitool) on GitHub, which makes it relatively easy to generate the info.json file. So maybe you could gibe it a try? It would be very fantastic if more of your great mods would be available for the Mac Mod Manager, especially because the release of Mac/console mods by Laran takes so long.
Yes, the modders' multitool is known among modders as it was the only way to package and unpackage mods before the official modding Toolkit came out that does it automatically (I already had it and used it before the toolkit came out). The info.json is only generated by the Modder's Multitool, but both the multitool and the Toolkit create a .pak. To be honest I'm not sure the info.json does anything useful anymore, but maybe the Mac Mod Manager specifically needs it for some reason, the BG3 Mod Manager for Windows doesn't need info.json's to import mods.
Thank you very much. As of right now, the Mac Mod Manager requires both files (info.json and some .pak file). I hope they will change it some day the same way the PC Version works now. Since Larian decided to bundle the Mac and console Mods instead of giving Mac users access to the PC Mods, the Mac Mod Manager is my only workaround.
It should affect the paladin himself too, yes, but there's a bug now that I noticed affecting that that I'll fix now with the next update I'm working on I'll upload in a few minutes. I'm considering expanding it to affect ranged attacks too.
11 comments
As it stands with vanilla this aura strangely applies to the enemy undead also, which is very weird since no other Paladin aura applies to enemies AND the only undead that actually use weapons in vanilla are enemies that players themselves are unable to use as summons.
Would it be possible to deliver it in a version with two files: info.json and .pak so I can use it with the Mac Mod Manager?
Yes, the modders' multitool is known among modders as it was the only way to package and unpackage mods before the official modding Toolkit came out that does it automatically (I already had it and used it before the toolkit came out). The info.json is only generated by the Modder's Multitool, but both the multitool and the Toolkit create a .pak. To be honest I'm not sure the info.json does anything useful anymore, but maybe the Mac Mod Manager specifically needs it for some reason, the BG3 Mod Manager for Windows doesn't need info.json's to import mods.
As of right now, the Mac Mod Manager requires both files (info.json and some .pak file). I hope they will change it some day the same way the PC Version works now. Since Larian decided to bundle the Mac and console Mods instead of giving Mac users access to the PC Mods, the Mac Mod Manager is my only workaround.