* Q1. What's the main differences between DoubleX RMMV Popularized ATB and
* this plugin?
* A1. There are at least 2 main differences:
* - The former uses the core addon approach, meaning that the core
* plugin, which is mandatory, will only have all the essential
* features, and each addon plugin, which is optional, will only have
* each set of extra features. This is useful when many users only
* use a small amount of the feature set provided by
* DoubleX RMMV Popularized ATB.
* On the other hand, the latter uses the single plugin approach,
* meaning that all the feature implementations will be included in a
* single plugin, even though unit tests and compatibility fixes will
* still be separate plugins. This is useful when many users use a
* large amount of the feature set provided by this plugin.
* - The former aims to be easy, simple and small while still being
* reasonably powerful for both users and ATB system plugin
* learners, while the latter aims to be the most flexible and
* powerful ATB system plugin ever by giving users the deepest and
* widest amount of control and freedom ever, thus making it much,
* much more demanding for both users and ATB system plugin learners.
* Q2. May you please make this plugin less demanding? The sheer number of
* parameters/configurations/notetags, most demanding Javascript
* function contents as values, are extremely overwhelming for less
* capable users. It's just far from being user-friendly enough.
* A2. While it's clearly my fault that makes this plugin so hard to use,
* I've already tried my best while still preserving the flexibility
* and power of thie plugin by maintaining the depth and width of
* control and freedom available for users.
* As for the sheer number of parameters/configurations/notetags, this
* plugin aims to include everything in a single plugin, which is
* preferred for some users.
* In case this plugin's really too hostile, you may want to use
* DoubleX RMMV Popularized ATB, which is much easier, simpler and
* smaller while still being reasonably powerful, instead. Also, it
* breaks each set of features into 1 plugin, meaning that you won't
* have to face a sheer number of parameters/configurations/notetags
* there.
* Alternatively, you can ask for help if you still want to use this
* plugin, if the demo doesn't provide enough help already.
* Q3. Why the Core Module itself doesn't show the ATB value of any
* battler and why doesn't it let players change among inputable
* actors? All these are essential UX features. Without them, using
* just the Core Module can only result in a fully broken ATB system.
* (Well, not being able to change the ATB wait conditions sucks too)
* A3. It's because these features aren't technically essential to run an
* ATB system plugin, nor they're behaviors inherited from the default
* RMMV battle system(It doesn't let you change the input sequence nor
* show the actual action execution sequence). All these features that
* are missing in the Core Module are covered in the Bar Module and
* Hotkey Module(The similar logic applies to the Wait Module). That's
* why only these 3 optional modules are enabled by default(All the
* other optional modules are disabled so you don't have to deal with
* so many modules all at once before being familiar with this plugin).
* Q4. Why the Bar Module doesn't use notetags? Isn't it going against the
* very goal of this plugin?
* A4. It's because it's very unlikely that anyone will need to use such
* notetags. If I added them anyway, the sheer number of notetags that
* almost no one's going to use would be too much of a nuance and
* clutter for users to access the functionalities that they really
* want. In case such notetags are indeed needed, I'll implement the
* needed ones, and perhaps one day all those notetags would be done.
* Q5. (Advanced)Why the caching mechanism's so complicated and convoluted
* in this plugin? It's extremely costly and troublesome to work around
* when I've some unintended and creative uses of this plugin.
* A5. It's because this plugin explicitly allows many effective notetags
* to be used in the same frame, which can cause significant lag and
* fps drop if the end result's not cached, epsecially when the
* functions called by those notetags are computationally expensive.
* This plugin's to balance among multiple key aspects, so I'm sorry
* that your use cases have to be at least slightly sacrificed for
* performance stability and ease of use for intended and ordinary use
* cases, which are likely much more common and important. That's the
* main reason why decent RMMV plugin development proficiency is needed
* to fully utilize this plugin with creative and unintended uses.