Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Hello there.

I looked into this and have made a patch which I have tested, and it does not cause the crash anymore. The interesting thing about this, is that my Block Chance test project already had the YEP_StatAllocation plugin in it, and enabled. I think I maybe had a modified version in there to prevent the crash, maybe? 

At any rate, the problem is actually very similar to the one I was talking to Zelanius about earlier, regarding the extra parameters formula plugin as well - the YEP plugins all assume that there are only 10 xparams, and I coded block (blk) to be xparam(10), which is number 11. Because of this, the YEP plugins attempt to lookup values for that xparam, but return null, or undefined values, because they weren't defined the correct way, and crash. In this case, both of us could be considered to be at fault, YEP because they hardcoded their plugin to assume there would always be 10 xparams, despite having the ability to dynamically assign the same null values, and me because defining a new xparam maybe isn't great for compatibility.

Anyways, I uploaded the fix for this to the store page. Import it into the project. I put it at the bottom of the list, but it should work anywhere below the StatAllocation plugin.

If you want to be able to allocate points to block chance, however, that's not going to be something I can help you with.

~Ramza

(1 edit)

Thank youRamza! And not at all. I was wanting to keep Block Chance attached to the shields and being able to allocate points to it would defeat the purpose. I appreciate your help!