Unable to Memorize Wizard Spells

SDShannonS · January 13th, 2020, 08:19 PM

I created a wizard and put spells into my spellbook and then memorized a bunch of spells. When I went to rearrange my spells, I found that I could no longer memorize any of my existing spells. I don't understand why.

What setting in my character would be preventing me from memorizing spells?

SDShannonS · 11:39 AM

The problem seems to persist across multiple characters. I completely deleted the entire character, created a brand new one, and I can't learn any of the spells I've put into the spellbook. The interface comes up, but it lists no spells to choose from.

Dami · January 15th, 2020, 01:24 AM

Use the link within HLO to raise a bug report, or send an email to support and they can work out what's happening.

Mathias · January 15th, 2020, 08:03 AM

And check again before you send the report - I think this is one we found in our internal testing yesterday and fixed Tuesday evening.

SDShannonS · January 15th, 2020, 03:44 PM

Yup, update seems to have fixed it. Thanks for the heads-up, Mathias.

SDShannonS Junior Member Join Date: Jan 2013 Posts: 26 January 13th, 2020, 08:19 PM	I created a wizard and put spells into my spellbook and then memorized a bunch of spells. When I went to rearrange my spells, I found that I could no longer memorize any of my existing spells. I don't understand why. What setting in my character would be preventing me from memorizing spells?
#1

Dami Senior Member Join Date: Mar 2013 Location: Melbourne, Australia Posts: 1,086 January 15th, 2020, 01:24 AM	Use the link within HLO to raise a bug report, or send an email to support and they can work out what's happening. Current RPG's: Pathfinder (GM), Pathfinder (Player), Gamma World (GM, Pathfinder homebrew). HeroLab: 3.5 & Pathfinder. HL User Files for PF: Greyhawk Setting, Gamma World (WIP). DM and player of D&D since 1980.
#3

Mathias Senior Member Lone Wolf Staff Join Date: May 2005 Posts: 13,213 January 15th, 2020, 08:03 AM	And check again before you send the report - I think this is one we found in our internal testing yesterday and fixed Tuesday evening.
#4