Base Parameter Control (YEP)

From Yanfly.moe Wiki
Jump to navigation Jump to search

Welcome to the wiki! This is where you can find resources from Yanfly.moe, Ækashics.moe,
VisuStella, Caz Wolf, Fallen Angel Olivia, Atelier Irina, and other affiliated content creators.



Download

System

This is a plugin created for RPG Maker MV.

For help on how to install plugins, click here.

For help on how to update plugins, click here.

Got errors with your RPG Maker MV plugin? Click here.


Masterarbeit Writer

Extension Plugins

The following plugins are Extension Plugins that require this plugin as its Parent Plugin.

Place the following plugins below this plugin located in the Plugin Manager if you plan on using them.

Yanfly Engine Plugins

This plugin is a part of the Yanfly Engine Plugins library.


Introduction

The base parameters, MaxHP, MaxMP, ATK, DEF, MAT, MDF, AGI, and LUK all play
a very important part of battle, yet, so very little control is given to the
developer in regards to these important stats. This plugin will give more
control over how the stats are handled and more.

Note: If you are using the Core Engine and have modified the settings there
for higher parameter caps, this plugin will override those settings if this
plugin is placed beneath the Core Engine (recommended).

Instructions

Base Parameter Explanation

For those who do not understand what the base parameters are used for in RPG
Maker MV, this section will provide a brief summary of their most important
roles of what the base parameters do.

---

MHP - MaxHP
- This is the maximum health points value. The amount of health points (HP)
a battler has determines whether or not the battler is in a living state or
a dead state. If the HP value is above 0, then the battler is living. If it
is 0 or below, the battler is in a dead state unless the battler has a way
to counteract death (usually through immortality). When the battler takes
damage, it is usually dealt to the HP value and reduces it. If the battler
is healed, then the HP value is increased. The MaxHP value determines what's
the maximum amount the HP value can be held at, meaning the battler cannot
be healed past that point.

---

MMP - MaxMP
- This is the maximum magic points value. Magic points (MP) are typically
used for the cost of skills and spells in battle. If the battler has enough
MP to fit the cost of the said skill, the battler is able to use the said
skill provided that all of the skill's other conditions are met. If not, the
battler is then unable to use the skill. Upon using a skill that costs MP,
the battler's MP is reduced. However, the battler's MP can be recovered and
results in a gain of MP. The MaxMP value determines what is the maximum
amount the MP value can be held at, meaning the battler cannot recover MP
past the MaxMP value.

---

ATK - Attack
- This is the attack value of the battler. By default, this stat is used for
the purpose of damage calculations only, and is typically used to represent
the battler's physical attack power. Given normal damage formulas, higher
values mean higher damage output for physical attacks.

---

DEF - Defense
- This is the defense value of the battler. By default, this stat is used
for the purpose of damage calculations only, and is typically used to
represent the battler's physical defense. Given normal damage formulas,
higher values mean less damage received from physical attacks.

---

MAT - Magic Attack
- This is the magic attack value of the battler. By default, this stat is
used for the purpose of damage calculations only, and is typically used to
represent the battler's magical attack power. Given normal damage formulas,
higher values mean higher damage output for magical attacks.

---

MDF - Magic Defense
- This is the magic defense value of the battler. By default, this stat is
used for the purpose of damage calculations only, and is typically used to
represent the battler's magical defense. Given normal damage formulas,
higher values mean less damage received from magical attacks.

---

AGI - Agility
- This is the agility value of the battler. By default, this stat is used to
determine battler's position in the battle turn's order. Given a normal turn
calculation formula, the higher the value, the faster the battler is, and
the more likely the battler will have its turn earlier in a turn.

---

LUK - Luck
- This is the luck value of the battler. By default, this stat is used to
affect the success rate of states, buffs, and debuffs applied by the battler
and received by the battler. If the user has a higher LUK value, the state,
buff, or debuff is more likely to succeed. If the target has a higher LUK
value, then the state, buff, or debuff is less likely to succeed.

---

Custom Formulas

The values calculated by the formulas in the plugin parameters are to come
out as integer values. If the result is a float, it will be rounded up and
then clamped based around the maximum and minimum values the parameter can
be (also calculated by the plugin parameters).

By default, the formula looks as such:

