What would cause the book to close while typing or sometimes for no reason at all. Everytime I'm adding a custom spawn and using the book it closes when I either turn the page or sometimes it just closes for who knows why. Any ideas? thx
if you move too far away from the spot that you first opened the book, it will close.
The way the book interface works is to create a temporary book at your current location.
That lets you open it and enter in text, but the client will close the gump if you move too far away from the temporary book.
I figured that was the case, on moving too far from the spawner or even moving at all in some cases. However, it does this to me when standing on the spawner and perfectly still. The dissapearing for no reason is not very often, but every single time I turn the page while typing it closes.
does it also do this if you turn the page manually?
About 90% of the time, yes.
hmm. I'll have to look into that. What happens normally when you turn the page of a book is that it closes the book gump and then reopens it to the next page. It sounds like for some reason you are not getting the book to reopen after it closes.
This is also on my beta 36 server, so it may just be a compatibility issue. If so, I'm not worried about a fix, it's just something else I'll deal with. thx for your help though
here is something to try. In BaseBook.cs, comment out this line around line 200
QUOTE |
public static void Initialize() { PacketHandlers.Register( 0xD4, 0, true, new OnPacketReceive( HeaderChange ) ); // PacketHandlers.Register( 0x66, 0, true, new OnPacketReceive( ContentChange ) ); PacketHandlers.Register( 0x93, 99, true, new OnPacketReceive( OldHeaderChange ) ); }
|
I'm about to fire up my test server, so I'll stick that in as well as try the fix for the other thread (xmlquestnpc). I'll be back in a few with some results

Thanks again Arte
I commented out that section of code and it didnt seem to help.
I'll take a look at the code and see what else I might be able to come up with.
Don't bust your head over it. If it's not an easy fix no problem, since I'm using the beta 36 with this I expect some things to not work perfect, and this is something that's not a high priority.