Limit Break (DVV's)

[DerVVulfman]

Oh, my gawd! It has been roughly ten years since I touched this script. It is definitely time for a ...

BUMP!
to Version 3.0

Dear lord! It is true! This is the first time I have ever bumped this script in Save-Point! I haven't worked on it since the forum STARTED!!! EVEN WHEN IT WAS RMVXP.Com or RMXPUniverse.Com!!!! And that's been YEARS!!!!!!

This script seriously needed some attention. Functional as it was, it was NOT up to my current coding standards. Hell, it used global variables for some configured settings, no module to house the settings, and code that wrapped off the screen! And along with that, poor naming conventions for the aliased methods AND the alias statements were all separate! Oh, wow... NOT up to my standards.

Well, it has taken the better part of a few hours, and the Limit Break system is now working well, and with a clearer set of instructions. The code was shortened thanks to some newer techniques (hey, it's been 10 years). And all this time, I did ensure it was STILL compliant with both the Cogwheel set of battlesystems (CTAB and RTAB) and the ATB by ParaDog.

Of note, 'element tagging' systems can affect battle damage. So a new set of protocols were added to eliminate the Limit Break Element from Skills when damage is being applied, and returned thereafter. You don't want botched up skill math, do you?

The Menu system by Alistor still works like a charm, and it's HIS. Not touching it. ^_^

But my "Attack" replacer script needed a major overhaul, now roughly 25% more compact! I eliminated the use of XRXS's Command Window add-on, as I really didn't wish to rely on outside code. What I wrote does take up more lines than his, but my edits also ensured proper placement of the revised 'Limitbreak' command window, all based on the location where the Actor Command Window is meant to be shown. At the same time, I altered the methods within Scene_Battle that are executed when the Actor Command Window pops up. What was initially half the script was cut down to maybe two dozen lines? Hahaha! Boy, lessons learned over the years can sure translate to optimized code.

I hope you enjoy the changes.