Allow Captured Information in Spellbooks

SF ID: 1541817
Last Update: Settings changed ( thpr )
Details:

It would be nice to separate out the known spells from
the spells in a spellbook. There is a case when a
wizard has a spellbook that has been captured from
another wizard, in this case we want to be able to view
the spells in the spellbook, but not be able to cast them.

At the moment the only way to do this is to create a
blank spellbook in the inventory, and then not put any
spells in it, but to just put the spells present in the
captured spellbook into the character notes under the
description tab.

A better way might be to drive the available spells
from the spellbooks rather than the other way around.
At the moment the spellbook can be populated onyl from
the spells that the wizard knows, which means that in
order to populate a captured spellbook the user needs
to make the spells available to the wizard which they
should not be.

If the functionality was driven from the spellbook then
we could keep a flag on each spell in the spellbook to
indicate if it should be in the known spells list or not.

The requirements would look something like this:

1. The user can add any spell in their class spell
lists into a spellbook.
2. Each spellbook will have a checkbox to indicate if
the spells should be also added to the known spells list.
3. Each spell class in the spellbook will have a
checkbox to indicate if the spells should be also added
to the known spells list.
4. Each Spell Level in the spellbook will have a
checkbox to indicate if the spells should be also added
to the known spells list.
5. Each spell in a spellbook will have a checkbox to
indicate if the spells should be also added to the
known spells list.
6. Togling the state of a checkbox will trickle the
change down to all of that elements children. (i.e. if
you toggle the check box for the "wizard" element then
the "level 0" element and the "detect magic" element
under it will also change state.
7. When adding a spell to a spellbook if the parent
tree element has the make available checkbox ticked
then the spell should be added with it's check box
ticked and the spell should also be added to the known
spells list.
8. If the check box for a spell is unticked then the
spell should be removed from the known spells list (and
any memorised spell lists).
9. If the check box for a spell is ticked then the
spell should be added to the known spells list.
10. A spell should be able to be added to the known
spells list more than once even if the GUI only
displays a single instance of it.
11. A spell in the known spell list should have some
piece of meta data attached to it to indicate that it
was added my a spellbook.
12. Deleting a spellbook will remove all of the spells
in that spellbook from the list of known spells (and
any memorised spell lists).
13. The GUI shall provide a clear indication of the
meaning of the check boxes on the spellbook tree.
14. The GUI shall provide the user with a notice when
they try to change a check box state that will affect
child elements (i.e. if the user tries to change the
tick box for the top level spellbook, or a class level
node it will warn the user if there are any spells in
the book and allow the user to abort the operation).
15. The user shall be able to add other spells to the
known spells list as normal.
16. If the user removes a spell from the known spells
list it should be removed from any spellbooks as well.
Submitted:

Frugal ( frugal ) - 2006-08-17 05:07:11 EDT