Welcome to PGMV! My goal is to make it easy for everyone to find and share great plugins for creating amazing games. As a plugin developer myself, I'm excited to grow this community with all of you.
HIME Custom Page Conditions - HIME_CustomPageConditions.js
Plugin desc : v1.6 - Create your own page conditions for your events using regular eventing!
License :
・Copyright: Retained
・Commercial Use: Allowed
・Modification: Allowed
・Redistribution: Allowed
・Details: See Download Page / In-plugin documentation
Author : Hime
Website : https://himeworks.com/
Desc page : https://himeworks.com/2015/10/custom-page-conditions-mv/
Download Page : https://raw.githubusercontent.com/munokura/HIME-MV-plugins-jp/master/HIME_CustomPageConditions.js
File name : HIME_CustomPageConditions.js
Help of plugin :
@title Custom Page Conditions
@author Hime --> HimeWorks (http://himeworks.com)
@version 1.6
@date Aug 20， 2020
@filename HIME_CustomPageConditions.js
@url http://himeworks.com/2015/10/custom-page-conditions-mv/
@plugindesc v1.6 - Create your own page conditions for your events using regular eventing!
@help
== Description ==
Events are a collection of pages. Depending on which page is active，
the event will appear and behave differently. To determine which page is
active， a set of page conditions are used. If all page conditions are met，
then that page can be activated.
By default， RPG Maker provides 5 different page conditions:
- Switch is ON
- Variable is at least a certain value
- self-switch is ON
- Party has an item
- Actor is in party
But if you wanted to have a different condition， you would need to find a
way to accomplish that using only these 5 conditions. This may involve using
parallel processes to check whether conditions are met， in order to turn
on a switch or change a variable.
This plugin provides you with an easy way to define your own page
conditions without having to come up with workarounds. If you want to
check whether you have a certain weapon or armor， or whether a given
combination of actors is in the party， you can directly specify this
in your event.
By using custom page conditions， it improves productivity and makes it
easier to manage your project.
== Terms of Use ==
- Free for use in non-commercial projects with credits
- Contact me for commercial use
== Change Log ==
1.6 - Aug 20， 2020
* support for MZ
1.5 - Apr 7， 2016
* Fixed bug where removing conditions from troop editor caused the
event to always run
1.4 - Feb 12， 2016
* Fixed issue where page conditions executed before map is set up
1.3 - Dec 14， 2015
* Fixed issue with self-switches
1.2 - Dec 5， 2015
* Added support for custom troop page conditions
1.1 - Dec 5， 2015
* Changed event condition processing to use an entire event list
1.0 - Oct 24， 2015
* Initial release
== Usage ==
To create a custom page condition， in your event， start by creating a
comment that reads
<page condition>
Then add any event commands that you would like to use as your page
condition.
In order to activate the page， you must use the plugin command
activate_page
Finally， end your page condition with a comment.
</page condition>
The page condition will not be executed as part of the regular event
processing.
- Custom Troop Page Conditions --
You can use custom page conditions for troops as well!
The instructions are the same as for a regular event: add the start comment，
write your logic， and then add an end comment.
However， note that troop events require one of the default page conditions to
be met. If you want it to run at anytime， reserve a switch that will always
be ON and then use that as the troop page condition.
-------------------------------------------------------------------------------
@command activate_page
@desc activates the page!
-------------------------------------------------------------------------------