Difference between revisions of "Category:Lunatic Mode (MV)"

Introduction

Lunatic Mode is a key phrase coined by Yanfly and is often seen used across the RPG Maker community by many users to refer to advanced usage of plugins involving code of some sort. It usually pertains to the usage of notetags, but it can also be applied to other things, such as Plugin Parameters and comment tags, too. It is recommended that users don't dabble with Lunatic Mode features unless they understand that what they're using can cause their game to crash if the code is made incorrectly.

Origin

The origin of Lunatic Mode came from Touhou Project, a Japanese bullet hell shoot 'em up game series. In the games, there are often four modes: Easy, Normal, Hard, and Lunatic. During the RPG Maker VX era, the Yanfly Engine ReDux series had their usage labeled in the four categories:

• Easy Mode: The scripts would be plug and play by simply adding the script to your list.
• Normal Mode: The scripts would require interaction with the game project through the usage of notetags.
• Hard Mode: The scripts would require alteration of the script's module settings.
• Lunatic Mode: The scripts would require basic coding knowledge to use correctly.

This difficulty scheme was never used again since the VX script libraries, but the term Lunatic Mode has stuck with the community since then.

Base Parameter Control

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.