TL;DR: Doesn't work properly, and it seems to accelerate save bloat.
So, as of 08 July 2023's version there's a problem. The books keep glowing whether they have been read or not. I was lazy enough to not uninstall this mod, and after a while the game got worse and worse(unstable, that is), until it started to crash every 15-20 minutes. With the face of my pfp i started to remove mods one-by-one. And after reading tons of logs with different combinations of esps, i found a funny thing while loading save's strings: within the span of ~11 hours of gameplay BooksGlow.esp deadlinked 8230 strings . huh, that's a lot. Removing the mod and forcefully resetting all cells reverted the save to a stable state.
I'm bad with all of this modding mumbo-jumbo, and can't really help with finding a bug. But, i've created a clean save with just obse + your mod, and entered into cells with lots of books and opend a bunch of them for 20 minutes or so. And yep, when loading save's strings there was 3260 variables for the esp (somehow?).
In logs I see entries: Processing boosk in cell... Adding glowing book to array. Ref: 00029AFE - EDID: - Ref Count: 1 There are several more glowing books which differ by Ref & Ref Count.
After opening one in logs I see entry: Found a book with empty EDID, skipping.. Book namw: Report: Disaster at Ionith
I don't have any other books or tracking books mods. Here is a list of active mods: - AULIAS_1_2_5-39635-1-2-5 - Better Saves-48106-2-0-1687019358 - Carry all you want-5118 - Clearer Underwater-17411 - DarkUId DarN - DZ Auto Harvest 11-17984 - Harvest Containers xOBSE-52317-2-1-2-1664040203 - Highly Visible Keys And Lockpicks - Default-49206-V1-1687622118 - LINK 1_4-50144-1-1593351845 - MenuQue v16b-32200-v16b - More and cheap training-8523 - Nighteye Shader Replacement-7327 - obmm 1_1_12 full installer-2097 - Unofficial Oblivion DLC Patches-9969-25-1635879747 - Unofficial Oblivion Patch-5296-3-5-7-1635873247 - Unofficial Shivering Isles Patch-10739-1-6-0-1635878152 - Unread Books Glow-53086-1-0-1-1688785757 - xOBSE 22.9-37952-22-9-1686868858
Can't just book name be used to store and distinguish read / unread state? :-) This will eliminate need for other mods, ex. MessageLogger or EditorIDs.
Those who had problems with mod not working correctly please try today's update and let me know if it helps. There's also a new option in INI to turn on debug mode, which logs mod actions to console and might help to identify what and where goes wrong, try it if you have problems.
The same thing happens as with the first version. When entering the game, the books glow. It is worth reading one - and that's it, the glow disappears. It does not matter if there is a reboot, or a change of locations, the glow does not return anyway. xOBSE 22.9 version
For the sake of interest, I downloaded and tested version 0.9 in the game. It works)). Two new versions - the glow flies after reading the first book. I repeat, I have OBSE 22.9. I leave version 0.9, thanks. ps. Unfortunately, there are bugs in version 0.9. After restarting the game, the glow remains on all books, but does not disappear when reading new books. It's even embarrassing. Nevertheless thank you. English is not my native language.
Well... can't fix what I can't reproduce. I'm in a 20h+ playthrough right now, and for me everything works great. I've tried starting new game, I've tried to figure out what can go wrong in the code, and tried to safeguard everything I could think of, and at this point I've done all I could.
The only way that I could *confirm* what you're describing can happen is when using older xOBSE - because of the absence of GetEditorID2 function all books get catalogued under an empty string (instead of proper EditorID of the book form) hence the glow disappears on all books, because script thinks they are all references of the same book. Other than that I could not find a single reason why the behavior you're describing can happen.
Anyway, if v0.9 works just use it. Otherwise plenty of debug messages are available for those who's gonna try to figure out what's going wrong really.
Running Unread Books Glow 1.01 with xOBSE v22.9 and the debug option turned on. Whenever I read any book the line "UBG | Found a book with empty EDID, skipping.. Book name: <book name>" is printed constantly to the console and the book does not get marked as read. Which would seem to suggest that GetEditorID2 isn't functioning properly?
Sorry for late response, thanks to @llde's comment below it seems like function behavior of GetEditorID and GetEditorID2 may depend on MessageLogger. I have MessageLogger installed, and for me (on xOBSE 22.9) GetEditorID returns form ID number and GetEditorID2 returns proper editor ID and I rely heavily on those returns in this mod. You're right that if you get debug messages of blank editor ID that means that some functions of xOBSE aren't doing what they should, I have no idea what's the design perspective behind it, but it is how it is. So you may try to install MessageLogger if you don't have it installed and see if it fixes things. When I have time I might do more tests and try to adapt the mod to make it work in different specific conditions, or maybe future versions of xOBSE might change the behavior of those functions and the problem will go away on its own.
Ah. Rereading LLDE's comment, I found my issue. I have Message Logger installed but also Runtime Editor IDs as well. The mod started working when I disabled Runtime Editor IDs. No idea why one interferes with the other. So a simple fix would be to use Runtime Editor IDs' function GetRuntimeEditorID instead if the plugin is detected. I've patched the scripts to do so in a copy of the plugin here, and it appears to be working.
you guessed right. this version works for both, I don't think that changes to GetEditorID in 22.9 are a good enough reason to make two versions, so I just reverted to using the older function for now, no issues so far
EDIT: actually looks like I was wrong, I tested a bit more and figured that GetEditorID on 22.9 returns FormID for some reason and this means that if you change the load order or something like that things might get out of hand
yes it was the behaviour of the GetEditorID function stated i the contract that was wrongly changed in 22.8 introducing multiple regressions. GetEditorID2 return the editorID for book forms (and most other instance-able forms) only when MessageLogger is installed with the EDID hooks active and REID is not installed
I've encountered similar problems on the newer 0.95 version. You could try reverting to the older 0.9 version, since that one didn't give me as many problems, though the developer also says that one was programmed incorrectly somehow and might have bugs of its own.
The "Read one, they all stop glowing" thing makes me realize why the mod wasn't working in my other game. It wasn't because I installed it AFTER I stated the game, it was because I installed it AFTER I had already read a book.
The error appears in the console after reloading the save, before that no logs, just the first book is marked and the mod breaks. Restarting the whole game does nothing.
I initially didn't need the glow effect, I wanted to disable it in the ini, but in the end, in your description, I switched to Book Tracker Updated. Thanks anyway for your mod.
Well, I'm using XOBSE 22.9, and 0.95 of this mod, and can't for the life of me get books to glow.
I'm not sure why, I'm not using any Book jacket mods or anything else that would change the books
Could it be the quest doesn't start if you use an Alternate Start Mod? Is the quest waiting for me to exit the Sewers in order to start and make the books glow? If so, what's the quest name so I can start it in the console and see if books start glowing
the quest name is zefUBGQuest, try starting it manually no idea why it's not working for you, it's pretty simple really, but if you don't see glow and book names don't change then script is probably isn't running
Well, I know OBSE is working. Is the Script set to run when you exit the sewers? If so, then it's probably not going to start for anybody using an alternate start mod. I tried the SetStage command, but nothing happened, I tried setstage zefUBGQuest 10, and 20, 30 , 40 eetc. No glow
Those kind of mods start an invisible quest as soon as you enter the game with mod enabled and attach a script to that quest that runs in the background. This mod works the same way. It doesn't matter if you are mid playthrough or starting fresh, quest should start anyway. It's technically possible to run a "completequest" command via script or manually which will stop the quest and the script, and the game will remember that the quest is completed and won't start it again at game restart. That's the only thing that I can come up with. Later bethesda games allow you to mark a quest as repeatable, so you can start it multiple times, but i don't think oblivion supports it. You may try to change formid & editorid (to whatever you like) of the quest in xEdit, this in theory should make the game think that its a different quest and it may start on game restart, but if that doesn't work then I have no idea what else can it be.
39 comments
After that I installed MessageLogger as jakoben91 recommended.
Works fine now!
Doesn't work properly, and it seems to accelerate save bloat.
So, as of 08 July 2023's version there's a problem. The books keep glowing whether they have been read or not. I was lazy enough to not uninstall this mod, and after a while the game got worse and worse(unstable, that is), until it started to crash every 15-20 minutes. With the face of my pfp i started to remove mods one-by-one. And after reading tons of logs with different combinations of esps, i found a funny thing while loading save's strings: within the span of ~11 hours of gameplay BooksGlow.esp deadlinked 8230 strings . huh, that's a lot. Removing the mod and forcefully resetting all cells reverted the save to a stable state.
I'm bad with all of this modding mumbo-jumbo, and can't really help with finding a bug. But, i've created a clean save with just obse + your mod, and entered into cells with lots of books and opend a bunch of them for 20 minutes or so. And yep, when loading save's strings there was 3260 variables for the esp (somehow?).
Processing boosk in cell...
Adding glowing book to array. Ref: 00029AFE - EDID: - Ref Count: 1
There are several more glowing books which differ by Ref & Ref Count.
After opening one in logs I see entry:
Found a book with empty EDID, skipping.. Book namw: Report: Disaster at Ionith
I don't have any other books or tracking books mods.
Here is a list of active mods:
- AULIAS_1_2_5-39635-1-2-5
- Better Saves-48106-2-0-1687019358
- Carry all you want-5118
- Clearer Underwater-17411
- DarkUId DarN
- DZ Auto Harvest 11-17984
- Harvest Containers xOBSE-52317-2-1-2-1664040203
- Highly Visible Keys And Lockpicks - Default-49206-V1-1687622118
- LINK 1_4-50144-1-1593351845
- MenuQue v16b-32200-v16b
- More and cheap training-8523
- Nighteye Shader Replacement-7327
- obmm 1_1_12 full installer-2097
- Unofficial Oblivion DLC Patches-9969-25-1635879747
- Unofficial Oblivion Patch-5296-3-5-7-1635873247
- Unofficial Shivering Isles Patch-10739-1-6-0-1635878152
- Unread Books Glow-53086-1-0-1-1688785757
- xOBSE 22.9-37952-22-9-1686868858
There's also a new option in INI to turn on debug mode, which logs mod actions to console and might help to identify what and where goes wrong, try it if you have problems.
xOBSE 22.9 version
ps. Unfortunately, there are bugs in version 0.9. After restarting the game, the glow remains on all books, but does not disappear when reading new books. It's even embarrassing. Nevertheless thank you. English is not my native language.
I'm in a 20h+ playthrough right now, and for me everything works great. I've tried starting new game, I've tried to figure out what can go wrong in the code, and tried to safeguard everything I could think of, and at this point I've done all I could.
The only way that I could *confirm* what you're describing can happen is when using older xOBSE - because of the absence of GetEditorID2 function all books get catalogued under an empty string (instead of proper EditorID of the book form) hence the glow disappears on all books, because script thinks they are all references of the same book. Other than that I could not find a single reason why the behavior you're describing can happen.
Anyway, if v0.9 works just use it. Otherwise plenty of debug messages are available for those who's gonna try to figure out what's going wrong really.
EDIT: actually looks like I was wrong, I tested a bit more and figured that GetEditorID on 22.9 returns FormID for some reason and this means that if you change the load order or something like that things might get out of hand
GetEditorID2 return the editorID for book forms (and most other instance-able forms) only when MessageLogger is installed with the EDID hooks active and REID is not installed
Then I read ONE book, and they ALL stopped glowing.
It wasn't because I installed it AFTER I stated the game, it was because I installed it AFTER I had already read a book.
I'm not sure why, I'm not using any Book jacket mods or anything else that would change the books
Could it be the quest doesn't start if you use an Alternate Start Mod?
Is the quest waiting for me to exit the Sewers in order to start and make the books glow?
If so, what's the quest name so I can start it in the console and see if books start glowing
no idea why it's not working for you, it's pretty simple really, but if you don't see glow and book names don't change then script is probably isn't running
If so, then it's probably not going to start for anybody using an alternate start mod.
I tried the SetStage command, but nothing happened, I tried setstage zefUBGQuest 10, and 20, 30 , 40 eetc.
No glow
It's technically possible to run a "completequest" command via script or manually which will stop the quest and the script, and the game will remember that the quest is completed and won't start it again at game restart. That's the only thing that I can come up with. Later bethesda games allow you to mark a quest as repeatable, so you can start it multiple times, but i don't think oblivion supports it.
You may try to change formid & editorid (to whatever you like) of the quest in xEdit, this in theory should make the game think that its a different quest and it may start on game restart, but if that doesn't work then I have no idea what else can it be.
It is a slowly pulsating glow, the picture shows the highest level of light.