Yeah, I remember that. Never managed to figure out what that problem was.
But there is no point to downgrade Eli Book, because if you do, you will also need to downgrade my other plugins, since their updated versions would not work with an older version of Eli Book.
Guess if the cook tool app matters to you, you will not be able to use my plugins at all.
Ahoy! A bit of an update regarding that issue: the issue turns out to be how the book plugin tries to find it's name. Since it's loaded via nwjs' built in mechanism (since the compiled version of the plugin can't be loaded through normal means), trying to find the name via looking up in the document, it will return null, thus breaking it during launch.
This was certainly a tough bug to figure out. But it was a pattern that I saw in other plugin. Took me a while to notice it here as well.
The current workaround for this is to hardcode the name.
I suspect that maybe all my plugins can be affected by this, since they all use the same method from Eli Book to get the plugin name. So, as I keep updating them, I'm already changing to get the plugin name by a string. The thing is, it may take a while, because I have a lot of plugins =/
If you want, you can try to put a compatibility warning somewhere you see fit on your tools, in case the user has any problems, he just need to open the plugin file and replace:
Eli.PluginManager.getPluginName() with the plugin filename, without the extension: "EliMZ_Book".
As I update my plugins, I'm putting on the update log that I already made this fix to be compatible with your tools.
