Hi Ramza, wanted to check, is this or your other plugins compatible with YEP's Stat Allocation? I was reading through the tutorial and it does not make any mention of this plugin anywhere. Appreciate your advise. Thanks in advance!
Hi there.
I haven't tested that plugin specifically, but here's what I can gleam by looking at it:
- It should be mechanically compatible. Stat points spent in ATK will apply correctly to both main and offhand attack values.
- It might be possible that ATK added from this might not be multiplied by the offhand or two-handed multipliers, I think it should work, but, like I said, I haven't tested it. The multiplier is added after other effects that modify the base param, so it should apply after this plugin.
- The scene showing the stat purchasing should only show base params, and by looking at the video for this plugin, it doesn't appear to be reusing one of the scenes I directly modified, so it should continue to do this, and will not show the split params in this window.
- As above, because this window doesn't show the split params at all, there should be no issue with a blank slot, or Block Chance showing up on this scene either, if you're using that plugin as well.
In conclusion, it should work, but it hasn't been tested. There's no reason why it shouldn't work, and any incompatibilities would be minor, and pretty easy for me to fix if someone were to report any.
-Ramza
Hi Ramza, I did some testing, including with the Block Chance, Parry, and Switchable plugins and everything worked fine. However, as soon as I start using the Menu Extension (both with and without the exparamfix), I got the below message. I think I can live without the Menu Extension, but just highlighting the bug I received.
I just tested myself and I am unable to duplicate this issue.
It looks like, from the error message, something on screen is attempting to draw block chance. Knowing that, I imported it into my test project, and set the default parameters to include both 'blk' and 'cri' to see if xparams were what was causing the issue for you. Block Chance doesn't show up on the scene at all, which it shouldn't as the YEP plugin has no idea what 'blk' stands for, and critical hit chance shows up fine with no crash and no issue.
Load order may be the problem. This worked for me with the Yanfly plugins in the proper load order (from the website). Block Chance loads right after Battle Engine Core, Dual Wield loads at the end of the other battle plugins. The Menu extension should be in the load order near the bottom, after any other menu plugins you have. In my case it was also below stat allocation in the load order.
That expram fix plugin you're using is meant only for people who aren't using the menu extension. It adds some short codes to show on the YEP Status Menu Core scene, but the menu extension already does this, so using both might also be causing a problem.
If you're still having problems, a few more screenshots, what you are doing exactly to cause the crash, and the text from the console when it crashes (press f12 when the above crash screen happens and click 'console') will make tracking it down much easier.
Hi Ramza, thanks for the response. I am following Yanfly's order, but the rest are a bit harder to figure out. I followed your instructions, but there is still an error (though somewhat different).
I managed to remove the Galv_WeaponProf error by moving it just below YEP Battle Engine the order but I could not figure out the rest. Below are the location where I slotted in your plugins.
3 years ago(+1)
Greetings.
I still can't reproduce this on my test project, and it looks like the version of the stat allocation plugin I'm using is not the same as the one you have, as the functions throwing the error are on different lines on my version.
With that being said, I suspect the problem is the below function:
Yanfly.StatAlc.Game_BattlerBase_xparam = Game_BattlerBase.prototype.xparam;
Game_BattlerBase.prototype.xparam = function(xparamId) {
var value = Yanfly.StatAlc.Game_BattlerBase_xparam.call(this, xparamId);
value += this.xparamAllocationBonus(xparamId);
return value;
};I'm not sure at what point it is called, but it would appear that it isn't playing nice with the fact that I've defined block chance as xparamId 10. So it's looping through the normal xparams and then getting to block chance and breaking. I think if we edit the function to abort if it detects that it's on Id 10, it should be fine, but since I can't duplicate the problem myself, I can't verify if the fix actually works either.
Copy the below text into a blank .js file, and import it into your plugin manager at the bottom of the list.
Yanfly.StatAlc.Game_BattlerBase_xparam = Game_BattlerBase.prototype.xparam;
Game_BattlerBase.prototype.xparam = function(xparamId) {
var value = Yanfly.StatAlc.Game_BattlerBase_xparam.call(this, xparamId);
if (xparamId != 10) value += this.xparamAllocationBonus(xparamId);
return value;
};
This will overwrite the function that I suspect is causing the issue, and should(hopefully?) fix it for you. Let me know if it doesn't work, and any new errors you get.
-Ramza
3 years ago(+1)
Sorry, take out the top line in the fix I posted earlier. By copying the alias function it ends up calling itself infinitely, causing the stack overflow error.