For a long time now I've wanted to write a big post about the direction Witness to Unity has taken since I previously properly discussed it, sometime in 2016. The problem with this is oh god that's such a long time. So much has changed in its design and code direction. I don't know if I even have it in me to write a proper rundown for each element, so maybe I'll just bullet-point it.
The thing about damage calculation is you kinda have to feel it out by vibes. You want increasing stats by certain amounts to feel like a noticeable difference in your damage output, whether that's +1 or +10, or anything else. But to achieve this, it feels like you need to write damage formula and then shape everything else around it and hope for the best.
Which is a problem if you reach a point or come back to it later and the vibes are off.
I'm presently struggling with looking at Witness To Unity's damage formula and thinking... this thing seems a mess. I'm multiplying or dividing the stats a lot just to get things into the "shape" I want, and maybe that's bad? I'm not sure how to explain this, so I'll start with how the stats and all currently work.
So since Witness to Unity uses a “side-view battle system”, it means I need to have animations mirror depending on where they’re coming from. Unfortunately, RPG Maker XP does not even have under the hood ability to understand this, because it was front-view by default. (VXAce meanwhile added some unused variables for scripters to make use of that made this sort of thing easier.)
Let me tell you about my adventures with multi-hit attacks. It was possibly the biggest nightmare I've had in programming in the longest time, not from getting errors or anything, but because of the game logic falling apart or misbehaving in ways I couldn't understand for a while.