Welcome to PGMZ! 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.
NRP Event Collision EX - NRP_EventCollisionEX.js
Plugin desc : v1.04 Extends the collision detection for events.
License :
・Copyright: Retained
・Commercial Use: Allowed
・Modification: Allowed
・Redistribution: Allowed
・Details: See Download Page / In-plugin documentation
Author : Takeshi Sunagawa (http://newrpg.seesaa.net/)
Website : https://github.com/NewRPGProject/MZMV_Plugin/blob/main/NRP_EventCollisionEX.js
Desc page : http://newrpg.seesaa.net/article/481944599.html
Download Page : https://raw.githubusercontent.com/NewRPGProject/MZMV_Plugin/main/NRP_EventCollisionEX.js
File name : NRP_EventCollisionEX.js
Help of plugin :
Extends the collision detection for events. * * This is useful for large objects and huge monsters. * It also extends the range of event execution by triggers. * * Note that only squares can be extended. * It does not support flexible changes such as circles and crosses. * * ■Usage * There are three ways to extend the event collision detection. * Please use the method that is easiest for you. * * ◆SettingList * You can register the target file and collision detection * in the plugin parameter SettingList. * This is convenient because you do not need to register each event. * * ◆Note Field * Please enter the following in the Note field of the event. * * <CollisionEX:?，?，?，?> * * Please set a numerical value in the ?. * The collision detection will be extended * in the following order: down， left， right， up. * * ◆Annotations * You can also enter the same information * in the annotation at the top of the event page. * You can switch the status of this annotation for each current page. * * In addition， the order of priority is "Annotations > Notes > SettingList". * Please note that if the event itself has a collision detection specification， * the contents registered in the SettingList will be ignored. * * ■Notice * This plugin has a relatively large impact. * In order to avoid conflicts， * it is recommended to place it as high up as possible. * * If normal movement of large events is not necessary， * turning off "ConsiderEventMove" may stabilize the situation. * * Also， the behavior near the boundary of a looping map is * I gave up on implementing it * because it was too complicated. Sorry....... * So， there is no collision detection for the part of the loop * that extends beyond the loop. * * [Terms] * There are no restrictions. * Modification， redistribution freedom， commercial availability， * and rights indication are also optional. * The author is not responsible， * but will deal with defects to the extent possible. * * @param ConsiderEventMove * @type boolean * @default true * @desc The collision detection is also calculated when a large event moves. Turning it off will reduce the processing. * * @param SettingList * @type struct<Setting>[] * @default [] * @desc List of settings related to collision detection.