Store Page
Divinity: Original Sin 2
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Divinity: Original Sin 2

Store Page
Divinity: Original Sin 2 >  Workshop > LaughingLeader's Workshop > LeaderLib - Definitive Edition > Discussions
LeaderLib - Definitive Edition
Description Discussions4 Comments407 Change Notes
 This topic has been pinned, so it's probably important
LaughingLeader  [developer] Mar 10, 2020 @ 3:48pm
Bug Reports
Please post all bug reports / issues here.

Providing Informaton
Fixing bugs / errors isn't always straightforward, but the easiest way for me to be able to resolve things is if I can reproduce the same problem.

So with that in mind, here's information that will help me figure out how to create the same problem, and ultimately resolve any issue (provided it's fixable on my end!):
  1. If known, how can this bug be reproduced? (it's easier to fix if I can make it happen as well!)
  2. What mods are you using?
    • Tip: In my Divinity Mod Manager program, click File -> Export Active Mods to Text File to create a list of all your active mods.
    • Bonus Tip: For bugs beyond working story errors, providing me with a copy of your save file will help immensely, as I can simply load your mod list with the mod manager.
  3. What version is LeaderLib? (Check the version in the mod manager or the in-game mods menu).
  4. If using the Script Extender, what version is that? (Hint: Look at the version displayed in the loading screen).

Creating Working Story Error Logs
With the Script Extender installed and the Divinity Mod Manager, you can quickly enable compile logging, which will output a text file with details on the working story error. To do so:
  1. In the mod manager, click Settings -> Preferences.
  2. Click the "OsiExtender" tab in the preferences window.
  3. Check "Enable Logging" and "Log Story Merges".
  4. Click "Export Settings". The mod manager will create an extender settings file with all the options listed here.
With logging enabled, if no log directory is set, logs will output to the OsirisLogs folder in your Documents folder. This folder will be created automatically by the extender.

Working story error logs will be named like so:
Compile 2020-03-27 12-34-21.final.log
With that created, simply provide me the log via any free hosting service.

Recommended sites for posting logs / text files:
https://gist.github.com/
https://paste.ee/
Last edited by LaughingLeader; Mar 27, 2020 @ 6:56am
< >
Showing 1-15 of 99 comments
tassadarsf Mar 27, 2020 @ 5:18am 
Hi, I had this mod installed, and it just updated this morning. After that, any game I attempted to load had a "couldn't generate valid story error", which apparently happens when a mod can't compile based on quick googling. I also tried starting a new game and got the same error.
Disabling this mod fixed it, so I suspect something in your most recent update caused an issue.

Thanks for the awesome mod!
#1
LaughingLeader  [developer] Mar 27, 2020 @ 5:31am 
Hi. Thanks for the report. Some quick questions:

1. What mods are you using?
2. Are you using the script extender?
3. Do you get this error with only LeaderLib enabled?

I suspect there may be a mod using a previous version of a LeaderLib function I'll need to either add back in, or update manually if it's one of my mods.

Before publishing the update I tested loading previous/new saves with and without the extender, but there may have been a mod I missed testing it with.
Last edited by LaughingLeader; Mar 27, 2020 @ 5:37am
#2
MrAbsentminded Mar 27, 2020 @ 5:40am 
I'm also receiving the above bug. I have the script extender installed from the mod manager and disabling this mod removes the error.

As far as other mods installed - my list has 87 mods on it, so I'm not sure how helpful this will be.
Currently my journal is full. I'll do some more tests to see if this breaks the game.

Edit: Did some more testing. Journal still loading. NPC's still acting as normal. Enemies still taking turns in combat. Was able to continue a quest line. No issues so far that I've seen associated with this bug.
Last edited by MrAbsentminded; Mar 27, 2020 @ 5:47am
#3
MrAbsentminded Mar 27, 2020 @ 5:51am 
Another Update: I started a new game with only this mod installed and got the error.
#4
Yebbeh Mar 27, 2020 @ 5:57am 
I've been encountering the same error.
After some testing it seems to be an issue with the script extender.
With script extender + LeaderLib as the only enabled mod: error
Without script extender and LeaderLib as the only enabled mod: no error
#5
LaughingLeader  [developer] Mar 27, 2020 @ 6:03am 
What version of the script extender do you see when the game is loading? It should display v42 now, as that is the latest public release. If you're seeing a lower number, that is probably the source of the error here.

Originally posted by MrAbsentminded:
Edit: Did some more testing. Journal still loading. NPC's still acting as normal. Enemies still taking turns in combat. Was able to continue a quest line. No issues so far that I've seen associated with this bug.

Basically when you get a "working story" error, the game will continue by reverting the underlying scripts to the game's defaults. So basically any mod scripts won't be active.
#6
Yebbeh Mar 27, 2020 @ 6:06am 
I'm on the latest version (v42), and the error is still present.
#7
Tragic Bronson Mar 27, 2020 @ 6:16am 
Same problem here. I'm using 23 mods and Norbyte's Script Extender (v42). But the error occurs only when both Norbyte's Script Extender and LeaderLib are enabled, other mods don't seem to affect this. The error stops showing only after I remove Script Extender or disable LeaderLib.
Last edited by Tragic Bronson; Mar 27, 2020 @ 6:17am
#8
LaughingLeader  [developer] Mar 27, 2020 @ 6:17am 
What version is LeaderLib? Should be 1.6.6.0. Tested starting a new game / loading an old save with the current public release, and no errors here, so this is puzzling.
Last edited by LaughingLeader; Mar 27, 2020 @ 6:17am
#9
Tragic Bronson Mar 27, 2020 @ 6:19am 
Originally posted by LaughingLeader:
What version is LeaderLib? Should be 1.6.6.0.

Shows 1.6.6.0 for me.
#10
Yebbeh Mar 27, 2020 @ 6:20am 
Shows 1.6.6.0 for me as well.
https://i.imgur.com/HMtyF0D.png
I tested an older version (1.6.3.2) from Nexus, and didn't encounter the error when creating a new game
#11
LaughingLeader  [developer] Mar 27, 2020 @ 6:27am 
I was able to reproduce the problem on my other computer (when the mod is in pak form). Thanks for all the reports.

I'll see if it's something I can fix quickly, though it seems it may be a bug with the extender that crops up when the mod is loaded as a pak.
#12
LaughingLeader  [developer] Mar 27, 2020 @ 6:37am 
Should be all fixed now. Turns out the problem was in the folder pathways used in some of the new Lua (extender) scripts, like this:
"Shared\\LeaderLib_Common.lua"
This fails to load when the mod is a pak, while this works:
"Shared/LeaderLib_Common.lua"
This is an extender bug I suspect will get fixed fairly quickly, but in the meantime it should work now.
#13
Yebbeh Mar 27, 2020 @ 6:42am 
No longer encountering the error. Cheers!
#14
Tragic Bronson Mar 27, 2020 @ 6:45am 
Yep, fixed. Thanks.
#15
< >
Showing 1-15 of 99 comments
Per page: 1530 50