I think I know why it crashes and it should be easy to fix. Although I'm a bit dazzled by how it came to that, the only current crash that could happen with regards to simply opening a(ny) book is if you activated the OMOD and then de-activated the OMOD. When you say it only crashes with the mod active, do you mean active in the load order or active as in the OMOD is (also) active? Also, which option did you select for the UI when you activated the OMOD and what UI mod (if any) are you using?
For now you can try deleting the book_menu.xml that is found in the Data\menus folder. That should fix the crash but also means some parts won't work. So first check if that fixes the crash and then try to re-activate the OMOD. Else try manually copying the appropriate book_menu_xx.xml from the archieve.
Oh and no, loadorder shouldn't matter.
-Kyoma
Well, first I installed the mod manually. Then, I decided to delete the manual install and make an OMOD instead. I wonder if
that caused the problems. When I say "active" I mean active as an OMOD. I have the Darn UI version.
I tried deactivating the OMOD and deleting it. Then, I reinstalled the mod manually again. The mod worked when I took out the book_menu.xml, but not when I had it in use. I tried manually copying it from the archive, but it still didn't work.
I decided to try one last test. Instead of using the Darn UI XML, I used the regular vanilla one. It works fine now. The buttons look a little mismatched occasionally, but its better than having a dysfunctional mod.
I appreciate the help, Kyoma.