did you check the
FAQ?
This almost certainly means you have your background fps too low.
the spellbook thing is addressed in each of the FAQ of each of the plugins. it is 99% likely that it is a *you* issue and not a plugin issue.
Unfortunately, if you have too low of a background fps set, and "instructions are missed" or whatnot - mq2 won't be able to report back the correct information about it. The is the same thing that will happen with follow or nav or even combat routine skipping stuff when your background fps is too low - just in this instance, we're not being given correct information about the state of your window.
Q. I sometimes get stuck in my spell book?
A. This is often due to your background fps not being high enough. It is strongly advised to utilize at LEAST 30 fps for background, recommended 60+ background fps. The fps cycle for eq is where "work" is done. If your background fps is set to "min" you can and will have undesired results with all sorts of automation activities.
Alt-O -> Display -> Advanced - > Max Background FPS
what is your alt-o in game background fps set to? do you have isboxer limit your background frames, or other software?
those should be 60+ otherwise you're likely going to run into those issues i spoke about.
eq does "work" during the fps cycle - if it is set too low --- work is skipped. the normal memming kicks you out of your book - and we check if the book is open more faster than you can count.
but if you are in manual mode - and the instruction after you memorized a spell was skipped due to your low frame rate - then you can and will get skipped because manual mode only takes you out of the book if you memorized a spell - if you manually open the book, then we don't kick you out - so if your frames being too low skips that communication and you're in manual mode - you're gonna be chilling in the book because it looks like you wanted to be in the book.
tl;dr - you need to check your in game fps settings in your alt-o window -> advanced as well as check what you have isboxer limiting your frames to.
limiting background frames is sweet for boxing - until you need them to do automation. since you already run eqwire you shouldn't need to limit those frames anyhow - eqwire just makes it not "draw" the stuff, but the "fps cycle" still occurs