...wait, so that's it? Just a stack overflow? I didn't notice that, likely because I was getting a bit different error (that there is no `sat` property on the actor, not that it started calling itself until stack overflowed...)
Also while my workaround worked in terms of resolving the issue, your fix feels much more elegant. Thank you!
Jacie1krece
Recent community posts
There is a problem with custom parameter failing to initialize when VisuMZ_0_CoreEngine defines a custom stat with the same short name, even if it refers to the same thing. The ordering of the plugins doesn't impact it - both placing Custom Parameters after and before CoreEngine on the plugin list still causes the problem.
Here is the JS I'm using for that custom stat (inside of CoreEngine):
// Declare Constants
const user = this;
let actorID = this.actorId();
// Calculations
return $gameActors.actor(actorID).sat;
When the Abbreviation of the CoreEngine Custom Parameter is also `sat`, the actor doesn't get applied the `sat` property at all, and accessing it either gives out a 0 or an error. Changing the CoreEngine Custom Parameter's Abbreviation to something else, like `satk`, solves the issue.
This is also my solution for this issue - so the problem doesn't happen anymore for me due to that solution, but I still want to let you know about this problem so you can decide whether it's possible to fix it (or worth to fix it).
Here is a sample project showcasing the issue, if you want to investigate it further: https://drive.google.com/file/d/1vC4Ycs9Z1ECRpD0lZ-bMVJk5Zp5aaz8f/view?usp=shari...