Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(+1)

So this one may be a stretch, but I'm hoping it'll make sense to you and you'll have insight on how to resolve it.  I have recently incorporated SumRndmDde's plugin to be able to retry a battle after defeat, with the Retry Upgrade plugin to provide an option of making adjustments to the party's equipment before doing so.  

However, upon hitting the scene prompt for the equipment menu from this approach, I'm hitting a crash that seems to be citing an issue from DualWield.  I've attached a screenshot of what I'm getting:

As far as I'm aware, the Retry Upgrade plugin is making a very basic call here--it's just hitting a SceneManager.push(Scene_Equip) when that option is being presented, and rolls back to a snapshot of the party prior to beginning the encounter.  

The crash occurs when selecting a character whose equipment you'd like to change; in this particular screenshot I was selecting a character who doesn't dual wield and just has a main hand + shield equipped.

(+1)

This looks like the same issue Miah1377 reported after updating from an older version.

That function being referenced as the cause of the crash is trying to read a property that is assumed to be present on all weapons as of v2.62. I just released a sort of patch that stops it from causing the crash error, but the cause of the problem is that it appears that you are testing using a save file that was made prior to upgrading the plugin to version 2.62. The way the database for items is loaded is weird, and because this plugin wasn't reading notetags for locked wtypes prior to v2.62, the property that it saves onto weapons isn't present on your items database for the save file. The plugin (prior to 2.65) assumed that the property is always present, so it goes right to reading from it, which causes the crash error you posted when it finds the property as undefined.

As I said, v2.65, which was just uploaded a few hours ago will stop the crash (or it should anyway), but the actual fix is to start a new save-game file from which to test further.

(+2)

Interesting!  Well, this seems to have resolved the issue collectively between fresh starts and otherwise.  Cheers!