Hello! We're using the TAA Book Menu (v1.6.0) on RPG Maker MZ (v1.2.1), every time we put a space in the title of the book, the book doesn't open and it gets skipped over in the event. In the log (F12) it doesn't say anything at all when this happens.
UPDATE: This even still happens in a brand new project with no other plugins. As soon as the title of a book has a space in it, for example "My Book" instead of "MyBook," the plugin no longer works.
UPDATE AGAIN: Using in the in-plugin method of storing books, when you call a book in an event, we discovered you cannot use spaces. The title of the book to be displayed can have spaces, but the plugin command in the event cannot. Kinda important to know. If anyone else has this problem, what's why.
I appreciate the reply. I did some testing and resetting the library on a game load resolves all the issues I was having. It seems that it caches the books.json/plugin information into a save game's memory or something and resetting will re-load the file.@resiI believe this is due to the way the system handles loading plugin data. I might be wrong but, once a save file is created, the system won't reload plugin data.
If you can test your changes out in a new game, you'll find the answer.
Hi there!I want to start out by saying amazing plugin. I love being able to use JSON to create the books rather than working within the plugin manager. Very smart design.
In older versions (1.4.0 or below) the plugin used to save all book data in your save data. Back then, new books added to the game wouldn't be recognized by a saved game, unless one of the reset functions were triggered (resetLibrary to reset everything, resetLibraryBookList to reset only available books and keep books read, or resetLibraryBooksRead to reset only books read).Edit: Looking into it, it seems $gameSystem.resetLibrary() is useful for refreshing the entries. That makes a lot of sense in terms of testing. I'll keep doing my best to work with this plugin and become proficient with it.
I am using your most recent version, perhaps I'm just dealing with a cascade of way too many plugins in my projectHi there!
Thanks for the feedback! I myself prefer using an external JSON file instead of the Plugin Manager, always. I figured some people out there would share this preference!
In older versions (1.4.0 or below) the plugin used to save all book data in your save data. Back then, new books added to the game wouldn't be recognized by a saved game, unless one of the reset functions were triggered (resetLibrary to reset everything, resetLibraryBookList to reset only available books and keep books read, or resetLibraryBooksRead to reset only books read).
If you're using the current version that shouldn't really be necessary. However, I'm glad those functions solved your issues!
In any case, I'll run some tests to double check this.
Hi there!@C64_Mat It's much more beneficial to post a screenshot of the crash report from the console. You can access the console with F12.
Also, I think you might have a plugin order issue. YEP Message Core and YEP Save Core and any extensions should be above YEP Battle Core.
I can't access the console as the game becomes completely unresponsive. I have to ALT+F4 to quit it.
The plug-ins I'll try in a different order, but according to Yanfly's site, it's the order of each section that's important and should be in the same as according to the page, i.e. the message core plugins should be in his order, the main core ones should be, the battle ones should be etc.
I will try it though!
Thank you for the advice, it's always appreciated.
I'm in London until Tuesday, so I'll report back then
Hi there!Hey there! Thanks for the great plugin @taaspider I like it a lot, especially the lengths you've gone to to support custom images.
I do have a weird problem though, and yes I'm one of those people who uses a hundred plugins to testing isn't easy.
The plugin works absolutely fine, until I actually try to read a book. Then the text shows up in the right hand window for a split second, before the plugin and the whole game crashes to nothing.
I've attached my full plugin list just to see if something I'm missing jumps out at someone else. I've tried it with and without several plugins, and in different orders.
This happens when reading the book from the menu (the default library). I haven't tried the pop up method yet.
Thanks in advance for any help!
I've included a bit more information in this image:
View attachment 202225
I've isolated the issue!Hi there!
That is a really long list of plugins! hehe
I noticed you're using version 1.6.0. Can you update it to 1.6.1?
This last version adds a failsafe to prevent game crash if there is any conflicts in the background image settings. As your print has no bg, I think the issue is probably occurring because there is no image set in the proper parameters, but the plugin is configured to add them. Version 1.6.1 is a bit smarter and can identify that to prevent a game crash!
If the issue persists, we'll have to test compatibility as DarkSearinox92 suggested!
I'll setup a test project over here and check if I'm able to do something about it. I'll need a few days to work on that, but I'll let you know of any updates as soon as possible.I've isolated the issue!
The single plugin causing the crash is CGMV_Core by @casper667 available here: https://caspergaming.com/legacy-resources/
As Casper (understandably) has moved on to MZ and no longer updates his MV plugins, is there any way at all compatibility between his core engine and your Book Menu can be achieved?
Thank you for reading!
Thank you, that's amazing. I'd be interested to know, if you do have the time / incentive to work on it, what was causing the incompatibility. But in any case, thank you so much for at least taking a look!I'll setup a test project over here and check if I'm able to do something about it. I'll need a few days to work on that, but I'll let you know of any updates as soon as possible.
I use CGMV Core, many Yanfly Plugins and this plugins and I havent had any issues.Thank you, that's amazing. I'd be interested to know, if you do have the time / incentive to work on it, what was causing the incompatibility. But in any case, thank you so much for at least taking a look!