Request: Allow SPELLLEVEL tag to refresh the UI - making the Spell List mutable

Description

this one is preventing Summoner from working properly. SPELLKNOWN updates immediately, but SPELLLEVEL does not. If we can fix this, then Unchained Support would be better off for me.

Cheers,

Environment

None

Activity

Show:
James Dempsey
December 25, 2015, 7:12 AM

Did you have an example of how to reproduce this, what results you expect to see and what actually happens?

Andrew Maitland
December 25, 2015, 7:51 AM

See https://github.com/PCGen/pcgen/pull/799. for code and set up to reproduce.

Andrew Maitland
December 25, 2015, 7:56 AM

Human Summoner Level 1 - Charisma set to 13.

Spells populate with Standard version (Expected Result).
Select Unchained Summoner for the class selection.
Switch to Spells - HASTE is listed as a Level 2 spell. (This proves that the standard list is still being used)
Save the character, and reload.
Switch to Spells - HASTE is listed as a Level 3 spell. (Spell list now using the Unchained Version)

I can do the more drastic version. Put the standard and unchained spell lists on the respective choice abilities. Then no spell list appears until reload of character.

Expected Results. When a spell is granted to the character via SPELLLEVEL:CLASS|ClassName=x|SpellName, I expect the spell to be available in the UI. What happens, the UI does not reflect any change until the character is reloaded. (This is worse than the Druid Domain issue, since at least the domain is granted after a level change).

Hope that helps. I can supply a base character if desired.

James Dempsey
December 25, 2015, 10:33 PM

There is a deeply rooted assumption that the class spell list for a character is immutable. The UI is only reflecting what the core character model holds, so this is not just a simple refresh issue. This isn't something that I am comfortable changing at this late stage and would itself likely be a big project for me (2-3 days full time).

As a result I recommend this be changed to a feature request and the code and data design be discussed.

Perhaps the best short term solution is to go with the proposed data implementation for now but add a note to the class feature that the character needs to be saved and reloaded after application of the ability.

Andrew Maitland
December 25, 2015, 10:44 PM

Sounds like a plan. Changed to a request. My only uhg factor is conveying the information about Unchained Summoner to the end user. We have no simple message delivery system. Best I can do is put a NOTE on the Ability itself.

Thanks for looking into this.

Assignee

Unassigned

Reporter

Andrew Maitland

Labels

None

Theme

None

Epic/Theme

None

Pending User Input

No

Affects versions

Priority

Minor
Configure