Arelith

Description
==========
Loss of sorcerer spell slots without casting spells due to equipping and unequipping magical staff that grants bonus spell slots.


Steps to reproduce
----------------------------
Equip staff with bonus Spell slots on a Sorcerer PC and rest to gain full spell slots from Stats and Item. Unequip staff while in town or meetings to keep one’s personal fashion sense and RP charisma in place. Re-equip staff when out and about. Do several times if popular or tortured by multiple meetings.


Expected result
-----------------------
When Equipped Bonus Spell slots are gained. When Un-equipped Bonus Spell Slots are lost. No change to Stat or Level given spell slots.


Actual result
-------------------
When the staff is equipped and one rests all spell slots and bonus spell slots are gained. The first time unequipping the staff, bonus spell slots are lost. Reequipping the staff does not return the bonus spell slots, however unequipping the staff will remove a spell slot from the same spell levels that were supposed to be granted.

Simply put, one can equip and unequip a magical staff that grants bonus spell slots (losing a spell slot each time) until zero spells remain from the bonus spell levels without once casting a spell.


Screenshot(s)
--------------------
N/A


Misc Notes
----------------
The only Spell levels effected are those in which bonus spell slots were granted by the equipped staff. In this case Levels 3,4,5,6 were effected due to the staff while remaining spell levels say no change.


Which Server(s)?
------------------------
C&P


Gaming Platform(s)?
------------------------------
PC

This has been a thing with NWN since forever. If you're a spontaneous caster (or even not) and you go equipping and unequipping as you say, that is what happens. You fix that by resting.

The difference for prepared casters is it keeps track of specific slots, spontaneous don't. So prepared will keep on taking away the last spot, while spontaneous will just take away slots on unequip.

There is a way that this could potentially be fixed with some extra pain in the butt coding, but the simplest answer for the past 20 years for this problem is either: 1) re equip and rest. Or 2) stop doing it

Addendum: same thing happens if you keep increasing and decreasing your casting ability score with bonus spell slots.

Further addendum: the reason why this does this is if you got all the slots back on equip without resting, you'd be able to have infinite spells of that slot.

So this isn't really a bug, this is entirely intentional by the base game.

Inkish wrote: Sun Jan 01, 2023 8:53 am This has been a thing with NWN since forever. If you're a spontaneous caster (or even not) and you go equipping and unequipping as you say, that is what happens. You fix that by resting.

The difference for prepared casters is it keeps track of specific slots, spontaneous don't. So prepared will keep on taking away the last spot, while spontaneous will just take away slots on unequip.

There is a way that this could potentially be fixed with some extra pain in the butt coding, but the simplest answer for the past 20 years for this problem is either: 1) re equip and rest. Or 2) stop doing it

Well bugger . . .

Thanks for explaining the issue nevertheless! It helps me understand the situation!

Please Close this Thread, as its a NWN bug and not an Arelith one.

This is actually a bug. While Inkish is correct for base NWN, this was fixed last September to no longer occur (thank you Silvard!).

https://forum.nwnarelith.com/viewtopic.php?f=23&t=25&start=1075#p307790 wrote:* Bonus spell slots from equipment for spontaneous casters now behave consistently with bonus spell slots for prepared classes. Unequipping an item with bonus spontaneous spell slots only diminishes slots from the pool of bonus spontaneous spell slots from gear, if they haven't been used, and only once. Subsequent equipping or unequipping of items with bonus spontaneous spell slots have no effect on the remaining usable spontaneous spell slots on your character.

So if it's no longer doing this, then it's a bug.

Found the culprit, I think. Expect a fix within the next few resets.

Should be fixed now, closing this.