---

     (base + plus) * paramRate * buffRate + flat

---

Below is an explanation of each of the parts of the formula.

BASE
- This value is determined in multiple ways. If the battler is an actor, the
base value is the base parameter value calculated by the position based on
the battler's level on the parameter curve for the battler's current class.
If the battler is an enemy, the base parameter value, by default, is equal
to the value inserted on the enemy's database entry for that parameter.

PLUS
- This value is determined in multiple ways. For both actors and enemies,
this value is a flat value given to the battler through events or script
calls that manually increase the battler's parameter value. If the battler
is an actor, this value is also increased by any equipment the battler has
equipped. This value can be influenced by notetags provided by this plugin.

PARAMRATE
- This value is determined the same way for both actors and enemies. This is
a percentile rate that is calculated by the multiplicative product of all
of the parameter spread across the battler's traits, independent of the
battler's buff rate. This value can be influenced by notetags provided by
this plugin.

BUFFRATE
- This value is determined by the number of buff stacks (or debuff stacks)
on a battler, regardless of whether or not the battler is an actor or enemy.
The percentile modifier is calculated relative to the number of stacks in
regards to that particular parameter for the battler. This value is NOT
influenced by notetags provided by this plugin.

FLAT
- This is a new variable added by this plugin. Its purpose is to provide a
final additive modifier to the total value of the parameter. This additive
value is determined by the various database objects through notetags and can
only be affected by those notetags.

---

The parameter Maximum and Minimum values also have formulas. They will work
something along the lines of this by default:

     customMax || (user.isActor() ? 9999 : 999999)
     customMin || 1

For those wondering about the 'customMax' and 'customMin' values, they are
new variables added by this plugin.

CUSTOMMAX
- This is the custom maximum limit provided by this plugin through either a
script call or notetags. The custom max will look through the battler's
individual noteboxes. If the battler is an actor, it will look through the
actor, class, each of the noteboxes of the equipment worn by the actor, and
the noteboxes of each of the states affecting the actor. If the battler is
an enemy, it wil look through the enemy notebox and each of the noteboxes of
the states affecting the enemy. The highest custom maximum value becomes the
newest 'customMax' value for the battler and will take priority over the
default maximum value. If there is no 'customMax' value, then the value
becomes the default maximum value written in the formula.

CUSTOMMIN
- This is the custom minimum limit provided by this plugin through either a
script call or notetags. The custom min will look through the battler's
individual noteboxes. If the battler is an actor, it will look through the
actor, class, each of the noteboxes of the equipment worn by the actor, and
the noteboxes of each of the states affecting the actor. If the battler is
an enemy, it wil look through the enemy notebox and each of the noteboxes of
the states affecting the enemy. The highest custom minimum value becomes the
newest 'customMin' value for the battler and will take priority over the
default minimum value. If there is no 'customMin' value, then the value
becomes the default minimum value written in the formula.

Notetags

NotetagsMV.png

RPG Maker MV's editor is unable to allow for custom traits/properties that a game dev may wish to associate with a database object, event, map, etc. Notetags are used to work around such limitations by allowing the game dev to tag certain traits/properties using specific Notetags declared by the related plugin.

Here is a list of Notetag(s) that you may use.

---

You can use the following notetags to alter the various aspects that modify
the base parameter values:

Actor, Class, Enemy, Weapon, Armor, and State Notetags:

  <stat Plus: +x>
  <stat Plus: -x>
  Replace 'stat' with 'maxhp', 'maxmp', 'atk', 'def', 'mat', 'mdf', 'agi',
  or 'luk'. This is the value added to the base parameter before the rate
  and flat values contribute to the total parameter value assuming the
  plugin's default formula is utilized.

  <stat Rate: x%>
  <stat Rate: x.y>
  Replace 'stat' with 'maxhp', 'maxmp', 'atk', 'def', 'mat', 'mdf', 'agi',
  or 'luk'. This is the value multiplied to the sum of the base and plus of
  the parameter before affected by the buffRate and flat value assuming the
  plugin's default formula is utilized.

  <stat Flat: +x>
  <stat Flat: -x>
  Replace 'stat' with 'maxhp', 'maxmp', 'atk', 'def', 'mat', 'mdf', 'agi',
  or 'luk'. This is the value added at the end after the sum of the base and
  plus parameters have been added and multiplied by the rate values assuming
  the plugin's default formula is utilized.

  <stat Max: x>
  <stat Min: x>
  Replace 'stat' with 'maxhp', 'maxmp', 'atk', 'def', 'mat', 'mdf', 'agi',
  or 'luk'. This sets the maximum or minimum cap of the the stat parameter
  to x. If a battler is affected by multiple of these notetags, then the
  value used will be the largest value of the notetag used.

