2025-02-18T00:25:22Z

Yanfly:

{{TOCright}}

{| style="width: 800px;" cellspacing="0" cellpadding="0"
| style="width: 100%; vertical-align: top;" |

[[File:RMMZ_CoreScript_Update.png]]

This is the changelog for the version differences in the base code for RPG Maker MZ across the versions.








== Update #15: 1.8.1 to 1.9.0 ==

[[File:RMMZ_190.png]]

[https://store.steampowered.com/news/app/1096900/view/527586104606458309?l=english Official Steam Update Notice Link]

* rmmz_core.js
** Version Number Update

* rmmz_managers.js
** Version Number Update
*** ImageManager
**** ImageManager.iconWidth can now be redefined by the editor
**** ImageManager.iconHeight can now be redefined by the editor
**** ImageManager.faceWidth can now be redefined by the editor
**** ImageManager.faceHeight can now be redefined by the editor
**** ImageManager.getIconSize new function added
**** ImageManager.getFaceSize new function added
*** BattleManager
**** BattleManager.applySubstitute function reverted to older variant
***** Substitution no longer checks if the target is no longer the substitute
***** The target check is now changed to the Game_Unit function

* rmmz_objects.js
** Version Number Update
*** Game_Screen
**** Game_Screen.maxPictures can now be redefined by the editor
**** Will default back to 100 if no such setting is found
*** Game_Unit
**** Game_Unit.substituteBattler updated
**** Added argument for 'target'
**** Checks to see if the substitute is not the target

* rmmz_scenes.js
** Version Number Update
*** Scene_Name
**** Scene_Name.editWindowRect updated to use 'ImageManager.standardFaceHeight' instead of 'ImageManager.faceHeight'

* rmmz_sprites.js
** Version Number Update

* rmmz_windows.js
** Version Number Update
*** Window_Base
**** Window_Base.processDrawIcon updated
***** Now calculates difference change for the new icon width and icon height
**** Window_Base.drawFace updated
***** Function updated for 'ImageManager.standardFaceWidth' instead of 'ImageManager.faceWidth'
***** Function updated for 'ImageManager.standardFaceHeight' instead of 'ImageManager.faceHeight'
**** Window_Base.drawItemName updated
***** Function updated for 'ImageManager.standardIconWidth' instead of 'ImageManager.iconWidth'
*** Window_StatusBase
**** Window_StatusBase.drawActorIcons updated
***** Function updated for 'ImageManager.standardIconWidth' instead of 'ImageManager.iconWidth'
*** Window_EquipStatus
**** Window_EquipStatus.paramY updated
***** Function updated for 'ImageManager.standardFaceHeight' instead of 'ImageManager.faceHeight'
*** Window_Message
**** Window_Message.drawMessageFace updated
***** Function updated for 'ImageManager.standardFaceWidth' instead of 'ImageManager.faceWidth'
*** Window_BattleStatus
**** Window_BattleStatus.stateIconX updated
***** Function updated for 'ImageManager.standardIconWidth' instead of 'ImageManager.iconWidth'
**** Window_BattleStatus.stateIconY updated
***** Function updated for 'ImageManager.standardIconHeight' instead of 'ImageManager.iconHeight'








== Update #14: 1.8.0 to 1.8.1 ==

[https://store.steampowered.com/news/app/1096900/view/4597700312707856063?l=english Official Steam Update Notice Link]

* rmmz_core.js
** Version Number Update

* rmmz_managers.js
** Version Number Update

* rmmz_objects.js
** Version Number Update
** Game_System.prototype.isMessageSkipEnabled function added
** Game_Unit.prototype.substituteBattler function updated
*** Substitute mechanic no longer prevents the target from substituting an attack for itself

* rmmz_scenes.js
** Version Number Update
** Scene_Equip.prototype.onSlotOk function updated
*** Equip Scene will forcefully select the first slot whenever player picks a slot to equip

* rmmz_sprites.js
** Version Number Update

* rmmz_windows.js
** Version Number Update
** Window_Message.prototype.cancelWait updated to acknowledge message skip feature








== Update #13: 1.7.0 to 1.8.0 ==

[[File:RMMZ_Update_180.png|228px]]

[https://steamcommunity.com/app/1096900/eventcomments/7119694909426620627 Official Steam Update Notice Link]

'''Changelog'''

* rmmz_core.js
** Version Number Update

* rmmz_managers.js
** Version Number Update
** BattleManager.isActionForced function added extra conditions to make sure no win or lose conditions are fulfilled

* rmmz_objects.js
** Version Number Update

* rmmz_scenes.js
** Version Number Update
** Scene_Boot.prototype.startNormalGame function exchanged a SceneManager.goto from Scene_Title to Scene_Splash
** Scene_Splash added
** Scene_Message.prototype.cancelMessageWait added
*** Related to the new ability to fast forward the <nowiki>\|</nowiki> wait timer
** Scene_Map.prototype.updateMainMultiply added cancelMessageWait() to its fastforward mode

* rmmz_sprites.js
** Version Number Update

* rmmz_windows.js
** Version Number Update
** Window_EventItem.prototype.initialize added new flag for _canRepeat
** Window_Message.prototype.cancelWait added
*** Linked to the added Scene_Message.prototype.cancelMessageWait function








== Update #12: 1.6.1 to 1.7.0 ==

[[File:RMMZ_Update_170.png]]

* rmmz_core.js
** Version Number Update
** Tilemap.prototype._createLayers function updated to use Tilemap.CombinedLayer() instead of Tilemap.Layer()
** New Function: Tilemap.Layer.prototype.size
** New Class: Tilemap.CombinedLayer

* rmmz_managers.js
** Version Number Update
** New Function: DataManager.isTitleSkip
** BattleManager.forceAction updated to check to see if there's existing actions before forcing the battler to perform a forced action

* rmmz_objects.js
** Version Number Update

* rmmz_scenes.js
** Version Number Update
** Scene_Boot.prototype.start updated to utilize the new Title Skip functionality

* rmmz_sprites.js
** Version Number Update

* rmmz_windows.js
** Version Number Update
** Window_ScrollText.prototype.refresh updated to calculate the y position in reference to the scroll position of the window
** Window_ScrollText.prototype.contentsHeight updated to check if allTextHeight variable is larger than 1 before returning a value
** Window_ScrollText.prototype.updateMessage updated to utilize the new scrollY check








== Update #11: 1.6.0 to 1.6.1 ==

The core scripts are identical to 1.6.0.

Not even the version numbers are changed to v1.6.1.








== Update #10: 1.5.0 to 1.6.0 ==

[[File:RMMZ_Update_160.png]]

* rmmz_core.js
** Version Number Update
** Graphics._updateErrorPrinter updated to show errors more relative to window scale

* rmmz_managers.js
** Version Number Update

* rmmz_objects.js
** Version Number Update

* rmmz_scenes.js
** Version Number Update
** Scene_Boot.prototype.adjustWindow updated to utilize new ScreenScale calculation
** New function: Scene_Boot.prototype.screenScale

* rmmz_sprites.js
** Version Number Update

* rmmz_windows.js
** Version Number Update
** Window_Base.prototype.convertEscapeCharacters updated to fully convert all \v[x] variables even when embedded.








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-1-5-0-patch-notes.148146/ Update #9: 1.4.4 to 1.5.0] ==

[[File:RMMZ_Update_150.png]]

* rmmz_core.js
** Version Number Update
** The following functions have _tileWidth and _tileHeight variables changed to tileWidth and tileHeight without the underscore _
*** Tilemap.prototype.initialize
*** Tilemap.prototype.updateTransform
*** Tilemap.prototype._addAllSpots
*** Tilemap.prototype._addSpot
*** Tilemap.prototype._addNormalTile
*** Tilemap.prototype._addAutotile
*** Tilemap.prototype._addTableEdge
*** Tilemap.prototype._addShadow

* rmmz_managers.js
** Version Number Update
** SceneManager.terminate now changed to detect if running a NodeJS client to close the app instead (just like what VisuMZ Core Engine does)

* rmmz_objects.js
** Version Number Update
** Game_Map.prototype.tileWidth updated to grab the new $dataSystem.tileSize property
** Game_Map.prototype.tileHeight now replicates Game_Map.prototype.tileWidth's result
** Game_Map.prototype.bushDepth new function added
** Game_CharacterBase.prototype.refreshBushDepth updated to utilize new bushDepth function
** Game_Interpreter.prototype.command109 added
*** Supposedly, this is for an Event Command that will be called "Skip" but I looked inside the RMMZ event editor and there's nothing there so it's probably not implemented yet.
*** Oh, this is what it is for:
*** [[File:RMMZ_Skip.png]]
*** You highlight the code you want to "comment out", right click, and click Toggle Skip
*** This is good for testing purposes and streamlining your events during testing so that you don't have to go through entire cutscenes to see if a switch was properly turned on at the end.

* rmmz_scenes.js
** Version Number Update
** Scene_Map.prototype.create updated to no longer check for a non-existent $dataMap or a changed $gameMap.mapId() (since it's results in the same thing anyway)

* rmmz_sprites.js
** Version Number Update
** Sprite_Character.prototype.updateFrame no longer checks to see if the sprite's bitmap is loaded and ready
*** Sprite_Enemy.prototype.initMembers updated the _battlerName variable to start with null instead of "" to avoid conflict

* rmmz_windows.js
** Version Number Update








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-1-4-4-patch-notes.145233/ Update #8: 1.4.3 to 1.4.4] ==

* rmmz_core.js
** Version Number Update

* rmmz_managers.js
** Version Number Update

* rmmz_objects.js
** Version Number Update

* rmmz_scenes.js
** Version Number Update

* rmmz_sprites.js
** Version Number Update
** Sprite_Character.prototype.updateFrame updated
*** Now checks to see if the bitmap is loaded and ready before making changes to the tile frame, presumably to avoid updating into errors when there is either no bitmap or the bitmap is in the middle of transitioning into some other image.

* rmmz_windows.js
** Version Number Update








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-1-4-3-patch-notes.144047 Update #7: 1.4.0 to 1.4.3] ==

* rmmz_core.js
** Version Number Update

* rmmz_managers.js
** Version Number Update
** BattleManager.updateTurnEnd updated to remove '''this.startInput()''' and replaced it with '''this._phase = "start"'''
*** This might be potentially troublesome

* rmmz_objects.js
** Version Number Update

* rmmz_scenes.js
** Version Number Update

* rmmz_sprites.js
** Version Number Update
** Spriteset_Map.prototype.updateParallax updated to scale better for mobile devices

* rmmz_windows.js
** Version Number Update








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-1-4-0-update.142845/ Update #6: 1.3.3 to 1.4.0] ==

* rmmz_core.js
** Version Number Update
** Bitmap.prototype.measureTextWidth returns width value, no longer rounded upwards

* rmmz_managers.js
** Version Number Update
** SceneManager.updateEffekseer will now only update if the game is currently active, too
** Function endAllBattlersTurn() is removed from BattleManager.endTurn and placed into BattleManager.updateTurnEnd
** BattleManager.checkAbort now checks if all party members are escaped before aborting to prevent a game over
** New Function added: BattleManager.processPartyEscape
** BattleManager.endBattle now clears any reserved common events

* rmmz_objects.js
** Version Number Update
** New function added: Game_Temp.prototype.clearCommonEventReservation
** New function added: Game_Timer.prototype.frames
** Game_Party.prototype.battleMembers function updated to use new functions:
** New function added: Game_Party.prototype.hiddenBattleMembers
** New function added: Game_Party.prototype.allBattleMembers
** New function added: Game_Party.prototype.isEscaped
** Game_Interpreter.prototype.command111 (Conditional Branch) updated to utilize the Game Timer frames function

* rmmz_scenes.js
** Version Number Update

* rmmz_sprites.js
** Version Number Update
** Sprite_Animation.prototype.shouldWaitForPrevious function is now completely disabled
** Sprite_Gauge.measureLabelWidth now rounds up the returned value

* rmmz_windows.js
** Version Number Update








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-1-3-3-update.140440/ Update #5: 1.3.2 to 1.3.3] ==

[[File:RMMZ_Update_133.png]]

* rmmz_core.js
** Version Number Update
** New function added: Utils.extractFileName

* rmmz_managers.js
** Version Number Update
** Updated functions:
*** ImageManager.isObjectCharacter
*** ImageManager.isBigCharacter
*** ImageManager.isZeroParallax
*** PluginManager.setup
**** To utilize the Utils.extractFileName for parsing extended filepaths

* rmmz_objects.js
** Version Number Update

* rmmz_scenes.js
** Version Number Update
** Updated function:
*** Scene_Item.prototype.createItemWindow
**** Removed this._itemWindow.createContents()

* rmmz_sprites.js
** Version Number Update
** Updated functions:
*** Sprite_Animation.prototype.initMembers
**** Removed this._originalViewport = null
*** Sprite_Animation.prototype._render
**** Removed this.saveViewport(renderer)
*** Sprite_Animation.prototype.resetViewport
**** Updated code to renderer.gl.viewport(0, 0, renderer.view.width, renderer.view.height)
*** Sprite_Gauge.prototype.bitmapHeight
**** Changed value from 24 to 32
*** Sprite_Gauge.prototype.drawLabel
*** Sprite_Gauge.prototype.drawValue
**** Changed a line to const height = this.textHeight() from const height = this.bitmapHeight()
** Added function:
*** Sprite_Gauge.prototype.textHeight
**** With a value of 24
** Removed function:
*** Sprite_Animation.prototype.saveViewport

* rmmz_windows.js
** Version Number Update








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-1-3-2-update.138130/ Update #4: 1.3.1 to 1.3.2] ==

Changes will be included in the next update list.








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-v1-3-0-update.137685/ Update #3: 1.3.0 to 1.3.1] ==

There aren't any changes made to the code base, but there are for the editor.

The aforementioned bugs are now fixed and the lag is now gone. Hooray! Go wild, download, back up your game, and update!








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-v1-3-0-update.137685/ Update #2: 1.2.0 to 1.3.0] ==

[[File:RMMZ_130.png]]

[https://dl.degica.com/rpgmakerweb/trial-download/RPGMZ_Setup_EN.exe Download Standalone Update Here]

'''NOTE:''' I highly recommend not updating to this version yet. There are a lot of lag issues going on and there's functionality lost regarding setting tiles as event graphics.

* rmmz_core.js
** Version Number Update
** Graphics.resize function updated with app.renderer.resize line added
** Tilemap.Renderer.prototype._createShader updated uSampler1 and uSampler2's values from 1 and 2 to 0 (both)
** Window.prototype._refreshBack calculations for tiling sprite are now different (and will most likely be fixed compared to before)

* rmmz_managers.js
** Version Number Update

* rmmz_objects
** Version Number Update
** Game_System.prototype.windowOpacity function added
** Game_Character.prototype.processRouteEnd updated to set forced movement success to false

* rmmz_scenes.js
** Version Number Update

* rmmz_sprites.js
** Version Number Update
** Sprite_Actor.prototype.setBattler updated so that when no battler is set, the battler name cache is cleared, too

* rmmz_windows.js
** Version Number Update
** Window_Base.prototype.updateBackOpacity updated to now take in the new database entry
** Window_ChoiceList.prototype.start updated to automatically scroll back to the top
** Window_Message.prototype.updateMessage and Window_Message.prototype.shouldBreakHere updated to use the new function:
** Window_Message.prototype.isWaiting new function added to determine waiting

'''NOTE:''' I highly recommend not updating to this version yet. There are a lot of lag issues going on and there's functionality lost regarding setting tiles as event graphics.








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-v1-1-1-update.131057/ Update #2: 1.1.1 to 1.2.0] ==

[[File:RMMZ_120.png]]

* rmmz_core.js
** Version Number Update
** Graphics._createEffekseerContext function updated with setRestorationOfStatesFlag function
** Window.prototype._refreshBack updated to use a value of 95 instead of 96 to avoid blurring edges

* rmmz_managers.js
** Version Number Update

* rmmz_objects.js
** Version Number Update

* rmmz_scenes.js
** Version Number Update
*** Scene_Item.prototype.createItemWindow

* rmmz_sprites.js
** Version Number Update
*** Sprite_Animation.prototype.onAfterRender removed contextChange function
*** Sprite_Gauge.prototype.measureLabelWidth updated to take global widths of HP, MP, and TP for visual consistency

* rmmz_windows.js
** Version Number Update








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-v1-1-1-update.131057/ Update #1: 1.1.0 to 1.1.1] ==

[[File:RMMZ_111.png]]

* rmmz_core.js
** Version Number Update
** Bitmap.prototype.measureTextWidth now returns a rounded value

* rmmz_managers.js
** Version Number Update

* rmmz_objects.js
** Version Number Update
** Game_Interpreter.prototype.command119 aka Jump to Label now breaks upon finding a match instead of a return.
*** This results in saving a frame count.

* rmmz_scenes.js
** Version Number Update

* rmmz_sprites.js
** Version Number Update

* rmmz_windows.js
** Version Number Update
** Window_Base.prototype.drawFace now uses a rounded value for sx and sy
** Window_MenuStatus.prototype.drawItemStatus now uses a rounded value for y
** Window_ScrollText.prototype.startMessage checks if there is text first








== [https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mz-v1-1-0-update.129288/ Update #1: 1.0.0 to 1.1.0] ==

[[File:RMMZ_110.png]]

* rmmz_core.js
** Version Number Update

* rmmz_managers.js
** Version Number Update
** StorageManager.saveToForage updated to arrow function
** StorageManager.removeForage updated to arrow function
** EffectManager.startLoading arguments added for onError
** BattleManager.startAction now cancels the subject's motion refresh

* rmmz_objects.js
** Version Number Update
** Game_Battler.prototype.cancelMotionRefresh function added
** Game_Actor.prototype.makeAutoBattleActions updated from Number.MIN_VALUE to -Number.MAX_VALUE
** Game_Map.prototype.screenTileX rounds to the nearest whole number
** Game_Map.prototype.screenTileY rounds to the nearest whole number
** Game_Player.prototype.centerX is now calculated using the $gameMap.screenTileX() function
** Game_Player.prototype.centerY is now calculated using the $gameMap.screenTileY() function

* rmmz_scenes.js
** Version Number Update

* rmmz_sprites.js
** Version Number Update
** Sprite_Animation.prototype.targetSpritePosition can now align to bottom
** Sprite_Gauge.prototype.gaugeX is now calculated using measureLabelWidth function for generic gauges
** Sprite_Gauge.prototype.measureLabelWidth function added

* rmmz_windows.js
** Version Number Update








== End of Page ==

<html><script type="text/javascript" src="https://www.free-counters.org/count/dnyy"></script><br>
<a href='https://www.easybooking.eu/produkte/julia-hotelsoftware'>Hotelsoftware mit Channelmanager</a> <script type='text/javascript' src='https://www.whomania.com/ctr?id=cc28662c449788c1a0c958c86722e66b6ac782e9'></script></html>

|}

Yanfly: /* Passive State Notetags */

Battle System Differences VisuStella MZ

2024-11-21T03:34:09Z

Yanfly:

{{TOCright}}

{| style="width: 800px;" cellspacing="0" cellpadding="0"
| style="width: 100%; vertical-align: top;" |

== Introduction ==

[[File:battlebegin.jpg|600px]]

Some of you may have been wondering about which battle system to use for your [[RPG Maker MZ]] game. After all, if you're going to design your game's battle system, you'll want to pick the right foundation for it from the start or else the problems will compound upon one another as the game project develops further. This article will highlight the key aspects to take into consideration when picking the battle system suited for your game.

{{Article by Yanfly}}

== Difference Chart ==

Since this is probably what many of you are looking for, I'll go ahead and include it towards the top of this article so that there's less need to search around.

{| class="wikitable" style="width:800px; text-align: center"

|-

! scope="row" colspan="99" | <hr>Battle System Comparison Chart<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | Stands For
|  Default Turn Battle
|  Time Progress Battle
|  [[Battle System - ATB VisuStella MZ|Active Turn Battle]]
|  [[Battle System - BTB VisuStella MZ|Brave Turn Battle]]
|  [[Battle System - CTB VisuStella MZ|Charge Turn Battle]]
|  [[Battle System - ETB VisuStella MZ|Energy Turn Battle]]
|  [[Battle System - FTB VisuStella MZ|Free Turn Battle]]
|  [[Battle System - OTB VisuStella MZ|Order Turn Battle]]
|  [[Battle System - PTB VisuStella MZ|Press Turn Battle]]
|  [[Battle System - STB VisuStella MZ|Standard Turn Battle]]

|-

! scope="row" colspan="99" | <hr>General Data<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | Turn-based
|  ✅
|  -
|  -
|  ✅
|  -
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Tick-based
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Team-based
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Proactive Playstyle
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Reactive Playstyle
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | DTB Base
|  ✅
|  -
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -
|  ✅

|-

! scope="row" | TPB Base
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Plugin
|  -
|  -
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅

|-

! scope="row" colspan="99" | <hr>Actions & Turn Order Handling<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | Immediate Action
|  -
|  ✅
|  ✅
|  -
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅

|-

! scope="row" | Delayed Action
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Team-Based Actions
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Multi-Action Queue
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Positive Action Speed
|  ✅
|  -
|  ✅
|  ✅
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Negative Action Speed
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Action Speed Carryover
|  -
|  -
|  ✅
|  -
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Turn Lapping
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Time Gauge
|  -
|  ✅
|  ✅
|  -
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Battle-Wide Turn Order
|  -
|  -
|  ✅
|  ✅
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Action Count Display
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Action Growth
|  -
|  -
|  -
|  ✅
|  -
|  ✅
|  -
|  -
|  ✅
|  -

|-

! scope="row" | Action Stability
|  ✅
|  ✅
|  ✅
|  -
|  ✅
|  -
|  ✅
|  ✅
|  -
|  ✅

|-

! scope="row" colspan="99" | <hr>Mechanics and Gimmicks<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | Action Count System
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Action Fusion System
|  -
|  -
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Brave System
|  -
|  -
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Exploit System
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅

|-

! scope="row" | Free Switching
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  -
|  -

|-

! scope="row" | Instant Action
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Interruption
|  -
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Speed Manipulation
|  -
|  -
|  ✅
|  -
|  ✅
|  -
|  -
|  ✅
|  -
|  -

|-

! scope="row" | Turn Order Manipulation
|  -
|  -
|  -
|  -
|  ✅
|  -
|  -
|  ✅
|  -
|  -

|-

! scope="row" colspan="99" | <hr>End of Chart<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | -
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" colspan="99" | <hr>

|}

'''NOTE*''': The battle systems in the chart above do not show which battle systems are "better" than others by having more ✅check marks. The number of ✅check marks is irrelevant to whether or not a battle system is fit for your game. Instead, you should be looking at where those ✅checkmarks are in order to determine which battle systems best suits your game design style.

== Structure: Action Economy and Turn Advantage ==

[[File:TurnAdvantageComic.png|800px]]

In traditional JRPG's, '''Action Economy''' refers to the quantity and frequency of how often a battler, an actor or an enemy, can perform during the scope of battle. The flow of battle determines the frequency of a traditional JRPG's action economy. This is extremely important to understand because the more actions a battler has, the more often he or she is able to apply pressure to the opposite team and move his or her own team towards victory.

'''Turn Advantage''' refers to describing the advantage a participating battler has based on turn-order. Depending on the battle flow, most of the time, those that act more quicker and more often have a better turn advantage than their opponents. Those with more turn advantage are also more likely to win the battle provided both sides are relatively balanced.

There is overlap between Action Economy and Turn Advantage but they are '''NOT''' the same. Action economy refers to the quantity of actions a battler can produce in a given time while Turn Advantage relates to the speed and priority of actions a battler can produce over time. Understanding both of these will help you understand the flow and structure of battle.

There are four types of battle flows that determine the frequency of when battlers get actions: Real-Time, Tick-Based, Turn-Based, Team-Based

<hr>

=== Real-Time Battle Structure ===

Real-time battles are seen in games like [https://en.wikipedia.org/wiki/Star_Ocean Star Ocean], [https://en.wikipedia.org/wiki/Tales_(video_game_series) Tales of series], and [https://en.wikipedia.org/wiki/Kingdom_Hearts Kingdom Hearts] just to name a few examples. Their battles have all participants performing actions on demand as long as they're not in the middle of an action and have enough resources to commit to that action.

'''Action Economy:''' The Action Economy in a real-time battle system is next to unlimited, only limited by the unit's resources, action's frequency of use, and unit's current state of being able to perform an action or not.

'''Turn Advantage:''' Turn Advantage in a real-time battle system almost does not exist. All units are able to move and act whenever they player or AI needs them to.

'''Balancing:''' Balancing these types of battles can be a real challenge.

'''VisuStella MZ Plugins:''' There are no VisuStella MZ plugins for this type of battle flow.

<hr>

=== Tick-Based Battle Structure ===

Tick-based battles are seen in games like many of the [https://en.wikipedia.org/wiki/Final_Fantasy_IV Final] [https://en.wikipedia.org/wiki/Final_Fantasy_V Fantasy] [https://en.wikipedia.org/wiki/Final_Fantasy_VI games], [https://en.wikipedia.org/wiki/Grandia_(video_game) Grandia], and the more recent [https://en.wikipedia.org/wiki/Atelier_Ryza:_Ever_Darkness_%26_the_Secret_Hideout Atelier Ryza]. The battle flow is entirely dependent on each battle participant's AGI (or speed). AGI becomes the most important parameter in most tick-based battle systems.

'''Action Economy:''' Battle participants typically only have one action each time they have a turn to perform an action. This is balanced for the most part. However, due to the nature of turn advantage in a tick-based battle system, anyone who can perform multiple actions per turn will usually and drastically outperform any other battle participant.

'''Turn Advantage:''' Turns are determined by each participant's AGI. The more AGI a battler has, the more often their turn comes up. There is no limit to how many turns a battler can acquire in a set amount of time. Battlers with high enough AGI can overlap battlers with less AGI.

'''Balancing:''' Balancing a tick-based battle system is extremely tricky. Most games that utilize them keep AGI levels around a similar range without letting them grow too much over time and without letting them vary by too much either. Status effects like Haste and Slow are far more potent than status effects that raise damage dealt or reduce damage taken. This is to avoid giving any battler too much Turn Advantage.

'''VisuStella MZ Plugins:''' [[Battle System - ATB VisuStella MZ|ATB]], [[Battle System - CTB VisuStella MZ|CTB]], TPB

<hr>

=== Turn-Based Battle Structure ===

Turn-based battle systems are seen in most [https://en.wikipedia.org/wiki/Dragon_Quest Dragon Quest] games, some of the spin off [https://en.wikipedia.org/wiki/Megami_Tensei Shin Megami Tensei] games, some of the [https://en.wikipedia.org/wiki/Persona_(series) Persona] games, and even the [https://en.wikipedia.org/wiki/Pok%C3%A9mon_(video_game_series) Pokémon] games. Battle flow revolves around (usually) giving an equal amount of turns and (usually) actions to perform to each battle participant in a balanced manner.

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

'''VisuStella MZ Plugins:''' [[Battle System - BTB VisuStella MZ|BTB]], DTB, [[Battle System - OTB VisuStella MZ|OTB]], [[Battle System - STB VisuStella MZ|STB]]

<hr>

=== Team-Based Battle Structure ===

Team-based battle systems revolve their turns around their teams than the individual battle participants. You see this in games like many of the [https://en.wikipedia.org/wiki/Fire_Emblem Fire Emblem] games, [https://en.wikipedia.org/wiki/Disgaea Disgaea] games, the main line [https://en.wikipedia.org/wiki/Megami_Tensei Shin Megami Tensei] games, and even some mobile games like [https://en.wikipedia.org/wiki/Granblue_Fantasy Granblue Fantasy]. Teams take turn performing for all of their battle participants at a time or as long sa there's enough actions to perform. AGI hass little influence in this battle system as it no longer determines the frequency of turns for each battle member.

'''Action Economy:''' Depending on the battle system, units usually have one or two actions to perform at a time, or as many as the team allows before the team's turn is considered over.

'''Turn Advantage:''' Instead of turn advantage going to participants with more frequent turns or participants with faster speed, turn advantage, instead, goes to the team that goes first. In most cases, the team that goes first is almost always leading the battle system, though counterbalancing the advantage for the team going second is a common practice to be seen, too.

'''Balancing:''' Balancing for this type of battle flow can be tricky. It can be easier or harder than either tick-based or turn-based depending on how the battle is designed. Strategies also shift from having the key participant perform more frequently to making the most optimal team play for each turn as the norm.

'''VisuStella MZ Plugins:''' [[Battle System - ETB VisuStella MZ|ETB]], [[Battle System - FTB VisuStella MZ|FTB]], [[Battle System - PTB VisuStella MZ|PTB]]

<hr>

== Individual Battle Systems ==

In this section, we'll take a look at each individual battle system and address the various aspects that make it unique.

<hr>

=== Default Turn Battle ===

[[File:RMMZ_DTB.png|300px]]

This is the default battle system found in RPG Maker MZ. It's also the default battle system for RPG Maker 2000, XP, VX, VX Ace, and MV. Players will input their actions for each party member that can act, then the turn starts, playing out the action order based on the speed of the individual actors and enemies.

---

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

---

A very vanilla and basic battle system.

<hr>

=== Time Progress Battle ===

[[File:RMMZ_TPB.png|300px]]

This is a new battle system found in RPG Maker MZ. It wasn't present for the past iterations of RPG Maker.

---

'''Action Economy:''' Battle participants typically only have one action each time they have a turn to perform an action. This is balanced for the most part. However, due to the nature of turn advantage in a tick-based battle system, anyone who can perform multiple actions per turn will usually and drastically outperform any other battle participant.

'''Turn Advantage:''' Turns are determined by each participant's AGI. The more AGI a battler has, the more often their turn comes up. There is no limit to how many turns a battler can acquire in a set amount of time. Battlers with high enough AGI can overlap battlers with less AGI.

'''Balancing:''' Balancing a tick-based battle system is extremely tricky. Most games that utilize them keep AGI levels around a similar range without letting them grow too much over time and without letting them vary by too much either. Status effects like Haste and Slow are far more potent than status effects that raise damage dealt or reduce damage taken. This is to avoid giving any battler too much Turn Advantage.

---

There's really not much else going for it other than breaking free of the turn-based structure of the DTB. Waiting times inbetween actions are dead and don't contribute much else.

<hr>

=== [[Battle System - ATB VisuStella MZ|Active Turn Battle]] ===

[[File:VisuMZ.022.jpg|300px|link=Battle System - ATB VisuStella MZ]]

The RPG Maker MZ Time Progress Battle (TPB) system is only a few steps away from the acclaimed Active Turn Battle (ATB) system. This plugin will grant it the various features needed to turn it from TPB into ATB.

This plugin will grant control over how the various mechanics work, ranging from penalties to calculations, to actions that can manipulate the ATB gauge of battlers. Battlers that are in the middle of casting a spell can also be interrupted with specific notetag traits.

ATB Gauges can also be displayed on enemies and/or allies, giving the player full access to the current battle state. The ATB Gauges are also improved, showing different colors for different states and showing a new gauge for the casting state.

---

'''Action Economy:''' Battle participants typically only have one action each time they have a turn to perform an action. This is balanced for the most part. However, due to the nature of turn advantage in a tick-based battle system, anyone who can perform multiple actions per turn will usually and drastically outperform any other battle participant.

'''Turn Advantage:''' Turns are determined by each participant's AGI. The more AGI a battler has, the more often their turn comes up. There is no limit to how many turns a battler can acquire in a set amount of time. Battlers with high enough AGI can overlap battlers with less AGI.

'''Balancing:''' Balancing a tick-based battle system is extremely tricky. Most games that utilize them keep AGI levels around a similar range without letting them grow too much over time and without letting them vary by too much either. Status effects like Haste and Slow are far more potent than status effects that raise damage dealt or reduce damage taken. This is to avoid giving any battler too much Turn Advantage.

---

'''Interruption:''' This mechanic allows actors and enemies to interrupt any battlers who happen to be casting/preparing a skill, causing them to lose progress and sending them back to having to ready up again. This takes advantage of the semi-real time nature of the battle system, which no turn-based battle system has.

'''Speed Manipulation:''' Speed manipulation allows the "Speed" stat of an action to influence the turn frequency/delay of future turns. This can be used strategically by the player to get in an extra action before an enemy can in the following turns.

<hr>

=== [[Battle System - BTB VisuStella MZ|Brave Turn Battle]] ===

[[File:VisuMZ.048.jpg|300px|link=Battle System - BTB VisuStella MZ]]

The Brave Turn Battle (BTB) system plays off RPG Maker MZ's default battle system with a twist of allowing actors (and enemies) to use up actions from the future or save up for later. These actions will be queued and delivered all in one go! Any borrowed actions from the future will result in following turns without any actions to use. Should a player decide to save up their actions instead through Guarding, they can charge actions with less repercussions. Players will have to be brave about how to go about the battle system strategically.

Because multiple actions can be queued up all at once, they can result in the creation of an action fusion. Some skills (and items) can appear instead of the originally queued actions to result in stronger, better, and more awesome effects, all of which, can be defined by the game dev.

A Turn Order Display will also appear on the screen to show the order the battlers will take their turns in. This lets the player plan in advance on how to go about the rest of the turn.

---

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

---

'''Action Fusion System:''' As a battle system that lets you queue up multiple actions at a time before heading off into battle, special action combinations can be created and checked to create new attacks. If "Attack" is queued up twice, it can result in "Dual Attack". If "Attack" is queued up four times, perhaps you can let the actor perform a "Quadra Attack". If "Attack" and "Fireball" is queued up together in any order, the actor can perform a "Fire Strike". The combinations are all up to you.

'''Brave System:''' While queuing up actions is possible with DTB, it has to be done through items in a more permanent sense. The Brave System allows the actor to access extra actions during the current turn by borrowing them from a future turn in which the actor wouldn't have any actions to utilize.

<hr>

=== [[Battle System - CTB VisuStella MZ|Charge Turn Battle]] ===

[[File:VisuMZ.031.jpg|300px|link=Battle System - CTB VisuStella MZ]]

This plugin creates a Charge Turn Battle (CTB) system using RPG Maker MZ's TPB as a base. CTB functions by calculating the speed of every battler and balancing them relative to one another. When it's a battler's turn, the battler will either choose an action to perform immediately or charge it for later depending if the skill requires charging.

This is a battle system where agility plays an important factor in the progress of battle where higher agility values give battlers more advantage and additional turns over lower agility values, which give battlers less advantage and less turns.

A turn order display will appear to compensate for the removal of gauges. The turn order display will show a preview of what the turn order could possibly be like. This turn order display is variable and can be changed due to player and enemy influence by using different action speeds, effects provided by this plugin that alter the turn order, and more!

---

'''Action Economy:''' Battle participants typically only have one action each time they have a turn to perform an action. This is balanced for the most part. However, due to the nature of turn advantage in a tick-based battle system, anyone who can perform multiple actions per turn will usually and drastically outperform any other battle participant.

'''Turn Advantage:''' Turns are determined by each participant's AGI. The more AGI a battler has, the more often their turn comes up. There is no limit to how many turns a battler can acquire in a set amount of time. Battlers with high enough AGI can overlap battlers with less AGI.

'''Balancing:''' Balancing a tick-based battle system is extremely tricky. Most games that utilize them keep AGI levels around a similar range without letting them grow too much over time and without letting them vary by too much either. Status effects like Haste and Slow are far more potent than status effects that raise damage dealt or reduce damage taken. This is to avoid giving any battler too much Turn Advantage.

---

'''Speed Manipulation:''' Speed manipulation allows the "Speed" stat of an action to influence the turn frequency/delay of future turns. This can be used strategically by the player to get in an extra action before an enemy can in the following turns.

'''Turn Order Manipulation:''' Battlers can delay enemy turns and hasten ally turns through direct manipulation instead of through AGI. This opens up lots of potential strategies that can be utilized to bring the tides of battle into one's favor.

<hr>

=== [[Battle System - ETB VisuStella MZ|Energy Turn Battle]] ===

[[File:VisuMZ.080.jpg|300px|link=Battle System - ETB VisuStella MZ]]

Energy Turn Battle (ETB) is a type of battle system made for RPG Maker MZ, where the teams for actors and enemies take turns attacking one another as a whole. Energy is accumulated as turns pass on, allowing each team to perform more actions each turn. Each team can freely perform actions among their teammates as wanted. When the energy count is depleted or if one team ran out of battler's that can act, the other team begins their turn and so forth.

Similar to how [https://playhearthstone.com/ Hearthstone] plays, energy count starts at 1, then climbs up by 1 each turn up to a maximum of 10. This lets battle progression scale linearly from slow paced to fast paced. This energy scaling can be altered through the Plugin Parameters.

---

'''Action Economy:''' Depending on the battle system, units usually have one or two actions to perform at a time, or as many as the team allows before the team's turn is considered over.

'''Turn Advantage:''' Instead of turn advantage going to participants with more frequent turns or participants with faster speed, turn advantage, instead, goes to the team that goes first. In most cases, the team that goes first is almost always leading the battle system, though counterbalancing the advantage for the team going second is a common practice to be seen, too.

'''Balancing:''' Balancing for this type of battle flow can be tricky. It can be easier or harder than either tick-based or turn-based depending on how the battle is designed. Strategies also shift from having the key participant perform more frequently to making the most optimal team play for each turn as the norm.

---

'''Action Count System:''' The Action Count System makes it possible for either party or troop to perform actions with various team members any way they want. If a team wants one member to act multiple times, then as long as the action counts permit it, they can. Also with this, some actions can consume multiple action costs if they happen to be stronger.

'''Free Switching:''' The player can (optionally) pick who they want to perform an action in battle as long as all other conditions are met (alive, enough action counts, not stunned, etc). This gives players more freedom and range for potential strategies. If a player wants the Warrior to act 4 times, that's possible. If the player wants each party member to act once each, that's also possible.

<hr>

=== [[Battle System - FTB VisuStella MZ|Free Turn Battle]] ===

[[File:VisuMZ.057.jpg|300px|link=Battle System - FTB VisuStella MZ]]

Free Turn Battle (FTB) is a type of battle system made for RPG Maker MZ, where the teams for actors and enemies take turns attacking one another as a whole. During each team's turns, an action count is given to them and they can freely perform actions among their teammates as wanted (or if turned off by the Plugin Parameters, in a cycle). When the action count is depleted or if one team ran out of battler's that can act, the other team begins their turn and so forth.

Unlike ETB, there are set amounts of actions each turn available based on the number of members for each group (party and troop). Usually, the more party members, the more actions. AGI buffs can also affect this. The action count can be modified via the Plugin Parameters.

---

'''Action Economy:''' Depending on the battle system, units usually have one or two actions to perform at a time, or as many as the team allows before the team's turn is considered over.

'''Turn Advantage:''' Instead of turn advantage going to participants with more frequent turns or participants with faster speed, turn advantage, instead, goes to the team that goes first. In most cases, the team that goes first is almost always leading the battle system, though counterbalancing the advantage for the team going second is a common practice to be seen, too.

'''Balancing:''' Balancing for this type of battle flow can be tricky. It can be easier or harder than either tick-based or turn-based depending on how the battle is designed. Strategies also shift from having the key participant perform more frequently to making the most optimal team play for each turn as the norm.

---

'''Action Count System:''' The Action Count System makes it possible for either party or troop to perform actions with various team members any way they want. If a team wants one member to act multiple times, then as long as the action counts permit it, they can. Also with this, some actions can consume multiple action costs if they happen to be stronger.

'''Free Switching:''' The player can (optionally) pick who they want to perform an action in battle as long as all other conditions are met (alive, enough action counts, not stunned, etc). This gives players more freedom and range for potential strategies. If a player wants the Warrior to act 4 times, that's possible. If the player wants each party member to act once each, that's also possible.

<hr>

=== [[Battle System - OTB VisuStella MZ|Order Turn Battle]] ===

[[File:VisuMZ.066.jpg|300px|link=Battle System - OTB VisuStella MZ]]

This plugin changes the RPG Maker MZ battle system to "Order Turn Battle", a turn-based battle system where actions are executed immediately and the orders for both the current and next turn are not only visible, but also malleable. New mechanics are introduced where the player can manipulate the turn order of an action's user or action's target in various ways they want.

The two Turn Orders are displayed at the top of the top of the screen to give the player a clear understanding of who's turn it will be when it becomes time to act, making it easier and viable for the player to formulate strategies and adapt to the situation in battle.

---

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

---

'''Instant Action:''' Instant actions allow the battler to perform a skill without consuming the current action. This is great for things like small spells that would otherwise never be a good pick in a highly competitive action economy. Examples would be stance changes, state toggles, and miniature self buffs.

'''Speed Manipulation:''' Speed manipulation allows the "Speed" stat of an action to influence the turn frequency/delay of future turns. This can be used strategically by the player to get in an extra action before an enemy can in the following turns.

'''Turn Order Manipulation:''' Battlers can delay enemy turns and hasten ally turns through direct manipulation instead of through AGI. This opens up lots of potential strategies that can be utilized to bring the tides of battle into one's favor.

<hr>

=== [[Battle System - PTB VisuStella MZ|Press Turn Battle]] ===

[[File:VisuMZ.086.jpg|300px|link=Battle System - PTB VisuStella MZ]]

Press Turn Battle (PTB) is a team-based battle system made for RPG Maker MZ where the teams for actors and enemies take turns attacking one another as a whole, consuming press actions in the process. When press actions have been emptied, the turn switches over to the opposite team and it repeats. Depending on the results of actions, Press Actions may consume a full action or be converted into a half action, allowing for more actions per turn. This is a battle system that rewards skillful play and punishes bad strategies.

Unlike ETB and FTB, more actions can be acquired based on better gameplay. Instead of favoring battle longevity or party member counts, this battle system focuses on player skill.

---

'''Action Economy:''' Depending on the battle system, units usually have one or two actions to perform at a time, or as many as the team allows before the team's turn is considered over.

'''Turn Advantage:''' Instead of turn advantage going to participants with more frequent turns or participants with faster speed, turn advantage, instead, goes to the team that goes first. In most cases, the team that goes first is almost always leading the battle system, though counterbalancing the advantage for the team going second is a common practice to be seen, too.

'''Balancing:''' Balancing for this type of battle flow can be tricky. It can be easier or harder than either tick-based or turn-based depending on how the battle is designed. Strategies also shift from having the key participant perform more frequently to making the most optimal team play for each turn as the norm.

---

'''Action Count System:''' The Action Count System makes it possible for either party or troop to perform actions with various team members any way they want. If a team wants one member to act multiple times, then as long as the action counts permit it, they can. Also with this, some actions can consume multiple action costs if they happen to be stronger.

'''Exploit System:''' The exploit system (optionally) grants teams extra advantages when hitting an opponent's weakness or landing a critical hit. These extra advantages often come in the form of extra turns or actions. This rewards good gameplay and makes lucky hits have even more impact.

<hr>

=== [[Battle System - STB VisuStella MZ|Standard Turn Battle]] ===

[[File:VisuMZ.039.jpg|300px|link=Battle System - STB VisuStella MZ]]

The Standard Turn Battle (STB) system uses RPG Maker MZ's default non-TPB battle system as a base. Action orders are determined by the battler's AGI values and they go from highest to lowest. However, actions are not selected at the start of the turn. Instead, as the turn progresses, actions are then picked as each battler's turn comes up and is executed immediately.

Optional to the battle system but fine tuned to it is the Exploit System. When landing an elemental weakness or critical hit against a foe, the battler can gain bonuses as well as an extra turn while the foe will become stunned or gain any desired state(s). When all enemies are exploited in a single turn, a common event can also be played, too.

A Turn Order Display will also appear on the screen to show the order the battlers will take their turns in. This lets the player plan in advance on how to go about the rest of the turn.

---

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

---

'''Instant Action:''' Instant actions allow the battler to perform a skill without consuming the current action. This is great for things like small spells that would otherwise never be a good pick in a highly competitive action economy. Examples would be stance changes, state toggles, and miniature self buffs.

'''Exploit System:''' The exploit system (optionally) grants teams extra advantages when hitting an opponent's weakness or landing a critical hit. These extra advantages often come in the form of extra turns or actions. This rewards good gameplay and makes lucky hits have even more impact.

== Why Battle Systems Can't Have Everything ==

[[File:ThanosEverything.jpg|600px]]

"Why can't you put x mechanic into y battle system?"

"Why can't you make everything mechanical available for all battle systems?"

These are common questions we receive as a team. We can understand how desirable certain mechanics are as they tend to make those battle systems unique. However, not all of them are possible to transplant over into different battle systems without lots of design issues and complications.

For example, the '''Action Count System''' would make very little sense in a battle system like [[Battle System - BTB VisuStella MZ|BTB]], where you can freely queue up actions already. Which ones take priority? Which ones shouldn't? Speed and Turn Order manipulation also doesn't really work well with team-based battle systems like [[Battle System - FTB VisuStella MZ|FTB]] and [[Battle System - PTB VisuStella MZ|PTB]]. '''Free Switching''' would also render turn orders meaningless for battle systems like [[Battle System - OTB VisuStella MZ|OTB]] and [[Battle System - STB VisuStella MZ|STB]].

Now, these examples are pretty obvious as no no's, but what about the others? Let's get into some specific cases that seem a bit more ''global'' but really aren't.

---

'''Brave System''' straight up borrows actions from future turns for the current turn. This feature could work in certain battle systems, but not mesh with it quite as well as the turn-based action queue structure. And the reason for this is due to the immediate action flow being broken up. The mechanic feels really out of place in comparison to everything else.

As an alternative to it that's more global, use the [[Boost Action VisuStella MZ|Boost Action]] to perform similar effects. Boost points do not take away future turns, but instead, they have to be slowly accumulated across battle, which invites a more steady flow and pacing.

---

'''Exploit Systems''' are very situational and fit only a select handful of battle systems based on their turn/action logistics. Getting an extra turn is a huge deal to some of these battle systems and in the sense of [[Battle System - ATB VisuStella MZ|ATB]] and [[Battle System - CTB VisuStella MZ|CTB]], when combined with AGI advantages, can result in balance breaking to the extremes.

It's why mechanics like these aren't made global, but instead, we offer a more mild version called [[Break Shields VisuStella MZ|Break Shields]] to allow for stuns instead, a softer version of turn advantage. A softer turn advantage through stuns is far less likely to break the mechanical balance of a game.

---

'''Instant Action''' is something you've seen in the [[Yanfly Engine Plugins]] library as a near global mechanic. However, this couldn't be further from the truth. For DTB, it broke the battle system in so many ways due to how actions were never meant to be used during the input phase. For its place in ATB and CTB, all it really did was just replace an after use speed of 0. For STB, it pushed forth an additional action. It was a completely different effect each and every battle system that it was used with. This means that the effect wasn't global, but instead, have to be custom tailored to each battle system. There's many of you that would like to see it return for DTB, but honestly? With how it completely breaks the mold and ruins the input phase, I'd rather it not.

Each battle system we've made for VisuStella MZ's plugin library has a way to create a free use condition without impeding on the action economy, which is more or less the primary reason why people used '''Instant Actions''' in the first place without having to be an "Instant" effect in and of itself. For those, reference the battle systems themselves. They're usually a notetag effect.

---

== To Sum It Up ==

[[File:SumsItUp.gif]]

There's a lot of nuances for each type battle system that makes them different from one another. These range from the types of data displayed to the mechanics they're able to access. By taking some time to read over each of them and learning their in's and out's, we hope that you can decide which battle system is the best fit for the type of game you'd like to make.

== End of Article ==

|}

<html><script type="text/javascript" src="https://www.free-counters.org/count/dag9"></script><br>
<a href='https://www.free-counters.org/'>... by Free-Counters.org</a> <script type='text/javascript' src='https://whomania.com/ctr?id=defd96e02d0659d336c51db9f09c77d6f7089973'></script></html>

Battle System Differences VisuStella MZ

2024-11-21T03:30:58Z

Yanfly: /* Structure: Action Economy and Turn Advantage */

{{TOCright}}

{| style="width: 800px;" cellspacing="0" cellpadding="0"
| style="width: 100%; vertical-align: top;" |

== Introduction ==

[[File:battlebegin.jpg|600px]]

Some of you may have been wondering about which battle system to use for your [[RPG Maker MZ]] game. After all, if you're going to design your game's battle system, you'll want to pick the right foundation for it from the start or else the problems will compound upon one another as the game project develops further. This article will highlight the key aspects to take into consideration when picking the battle system suited for your game.

{{Article by Yanfly}}

== Difference Chart ==

Since this is probably what many of you are looking for, I'll go ahead and include it towards the top of this article so that there's less need to search around.

{| class="wikitable" style="width:800px; text-align: center"

|-

! scope="row" colspan="99" | <hr>Battle System Comparison Chart<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | Stands For
|  Default Turn Battle
|  Time Progress Battle
|  [[Battle System - ATB VisuStella MZ|Active Turn Battle]]
|  [[Battle System - BTB VisuStella MZ|Brave Turn Battle]]
|  [[Battle System - CTB VisuStella MZ|Charge Turn Battle]]
|  [[Battle System - ETB VisuStella MZ|Energy Turn Battle]]
|  [[Battle System - FTB VisuStella MZ|Free Turn Battle]]
|  [[Battle System - OTB VisuStella MZ|Order Turn Battle]]
|  [[Battle System - PTB VisuStella MZ|Press Turn Battle]]
|  [[Battle System - STB VisuStella MZ|Standard Turn Battle]]

|-

! scope="row" colspan="99" | <hr>General Data<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | Turn-based
|  ✅
|  -
|  -
|  ✅
|  -
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Tick-based
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Team-based
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Proactive Playstyle
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Reactive Playstyle
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | DTB Base
|  ✅
|  -
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -
|  ✅

|-

! scope="row" | TPB Base
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Plugin
|  -
|  -
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅

|-

! scope="row" colspan="99" | <hr>Actions & Turn Order Handling<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | Immediate Action
|  -
|  ✅
|  ✅
|  -
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅

|-

! scope="row" | Delayed Action
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Team-Based Actions
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Multi-Action Queue
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Positive Action Speed
|  ✅
|  -
|  ✅
|  ✅
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Negative Action Speed
|  ✅
|  ✅
|  ✅
|  ✅
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Action Speed Carryover
|  -
|  -
|  ✅
|  -
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Turn Lapping
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Time Gauge
|  -
|  ✅
|  ✅
|  -
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Battle-Wide Turn Order
|  -
|  -
|  ✅
|  ✅
|  ✅
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Action Count Display
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Action Growth
|  -
|  -
|  -
|  ✅
|  -
|  ✅
|  -
|  -
|  ✅
|  -

|-

! scope="row" | Action Stability
|  ✅
|  ✅
|  ✅
|  -
|  ✅
|  -
|  ✅
|  ✅
|  -
|  ✅

|-

! scope="row" colspan="99" | <hr>Mechanics and Gimmicks<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | Action Count System
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  ✅
|  -

|-

! scope="row" | Action Fusion System
|  -
|  -
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Brave System
|  -
|  -
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Exploit System
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅

|-

! scope="row" | Free Switching
|  -
|  -
|  -
|  -
|  -
|  ✅
|  ✅
|  -
|  -
|  -

|-

! scope="row" | Instant Action
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  ✅
|  -
|  ✅

|-

! scope="row" | Interruption
|  -
|  -
|  ✅
|  -
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" | Speed Manipulation
|  -
|  -
|  ✅
|  -
|  ✅
|  -
|  -
|  ✅
|  -
|  -

|-

! scope="row" | Turn Order Manipulation
|  -
|  -
|  -
|  -
|  ✅
|  -
|  -
|  ✅
|  -
|  -

|-

! scope="row" colspan="99" | <hr>End of Chart<hr>

|-

! scope="col" | Category
! scope="col" | DTB
! scope="col" | TPB
! scope="col" | [[Battle System - ATB VisuStella MZ|ATB]]
! scope="col" | [[Battle System - BTB VisuStella MZ|BTB]]
! scope="col" | [[Battle System - CTB VisuStella MZ|CTB]]
! scope="col" | [[Battle System - ETB VisuStella MZ|ETB]]
! scope="col" | [[Battle System - FTB VisuStella MZ|FTB]]
! scope="col" | [[Battle System - OTB VisuStella MZ|OTB]]
! scope="col" | [[Battle System - PTB VisuStella MZ|PTB]]
! scope="col" | [[Battle System - STB VisuStella MZ|STB]]

|-

! scope="row" | -
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  -
|  -

|-

! scope="row" colspan="99" | <hr>

|}

'''NOTE*''': The battle systems in the chart above do not show which battle systems are "better" than others by having more ✅check marks. The number of ✅check marks is irrelevant to whether or not a battle system is fit for your game. Instead, you should be looking at where those ✅checkmarks are in order to determine which battle systems best suits your game design style.

== Structure: Action Economy and Turn Advantage ==

[[File:TurnAdvantageComic.png|800px]]

In traditional JRPG's, '''Action Economy''' refers to the quantity and frequency of how often a battler, an actor or an enemy, can perform during the scope of battle. The flow of battle determines the frequency of a traditional JRPG's action economy. This is extremely important to understand because the more actions a battler has, the more often he or she is able to apply pressure to the opposite team and move his or her own team towards victory.

'''Turn Advantage''' refers to describing the advantage a participating battler has based on turn-order. Depending on the battle flow, most of the time, those that act more quicker and more often have a better turn advantage than their opponents. Those with more turn advantage are also more likely to win the battle provided both sides are relatively balanced.

There is overlap between Action Economy and Turn Advantage but they are '''NOT''' the same. Action economy refers to the quantity of actions a battler can produce in a given time while Turn Advantage relates to the speed and priority of actions a battler can produce over time. Understanding both of these will help you understand the flow and structure of battle.

There are four types of battle flows that determine the frequency of when battlers get actions: Real-Time, Tick-Based, Turn-Based, Team-Based

<hr>

=== Real-Time Battle Structure ===

Real-time battles are seen in games like [https://en.wikipedia.org/wiki/Star_Ocean Star Ocean], [https://en.wikipedia.org/wiki/Tales_(video_game_series) Tales of series], and [https://en.wikipedia.org/wiki/Kingdom_Hearts Kingdom Hearts] just to name a few examples. Their battles have all participants performing actions on demand as long as they're not in the middle of an action and have enough resources to commit to that action.

'''Action Economy:''' The Action Economy in a real-time battle system is next to unlimited, only limited by the unit's resources, action's frequency of use, and unit's current state of being able to perform an action or not.

'''Turn Advantage:''' Turn Advantage in a real-time battle system almost does not exist. All units are able to move and act whenever they player or AI needs them to.

'''Balancing:''' Balancing these types of battles can be a real challenge.

'''VisuStella MZ Plugins:''' There are no VisuStella MZ plugins for this type of battle flow.

<hr>

=== Tick-Based Battle Structure ===

Tick-based battles are seen in games like many of the [https://en.wikipedia.org/wiki/Final_Fantasy_IV Final] [https://en.wikipedia.org/wiki/Final_Fantasy_V Fantasy] [https://en.wikipedia.org/wiki/Final_Fantasy_VI games], [https://en.wikipedia.org/wiki/Grandia_(video_game) Grandia], and the more recent [https://en.wikipedia.org/wiki/Atelier_Ryza:_Ever_Darkness_%26_the_Secret_Hideout Atelier Ryza]. The battle flow is entirely dependent on each battle participant's AGI (or speed). AGI becomes the most important parameter in most tick-based battle systems.

'''Action Economy:''' Battle participants typically only have one action each time they have a turn to perform an action. This is balanced for the most part. However, due to the nature of turn advantage in a tick-based battle system, anyone who can perform multiple actions per turn will usually and drastically outperform any other battle participant.

'''Turn Advantage:''' Turns are determined by each participant's AGI. The more AGI a battler has, the more often their turn comes up. There is no limit to how many turns a battler can acquire in a set amount of time. Battlers with high enough AGI can overlap battlers with less AGI.

'''Balancing:''' Balancing a tick-based battle system is extremely tricky. Most games that utilize them keep AGI levels around a similar range without letting them grow too much over time and without letting them vary by too much either. Status effects like Haste and Slow are far more potent than status effects that raise damage dealt or reduce damage taken. This is to avoid giving any battler too much Turn Advantage.

'''VisuStella MZ Plugins:''' [[Battle System - ATB VisuStella MZ|ATB]], [[Battle System - CTB VisuStella MZ|CTB]], TPB

<hr>

=== Turn-Based Battle Structure ===

Turn-based battle systems are seen in most [https://en.wikipedia.org/wiki/Dragon_Quest Dragon Quest] games, some of the spin off [https://en.wikipedia.org/wiki/Megami_Tensei Shin Megami Tensei] games, some of the [https://en.wikipedia.org/wiki/Persona_(series) Persona] games, and even the [https://en.wikipedia.org/wiki/Pok%C3%A9mon_(video_game_series) Pokémon] games. Battle flow revolves around (usually) giving an equal amount of turns and (usually) actions to perform to each battle participant in a balanced manner.

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

'''VisuStella MZ Plugins:''' [[Battle System - BTB VisuStella MZ|BTB]], DTB, [[Battle System - OTB VisuStella MZ|OTB]], [[Battle System - STB VisuStella MZ|STB]]

<hr>

=== Team-Based Battle Structure ===

Team-based battle systems revolve their turns around their teams than the individual battle participants. You see this in games like many of the [https://en.wikipedia.org/wiki/Fire_Emblem Fire Emblem] games, [https://en.wikipedia.org/wiki/Disgaea Disgaea] games, the main line [https://en.wikipedia.org/wiki/Megami_Tensei Shin Megami Tensei] games, and even some mobile games like [https://en.wikipedia.org/wiki/Granblue_Fantasy Granblue Fantasy]. Teams take turn performing for all of their battle participants at a time or as long sa there's enough actions to perform. AGI hass little influence in this battle system as it no longer determines the frequency of turns for each battle member.

'''Action Economy:''' Depending on the battle system, units usually have one or two actions to perform at a time, or as many as the team allows before the team's turn is considered over.

'''Turn Advantage:''' Instead of turn advantage going to participants with more frequent turns or participants with faster speed, turn advantage, instead, goes to the team that goes first. In most cases, the team that goes first is almost always leading the battle system, though counterbalancing the advantage for the team going second is a common practice to be seen, too.

'''Balancing:''' Balancing for this type of battle flow can be tricky. It can be easier or harder than either tick-based or turn-based depending on how the battle is designed. Strategies also shift from having the key participant perform more frequently to making the most optimal team play for each turn as the norm.

'''VisuStella MZ Plugins:''' [[Battle System - ETB VisuStella MZ|ETB]], [[Battle System - FTB VisuStella MZ|FTB]], [[Battle System - PTB VisuStella MZ|PTB]]

<hr>

== Individual Battle Systems ==

In this section, we'll take a look at each individual battle system and address the various aspects that make it unique.

<hr>

=== [[Battle System - ATB VisuStella MZ|Active Turn Battle]] ===

[[File:VisuMZ.022.jpg|300px|link=Battle System - ATB VisuStella MZ]]

The RPG Maker MZ Time Progress Battle (TPB) system is only a few steps away from the acclaimed Active Turn Battle (ATB) system. This plugin will grant it the various features needed to turn it from TPB into ATB.

This plugin will grant control over how the various mechanics work, ranging from penalties to calculations, to actions that can manipulate the ATB gauge of battlers. Battlers that are in the middle of casting a spell can also be interrupted with specific notetag traits.

ATB Gauges can also be displayed on enemies and/or allies, giving the player full access to the current battle state. The ATB Gauges are also improved, showing different colors for different states and showing a new gauge for the casting state.

---

'''Action Economy:''' Battle participants typically only have one action each time they have a turn to perform an action. This is balanced for the most part. However, due to the nature of turn advantage in a tick-based battle system, anyone who can perform multiple actions per turn will usually and drastically outperform any other battle participant.

'''Turn Advantage:''' Turns are determined by each participant's AGI. The more AGI a battler has, the more often their turn comes up. There is no limit to how many turns a battler can acquire in a set amount of time. Battlers with high enough AGI can overlap battlers with less AGI.

'''Balancing:''' Balancing a tick-based battle system is extremely tricky. Most games that utilize them keep AGI levels around a similar range without letting them grow too much over time and without letting them vary by too much either. Status effects like Haste and Slow are far more potent than status effects that raise damage dealt or reduce damage taken. This is to avoid giving any battler too much Turn Advantage.

---

'''Interruption:''' This mechanic allows actors and enemies to interrupt any battlers who happen to be casting/preparing a skill, causing them to lose progress and sending them back to having to ready up again. This takes advantage of the semi-real time nature of the battle system, which no turn-based battle system has.

'''Speed Manipulation:''' Speed manipulation allows the "Speed" stat of an action to influence the turn frequency/delay of future turns. This can be used strategically by the player to get in an extra action before an enemy can in the following turns.

<hr>

=== [[Battle System - BTB VisuStella MZ|Brave Turn Battle]] ===

[[File:VisuMZ.048.jpg|300px|link=Battle System - BTB VisuStella MZ]]

The Brave Turn Battle (BTB) system plays off RPG Maker MZ's default battle system with a twist of allowing actors (and enemies) to use up actions from the future or save up for later. These actions will be queued and delivered all in one go! Any borrowed actions from the future will result in following turns without any actions to use. Should a player decide to save up their actions instead through Guarding, they can charge actions with less repercussions. Players will have to be brave about how to go about the battle system strategically.

Because multiple actions can be queued up all at once, they can result in the creation of an action fusion. Some skills (and items) can appear instead of the originally queued actions to result in stronger, better, and more awesome effects, all of which, can be defined by the game dev.

A Turn Order Display will also appear on the screen to show the order the battlers will take their turns in. This lets the player plan in advance on how to go about the rest of the turn.

---

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

---

'''Action Fusion System:''' As a battle system that lets you queue up multiple actions at a time before heading off into battle, special action combinations can be created and checked to create new attacks. If "Attack" is queued up twice, it can result in "Dual Attack". If "Attack" is queued up four times, perhaps you can let the actor perform a "Quadra Attack". If "Attack" and "Fireball" is queued up together in any order, the actor can perform a "Fire Strike". The combinations are all up to you.

'''Brave System:''' While queuing up actions is possible with DTB, it has to be done through items in a more permanent sense. The Brave System allows the actor to access extra actions during the current turn by borrowing them from a future turn in which the actor wouldn't have any actions to utilize.

<hr>

=== [[Battle System - CTB VisuStella MZ|Charge Turn Battle]] ===

[[File:VisuMZ.031.jpg|300px|link=Battle System - CTB VisuStella MZ]]

This plugin creates a Charge Turn Battle (CTB) system using RPG Maker MZ's TPB as a base. CTB functions by calculating the speed of every battler and balancing them relative to one another. When it's a battler's turn, the battler will either choose an action to perform immediately or charge it for later depending if the skill requires charging.

This is a battle system where agility plays an important factor in the progress of battle where higher agility values give battlers more advantage and additional turns over lower agility values, which give battlers less advantage and less turns.

A turn order display will appear to compensate for the removal of gauges. The turn order display will show a preview of what the turn order could possibly be like. This turn order display is variable and can be changed due to player and enemy influence by using different action speeds, effects provided by this plugin that alter the turn order, and more!

---

'''Action Economy:''' Battle participants typically only have one action each time they have a turn to perform an action. This is balanced for the most part. However, due to the nature of turn advantage in a tick-based battle system, anyone who can perform multiple actions per turn will usually and drastically outperform any other battle participant.

'''Turn Advantage:''' Turns are determined by each participant's AGI. The more AGI a battler has, the more often their turn comes up. There is no limit to how many turns a battler can acquire in a set amount of time. Battlers with high enough AGI can overlap battlers with less AGI.

'''Balancing:''' Balancing a tick-based battle system is extremely tricky. Most games that utilize them keep AGI levels around a similar range without letting them grow too much over time and without letting them vary by too much either. Status effects like Haste and Slow are far more potent than status effects that raise damage dealt or reduce damage taken. This is to avoid giving any battler too much Turn Advantage.

---

'''Speed Manipulation:''' Speed manipulation allows the "Speed" stat of an action to influence the turn frequency/delay of future turns. This can be used strategically by the player to get in an extra action before an enemy can in the following turns.

'''Turn Order Manipulation:''' Battlers can delay enemy turns and hasten ally turns through direct manipulation instead of through AGI. This opens up lots of potential strategies that can be utilized to bring the tides of battle into one's favor.

<hr>

=== Default Turn Battle ===

[[File:RMMZ_DTB.png|300px]]

This is the default battle system found in RPG Maker MZ. It's also the default battle system for RPG Maker 2000, XP, VX, VX Ace, and MV. Players will input their actions for each party member that can act, then the turn starts, playing out the action order based on the speed of the individual actors and enemies.

---

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

---

A very vanilla and basic battle system.

<hr>

=== [[Battle System - ETB VisuStella MZ|Energy Turn Battle]] ===

[[File:VisuMZ.080.jpg|300px|link=Battle System - ETB VisuStella MZ]]

Energy Turn Battle (ETB) is a type of battle system made for RPG Maker MZ, where the teams for actors and enemies take turns attacking one another as a whole. Energy is accumulated as turns pass on, allowing each team to perform more actions each turn. Each team can freely perform actions among their teammates as wanted. When the energy count is depleted or if one team ran out of battler's that can act, the other team begins their turn and so forth.

Similar to how [https://playhearthstone.com/ Hearthstone] plays, energy count starts at 1, then climbs up by 1 each turn up to a maximum of 10. This lets battle progression scale linearly from slow paced to fast paced. This energy scaling can be altered through the Plugin Parameters.

---

'''Action Economy:''' Depending on the battle system, units usually have one or two actions to perform at a time, or as many as the team allows before the team's turn is considered over.

'''Turn Advantage:''' Instead of turn advantage going to participants with more frequent turns or participants with faster speed, turn advantage, instead, goes to the team that goes first. In most cases, the team that goes first is almost always leading the battle system, though counterbalancing the advantage for the team going second is a common practice to be seen, too.

'''Balancing:''' Balancing for this type of battle flow can be tricky. It can be easier or harder than either tick-based or turn-based depending on how the battle is designed. Strategies also shift from having the key participant perform more frequently to making the most optimal team play for each turn as the norm.

---

'''Action Count System:''' The Action Count System makes it possible for either party or troop to perform actions with various team members any way they want. If a team wants one member to act multiple times, then as long as the action counts permit it, they can. Also with this, some actions can consume multiple action costs if they happen to be stronger.

'''Free Switching:''' The player can (optionally) pick who they want to perform an action in battle as long as all other conditions are met (alive, enough action counts, not stunned, etc). This gives players more freedom and range for potential strategies. If a player wants the Warrior to act 4 times, that's possible. If the player wants each party member to act once each, that's also possible.

<hr>

=== [[Battle System - FTB VisuStella MZ|Free Turn Battle]] ===

[[File:VisuMZ.057.jpg|300px|link=Battle System - FTB VisuStella MZ]]

Free Turn Battle (FTB) is a type of battle system made for RPG Maker MZ, where the teams for actors and enemies take turns attacking one another as a whole. During each team's turns, an action count is given to them and they can freely perform actions among their teammates as wanted (or if turned off by the Plugin Parameters, in a cycle). When the action count is depleted or if one team ran out of battler's that can act, the other team begins their turn and so forth.

Unlike ETB, there are set amounts of actions each turn available based on the number of members for each group (party and troop). Usually, the more party members, the more actions. AGI buffs can also affect this. The action count can be modified via the Plugin Parameters.

---

'''Action Economy:''' Depending on the battle system, units usually have one or two actions to perform at a time, or as many as the team allows before the team's turn is considered over.

'''Turn Advantage:''' Instead of turn advantage going to participants with more frequent turns or participants with faster speed, turn advantage, instead, goes to the team that goes first. In most cases, the team that goes first is almost always leading the battle system, though counterbalancing the advantage for the team going second is a common practice to be seen, too.

'''Balancing:''' Balancing for this type of battle flow can be tricky. It can be easier or harder than either tick-based or turn-based depending on how the battle is designed. Strategies also shift from having the key participant perform more frequently to making the most optimal team play for each turn as the norm.

---

'''Action Count System:''' The Action Count System makes it possible for either party or troop to perform actions with various team members any way they want. If a team wants one member to act multiple times, then as long as the action counts permit it, they can. Also with this, some actions can consume multiple action costs if they happen to be stronger.

'''Free Switching:''' The player can (optionally) pick who they want to perform an action in battle as long as all other conditions are met (alive, enough action counts, not stunned, etc). This gives players more freedom and range for potential strategies. If a player wants the Warrior to act 4 times, that's possible. If the player wants each party member to act once each, that's also possible.

<hr>

=== [[Battle System - OTB VisuStella MZ|Order Turn Battle]] ===

[[File:VisuMZ.066.jpg|300px|link=Battle System - OTB VisuStella MZ]]

This plugin changes the RPG Maker MZ battle system to "Order Turn Battle", a turn-based battle system where actions are executed immediately and the orders for both the current and next turn are not only visible, but also malleable. New mechanics are introduced where the player can manipulate the turn order of an action's user or action's target in various ways they want.

The two Turn Orders are displayed at the top of the top of the screen to give the player a clear understanding of who's turn it will be when it becomes time to act, making it easier and viable for the player to formulate strategies and adapt to the situation in battle.

---

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

---

'''Instant Action:''' Instant actions allow the battler to perform a skill without consuming the current action. This is great for things like small spells that would otherwise never be a good pick in a highly competitive action economy. Examples would be stance changes, state toggles, and miniature self buffs.

'''Speed Manipulation:''' Speed manipulation allows the "Speed" stat of an action to influence the turn frequency/delay of future turns. This can be used strategically by the player to get in an extra action before an enemy can in the following turns.

'''Turn Order Manipulation:''' Battlers can delay enemy turns and hasten ally turns through direct manipulation instead of through AGI. This opens up lots of potential strategies that can be utilized to bring the tides of battle into one's favor.

<hr>

=== [[Battle System - PTB VisuStella MZ|Press Turn Battle]] ===

[[File:VisuMZ.086.jpg|300px|link=Battle System - PTB VisuStella MZ]]

Press Turn Battle (PTB) is a team-based battle system made for RPG Maker MZ where the teams for actors and enemies take turns attacking one another as a whole, consuming press actions in the process. When press actions have been emptied, the turn switches over to the opposite team and it repeats. Depending on the results of actions, Press Actions may consume a full action or be converted into a half action, allowing for more actions per turn. This is a battle system that rewards skillful play and punishes bad strategies.

Unlike ETB and FTB, more actions can be acquired based on better gameplay. Instead of favoring battle longevity or party member counts, this battle system focuses on player skill.

---

'''Action Economy:''' Depending on the battle system, units usually have one or two actions to perform at a time, or as many as the team allows before the team's turn is considered over.

'''Turn Advantage:''' Instead of turn advantage going to participants with more frequent turns or participants with faster speed, turn advantage, instead, goes to the team that goes first. In most cases, the team that goes first is almost always leading the battle system, though counterbalancing the advantage for the team going second is a common practice to be seen, too.

'''Balancing:''' Balancing for this type of battle flow can be tricky. It can be easier or harder than either tick-based or turn-based depending on how the battle is designed. Strategies also shift from having the key participant perform more frequently to making the most optimal team play for each turn as the norm.

---

'''Action Count System:''' The Action Count System makes it possible for either party or troop to perform actions with various team members any way they want. If a team wants one member to act multiple times, then as long as the action counts permit it, they can. Also with this, some actions can consume multiple action costs if they happen to be stronger.

'''Exploit System:''' The exploit system (optionally) grants teams extra advantages when hitting an opponent's weakness or landing a critical hit. These extra advantages often come in the form of extra turns or actions. This rewards good gameplay and makes lucky hits have even more impact.

<hr>

=== [[Battle System - STB VisuStella MZ|Standard Turn Battle]] ===

[[File:VisuMZ.039.jpg|300px|link=Battle System - STB VisuStella MZ]]

The Standard Turn Battle (STB) system uses RPG Maker MZ's default non-TPB battle system as a base. Action orders are determined by the battler's AGI values and they go from highest to lowest. However, actions are not selected at the start of the turn. Instead, as the turn progresses, actions are then picked as each battler's turn comes up and is executed immediately.

Optional to the battle system but fine tuned to it is the Exploit System. When landing an elemental weakness or critical hit against a foe, the battler can gain bonuses as well as an extra turn while the foe will become stunned or gain any desired state(s). When all enemies are exploited in a single turn, a common event can also be played, too.

A Turn Order Display will also appear on the screen to show the order the battlers will take their turns in. This lets the player plan in advance on how to go about the rest of the turn.

---

'''Action Economy:''' Battle participants usually have one action they can perform each turn. However, in the scenarios where they can perform multiple actions a turn, the advantages given here are not as skewed as they would be in a tick-based battle system since every battle participant is guaranteed a turn within a set time frame (as long as they're able to act). Some games, like the SMT series, even allow performing multiple actions a turn without disrupting the balance and battle flow too much.

'''Turn Advantage:''' Turns are granted to each battle participant evenly. Instead of AGI determining how frequent the battlers acquire turns, AGI instead determines how fast the battlers go in a given turn set. The faster the AGI, the earlier the battler can perform for that round. Battlers cannot overlap each other for turn advantage through AGI. A battler with 999 AGI will not have more turns than a battler with 20 AGI during a single battle round.

'''Balancing:''' Balancing a turn-based battle system is far easier than balancing one for a tick-based battle system. AGI values can vary drastically without giving one participant too much turn advantage. Characters with high action economies are also easier to manage for this reason, too.

---

'''Instant Action:''' Instant actions allow the battler to perform a skill without consuming the current action. This is great for things like small spells that would otherwise never be a good pick in a highly competitive action economy. Examples would be stance changes, state toggles, and miniature self buffs.

'''Exploit System:''' The exploit system (optionally) grants teams extra advantages when hitting an opponent's weakness or landing a critical hit. These extra advantages often come in the form of extra turns or actions. This rewards good gameplay and makes lucky hits have even more impact.

<hr>

=== Time Progress Battle ===

[[File:RMMZ_TPB.png|300px]]

This is a new battle system found in RPG Maker MZ. It wasn't present for the past iterations of RPG Maker.

---

'''Action Economy:''' Battle participants typically only have one action each time they have a turn to perform an action. This is balanced for the most part. However, due to the nature of turn advantage in a tick-based battle system, anyone who can perform multiple actions per turn will usually and drastically outperform any other battle participant.

'''Turn Advantage:''' Turns are determined by each participant's AGI. The more AGI a battler has, the more often their turn comes up. There is no limit to how many turns a battler can acquire in a set amount of time. Battlers with high enough AGI can overlap battlers with less AGI.

'''Balancing:''' Balancing a tick-based battle system is extremely tricky. Most games that utilize them keep AGI levels around a similar range without letting them grow too much over time and without letting them vary by too much either. Status effects like Haste and Slow are far more potent than status effects that raise damage dealt or reduce damage taken. This is to avoid giving any battler too much Turn Advantage.

---

There's really not much else going for it other than breaking free of the turn-based structure of the DTB. Waiting times inbetween actions are dead and don't contribute much else.

== Why Battle Systems Can't Have Everything ==

[[File:ThanosEverything.jpg|600px]]

"Why can't you put x mechanic into y battle system?"

"Why can't you make everything mechanical available for all battle systems?"

These are common questions we receive as a team. We can understand how desirable certain mechanics are as they tend to make those battle systems unique. However, not all of them are possible to transplant over into different battle systems without lots of design issues and complications.

For example, the '''Action Count System''' would make very little sense in a battle system like [[Battle System - BTB VisuStella MZ|BTB]], where you can freely queue up actions already. Which ones take priority? Which ones shouldn't? Speed and Turn Order manipulation also doesn't really work well with team-based battle systems like [[Battle System - FTB VisuStella MZ|FTB]] and [[Battle System - PTB VisuStella MZ|PTB]]. '''Free Switching''' would also render turn orders meaningless for battle systems like [[Battle System - OTB VisuStella MZ|OTB]] and [[Battle System - STB VisuStella MZ|STB]].

Now, these examples are pretty obvious as no no's, but what about the others? Let's get into some specific cases that seem a bit more ''global'' but really aren't.

---

'''Brave System''' straight up borrows actions from future turns for the current turn. This feature could work in certain battle systems, but not mesh with it quite as well as the turn-based action queue structure. And the reason for this is due to the immediate action flow being broken up. The mechanic feels really out of place in comparison to everything else.

As an alternative to it that's more global, use the [[Boost Action VisuStella MZ|Boost Action]] to perform similar effects. Boost points do not take away future turns, but instead, they have to be slowly accumulated across battle, which invites a more steady flow and pacing.

---

'''Exploit Systems''' are very situational and fit only a select handful of battle systems based on their turn/action logistics. Getting an extra turn is a huge deal to some of these battle systems and in the sense of [[Battle System - ATB VisuStella MZ|ATB]] and [[Battle System - CTB VisuStella MZ|CTB]], when combined with AGI advantages, can result in balance breaking to the extremes.

It's why mechanics like these aren't made global, but instead, we offer a more mild version called [[Break Shields VisuStella MZ|Break Shields]] to allow for stuns instead, a softer version of turn advantage. A softer turn advantage through stuns is far less likely to break the mechanical balance of a game.

---

'''Instant Action''' is something you've seen in the [[Yanfly Engine Plugins]] library as a near global mechanic. However, this couldn't be further from the truth. For DTB, it broke the battle system in so many ways due to how actions were never meant to be used during the input phase. For its place in ATB and CTB, all it really did was just replace an after use speed of 0. For STB, it pushed forth an additional action. It was a completely different effect each and every battle system that it was used with. This means that the effect wasn't global, but instead, have to be custom tailored to each battle system. There's many of you that would like to see it return for DTB, but honestly? With how it completely breaks the mold and ruins the input phase, I'd rather it not.

Each battle system we've made for VisuStella MZ's plugin library has a way to create a free use condition without impeding on the action economy, which is more or less the primary reason why people used '''Instant Actions''' in the first place without having to be an "Instant" effect in and of itself. For those, reference the battle systems themselves. They're usually a notetag effect.

---

== To Sum It Up ==

[[File:SumsItUp.gif]]

There's a lot of nuances for each type battle system that makes them different from one another. These range from the types of data displayed to the mechanics they're able to access. By taking some time to read over each of them and learning their in's and out's, we hope that you can decide which battle system is the best fit for the type of game you'd like to make.

== End of Article ==

|}

<html><script type="text/javascript" src="https://www.free-counters.org/count/dag9"></script><br>
<a href='https://www.free-counters.org/'>... by Free-Counters.org</a> <script type='text/javascript' src='https://whomania.com/ctr?id=defd96e02d0659d336c51db9f09c77d6f7089973'></script></html>

Template:VisuMZ Battle Core Notetags

2024-11-10T11:53:28Z

Yanfly: /* JavaScript Notetag: Targeting-Related */

<noinclude>[[Category:Display templates|VisuMZ Battle Core Notetags]]</noinclude>

The following are notetags that have been added through this plugin. These
notetags will not work with your game if this plugin is OFF or not present.

=== HP Gauge-Related Notetags ===

[[File:BattleCoreHpGauge.png|400px]]

The following notetags allow you to set whether or not HP Gauges can be
displayed by enemies regardless of Plugin Parameter settings.

---

<pre>
<Show HP Gauge>

- Used for: Enemy Notetags
- Will always show the HP Gauge for the enemy regardless of the defeat
requirement setting.
- This does not bypass the player's Options preferences.
- This does not bypass disabling enemy HP Gauges as a whole.
</pre>

---

<pre>
<Hide HP Gauge>

- Used for: Enemy Notetags
- Will always hide the HP Gauge for the enemy regardless of the defeat
requirement setting.
- This does not bypass the player's Options preferences.
</pre>

---

<pre>
<Battle UI Offset: +x, +y>
<Battle UI Offset: -x, -y>

<Battle UI Offset X: +x>
<Battle UI Offset X: -x>

<Battle UI Offset Y: +y>
<Battle UI Offset Y: -y>

- Used for: Actor and Enemy Notetags
- Adjusts the offset of HP Gauges and State Icons above the heads of actors
and enemies.
- Replace 'x' with a number value that offsets the x coordinate.
- Negative x values offset left. Positive x values offset right.
- Replace 'y' with a number value that offsets the y coordinate.
- Negative y values offset up. Positive x values offset down.
</pre>

---

=== Animation-Related Notetags ===

[[File:BattleCoreCastAni.gif]]

The following notetags allow you to set animations to play at certain
instances and/or conditions.

---

<pre>
<Slip Animation: x>

- Requires VisuMZ_0_CoreEngine!
- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- During the phase at which the user regenerates HP, MP, or TP, this
animation will play as long as the user is alive and visible.
- Replace 'x' with a number value representing the Animation ID to play.
</pre>

---

<pre>
<Cast Animation: x>

- Used for: Skill Notetags
- Plays a battle animation at the start of the skill.
- Replace 'x' with a number value representing the Animation ID to play.
</pre>

---

<pre>
<Attack Animation: x>

- Used for: Enemy Notetags
- Gives an enemy an attack animation to play for its basic attack.
- Replace 'x' with a number value representing the Animation ID to play.
</pre>

---

=== Battleback-Related Notetags ===

[[File:BattleCoreBattleBack.png|400px]]

You can apply these notetags to have some control over the battlebacks that
appear in different regions of the map for random or touch encounters.

---

<pre>
<Region x Battleback1: filename>
<Region x Battleback2: filename>

- Used for: Map Notetags
- If the player starts a battle while standing on 'x' region, then the
'filename' battleback will be used.
- Replace 'x' with a number representing the region ID you wish to use.
- Replace 'filename' with the filename of the graphic to use. Do not insert
any extensions. This means the file 'Castle1.png' will be only inserted
as 'Castle1' without the '.png' at the end.
- *NOTE: This will override any specified battleback settings.
</pre>

---

=== Battle Command-Related Notetags ===

[[File:BattleCoreBattleCommands.png]]

You can use notetags to change how the battle commands of playable
characters appear in battle as well as whether or not they can be used.

---

<pre>
<Seal Attack>
<Seal Guard>
<Seal Item>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Prevents specific battle commands from being able to be used.
</pre>

---

<pre>
<Battle Commands>
Attack
Skills
SType: x
SType: name
All Skills
Skill: x
Skill: name
Guard
Item
Party
Escape
Auto Battle
Combat Log
Talk
Weapon Swap
</Battle Commands>

- Used for: Class Notetags
- Changes which commands appear in the Actor Command Window in battle.
If this notetag is not used, then the default commands determined in
Plugin Parameters => Actor Command Window => Command List will be used.
- Add/remove/modify entries as needed.

- Attack
- Adds the basic attack command.

- Skills
- Displays all the skill types available to the actor.

- SType: x
- Stype: name
- Adds in a specific skill type.
- Replace 'x' with the ID of the skill type.
- Replace 'name' with the name of the skill type (without text codes).

- All Skills
- Adds all usable battle skills as individual actions.

- Skill: x
- Skill: name
- Adds in a specific skill as a usable action.
- Replace 'x' with the ID of the skill.
- Replace 'name' with the name of the skill.

- Guard
- Adds the basic guard command.

- Item
- Adds the basic item command.

- Party
- Requires VisuMZ_2_PartySystem.
- Allows this actor to switch out with a different party member.

- Escape
- Adds the escape command.

- Auto Battle
- Adds the auto battle command.

- Combat Log
- Requires VisuMZ_4_CombatLog.
- Opens up the combat log.

- Talk
- Requires VisuMZ_3_BattleCmdTalk!
- Shows talk command if applicable.

- Weapon Swap
- Requires VisuMZ_2_WeaponSwapSystem.
- Swaps the current weapon.

Example:

<Battle Commands>
Attack
Skill: Heal
Skills
Guard
Item
Escape
</Battle Commands>
</pre>

---

<pre>
<Command Text: x>

- Used for: Skill Notetags
- When a skill is used in a <Battle Commands> notetag set, you can change
the skill name text that appears to something else.
- Replace 'x' with the skill's name you want to shown in the Actor Battle
Command window.
- Recommended Usage: Shorten skill names that are otherwise too big to fit
inside of the Actor Battle Command window.
</pre>

---

<pre>
<Command Icon: x>

- Used for: Skill Notetags
- When a skill is used in a <Battle Commands> notetag set, you can change
the skill icon that appears to something else.
- Replace 'x' with the ID of icon you want shown in the Actor Battle Command
window to represent the skill.
</pre>

---

<pre>
<Command Require Learn>

- Used for: Skill Notetags
- Determines if a battle command is visible or not by whether the actor has
learned the skill.
- Learning the skill is a requirement. Acquiring the skill through traits
does not count as learning the skill.
</pre>

---

<pre>
<Command Require Access>

- Used for: Skill Notetags
- Determines if a battle command is visible or not by whether the actor has
access to the skill.
- Having access to the skill can come through either learning the skill or
temporarily acquiring it through trait objects.
</pre>

---

<pre>
<Command Show Switch: x>

<Command Show All Switches: x,x,x>
<Command Show Any Switches: x,x,x>

- Used for: Skill Notetags
- Determines if a battle command is visible or not through switches.
- Replace 'x' with the switch ID to determine the skill's visibility.
- If 'All' notetag variant is used, item will be hidden until all
switches are ON. Then, it would be shown.
- If 'Any' notetag variant is used, item will be shown if any of the
switches are ON. Otherwise, it would be hidden.
- This can be applied to Attack and Guard commands, too.
</pre>

---

<pre>
<Command Hide Switch: x>

<Command Hide All Switches: x,x,x>
<Command Hide Any Switches: x,x,x>

- Used for: Skill Notetags
- Determines if a battle command is visible or not through switches.
- Replace 'x' with the switch ID to determine the skill's visibility.
- If 'All' notetag variant is used, item will be shown until all
switches are ON. Then, it would be hidden.
- If 'Any' notetag variant is used, item will be hidden if any of the
switches are ON. Otherwise, it would be shown.
- This can be applied to Attack and Guard commands, too.
</pre>

---

<pre>
<Battle Portrait: filename>

- Used for: Actor
- This is used with the "Portrait" Battle Layout.
- Sets the battle portrait image for the actor to 'filename'.
- Replace 'filename' with a picture found within your game project's
img/pictures/ folder. Filenames are case sensitive. Leave out the filename
extension from the notetag.
- This will override any menu images used for battle only.
</pre>

---

<pre>
<Battle Portrait Offset: +x, +y>
<Battle Portrait Offset: -x, -y>

<Battle Portrait Offset X: +x>
<Battle Portrait Offset X: -x>

<Battle Portrait Offset Y: +y>
<Battle Portrait Offset Y: -y>

- Used for: Actor
- This is used with the "Portrait" and "Border" Battle Layouts.
- Offsets the X and Y coordinates for the battle portrait.
- Replace 'x' with a number value that offsets the x coordinate.
- Negative x values offset left. Positive x values offset right.
- Replace 'y' with a number value that offsets the y coordinate.
- Negative y values offset up. Positive x values offset down.
</pre>

---

<pre>
<Help Description>
text
text
</Help Description>

- Used for: State Notetags
- Assigns a help description for the state that's displayed under the
"Status" actor command.
- Replace 'text' with text you want displayed for the help window.
- This best works with one line for compatibility with other plugins.
- Insert %1 into the help description to show any data that would otherwise
be shown as the state display, such as Absorption Barrier count.
- This is used as a common notetag between Battle Core's state descriptions
and State Tooltips' state descriptions.
</pre>

---

<pre>
<In-Battle Status Description>
text
text
</In-Battle Status Description>
- Assigns a help description for the state that's displayed under the
"Status" actor command.
- Replace 'text' with text you want displayed for the help window.
- This best works with one line for compatibility with other plugins.
- Insert %1 into the help description to show any data that would otherwise
be shown as the state display, such as Absorption Barrier count.
- The description used here will not be used for State Tooltips.
- If both <Help Description> and <In-Battle Status Description> notetags
exist in the same state, priority will be given to this one for the
In-Battle Status Window.
</pre>

---

<pre>
<Exclude From Status Listing>

- Used for: State Notetags
- Excludes the state from being displayed in the status listing.
</pre>

---

=== JavaScript Notetag: Battle Command-Related ===

The following are notetags made for users with JavaScript knowledge to
determine if skill-based battle commands are visible or hidden.

---

<pre>
<JS Command Visible>
code
code
visible = code;
</JS Command Visible>

- Used for: Skill Notetags
- The 'visible' variable is the final returned variable to determine the
skill's visibility in the Battle Command Window.
- Replace 'code' with JavaScript code to determine the skill's visibility in
the Battle Command Window.
- The 'user' variable represents the user who will perform the skill.
- The 'skill' variable represents the skill to be used.
</pre>

---

=== Targeting-Related Notetags ===

The following notetags are related to the targeting aspect of skills and
items and may adjust the scope of how certain skills/items work.

---

<pre>
<Always Hit>

<Always Hit Rate: x%>

- Used for: Skill, Item Notetags
- Causes the action to always hit or to always have a hit rate of exactly
the marked x%.
- Replace 'x' with a number value representing the hit success percentage.
</pre>

---

<pre>
<Repeat Hits: x>

- Used for: Skill, Item Notetags
- Changes the number of hits the action will produce.
- Replace 'x' with a number value representing the number of hits to incur.
</pre>

---

<pre>
<Target: x Random Any>

- Used for: Skill, Item Notetags
- Makes the skill pick 'x' random targets when used.
- Targets can be both actors and enemies.
- This will overwrite the existing database scope and ignore the database's
existing scope in favor of this.
- Replace 'x' with a number value representing the number of random targets.
</pre>

---

<pre>
<Target: x Random Enemies>

- Used for: Skill, Item Notetags
- Makes the skill pick 'x' random targets when used.
- Targets are only enemies.
- This will overwrite the existing database scope and ignore the database's
existing scope in favor of this.
- Replace 'x' with a number value representing the number of random targets.
</pre>

---

<pre>
<Target: x Random Allies>

- Used for: Skill, Item Notetags
- Makes the skill pick 'x' random targets when used.
- Targets are only actors.
- This will overwrite the existing database scope and ignore the database's
existing scope in favor of this.
- Replace 'x' with a number value representing the number of random targets.
</pre>

---

<pre>
<Target: All Allies But User>

- Used for: Skill, Item Notetags
- This will overwrite the existing database scope and ignore the database's
existing scope in favor of this.
- Targets all allies with the exception of the user.
</pre>

---

<pre>
<Target: Ally or Enemy>

- Used for: Skill, Item Notetags
- Allows the player to target allies or enemies with the skill/item.
- Keep in mind this does NOT allow you to select dead party members.
- This will overwrite the existing database scope and ignore the database's
existing scope in favor of this.
- Target selection emphasis will go to allies first.
- Ignored when used by enemies and will be treated as an ally scope.
- Auto-battle actors will also treat this action as an ally scope.
- For certain battle layouts in frontview, this will open the Actor Select
window in order for Touch Input to be able to select actors.
</pre>

---

<pre>
<Target: Enemy or Ally>

- Used for: Skill, Item Notetags
- Allows the player to target enemies or allies with the skill/item.
- Keep in mind this does NOT allow you to select dead party members.
- This will overwrite the existing database scope and ignore the database's
existing scope in favor of this.
- Target selection emphasis will go to enemies first.
- Ignored when used by enemies and will be treated as an enemy scope.
- Auto-battle actors will also treat this action as an enemy scope.
- For certain battle layouts in frontview, this will open the Actor Select
window in order for Touch Input to be able to select actors.
</pre>

---

<pre>
<Single or Multiple Select>

- Used for: Skill, Item Notetags
- Requires an original scope that can select individual targets.
- This will allow the skill/item to be able to select either single targets
or multiple targets at once.
- In order to select "all enemies", the player must press the "Page Up"
keyboard button or the visual on screen "All Enemies" button.
- In order to select "all allies", the player must press the "Page Down"
keyboard button or the visual on screen "All Allies" button.
- Those wondering why this isn't regulated to a command left or right of
the enemies and actors is because mouse controls and touch controls
would not be able to select all enemies or all allies that way.
- This can NOT be used with single dead ally scopes.
- If there is an enemy with Taunt or Provoke, the option to select
"All Enemies" does not become possible.
- The enemy AI and Auto-Battle actor AI will NOT make use of the ability to
toggle between single and multiple target scopes. They will only use the
single target versions of these skills.
</pre>

---

<pre>
<Disperse Damage>

- Used for: Skill, Item Notetags
- This will cause any damage dealt by this skill to be split equally amongst
all targets of the skill including repeats.
- For basic attacks, any damage reduction added attack trait totals will
by reverted.
- This does NOT have to be used with <Single or Multiple Select> notetag and
can be used by itself for an "All" scope, making the skill/item deal less
damage if there's more enemies and more damage if there's less enemies.
</pre>

---

<pre>
<Cannot Target User>

- Used for: Skill, Item Notetags
- This will cause the action to be unable to select the user as the target.
- This is not a targeting scope. Instead, it is used in addition to any
other targeting scopes out there.
- When used with "All" scopes, the user is removed from the target pool.
- This is also applied outside of battle.
- If the user somehow enters the target pool, the user is then replaced by
a random ally found in the party.
</pre>

---

=== JavaScript Notetag: Targeting-Related ===

---

<pre>
<JS Accuracy>
code
code
rate = code;
</JS Accuracy>

- Used for: Skill, Item Notetags
- Only applies during battle.
- The 'rate' variable is the final returned amount to determine the
accuracy hit success rate.
- Base value comes from Game_Action.itemHit
- Skill/Item <JS Accuracy> runs
- Then <JS Accuracy as User/Target> notetags run
- Replace 'code' with JavaScript code to determine the final 'rate' to be
returned as the accuracy hit success rate.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
- Works best with VisuMZ Core Engine's "Improved Accuracy" QoL formula in
order to consolidate both HIT and EVA.
</pre>

---

<pre>
<JS Accuracy as User>
code
code
rate = code;
</JS Accuracy as User>

<JS Accuracy as Target>
code
code
rate = code;
</JS Accuracy as Target>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Only applies during battle.
- The 'rate' variable is the final returned amount to determine the
accuracy hit success rate.
- Base value comes from Game_Action.itemHit
- Skill/Item <JS Accuracy> runs
- Then <JS Accuracy as User/Target> notetags run
- If used on trait objects, this will apply to any skills/items used as long
as the unit affected by the trait object has access to the trait object.
- If the 'as User' notetag variant is used, this code will be run as a
response to the action from the action user end.
- If the 'as Target' notetag variant is used, this code will be run as a
response to the action from the action target end.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Targets>
code
code
targets = [code];
</JS Targets>

- Used for: Skill, Item Notetags
- The 'targets' variable is an array that is returned to be used as a
container for all the valid action targets.
- This is NOT used for filtering out who the player can or cannot select.
- This determines a final result.
- The 'targets' variable will include the original set of targets determined
by the skill/item's original scale.
- Replace 'code' with JavaScript code to determine valid targets.
</pre>

---

=== Damage-Related Notetags ===

[[File:BattleCoreDmgStyles.png|400px]]

---

<pre>
<Damage Style: name>

- Used for: Skill, Item Notetags
- Replace 'name' with a Damage Style name to change the way calculations are
made using the damage formula input box.
- Names can be found in Plugin Parameters => Damage Settings => Style List
</pre>

---

<pre>
<Armor Reduction: x>
<Armor Reduction: x%>
- Used for: Actor, Class, Skill, Item, Weapon, Armor, Enemy, State Notetags
- If used on skills and/or items, sets the current skill/item's armor
reduction properties to 'x' and/or 'x%'.
- If used on trait objects, adds 'x' and/or 'x%' armor reduction properties
when calculating one's own armor.
- Use the 'x' notetag variant to determine a flat reduction value.
- Use the 'x%' notetag variant to determine a percentile reduction value.
</pre>

---

<pre>
<Armor Penetration: x>
<Armor Penetration: x%>
- Used for: Actor, Class, Skill, Item, Weapon, Armor, Enemy, State Notetags
- If used on skills and/or items, sets the current skill/item's armor
penetration properties to 'x' and/or 'x%'.
- If used on trait objects, adds 'x' and/or 'x%' armor penetration
properties when calculating a target's armor.
- Use the 'x' notetag variant to determine a flat penetration value.
- Use the 'x%' notetag variant to determine a percentile penetration value.
</pre>

---

<pre>
<Magic Reduction: x>
<Magic Reduction: x%>
- Used for: Actor, Class, Skill, Item, Weapon, Armor, Enemy, State Notetags
- If used on skills and/or items, sets the current skill/item's armor
reduction properties to 'x' and/or 'x%'.
- If used on trait objects, adds 'x' and/or 'x%' armor reduction properties
when calculating one's own armor.
- This applies to magical attacks.
- Use the 'x' notetag variant to determine a flat reduction value.
- Use the 'x%' notetag variant to determine a percentile reduction value.
</pre>

---

<pre>
<Magic Penetration: x>
<Magic Penetration: x%>
- Used for: Actor, Class, Skill, Item, Weapon, Armor, Enemy, State Notetags
- If used on skills and/or items, sets the current skill/item's armor
penetration properties to 'x' and/or 'x%'.
- If used on trait objects, adds 'x' and/or 'x%' armor penetration
properties when calculating a target's armor.
- This applies to magical attacks.
- Use the 'x' notetag variant to determine a flat penetration value.
- Use the 'x%' notetag variant to determine a percentile penetration value.
</pre>

---

<pre>
<Bypass Damage Cap>

- Used for: Actor, Class, Skill, Item, Weapon, Armor, Enemy, State Notetags
- If used on skills and/or items, this will cause the action to never have
its damage capped.
- If used on trait objects, this will cause the affected unit to never have
its damage capped.
</pre>

---

<pre>
<Damage Cap: x>

- Used for: Actor, Class, Skill, Item, Weapon, Armor, Enemy, State Notetags
- If used on skills and/or items, this will declare the hard damage cap to
be the 'x' value.
- If used on trait objects, this will raise the affect unit's hard damage
cap to 'x' value. If another trait object has a higher value, use that
value instead.
</pre>

---

<pre>
<Bypass Soft Damage Cap>

- Used for: Actor, Class, Skill, Item, Weapon, Armor, Enemy, State Notetags
- If used on skills and/or items, this will cause the action to never have
its damage scaled downward to the soft cap.
- If used on trait objects, this will cause the affected unit to never have
its damage scaled downward to the soft cap.
</pre>

---

<pre>
<Soft Damage Cap: +x%>
<Soft Damage Cap: -x%>

- Used for: Actor, Class, Skill, Item, Weapon, Armor, Enemy, State Notetags
- If used on skills and/or items, this will increase/decrease the action's
soft cap by x% where 'x' is a percentage value representing the increment
changed by the hard cap value.
- If used on trait objects, this will raise the affect unit's soft damage
limit by x% where 'x' is a percentage value representing the increment
changed by the hard cap value.
</pre>

---

<pre>
<Unblockable>

- Used for: Skill, Item Notetags
- Using "Guard" against this skill will not reduce any damage.
</pre>

---

<pre>
<Popup Position: Head>
<Popup Position: Center>
<Popup Position: Base>

- Used for: Enemy Notetags
- Determines the popup starting position for this enemy.
- Head makes the popups start at the top of the ennemy.
- Center makes the popups start at the center of the ennemy.
- Base makes the popups start at the bottom of the ennemy.
- If this notetag is not used, refer to the default Plugin Parameter setting
found in Damage Settings.
</pre>

---

<pre>
<Popup Offset X: +x>
<Popup Offset X: -x>
<Popup Offset Y: +y>
<Popup Offset Y: -y>

- Used for: Enemy Notetags
- Alters the popup x/y position offset for this enemy.
- Replace 'x' with a number representing the horizontal position x offset.
- Negative: left. Positive: right.
- Replace 'y' with a number representing the vertical position y offset.
- Negative: up. Positive: down.
- If these notetags are not used, refer to the default Plugin Parameter
settings found in Damage Settings.
</pre>

---

=== Critical-Related Notetags ===

The following notetags affect skill and item critical hit rates and the
critical damage multiplier.

---

<pre>
<Always Critical>

- Used for: Skill, Item Notetags
- This skill/item will always land a critical hit regardless of the
user's CRI parameter value.
</pre>

---

<pre>
<Set Critical Rate: x%>

- Used for: Skill, Item Notetags
- This skill/item will always have a x% change to land a critical hit
regardless of user's CRI parameter value.
- Replace 'x' with a percerntage value representing the success rate.
</pre>

---

<pre>
<Modify Critical Rate: x%>
<Modify Critical Rate: +x%>
<Modify Critical Rate: -x%>

- Used for: Skill, Item Notetags
- Modifies the user's CRI parameter calculation for this skill/item.
- The 'x%' notetag variant will multiply the user's CRI parameter value
for this skill/item.
- The '+x%' and '-x%' notetag variants will incremenetally increase/decrease
the user's CRI parameter value for this skill/item.
</pre>

---

<pre>
<Modify Critical Multiplier: x%>
<Modify Critical Multiplier: +x%>
<Modify Critical Multiplier: -x%>

- Used for: Skill, Item Notetags
- These notetags determine the damage multiplier when a critical hit lands.
- The 'x%' notetag variant multiply the multiplier to that exact percentage.
- The '+x%' and '-x%' notetag variants will change the multiplier with an
incremenetal rate for this skill/item.
</pre>

---

<pre>
<Modify Critical Bonus Damage: x%>
<Modify Critical Bonus Damage: +x%>
<Modify Critical Bonus Damage: -x%>

- Used for: Skill, Item Notetags
- These notetags determine the bonus damage added when a critical hit lands.
- The 'x%' notetag variant multiply the damage to that exact percentage.
- The '+x%' and '-x%' notetag variants will change the bonus damage with an
incremenetal rate for this skill/item.
</pre>

---

=== JavaScript Notetags: Critical-Related ===

The following are notetags made for users with JavaScript knowledge to
determine how critical hit-related aspects are calculated.

---

<pre>
<JS Critical Rate>
code
code
rate = code;
</JS Critical Rate>

- Used for: Skill, Item Notetags
- The 'rate' variable is the final returned amount to determine the
critical hit success rate.
- Replace 'code' with JavaScript code to determine the final 'rate' to be
returned as the critical hit success rate.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Critical Rate as User>
code
code
rate = code;
</JS Critical Rate as User>

<JS Critical Rate as Target>
code
code
rate = code;
</JS Critical Rate as Target>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Only applies during battle.
- The 'rate' variable is the final returned amount to determine the
critical hit success rate.
- Base value comes from Game_Action.itemCri
- Skill/Item <JS Critical Rate> runs
- Then <JS Critical Rate as User/Target> notetags run
- Replace 'code' with JavaScript code to determine the final 'rate' to be
returned as the critical hit success rate.
- If used on trait objects, this will apply to any skills/items used as long
as the unit affected by the trait object has access to the trait object.
- If the 'as User' notetag variant is used, this code will be run as a
response to the action from the action user end.
- If the 'as Target' notetag variant is used, this code will be run as a
response to the action from the action target end.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Critical Damage>
code
code
multiplier = code;
bonusDamage = code;
</JS Critical Damage>

- Used for: Skill, Item Notetags
- The 'multiplier' variable is returned later and used as the damage
multiplier used to amplify the critical damage amount.
- The 'bonusDamage' variable is returned later and used as extra added
damage for the critical damage amount.
- Replace 'code' with JavaScript code to determine how the 'multiplier' and
'bonusDamage' variables are calculated.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

=== Life Steal-Related Notetags ===

[[File:BattleCore_Update123_Preview1.png|600px]]

---

<pre>
<HP Life Steal: x%>
<MP Life Steal: x%>

- Used for: Skill, Item Notetags
- Causes this skill/item to have Life Steal properties, allowing the user to
take x% of the HP/MP Damage as recovered HP/MP.
- HP Life Steal can only take HP from dealt HP damage.
- MP Life Steal can only take MP from dealt MP damage.
- Replace 'x' with a number representing the percentage of the dealt damage
used as HP/MP recovery.
- This cannot be used with skills/items with HP Drain/MP Drain. Life Steal
is a different mechanic from HP Drain/MP Drain.
</pre>

---

<pre>
<HP Life Steal Certain Hit: +x%>
<HP Life Steal Physical Hit: +x%>
<HP Life Steal Magical Hit: +x%>

<HP Life Steal Certain Hit: -x%>
<HP Life Steal Physical Hit: -x%>
<HP Life Steal Magical Hit: -x%>

<MP Life Steal Certain Hit: +x%>
<MP Life Steal Physical Hit: +x%>
<MP Life Steal Magical Hit: +x%>

<MP Life Steal Certain Hit: -x%>
<MP Life Steal Physical Hit: -x%>
<MP Life Steal Magical Hit: -x%>

- Used for: Used for: Actor, Class, Armor, Enemy, State Notetags
- The related battler's various trait properties can have passive life steal
properties that will trigger upon using skills/items with matching hit
types regardless of whether or not the skill/item innately has Life Steal.
- Notetag variants with "Certain Hit" will only trigger from "Certain Hit"
skill and item types. Same with "Physical" and "Magical" variants.
- HP Life Steal can only take HP from dealt HP damage.
- MP Life Steal can only take HP from dealt MP damage.
- Replace 'x' with a number representing the additive stacking percentage
boost of the dealt damage used as HP/MP recovery. The effects will stack
additively with other trait objects.
- This cannot be used with skills/items with HP Drain/MP Drain. Life Steal
is a different mechanic from HP Drain/MP Drain.
</pre>

---

<pre>
<Cancel Life Steal>

<Cancel HP Life Steal>
<Cancel MP Life Steal>

- Used for: Skill, Item Notetags
- Prevents this skill from allowing Life Steal effects to occur including
the passive life steal calculators from the skill/item user.
- This does not affect HP Drain/MP Drain. Life Steal is a different mechanic
from HP Drain/MP Drain.
</pre>

---

<pre>
<Guard Life Steal>

<Guard HP Life Steal>
<Guard MP Life Steal>

- Used for: Used for: Actor, Class, Armor, Enemy, State Notetags
- If the related battler becomes the target of Life Steal, this will prevent
the Life Steal effects from taking effect.
- This does not affect HP Drain/MP Drain. Life Steal is a different mechanic
from HP Drain/MP Drain.
</pre>

---

<pre>
<Disarm Life Steal>

<Disarm HP Life Steal>
<Disarm MP Life Steal>

- Used for: Used for: Actor, Class, Armor, Enemy, State Notetags
- Makes the related battler unable to HP/MP Life Steal regardless of the
skill/item and its related properties like equipment.
- This does not prevent skills/items with innate Life Steal from being used.
Only the Life Steal part of the skill/item will have no effect.
- This does not affect HP Drain/MP Drain. Life Steal is a different mechanic
from HP Drain/MP Drain.
</pre>

---

<pre>
<Negative Life Steal>

<Negative HP Life Steal>
<Negative MP Life Steal>

- Used for: Used for: Actor, Class, Armor, Enemy, State Notetags
- If the related battler becomes the target of Life Steal, this will invert
the healing properties of Life Steal, causing the Life Steal user to
instead take HP/MP damage.
- This does NOT heal the target related battler.
- This does not prevent skills/items with innate Life Steal from being used.
Only the Life Steal part of the skill/item will have no effect.
- This does not affect HP Drain/MP Drain. Life Steal is a different mechanic
from HP Drain/MP Drain.
</pre>

---

=== Action Sequence-Related Notetags ===

[[File:BattleCoreActSeq.png|400px]]

Action Sequences allow you full control over how a skill and/or item plays
through its course. These notetags give you control over various aspects of
those Action Sequences. More information is found in the Action Sequences
help section.

---

[[File:BattleCorePentaSlash.gif]]

<pre>
<Custom Action Sequence>

- Used for: Skill, Item Notetags
- Removes all automated Action Sequence parts from the skill.
- Everything Action Sequence-related will be done by Common Events.
- Insert Common Event(s) into the skill/item's effects list to make use of
the Custom Action Sequences.
- This will prevent common events from loading in the Item Scene and Skill
Scene when used outside of battle.
</pre>

---

<pre>
<Auto Action Sequence>

- Used for: Skill, Item Notetags
- If the Action Sequence Plugin Parameter "Auto Notetag" is enabled, this
plugin will prevent custom action sequences from happening for the skill
or item, and instead, use an Automatic Action Sequence instead.
- Ignore this if you have "Auto Notetag" disabled or set to false. By
default, this setting is set to false. Please be aware of the changes
you've made to your game before using it.
</pre>

---

<pre>
<Bypass Auto Action Sequence>

- Used for: Skill, Item Notetags
- This notetag is used for the game devs that have the Action Sequence
Plugin Parameter "Auto Notetag" on for applying <Custom Action Sequence>
to everything.
- This will allow items and skills to be able to launch their common
events from the menu scene regardless of the inherent restriction to
prevent action sequence based skills/items with common events from
launching.
- Ignore this if you have "Auto Notetag" disabled or set to false. By
default, this setting is set to false. Please be aware of the changes
you've made to your game before using it.
</pre>

---

<pre>
<Common Event: name>

- Used for: Skill, Item Notetags
- Battle only: calls forth a Common Event of a matching name.
- Replace 'name' with the name of a Common Event to call from when this
skill/item is used in battle.
- Remove any \I[x] in the name.
- Insert multiple notetags to call multiple Common Events in succession.
- This will occur after any Common Event Trait Effects for the skill/item's
database entry.
- This is primarily used for users who are reorganizing around their Common
Events and would still like to have their skills/items perform the correct
Action Sequences in case the ID's are different.
</pre>

---

<pre>
<Display Icon: x>
<Display Text: string>

- Used for: Skill, Item Notetags
- When displaying the skill/item name in the Action Sequence, determine the
icon and/or text displayed.
- Replace 'x' with a number value representing the icon ID to be displayed.
- Replace 'string' with a text value representing the displayed name.
</pre>

---

[[File:BattleCore_CommonEventKeys.png]]

<pre>
<Common Event Key: name>
<Common Event Keys: name, name, name>

<Common Event Keys>
key
key
key
</Common Event Keys>

- Used for: Skill, Item Notetags
- Will generate Common Events for the skill/item with a corresponding key.
- Replace 'name' with the name of the Common Event's key that you want to
reference. That key will be converted into a Common Event effect for the
skill/item and be treated as an action sequence.
- The notetag variants that use multiple keys will have the keys added in
the order they are listed.
- If keys do not reference any Common Events, no Common Events will be
added for that key.
- To mark a Common Event with a key, insert inside a Common Event's name the
[ and ] brackets around the text that will be used as the Common Event's
key text.
- For example, if Common Event's name is "Penta Slash [PENTA]", then the
key used is "PENTA" without the quotes.
- This key could then be referenced by <Common Event Key: PENTA> notetag.
- Do not use commas (,) inside the key text as it will be automatically
removed for the sake of consistency.
- This feature is made for make the process of sharing Action Sequences to
become easier without needing to line up Common Event ID's.
</pre>

---

=== Animated Sideview Battler-Related Notetags ===

[[File:BattleCoreSvEnemies.png|600px]]

Enemies can use Animated Sideview Actor graphics thanks to this plugin.
These notetags give you control over that aspect. Some of these also affect
actors in addition to enemies.

---

<pre>
<Sideview Battler: filename>

<Sideview Battlers>
filename: weight
filename: weight
filename: weight
</Sideview Battlers>

- Used for: Enemy Notetags
- Replaces the enemy's battler graphic with an animated Sideview Actor
graphic found in the img/sv_actors/ folder.
- Replace 'filename' with the filename of the graphic to use. Do not insert
any extensions. This means the file 'Actor1_1.png' will be only inserted
as 'Actor1_1' without the '.png' at the end.
- If the multiple notetag vaiant is used, then a random filename is selected
from the list upon the enemy's creation.
- Replace 'weight' with a number value representing how often the 'filename'
would come up. The higher the weight, the more often. You may omit this
and the colon(:) and just type in the 'filename' instead.
- Add/remove lines as you see fit.

Example:

<Sideview Battlers>
Actor1_1: 25
Actor1_3: 10
Actor1_5
Actor1_7
</Sideview Battlers>
</pre>

---

<pre>
<Sideview Anchor: x, y>

- Used for: Actor, Enemy Notetags
- Sets the sprite anchor positions for the sideview sprite.
- Replace 'x' and 'y' with numbers depicting where the anchors should be for
the sideview sprite.
- By default, the x and y anchors are 0.5 and 1.0.
</pre>

---

<pre>
<Sideview Home Offset: +x, +y>
<Sideview Home Offset: -x, -y>

- Used for: Actor, Class, Weapon, Armor, State Notetags
- Offsets the sideview actor sprite's home position by +/-x, +/-y.
- Replace 'x' and 'y' with numbers depicting how much to offset each of the
coordinates by. For '0' values, use +0 or -0.
- This notetag will not work if you remove it from the JavaScript code in
Plugin Parameters > Actor > JS: Home Position
</pre>

---

<pre>
<Sideview Weapon Offset: +x, +y>
<Sideview Weapon Offset: -x, -y>

- Used for: Actor, Class, Weapon, Armor, Enemy State Notetags
- Offsets the sideview weapon sprite's position by +/-x, +/-y.
- Replace 'x' and 'y' with numbers depicting how much to offset each of the
coordinates by. For '0' values, use +0 or -0.
</pre>

---

<pre>
<Sideview Show Shadow>
<Sideview Hide Shadow>

- Used for: Actor, Enemy Notetags
- Sets it so the sideview battler's shadow will be visible or hidden.
</pre>

---

<pre>
<Sideview Shadow Scale: x%>
<Sideview Shadow Scale: x.y>

- Used for: Actor, Enemy Notetags
- Adjusts the scaling size of the sideview battler's shadow.
- This affects both the X and Y scale.
</pre>

---

<pre>
<Sideview Shadow Scale X: x%>
<Sideview Shadow Scale X: x.y>

<Sideview Shadow Scale Y: x%>
<Sideview Shadow Scale Y: x.y>

- Used for: Actor, Enemy Notetags
- Adjusts the scaling size of the sideview battler's shadow.
- These affect their respective X and Y scales separately.
</pre>

---

<pre>
<Sideview Collapse>
<Sideview No Collapse>

- Used for: Enemy Notetags
- Either shows the collapse graphic or does not show the collapse graphic.
- Collapse graphic means the enemy will 'fade away' once it's defeated.
- No collapse graphic means the enemy's corpse will remain on the screen.
</pre>

---

<pre>
<Sideview Idle Motion: name>

<Sideview Idle Motions>
name: weight
name: weight
name: weight
</Sideview Idle Motions>

- Used for: Enemy Notetags
- Changes the default idle motion for the enemy.
- Replace 'name' with any of the following motion names:
- 'walk', 'wait', 'chant', 'guard', 'damage', 'evade', 'thrust', 'swing',
'missile', 'skill', 'spell', 'item', 'escape', 'victory', 'dying',
'abnormal', 'sleep', 'dead'
- If the multiple notetag vaiant is used, then a random motion name is
selected from the list upon the enemy's creation.
- Replace 'weight' with a number value representing how often the 'name'
would come up. The higher the weight, the more often. You may omit this
and the colon(:) and just type in the 'name' instead.
- Add/remove lines as you see fit.

Example:

<Sideview Idle Motions>
walk: 25
wait: 50
guard
victory
abnormal
</Sideview Idle Motions>
</pre>

---

<pre>
<Sideview Size: width, height>

- Used for: Enemy Notetags
- When using a sideview battler, its width and height will default to the
setting made in Plugin Parameters => Enemy Settings => Size: Width/Height.
- This notetag lets you change that value to something else.
- Replace 'width' and 'height' with numbers representing how many pixels
wide/tall the sprite will be treated as.
- This does NOT change the image size. This only changes the HITBOX size.
</pre>

---

<pre>
<Sideview Weapon: weapontype>

<Sideview Weapons>
weapontype: weight
weapontype: weight
weapontype: weight
</Sideview Weapons>

- Used for: Enemy Notetags
- Give your sideview enemies weapons to use.
- Replace 'weapontype' with the name of the weapon type found under the
Database => Types => Weapon Types list (without text codes).
- If the multiple notetag vaiant is used, then a random weapon type is
selected from the list upon the enemy's creation.
- Replace 'weight' with a number value representing how often the weapontype
would come up. The higher the weight, the more often. You may omit this
and the colon(:) and just type in the 'weapontype' instead.
- Add/remove lines as you see fit.

Example:

<Sideview Weapons>
Dagger: 25
Sword: 25
Axe
</Sideview Weapons>
</pre>

---

<pre>
<traitname Sideview Battler: filename>

<traitname Sideview Battlers>
filename: weight
filename: weight
filename: weight
</traitname Sideview Battlers>

- Used for: Enemy Notetags
- Requires VisuMZ_1_ElementStatusCore
- Allows certain Trait Sets to cause battlers to have a unique appearance.
- Replace 'filename' with the filename of the graphic to use. Do not insert
any extensions. This means the file 'Actor1_1.png' will be only inserted
as 'Actor1_1' without the '.png' at the end.
- If the multiple notetag vaiant is used, then a random filename is selected
from the list upon the enemy's creation.
- Replace 'weight' with a number value representing how often the 'filename'
would come up. The higher the weight, the more often. You may omit this
and the colon(:) and just type in the 'filename' instead.
- Add/remove lines as you see fit.

Examples:

<Male Sideview Battlers>
Actor1_1: 25
Actor1_3: 10
Actor1_5
Actor1_7
</Male Sideview Battlers>

<Female Sideview Battlers>
Actor1_2: 25
Actor1_4: 10
Actor1_6
Actor1_8
</Female Sideview Battlers>
</pre>

---

<pre>
<traitname Sideview Idle Motion: name>

<traitname Sideview Idle Motions>
name: weight
name: weight
name: weight
</traitname Sideview Idle Motions>

- Used for: Enemy Notetags
- Requires VisuMZ_1_ElementStatusCore
- Allows certain Trait Sets to cause battlers to have unique idle motions.
- Replace 'name' with any of the following motion names:
- 'walk', 'wait', 'chant', 'guard', 'damage', 'evade', 'thrust', 'swing',
'missile', 'skill', 'spell', 'item', 'escape', 'victory', 'dying',
'abnormal', 'sleep', 'dead'
- If the multiple notetag vaiant is used, then a random motion name is
selected from the list upon the enemy's creation.
- Replace 'weight' with a number value representing how often the 'name'
would come up. The higher the weight, the more often. You may omit this
and the colon(:) and just type in the 'name' instead.
- Add/remove lines as you see fit.

Examples:

<Jolly Sideview Idle Motions>
wait: 25
victory: 10
walk
</Jolly Sideview Idle Motions>

<Serious Sideview Idle Motions>
walk: 25
guard: 10
wait
</Jolly Sideview Idle Motions>
</pre>

---

<pre>
<traitname Sideview Weapon: weapontype>

<traitname Sideview Weapons>
weapontype: weight
weapontype: weight
weapontype: weight
</traitname Sideview Weapons>

- Used for: Enemy Notetags
- Requires VisuMZ_1_ElementStatusCore
- Allows certain Trait Sets to cause battlers to have unique weapons.
- Replace 'weapontype' with the name of the weapon type found under the
Database => Types => Weapon Types list (without text codes).
- If the multiple notetag vaiant is used, then a random weapon type is
selected from the list upon the enemy's creation.
- Replace 'weight' with a number value representing how often the weapontype
would come up. The higher the weight, the more often. You may omit this
and the colon(:) and just type in the 'weapontype' instead.
- Add/remove lines as you see fit.

Examples:

<Male Sideview Weapons>
Dagger: 25
Sword: 25
Axe
</Male Sideview Weapons>

<Female Sideview Weapons>
Dagger: 25
Spear: 25
Cane
</Female Sideview Weapons>
</pre>

---

=== Enemy-Related Notetags ===

---

<pre>
<Battler Sprite Cannot Move>

- Used for: Enemy Notetags
- Prevents the enemy from being able to move, jump, and/or float due to
Action Sequences. Useful for rooted enemies.
</pre>

---

[[File:BattleCoreSwap.png|600px]]

<pre>
<Swap Enemies>
name: weight
name: weight
name: weight
</Swap Enemies>

- Used for: Enemy Notetags
- Causes this enemy database object to function as a randomizer for any of
the listed enemies inside the notetag. When the enemy is loaded into the
battle scene, the enemy is immediately replaced with one of the enemies
listed. The randomization is based off the 'weight' given to each of the
enemy 'names'.
- Replace 'name' with the database enemy of the enemy you wish to replace
the enemy with.
- Replace 'weight' with a number value representing how often the 'name'
would come up. The higher the weight, the more often. You may omit this
and the colon(:) and just type in the 'name' instead.
- Add/remove lines as you see fit.

Example:

<Swap Enemies>
Bat: 50
Slime: 25
Orc
Minotaur
</Swap Enemies>
</pre>

---

<pre>
<Aspect Name: name>

- Used for: Enemy Notetags
- Changes enemy's aspect name shown in the In-Battle Status and other
supported plugin menus.
- Requires <Aspect Description> in order to show.
- Replace 'name' with text for how enemy aspect should be renamed.
</pre>

---

<pre>
<Aspect Color: color>

- Used for: Enemy Notetags
- Changes enemy's aspect name color shown in the In-Battle Status and other
supported plugin menus.
- Requires <Aspect Description> in order to show.
- Replace 'color' with either a number from 0 to 31 representing the text
color or in the format of '#rrggbb' to custom pick a hex color.
</pre>

---

<pre>
<Aspect Icon: x>

- Used for: Enemy Notetags
- Changes enemy's aspect icon shown in the In-Battle Status and other
supported plugin menus.
- Requires <Aspect Description> in order to show.
- Replace 'x' with a number representing the icon index used to represent
the enemy aspect.
</pre>

---

<pre>
<Aspect Description>
text
text
</Aspect Description>

- Used for: Enemy Notetags
- Changes enemy's aspect description shown in the In-Battle Status and other
supported plugin menus.
- Replace 'text' with the text you would like to appear as a description for
the enemy's aspect.
</pre>

---

=== JavaScript Notetags: Mechanics-Related ===

These JavaScript notetags allow you to run code at specific instances during
battle provided that the unit has that code associated with them in a trait
object (actor, class, weapon, armor, enemy, or state). How you use these is
entirely up to you and will depend on your ability to understand the code
used and driven for each case.

---

<pre>
<JS Pre-Start Battle>
code
code
code
</JS Pre-Start Battle>

<JS Post-Start Battle>
code
code
code
</JS Post-Start Battle>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code at the start of battle aimed at the function:
BattleManager.startBattle()
- 'Pre' runs before the function runs.
- 'Post' runs after the function runs.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Pre-Start Turn>
code
code
code
</JS Pre-Start Turn>

<JS Post-Start Turn>
code
code
code
</JS Post-Start Turn>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code at the start of a turn aimed at the function:
BattleManager.startTurn()
- 'Pre' runs before the function runs.
- 'Post' runs after the function runs.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Pre-Start Action>
code
code
code
</JS Pre-Start Action>

<JS Post-Start Action>
code
code
code
</JS Post-Start Action>

- Used for: Actor, Class, Skill, Item, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code at the start of an action aimed at the function:
BattleManager.startAction()
- 'Pre' runs before the function runs.
- 'Post' runs after the function runs.
- If used on skills and/or items, this will only apply to the skill/item
being used and does not affect other skills and items.
- If used on trait objects, this will apply to any skills/items used as long
as the unit affected by the trait object has access to the trait object.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Pre-Apply>
code
code
code
</JS Pre-Apply>

- Used for: Skill, Item Notetags
- Runs JavaScript code at the start of an action hit aimed at the function:
Game_Action.prototype.apply()
- 'Pre' runs before the function runs.
- If used on skills and/or items, this will only apply to the skill/item
being used and does not affect other skills and items.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Pre-Apply as User>
code
code
code
</JS Pre-Apply as User>

<JS Pre-Apply as Target>
code
code
code
</JS Pre-Apply as Target>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code at the start of an action hit aimed at the function:
Game_Action.prototype.apply()
- 'Pre' runs before the function runs.
- If used on trait objects, this will apply to any skills/items used as long
as the unit affected by the trait object has access to the trait object.
- If the 'as User' notetag variant is used, this code will be run as a
response to the action from the action user end.
- If the 'as Target' notetag variant is used, this code will be run as a
response to the action from the action target end.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Pre-Damage>
code
code
code
</JS Pre-Damage>

- Used for: Skill, Item Notetags
- Runs JavaScript code before damage is dealt aimed at the function:
Game_Action.prototype.executeDamage()
- 'Pre' runs before the function runs.
- If used on skills and/or items, this will only apply to the skill/item
being used and does not affect other skills and items.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Pre-Damage as User>
code
code
code
</JS Pre-Damage as User>

<JS Pre-Damage as Target>
code
code
code
</JS Pre-Damage as Target>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code before damage is dealt aimed at the function:
Game_Action.prototype.executeDamage()
- 'Pre' runs before the function runs.
- If used on trait objects, this will apply to any skills/items used as long
as the unit affected by the trait object has access to the trait object.
- If the 'as User' notetag variant is used, this code will be run as a
response to the action from the action user end.
- If the 'as Target' notetag variant is used, this code will be run as a
response to the action from the action target end.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Post-Damage>
code
code
code
</JS Post-Damage>

- Used for: Skill, Item Notetags
- Runs JavaScript code after damage is dealt aimed at the function:
Game_Action.prototype.executeDamage()
- 'Post' runs after the function runs.
- If used on skills and/or items, this will only apply to the skill/item
being used and does not affect other skills and items.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Post-Damage as User>
code
code
code
</JS Post-Damage as User>

<JS Post-Damage as Target>
code
code
code
</JS Post-Damage as Target>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code after damage is dealt aimed at the function:
Game_Action.prototype.executeDamage()
- 'Post' runs after the function runs.
- If used on trait objects, this will apply to any skills/items used as long
as the unit affected by the trait object has access to the trait object.
- If the 'as User' notetag variant is used, this code will be run as a
response to the action from the action user end.
- If the 'as Target' notetag variant is used, this code will be run as a
response to the action from the action target end.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Post-Apply>
code
code
code
</JS Post-Apply>

- Used for: Skill, Item Notetags
- Runs JavaScript code at the end of an action hit aimed at the function:
Game_Action.prototype.apply()
- 'Post' runs after the function runs.
- If used on skills and/or items, this will only apply to the skill/item
being used and does not affect other skills and items.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one using the skill/item.
- The 'target' variable represents the one receiving the skill/item hit.
</pre>

---

<pre>
<JS Post-Apply as User>
code
code
code
</JS Post-Apply as User>

<JS Post-Apply as Target>
code
code
code
</JS Post-Apply as Target>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code at the end of an action hit aimed at the function:
Game_Action.prototype.apply()
- 'Post' runs after the function runs.
- If used on trait objects, this will apply to any skills/items used as long
as the unit affected by the trait object has access to the trait object.
- If the 'as User' notetag variant is used, this code will be run as a
response to the action from the action user end.
- If the 'as Target' notetag variant is used, this code will be run as a
response to the action from the action target end.
- Replace 'code' with JavaScript code to run desired effects.
</pre>

---

<pre>
<JS Pre-End Action>
code
code
code
</JS Pre-End Action>

<JS Post-End Action>
code
code
code
</JS Post-End Action>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code at the end of an action aimed at the function:
BattleManager.endAction()
- 'Pre' runs before the function runs.
- 'Post' runs after the function runs.
- If used on trait objects, this will apply to any skills/items used as long
as the unit affected by the trait object has access to the trait object.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Pre-End Turn>
code
code
code
</JS Pre-End Turn>

<JS Post-End Turn>
code
code
code
</JS Post-End Turn>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code at the end of a turn aimed at the function:
Game_Battler.prototype.onTurnEnd()
- 'Pre' runs before the function runs.
- 'Post' runs after the function runs.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Pre-Regenerate>
code
code
code
</JS Pre-Regenerate>

<JS Post-Regenerate>
code
code
code
</JS Post-Regenerate>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code when a unit regenerates HP/MP aimed at the function:
Game_Battler.prototype.regenerateAll()
- 'Pre' runs before the function runs.
- 'Post' runs after the function runs.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Battle Victory>
code
code
code
</JS Battle Victory>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code when a battle is won aimed at the function:
BattleManager.processVictory()
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Escape Success>
code
code
code
</JS Escape Success>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code when escaping succeeds aimed at the function:
BattleManager.onEscapeSuccess()
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Escape Failure>
code
code
code
</JS Escape Failure>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code when escaping fails aimed at the function:
BattleManager.onEscapeFailure()
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Battle Defeat>
code
code
code
</JS Battle Defeat>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code when a battle is lost aimed at the function:
BattleManager.processDefeat()
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

<pre>
<JS Pre-End Battle>
code
code
code
</JS Pre-End Battle>

<JS Post-End Battle>
code
code
code
</JS Post-End Battle>

- Used for: Actor, Class, Weapon, Armor, Enemy, State Notetags
- Runs JavaScript code when the battle is over aimed at the function:
BattleManager.endBattle()
- 'Pre' runs before the function runs.
- 'Post' runs after the function runs.
- Replace 'code' with JavaScript code to run desired effects.
- The 'user' variable represents the one affected by the trait object.
</pre>

---

=== Battle Layout-Related Notetags ===

[[File:BattleCoreBattleStyleBorder.png|600px]]

These tags will change the battle layout for a troop regardless of how the
plugin parameters are set up normally. Insert these tags in either the
noteboxes of maps or the names of troops for them to take effect. If both
are present for a specific battle, then priority goes to the setting found
in the troop name.

---

<pre>
<Layout: type>
<Battle Layout: type>

- Used for: Map Notetags, Troop Name Tags, and Troop Comment Tags
- Changes the battle layout style used for this specific map or battle.
- Replace 'type' with 'default', 'list', 'xp', 'portrait', or 'border'.
- Those with VisuMZ_3_FrontviewBattleUI can use 'frontview'.
- Those with VisuMZ_3_SideviewBattleUI can use 'sideview'.
- If using Troop Comment Tags, then as long as the tag appears in a comment
found on any of the Troop's pages (even if they don't run), the tag will
be considered in effect.
</pre>

---

=== Troop Size Tags ===

[[File:BattleCore_ExtTroop.png|600px]]

---

<pre>
<Extend: x>
<Extend: x, x, x>

- Used for: Troop Name Tags and Troop Comment Tags
- Adds enemies from another troop to the current troop.
- Enemies from another troop will retain their database positions.
- Replace 'x' with the ID of the database troop entry you wish to add enemy
members from.
- Insert multiple x's to add from more troops.
- Extended troop members will be added in the order they're listed.
- Be cautious of how many enemies you add as too many will lag the battle
system. We are not responsible for frame drops due to this.
</pre>

---

=== Troop Comment Tags ===

Place these tags inside of a comment found in a troop page's event list.

---

[[File:BattleCore_OnceParallelWhenStartBattle.png|600px]]

<pre>
<Once Parallel When Start Battle>

- Used for: Troop Page Comment Tags
- Causes the troop page to immediately load the moment the battle scene
begins to fade in (not after it fades in). This is faster than a turn 0
condition troop page. Troop page conditions are ignored.
- This can be used for things like the Action Sequence Camera plugin, the
Visual Battle Environment plugin, and/or initial battle poses and such in
order to provide a near seamless battle transition experience.
- This does NOT trigger when coming out of the options menu or party menu.
- This WILL trigger when going from battle to battle nonstop via plugins
like VisuStella MZ's Chain Battles.
- When actors are moving towards their home positions, it will take around
30 frames by default. Use this information however you like.
</pre>

---

Main Menu Core VisuStella MZ

2024-11-03T12:09:27Z

Yanfly:

{{MzPlugin
|preview = <youtube>https://www.youtube.com/watch?v=jfNFvcD7okg</youtube>
|link1 = {{VisuStella Wave 1}}
|link2 = {{VisuStella All Waves Collection}}

}}



{|
| [[File:MainMenuCorePortrait.png|400px]]
| [[File:MainMenuCoreDefaultStyle.png|400px]]

|-

| [[File:MainMenuCoreFullScreenStyle.png|400px]]
| [[File:MainMenuCoreInnerSolo.png|400px]]

|}

{| style="width: 800px;" cellspacing="0" cellpadding="0"
| style="width: 100%; vertical-align: top;" |



{{Visustella MZ}}

== Introduction ==

The Main Menu Core plugin is designed to give you more control over the Main
Menu outside of RPG Maker MZ's editor's control. Game devs are given control
over how commands work, visual aesthetics pertaining to the Main Menu, and
assign menu images to actors as background portraits.

Features include all (but not limited to) the following:

* Control over general Main Menu settings.
* The ability to set Menu Background Portraits for individual actors.
* Flexibility in changing which commands appear in the Main Menu.
* Add new windows like the Playtime Window and Variable windows.
* Change the style of how the windows are arranged in the Main Menu.
* Change the way the status list is displayed and the way it's displayed.

== Requirements ==

This plugin is made for RPG Maker MZ. This will not work in other iterations
of RPG Maker.

{{MZ Tier 1}}

{{Notetags MZ}}

{{VisuMZ Main Menu Core Notetags}}

{{Plugin Commands MZ}}

{{VisuMZ Main Menu Core Plugin Commands}}

== Plugin Parameters ==

=== General Settings ===

[[File:MainMenuCoreParam1new.png]]

These general settings contain various settings on how the Main Menu scene
displays certain windows, alters how specific windows behave, and determines
which scenes would display actor menu images as background portraits.

---

Gold Window

Thinner Gold Window:
- Make the Gold Window thinner in the Main Menu?
- Used to match the Playtime and Variable Windows.
- Only applies to the Command Window style: Default Vertical.

Auto Adjust Height:
- Automatically adjust the height for the thinner Gold Window?

Auto Adjust Y:
- Automatically adjust the Y position for the thinner Gold Window?

---

Status Window

Select Last?:
- When picking a personal command from the Command Window, select the
last picked actor or always the first?

---

Solo Party

Solo Quick Mode:
- When selecting "Skills", "Equip", or "Status" with one party member,
immediately go to the scene.

---

Sub Menus

Menus with Actor BG's:
- A list of the menus that would be compatible with Actor Menu Backgrounds

JS: Actor BG Action:
- Code used to determine how to display the sprites upon loading.

---

Party Window

Show Reserve Memebers:
- Show reserve members while on the Main Menu scene?

Hide Main Menu Only
- If reserve members are hidden, hide them only in the main menu or
all scenes?

---

=== Command Window List ===

[[File:MainMenuCoreParam2.png]]

The Command Window functions as a hub to the various scenes linked from the
Main Menu. These include 'Item', 'Skill', 'Equip', 'Status', 'Save', and
so on. This Plugin Parameter is an array that lets you add, remove, and/or
alter the Command Window's various commands, how they're handled, whether or
not they're visible, and how they react when selected.

These will require knowledge of JavaScript to use them properly.

---

[[File:MainMenuCoreParam2a.png]]

Command Window List

Symbol:
- The symbol used for this command.

Icon:
- Icon used for this command.
- Use 0 for no icon.

STR: Text:
- Displayed text used for this title command.
- If this has a value, ignore the JS: Text version.

JS: Text:
- JavaScript code used to determine string used for the displayed name.

JS: Show:
- JavaScript code used to determine if the item is shown or not.

JS: Enable:
- JavaScript code used to determine if the item is enabled or not.

JS: Ext:
- JavaScript code used to determine any ext data that should be added.

JS: Run Code:
- JavaScript code that runs once this command is selected.

JS: Personal Code:
- JavaScript code that runs once the actor list is selected with this
command highlighted.

---

==== Subcategories ====

[[File:MainMenuCore_Subcategories.gif]]

Subcategories are a new addition to the Main Menu Core version 1.18. When a
subcategory is set, it will only display Command Window items that belong
to that subcategory. Those Command Window items do not appear when there is
no subcategory active or if it's a different subcategory.

---

To create a subcategory, a few things must be done:

1. The subcategory symbol must be "subcategory".

2. The string returned by JS: Ext determines the subcategory. In the default Plugin Parameters, 'datalog' is returned as the subcategory. This becomes the subcategory when picked.

3. For the JS: Run Code, have the following code somewhere in it:

const ext = arguments[0];
this.setSubcategory(ext);

---

To make a Command Window item be a part of a subcategory do the following:

1. Take the JS: Ext string value (case sensitive).

2. Set it as the target Command Window item's "Subcategory" value.

3. If the subcategory doesn't exist, then this Command Window item will appear normally.

---

=== Playtime Window ===

[[File:MainMenuCoreParam3.png]]

The Playtime Window is an optional feature that can be displayed in the
Main Menu. As its name suggests, it displays the playtime of the player's
current play through.

---

Playtime Window

Enable:
- Use the Playtime Window?

Adjust Command Window:
- Adjust the command window's height to fit in the Playtime Window?

Background Type:
- Select background type for the Playtime window.

Font Size:
- Font size used for displaying Gold inside the Playtime window.

Time Icon:
- Icon displayed for the 'Time' label.

Time Text:
- Text for the display of 'Time' in the Playtime window.

JS: X, Y, W, H:
- Code used to determine the dimensions for the Playtime window.

---

=== Variable Window ===

[[File:MainMenuCoreParam4.png]]

The Variable Window is an optional feature that can be displayed in the
Main Menu. If enabled, the Variable Window will display variables of the
game dev's choice in the Main Menu itself.

---

Variable Window

Enable:
- Use the Variable Window?

Adjust Command Window:
- Adjust the command window's height to fit in the Variable Window?

Background Type:
- Select background type for the Variable window.

Font Size:
- Font size used for displaying Gold inside the Variable window.

Variable List:
- Select variables to be displayed into the window.
Use \i[x] to determine their icon.

JS: X, Y, W, H:
- Code used to determine the dimensions for the Variable window.

---

=== Command Window Style & Command Style Settings ===

[[File:MainMenuCoreParam5.png]]

This determines how the Main Menu appears based on the Command Window Style.
If anything but the 'Default' is used, then these settings will take over
the window placement settings for the Main Menu. This means that even if you
are using VisuStella's Core Engine, the window layouts will be overwritten.

---

Command Window Style:
- Choose the positioning and style of the Main Menu Command Window.
- This will automatically rearrange windows.
- We're not responsible for visual incompatibilities.

[[File:MainMenuCoreDefaultStyle.png|600px]]

Default Vertical Side Style:
- The default Main Menu layout style.
- Affected by VisuStella's Core Engine's Plugin Parameter settings.

[[File:MainMenuCoreTopHorzStyle.png|600px]]

Top Horizontal Style:
- Puts the Command Window at the top of the screen.
- Gold, Playlist, and Variable Windows are moved to the bottom.
- The Actor List Window is placed in the middle.
- Unaffected by VisuStella's Core Engine's Plugin Parameter settings.

[[File:MainMenuCoreTopThinHorzStyle.png|600px]]

Top Thin Horizontal Style:
- Puts the Command Window at the top of the screen.
- It's one line thick.
- Gold, Playlist, and Variable Windows are moved to the bottom.
- The Actor List Window is placed in the middle.
- Unaffected by VisuStella's Core Engine's Plugin Parameter settings.

[[File:MainMenuCoreBottomHorzStyle.png|600px]]

Bottom Horizontal Style:
- Puts the Command Window at the bottom of the screen.
- Gold, Playlist, and Variable Windows are moved to the top.
- The Actor List Window is placed in the middle.
- Unaffected by VisuStella's Core Engine's Plugin Parameter settings.

[[File:MainMenuCoreBottomThinHorzStyle.png|600px]]

Bottom Horizontal Style:
- Puts the Command Window at the bottom of the screen.
- It's one line thick.
- Gold, Playlist, and Variable Windows are moved to the top.
- The Actor List Window is placed in the middle.
- Unaffected by VisuStella's Core Engine's Plugin Parameter settings.

[[File:MainMenuCoreFullScreenStyle.png|600px]]

Mobile Full Screen Style:
- Puts the Command Window at the center of the screen with larger buttons.
- Gold, Playlist, and Variable Windows are moved to the bottom.
- The Actor List Window is hidden until prompted to be selected.
- Unaffected by VisuStella's Core Engine's Plugin Parameter settings.

---

[[File:MainMenuCoreParam5a.png]]

Command Style Settings

Style:
- How do you wish to draw command entries in the Command Window?
- Text Only: displays only text.
- Icon Only: displays only the icon.
- Icon + Text: displays icon first, then text.
- Automatic: determines the best fit for the size

Text Alignment:
- Decide how you want the text to be aligned.
- Left, Center, or Right

Rows:
- Number of visible rows.
- Applies only to Top, Bottom, and Mobile styles.

Columns:
- Number of maximum columns.
- Applies only to Top, Bottom, and Mobile styles.

Mobile Thickness:
- The thickness of the buttons for mobile version.
- Applies only to Top, Bottom, and Mobile styles.

---

=== Status Graphic, Status List Style, & List Style Settings ===

Choose how the contents Actor Status List Window in the Main Menu appears.
This can range from the which actor graphic is drawn to the style used for
the data that's displayed.

---

[[File:MainMenuCoreParam6.png]]

Status Graphic:
- Choose how the graphic for actor graphics appear in status-like menus.

[[File:MainMenuCoreNoFace.png|600px]]

None:
- Don't display any graphic for the actors.

[[File:MainMenuCoreDefaultStyle.png|600px]]

Face:
- Display the actors' faces. This is the default option in RPG Maker MZ.

[[File:MainMenuCoreMapSprite.png|600px]]

Map Sprite:
- Display the actors' map sprites.

[[File:MainMenuCoreSvBattler.png|600px]]

Sideview Battler:
- Display the actors' sideview battlers.

---

[[File:MainMenuCoreParam6a.png]]

Main Menu List Style
- Choose how the actor status list looks in the Main Menu.
- We're not responsible for visual incompatibilities.

[[File:MainMenuCoreParam6b.png]]

Inner-Menu List Style
- Choose how the actor status list looks in the inner menus like Scene_Item,
Scene_Skill, etc.
- We're not responsible for visual incompatibilities.

[[File:MainMenuCoreDefaultStyle.png|600px]]

Default Horizontal Style:
- This is the default style found in RPG Maker MZ's Main Menu.

[[File:MainMenuCoreInnerVert.png|600px]]

Vertical Style:
- Makes the display for the actor list vertical instead of horizontal.

[[File:MainMenuCorePortrait.png|600px]]

Portrait Style:
- Similar to the vertical style, except each actor's Menu Image is
displayed in the background instead. Portraits are required.
- If there is no Menu Image used, this will switch over to the Vertical
Style and use a face graphic instead.

[[File:MainMenuCoreInnerSolo.png|600px]]

Solo Style:
- Used for solo party member games. Extends the whole view of the Status
Window to accomodate a single actor.

[[File:MainMenuCoreInnerThinHorz.png|600px]]

Thin Horizontal Style:
- Makes the selectable menu entries for the actors a single line thin.

[[File:MainMenuCoreInnerThickerHorz.png|600px]]

Thicker Horizontal Style:
- Makes the selectable menu entries for the actors two lines thick.

---

[[File:MainMenuCoreParam6c.png]]

List Styles
JavaScript code used to determine how the individual styles are drawn.

JS: Default:
JS: Vertical:
JS: Portrait:
JS: Solo:
JS: Thin:
JS: Thicker:
- Code used to draw the data for these styles.

---

=== Custom Mouse Cursor Settings ===

[[File:MainMenuCore_CustomCursor.gif]]

Add/enable a custom mouse cursor for your game. This will use a graphic
found in the game project's /icon/ folder to use as the custom mouse
cursor when hovering over the game.

Does not work on mobile devices.

---

General Settings

Enable?:
- Enable custom cursor?
- Requires a custom 'Idle' graphic.

---

Graphic Settings

Idle Filename:
- Graphic used for mouse cursor when idle or moving.
- Located in game project's /icon/ folder.
- Required for a custom mouse cursor.

Click Filename:
- Graphic used for mouse cursor when clicked or held.
- Located in game project's /icon/ folder.
- Uses the 'Idle' graphic if 'Click' graphic is not used.

---

Anchor Settings

Anchor X:
- Anchor X value for the custom cursor.
- 0.0 - left; 0.5 - center; 1.0 - right

Anchor Y:
- Anchor Y value for the custom cursor.
- 0.0 - top; 0.5 - middle; 1.0 - bottom

---

{{VisuStella MZ Terms of Use}}

== Credits ==

If you are using this plugin, credit the following people in your game:

Team VisuStella

* [[Yanfly]]
* [[Arisu]]
* [[Olivia]]
* [[Irina]]

== Changelog ==

Version 1.26: October 17, 2024
* Documentation Update!
** Help file updated for updated features.
* Feature Update!
** Due to conflicts with deployment, the Custom Mouse Cursor has its base location moved from /img/system/ to /icon/.
** Please move the cursor file(s) as well as update the Plugin Parameters.
** Sorry for the inconvenience.

Version 1.25: September 19, 2024
* Documentation Update!
** Help file updated for new features.
* New Features!
** New Plugin Parameters added by Arisu:
*** Parameters > Custom Mouse Cursor
**** Add/enable a custom mouse cursor for your game.

Version 1.24: August 29, 2024
* Compatibility Update
** When "Load" command is used with Save Core's Single-Save Mode, automatically load up the save instead of going to the Load Menu.
* Documentation Update!
** Help file updated for new features.
* Feature Update!
** Plugin Command renamed:
*** Actor: Change Menu Image (JS) to Actor: Change Menu Image (JS) (Legacy)
* New Features!
** New Plugin Command added by Arisu:
*** Actor: Change Menu Image (JS) (v1.24)
**** Changes an actor's Menu Image using JavaScript.
**** Allows more control with more text entry.

Version 1.23: February 15, 2024
* Compatibility Update!
** Added compatibility functionality for future plugins.
* Feature Update!
** Updated the default Plugin Parameters for 'Command Window List' to include a 'Battle Tactics' command.
*** This is for the upcoming VisuStella MZ plugins.
*** Projects with the Main Menu Core already installed will not have this update, but you can copy over the settings from a new project with the following steps:
**** Create a new project. Install Main Menu Core. Open up the new project's 'Command Window List'. Right click the 'battleGridTactics' option(s) and click copy. Go to the target project's Main Menu Core's 'Command Window List' plugin parameter. Paste the command where you want it to go.

Version 1.22: October 12, 2023
* Feature Update!
** Subcategories are now maintained when exiting a scene pushed forward by a subcategory. Added by Olivia and sponsored by AndyL.

Version 1.21: April 13, 2023
* Bug Fixes!
** Multiple subcategories should now work properly. Fix made by Arisu.

Version 1.20: March 16, 2022
* Compatibility Update!
** Added compatibility functionality for future plugins.
* Feature Update!
** Updated the default Plugin Parameters for 'Command Window List' to include a 'Bestiary' command.
*** This is for the upcoming VisuStella MZ plugins.
*** Projects with the Main Menu Core already installed will not have this update, but you can copy over the settings from a new project with the following steps:
**** Create a new project. Install Main Menu Core. Open up the new project's 'Command Window List'. Right click the 'bestiary' option(s) and click copy. Go to the target project's Main Menu Core's 'Command Window List' plugin parameter. Paste the command where you want it to go.

Version 1.19: December 15, 2022
* Compatibility Update!
** Added compatibility functionality for future plugins.
* Feature Update!
** Updated the default Plugin Parameters for 'Command Window List' to include a 'CG Gallery', 'Credits Page', and 'Patch Notes' command.
*** This is for the upcoming VisuStella MZ plugins.
*** Projects with the Main Menu Core already installed will not have this update, but you can copy over the settings from a new project with the following steps:
**** Create a new project. Install Main Menu Core. Open up the new project's 'Command Window List'. Right click the 'cgGallery', 'creditsPage', or 'patchNotes' option(s) and click copy. Go to the target project's Main Menu Core's 'Command Window List' plugin parameter. Paste the command where you want it to go.

Version 1.18: October 27, 2022
* Compatibility Update!
** Added compatibility functionality for future plugins.
* Documentation Update!
** Help file updated for new features.
** Added a new section into Plugin Parameters: Command Window List for "Subcategories" and adding info on how they are handled.
* Feature Update!
** Updated the default Plugin Parameters for 'Command Window List' to include a 'Tutorial List' command.
*** This is for the upcoming VisuMZ_2_TutorialPanelSys plugin.
*** Projects with the Main Menu Core already installed will not have this update, but you can copy over the settings from a new project with the following steps:
**** Create a new project. Install Main Menu Core. Open up the new project's 'Command Window List'. Right click the 'tutorialList' option and click copy. Go to the target project's Main Menu Core's 'Command Window List' plugin parameter. Paste the command where you want it to go.
** Subcategory called "Datalog" is now added.
*** Projects with the Main Menu Core already installed will not have this update, but you can copy over the settings from a new project with the following steps:
**** Create a new project. Install Main Menu Core. Open up the new project's 'Command Window List'. Right click the 'subcategory' option and click copy. Go to the target project's Main Menu Core's 'Command Window List' plugin parameter. Paste the command where you want it to go.
**** Existing entries for Quest, Message Log, and Combat Log are now added to the Datalog subcategory.
* New Features!
** Subcategory support is now added for the Main Menu Command Window.
*** Subcategories allow you to make some Command Window items invisible until a subcategory is selected. This helps reduce clutter and save room on the Command Window command list.

Version 1.17: August 18, 2022
* Bug Fixes!
** Changed actor graphics now reflect properly for those using the default status menu. Fix made by Irina.

Version 1.16: April 21, 2022
* Documentation Update!
** Help file updated for new features.
* New Features!
** New Plugin Commands added by Arisu and sponsored by AndyL:
*** Menu Command: Clear Forced Settings
*** Menu Command: Force Disable
*** Menu Command: Force Enable
*** Menu Command: Force Hide
*** Menu Command: Force Show
**** These new Plugin Commands allow you to forcefully show, hide, enable, or disable Menu Commands regardless of their required settings.
**** We are not responsible for errors that occur by accessing menus that should otherwise be disabled or hidden.

Version 1.15: February 10, 2022
* Optimization Update!
** Plugin should run more optimized.

Version 1.14: October 25, 2021
* Bug Fixes!
** Plugin Parameter settings for automatic Command Window height adjustment should now work properly. Fix made by Irina.
* Documentation Update!
** Added a note for the Help File: Gold Window > Thinner Gold Window
*** Only applies to the Command Window style: Default Vertical.

Version 1.13: October 21, 2021
* Feature Update!
** Rounding update applied to picture portraits so that coordinates aren't drawn on non-whole numbers due to base images having odd values. Update made by Olivia.

Version 1.12: July 16, 2021
* Compatibility Update!
** Added compatibility functionality for future plugins.
* Feature Update!
** Updated the default Plugin Parameters for 'Command Window List' to include a 'Message Log' command.
*** This is for the upcoming VisuMZ_3_MessageLog plugin.
*** Projects with the Main Menu Core already installed will not have this update, but you can copy over the settings from a new project with the following steps:
**** Create a new project. Install Main Menu Core. Open up the new project's 'Command Window List'. Right click the 'MessageLog' option and click copy. Go to the target project's Main Menu Core's 'Command Window List' plugin parameter. Paste the command where you want it to go.

Version 1.11: May 14, 2021
* Feature Update!
** Updated the default Plugin Parameters for 'Command Window List' to include a 'Load' command after the 'Save' command.
*** This allows players to access the load game screen from the Main Menu.
*** Projects with the Main Menu Core already installed will not have this update, but you can copy over the settings from a new project with the following steps:
**** Create a new project. Install Main Menu Core. Open up the new project's 'Command Window List'. Right click the 'Load' option and click copy. Go to the target project's Main Menu Core's 'Command Window List' plugin parameter. Paste the command where you want it to go.

Version 1.10: April 16, 2021
* Feature Update!
** Default style for List Styles now have its code updated with the JS: Default plugin parameter for games whose vertical screen resolution is larger than normal.
*** To update this, do either of the following:
**** Open up the Main Menu Core Plugin Parameters. Select and press delete on "List Style Settings". Press Enter. New updated settings will be replaced for the JS: Default settings.
**** Or Delete the existing VisuMZ_1_MainMenuCore.js in the Plugin Manager list and install the newest version.

Version 1.09: March 19, 2021
* Documentation Update!
** Added clarity for the "Portrait Style" in Plugin Parameters section for "Status Graphic, Status List Style, & List Style Settings":
*** If there is no Menu Image used, this will switch over to the Vertical Style and use a face graphic instead.

Version 1.08: February 26, 2021
* Feature Update!
** Default Plugin Parameters for the List Style Settings defaults have been updated with tighter coordinate values to allow for more accurate display of UI element positioning. Update made by Olivia.

Version 1.07: January 1, 2021
* Documentation Update!
** Added documentation for new feature(s)!
** Removed "<Menu Image: filename>" version of notetag to reduce confusion and to stick with the norm declared by the Battle Core.
* New Features!
** New notetags added by Yanfly:
*** <Menu Portrait Offset: +x, +y>
*** <Menu Portrait Offset X: +x>
*** <Menu Portrait Offset Y: +y>
**** This is used with the "Portrait" style Main Menu list.
**** Offsets the X and Y coordinates for the menu portrait.

Version 1.06: December 11, 2020
* Compatibility Update!
** Added compatibility functionality for future plugins.

Version 1.05: October 11, 2020
* Documentation Update!
** Documentation added for the new plugin parameter.
* New Features!
** New plugin parameter added by Yanfly.
*** Plugin Parameters > General > Status Window > Select Last?
**** When picking a personal command from the Command Window, select the last picked actor or always the first?

Version 1.04: October 4, 2020
* Feature Update!
** Certain windows will now pre-load all associated image types for the actor upon being created to avoid custom JS drawing problems. Change made by Irina.
** Failsafes have been added to prevent non-existent variables from crashing the game if a user does not remove them from the variable list. Change made by Irina.

Version 1.03: September 20, 2020
* Documentation Update!
** Added the alternative notetag <Menu Portrait: filename> that also works the same way as <Menu Image: filename>.

Version 1.02: September 13, 2020
* Compatibility Update!
** Better compatibility for SV Actor graphics.

Version 1.01: August 23, 2020
* Bug Fixes!
** Skill check plugin parameter for show fixed. Fixed by Yanfly and Shaz.
*** Users updating from version 1.00 will need to fix this problem by either removing the plugin from the Plugin Manager list and reinstalling it, or going to Plugin Parameters > Command Window List > skill > JS: Show > and changing 'this.needsCommand("item")' to 'this.needsCommand("skill")'

Version 1.00: August 20, 2020
* Plugin released!

== See Also ==

* [[Inspiration Behind Wave 1]]

== End of File ==

|}


[[Category: RPG Maker MZ Core Plugins]]










[[Category: RPG Maker MZ Utility Plugins]]
[[Category: RPG Maker MZ Mechanical Plugins]]
[[Category: RPG Maker MZ Visual Plugins]]
[[Category: RPG Maker MZ Menu Plugins]]

[[Category: RPG Maker MZ Quality of Life Plugins]]

2024-05-28T12:46:09Z

Yanfly:

{| style="width: 100%;" cellspacing="5" cellpadding="0"

| colspan="99" style="padding: 20px; vertical-align: top; background: #363636;" |

{{TopBannerMain}}

{{Announcements}}

|-

| style="text-align: center; background: #252525; font-weight: bold; font-size: 120%" colspan="2" |
✨[[Featured Articles|Featured Article]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
🗳️Suggestion Box

|-

| style="padding: 20px; vertical-align: top; background: #363636;" colspan="2" |
{{Featured Article Automated}} 

| style="padding: 20px; text-align: center; vertical-align: top; background: #363636;" |
[[File:SuggestionBoxImage.png|300px|link=]]

[https://forms.gle/c9pbrqGbJCzWETC97 Suggestion Box (Graphics)]

[https://forms.gle/73bPT3nfXZFRn6BNA Suggestion Box (Plugins)]

|-

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[:Template:MainPageLatestPlugins|🖥️Latest Plugins]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[:Template:MainPageLatestAssets|🎨Latest Assets]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[:Template:MainPageLatestUpdates|📣Latest Updates]]

|-

| style="padding: 20px; text-align: center; vertical-align: top; background: #363636;" |
{{MainPageLatestPlugins}}

| style="padding: 20px; text-align: center; vertical-align: top; background: #363636;" |
{{MainPageLatestAssets}}

| style="padding: 20px; text-align: center; vertical-align: top; background: #363636;" |
{{MainPageLatestUpdates}}

|-

| style="text-align: center; vertical-align: top; background: #363636;" |
📦[[Template:MainPageLatestPlugins|View Archives]]

| style="text-align: center; vertical-align: top; background: #363636;" |
🖼️[[Template:MainPageLatestAssets|View Archives]]

| style="text-align: center; vertical-align: top; background: #363636;" |
📚[[Template:MainPageLatestUpdates|View Archives]]

|-

| colspan="3" style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
🤝Affiliates

|-

| colspan="3" style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
{{MainPageAffiliatesHorz}}

|-

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[How to Install Plugins (RPG Maker MZ)|🖥️Installing Plugins]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[How to Update Plugins RPG Maker MZ|🔄Updating Plugins]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[Troubleshooting Plugins RPG Maker MZ|🕵️Troubleshooting]]

|-

| style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
[[File:InstallPluginsMz.png|x150px|link=How to Install Plugins (RPG Maker MZ)]]

[[How to Install Plugins (RPG Maker MZ)|Click here]] for help on how to install plugins<br>and an explanation on the Tier Hierarchy System.

| style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
[[File:UpdatePlugins.png|x150px|link=How to Update Plugins RPG Maker MZ]]

[[How to Update Plugins RPG Maker MZ|Click here]] to learn how to update plugins.

| style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
[[File:Troubleshooting.jpg|x150px|link=Troubleshooting Plugins (RPG_Maker_MZ)]]

[[Troubleshooting Plugins (RPG_Maker_MZ)|Click here]] for how to troubleshoot plugins if you get an error.

|-

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[VisuStella Sample Game Project|🌻VisuStella MZ Sample Project]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[VisuStella MZ|🎭VisuStella MZ Plugin Library]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[:Category:Yanfly_Engine_Plugins|🐇Yanfly Engine Plugins (MV)]]

|-

| style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
[[File:VisuMzSample.png|300px|link=VisuStella Sample Game Project]]

| style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
[[File:VisuMzPlugins.png|300px|link=VisuStella MZ]]

| style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
[[File:YepLibrary.png|300px|link=Category:Yanfly_Engine_Plugins]]

|-

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[Fallen Angel Olivia|👼Fallen Angel Olivia (MV)]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[Atelier Irina|👓Atelier Irina (MV)]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[Arisu's Dollhouse|🎎Arisu's Dollhouse (MV)]]

|-

| style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
<html><a href='http://www.yanfly.moe/wiki/Fallen_Angel_Olivia'><img src='http://yanfly.moe/img/sidebar/OliviaLink.gif' width="300"></a></html>

| style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
<html><a href='http://www.yanfly.moe/wiki/Atelier_Irina'><img src='http://yanfly.moe/img/sidebar/IrinaSide.gif' width="300"></a></html>

| style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
<html><a href='http://www.yanfly.moe/wiki/Arisu%27s_Dollhouse'><img src='http://yanfly.moe/img/sidebar/ArisuSidebar.gif' width="300"></a></html>

|-

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[:Template:MainPageArticlesRpgMaker|🏰RPG Maker Articles]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[:Template:MainPageArticlesPlugins|🛠️Plugin Articles]]

| style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
[[:Template:MainPageArticlesVisuStella|🎭VisuStella Articles]]

|-

| style="padding: 20px; vertical-align: top; background: #363636;" |
{{MainPageArticlesRpgMaker}}

| style="padding: 20px; vertical-align: top; background: #363636;" |
{{MainPageArticlesPlugins}}

| style="padding: 20px; vertical-align: top; background: #363636;" |
{{MainPageArticlesVisuStella}}

|-

| colspan="3" style="width: 33%; text-align: center; background: #252525; font-weight: bold; font-size: 120%" |
🤝Affiliates

|-

| colspan="3" style="padding: 20px; vertical-align: top; background: #363636; text-align: center" |
{{MainPageAffiliatesHorz}}

<html><script type="text/javascript" src="https://www.free-counters.org/count/dg89"></script><br>
<a href='https://www.acadoo.de/'>Masterarbeit Writer</a> <script type='text/javascript' src='https://whomania.com/ctr?id=6bff02d7f5f798a6aa28f3a03024fdfe889d95d5'></script></html>

|-

| colspan="99" style="padding: 20px; vertical-align: top; background: #363636;" |

<div style="margin-right: 10px; text-align: right; font-style: italic; font-size: 85%;">Happy RPG Making!
<br><br>[[Sandbox]]</div>

|}