Excelsior

Seems like if I open my rune book once before I put a rune in it the client says you cant place a rune in a book your reading until I restart the client.

Just for reference my rune book is in my blessed bag so dont know if that affects anything.

Me and my wife have this gag on the internet "woops wrong button". We have itchy trigger fingers and have a tendancy just to click/open something cuz its there so if I even think about putting a rune in a rune book I open the rune book on reflex even though I dont have to lol. In this case I SHOULDNT so now I have to train myself to not woops wrong button the rune book until I've put all the runes in it I want for the session.

lol.

Test it again - I've isolated what caused the problem for me, and it's just a little bit more specific.
I had this issue a while back and I noticed that if I opened the rune book, and closed it normally by right clicking the gump, it would be absolutely fine if I wanted to add more runes to it. Never had any issues as long as I make sure that I close the rune book gump the correct way before trying to add a rune.

The issue occurred only when I opened the rune book, and then opened it again by double clicking the book/use last item macro while it was still open.
Then, without fail, I would get an error message saying I could not add a rune to the book while viewing the contents.


For the record, I keep all my rune books in a blessed bag too, to reduce clutter.

Simply log out, then log back in. That fixes it

from past experiences (and I also think there are other posts on the forum about this same topic), I think one of the major causes of this(but maybe not the only one) is opening a 2nd runebook without first closing the 1st. So, if you open it, close it before opening another one

test that and see if that is the issue...

and as +Colibri said... if that happens... just do a quick relog and all better

I'll do some testing when I get a chance but I have two other ideas to throw into the mix.

One is if the rune book closes by using it then it might cause the bug.

The other is the rune book being in a blessed bag.

I didnt do either of those things today and opened a rune book to see which one it was and thought crud now i cant add the rune, and then closed it and tried anyway and it worked.

I'll keep an eye on it and see if i can play around with it when im not tired. Just get anoyed when im tired having to constantly relog every time to test what does and doesnt work lol.

Schwanke wrote: One is if the rune book closes by using it then it might cause the bug.

The other is the rune book being in a blessed bag.

The former one shouldn't cause the issue. I've been able to remove and add runes without a hitch after using all of my rune books that way. In fact that's the way I usually use them out of habit, only rarely do I target the whole book with a recall spell these days.


As for the latter, I've had a blessed bag for a long long time and my runebooks have sat solidly inside for a while - I can't remember if I encountered this issue before I obtained a blessed bag, so I'll test it right now.
Result of test - I can flawlessly reproduce the bug in a runebook in my main backpack as well, not just the blessed bag.



As long as I remember to never open a runebook when I have another rune book open, I'm safe.
I just have to make sure I either use (so it automatically shuts), or manually right-click-close any open runebook before opening another runebook/the same runebook again for whatever reason.