Posted November 11, 2020 by Ramza
#feature-update #rpgmaker #crafting #synthesis #bugfix
Greetings all.
Late last week I uploaded version 1.15 of the base Crafting System plugin, which finally brought back the ability to have recipes with multiple wildcard items in them. Unfortunately, that update broke the recipe list extension, as the menu was not designed in the correct way to be able to show multiple category ingredients, and definitely wasn't capable of making the player pick from multiple category ingredients, either.
Fixing this was intended to be a quick fix, but it turned out I needed to rewrite a lot of this plugin to make it actually workable in the first place. The way it was originally written actually caused a display bug where an item that had two different recipes, which each had a category ingredient, but not the same category ingredient, would display the same category ingredient for each, even if the second one was different!
So I rewrote that part of the recipe list window to actually be able to handle category ingredients correctly, and now it will properly show as many category ingredients as you can shove into it!
Additionally, selecting to craft a recipe which has more than one category ingredient in it will now allow the player to select an ingredient for each category. This isn't really a bugfix so much as it is a feature enable, because previous to this update, recipes with multiple category ingredients didn't work at all, and if you managed to get past the buggy recipe list window to actually craft one, it would only ask you for the first category item, and then total fail because the ingredients provided wouldn't have matched the recipe selected.
Here's a list of bugs that have also been fixed:
Most of the above bugs were fixed in what I'm calling version 1.02, but which was never publicly released. I fixed several of the above early on, and intended version 1.02 to add in some new features, which I ended up sitting on for a long time before scrapping entirely. I rolled those fixes into version 1.10, but marked them as fixed in 1.02 because they weren't technically fixed in v1.10!
That's all for now, folks.
~Ramza