Visustella is really proactive here, and their modifications on gauges precede mine. Again, you have 2 plugins that do similar things, so in the end, one plugin (in this case, VS) will "win" over the other. By the way, in this case, it doesn't matter which plugin is loaded "more on the bottom" in the plugin manager.
In my opinion, VS should add more toggles to let the game devs decide whether they want VS to modify the gauges, or not. I'm a bit reluctant to implement a procedure into my plugin that actively force-reverts a feature of another plugin. By the way, that has nothing to do with their code obfuscation (the debugger already exposes how to revert VS functions), but it's more of a psychological question.
Fortunately, VS shows some mercy and lets the game devs actually revert their gauge modifications via some hidden way:
- Go into the Plugin Manager -> VS SkillAndStatesCore -> Skill Cost Types
- Repeat the following for HP, MP, TP:
- Open the setting "JS: draw Gauge", clear everything, and paste:
// Declare Variables const sprite = this; // Draw Gauge sprite.drawGauge() // Draw Label sprite.drawLabel() // Draw Value sprite.drawValue()
From a technical point of view, this is the cleanest way to drop VS modifications for gauges, and let my plugin take over control again.