Spell Scroll Duplication - And No More Revivify

Description

I have two unrelated problems with Baldur's Gate 3:

1) Scrolls of Revivify are everywhere. It cheapens the value and impact of Withers, it makes red areas of the map far less dangerous, and it makes death a pretty tough concept to sell.

2) I want to craft spell scrolls. They're already so abundant that it doesn't really affect balance, and I think it's neat.

So I decided to solve both problems at once.

Scrolls of Revivify no longer do anything. Their value is massively reduced, and they're renamed Blank Spell Scrolls. Blank scrolls can be combined with any other spell scroll to create an Inert Spell Scroll, of the same spell level. The combination consumes the blank scroll. The inert scroll can activated as an action by any character with the appropriate-level Spell Slot (at the cost of that slot), which will turn it into a copy of the combined spell scroll, effectively duplicating it.

Compatibility

Will almost certainly conflict with any mod that edit Scrolls of Revivify.

Only implements scroll duplication for vanilla spell scrolls. I automated a lot of the stats generation, so adding support for modded spell scrolls is actually very easy, but I don't want to bloat the main mod. If there's interest in adding support for modded spell scrolls, I'll touch up the automation script and throw it in a public Git repo.

If you experience bugs or issues, please try to replicate them on an otherwise vanilla save (with no other mods installed) before reporting. Include as many details as possible, including a guide to replicating the issue, if the bug persists.

The spell level of each inert scroll is derived from the ObjectCategory of the duplicated spell scroll's spell's stats - which Larian doesn't always get right. If an inert scroll generates at the wrong level, please let me know and I'll fix it manually.

In my testing, the Spell Slot requirement on the inert spell scrolls always shows the red warning texture. I have no idea why, but it's a purely visual bug. I don't plan to address it.