Quote:
Originally Posted by Lord_Greywolf
cool
I will be adding this in on my next restart
just have to figure out how much crap & skill will be needed to make this thing
one one question:
you said can extract a runebook
is that just runes only or the book with runes in it?
does it totaly remove it form the list then (and same when extracting runes)?
and if it is the books - where is that at in the scripts - i might make an option where you have to have materials in pack for doing that (like an empty book)
|
InternalRunebookGump:
Code:
if (buttonID == 96)
{
from.CloseGump(typeof(InternalRunebookGump));
from.SendGump(new OKTargetGump("Remove Runebook?", 16777215,
"Are you sure you want to remove this Runebook?",
16777215, 300, 300, new GenericOKCallback(RemoveRunebook_Callback), m_MasterBook, m_Book, m_BookNum));
}
Thats where the Gump calls it, but the actual extraction occurs down further in the script, in the
RemoveRunebook_Callback method.
This extraction takes the runes and the name and creates a Runebook in your pack. It removes them from the MasterRunebook.
One thing I forgot to do was handle the charges, both coming in and going out. If you drop a Runebook onto the MasterRunebook, you lose whatever charges you had left. If you extract the Runebook, you lose the charges there too. (I get em coming AND going. hehe)