Script Calls

ScriptCallsMV.png

Script Calls are event commands that are used to run JavaScript code during an event to call upon unique functions, usually added by the related plugin.

Here is a list of Script Call(s) that you may use:

You can use the following JavaScript functions to alter the base parameter
values of the battlers. In these listed functions, the 'battler' variable
is to be referenced by an actor:

ie. battler = $gameActors.actor(3);
    - or -
    battler = $gameTroop.members()[2];

Function:

  battler.clearParamPlus()
  - This will clear all 'plus' variable modifiers for all base parameters.

  battler.setMaxHp(x)
  battler.setMaxMp(x)
  battler.setAtk(x)
  battler.setDef(x)
  battler.setMat(x)
  battler.setMdf(x)
  battler.setAgi(x)
  battler.setLuk(x)
  - Sets the battler's respective base parameter value to x. This will alter
  the 'plus' variable to fit this setting as best as possible without taking
  into consideration the rates and flats.

  battler.setMaxHpPlus(x)
  battler.setMaxMpPlus(x)
  battler.setAtkPlus(x)
  battler.setDefPlus(x)
  battler.setMatPlus(x)
  battler.setMdfPlus(x)
  battler.setAgiPlus(x)
  battler.setLukPlus(x)
  - Sets the battler's respective base parameter plus value to x.

  battler.addMaxHp(x)
  battler.addMaxMp(x)
  battler.addAtk(x)
  battler.addDef(x)
  battler.addMat(x)
  battler.addMdf(x)
  battler.addAgi(x)
  battler.addLuk(x)
  - Adds x value to battler's respective base parameter plus value.

  battler.minusMaxHp(x)
  battler.minusMaxMp(x)
  battler.minusAtk(x)
  battler.minusDef(x)
  battler.minusMat(x)
  battler.minusMdf(x)
  battler.minusAgi(x)
  battler.minusLuk(x)
  - Subtracts x value to battler's respective base parameter plus value.

  battler.clearCustomParamLimits();
  - Clears any custom parameter limits placed upon the battler through a
  script call. This does not remove the custom parameter limits applied to
  a battler through notetags.

  battler.setCustomMaxHpMax(x)
  battler.setCustomMaxMpMax(x)
  battler.setCustomAtkMax(x)
  battler.setCustomDefMax(x)
  battler.setCustomMatMax(x)
  battler.setCustomMdfMax(x)
  battler.setCustomAgiMax(x)
  battler.setCustomLukMax(x)
  - Sets the maximum parameter limit of the respective base parameter to x.
  This value is calculated against any <stat Max: x> notetags that the
  battler may have. If there are multiple max values, the larges value is
  used as the parameter maximum.

  battler.setCustomMaxHpMin(x)
  battler.setCustomMaxMpMin(x)
  battler.setCustomAtkMin(x)
  battler.setCustomDefMin(x)
  battler.setCustomMatMin(x)
  battler.setCustomMdfMin(x)
  battler.setCustomAgiMin(x)
  battler.setCustomLukMin(x)
  - Sets the minimum parameter limit of the respective base parameter to x.
  This value is calculated against any <stat Min: x> notetags that the
  battler may have. If there are multiple min values, the larges value is
  used as the parameter minimum.

Changelog

Version 1.04:
- Bypass the isDevToolsOpen() error when bad code is inserted into a script
call or custom Lunatic Mode code segment due to updating to MV 1.6.1.
- Fixed a typo in the documentation for script calls regarding LUK.

Version 1.03:
- Updated for RPG Maker MV version 1.5.0.

Version 1.02:
- Lunatic Mode fail safes added.

Version 1.01:
- Fixed an issue with the battler.setParam functions that made them take the
wrong value due caching issues.