Yanfly

Developer
  • Content count

    1,669
  • Joined

  • Last visited

About Yanfly

  • Rank

Profile Information

  • Gender Not Telling
  • Primarily Uses RMMV

Recent Profile Visitors

15,909 profile views
  1. Thanks Talonos! I'll get this fixed! --- Thanks, I'll get this fixed, too! --- Thanks, I'll get this fixed. --- Please remake the download file. I'm not getting any kind of RM project file with this. --- A touch input means by mouse click or smartphone touch, yes. --- WHY I NEED A CLEAN SAMPLE PROJECT FOR BUG REPORTS: If you're wondering why I make it an absolute requirement for sample projects containing to be made, it's because in the past, I've chased and hunted bugs that do not exist either because a user had a conflicting error with a non-Yanfly plugin, has not updated the plugins, using the plugin incorrectly, or think something is a bug when it really isn't. The amount of time I've wasted chasing these "bugs" is unfathomable as that time could have been spent developing new content. To mitigate this issue, I made it an absolute requirement for bugs to be reported in such a manner because of the following: It makes the user go through all of the troubleshooting steps to reduce the amount of user errors. If the user identifies it as a user error, then the user would also have gained troubleshooting skills, which are essential for game development. If you cannot be bothered to learn how to troubleshoot, I'm afraid RPG Maker will be giving you a whole lot more stress later on. Isolate the bugs caused by Yanfly plugins away from non-Yanfly plugins. As stated above, I do not provide support for non-Yanfly plugins due to my lack of time to create compatibility patches for non-Yanfly plugins. Having over 100+ plugins, making a compatibility patch for each one of those with every other plugin out there is absolute insanity. It shows that the user is serious about getting the bug fixed as I am. Being able to put out time to isolate a problem so it can be fixed means the user is serious about getting their game made. If you are not serious about getting a bug fixed for your game, then I have no reason to be serious about getting it fixed for you. As a user's time is important to them, my time is also important to me, and this is our mutual agreement to get things done cooperatively. Thank you for understanding.
  2. Did you invent this? https://twitter.com/bunnybuddhism


     

     

    1. ALTERED STATE 🍕

      ALTERED STATE 🍕

      Another mystery of Yanfly revealed!

  3. Thanks, I'll get this fixed. Keep an eye out for the update this weekend. (sorry I have PM's disabled) --- I'm afraid I can't provide much help here. FPS Synch is one of those plugins that should never have to been made as it's done primarily to correct the fluid timesteps implementation for the MV source code. My only suggestion to you is to simply not include this plugin when making your deployment for iOS. --- This is not a bug. This is because MV doesn't support decimals for HP values, hence why it ends up like this.
  4. Do you have any plans for releasing a Neo Tactical Battle System for MV?

     

    My project kind of hinges on it. What if I paid you? 

     

    Shoot me a message. I know you were tinkering with something a while back and I really want it.

     

    neo_tactical1.jpg?w=593

    1. Kes

      Kes

      This is not the sort of query which can be done by Status Updates, which are meant more for exchanges of bits of info, random thoughts etc.  Please do not try and do commissions this way.  If you want to try and commission Yanfly, then the most appropriate way would be by pm.

    2. RetroBoy

      RetroBoy

      I can't PM him or I would have.

       

      Though luck, I found this:

      Which is really promising for now.

    3. Engr. Adiktuzmiko

      Engr. Adiktuzmiko

      I just tried it an I can compose a message and choose Yanfly as the receipient

  5. YEP.122 - Extended Doodad Pack 1 - RPG Maker MV This plugin allows you to add more options to the settings menu in the doodads editor. This allows you to set the tone for doodads to change them into colors that hues will not allow, the option for doodads to appear under certain switch conditions, whether or not party members have joined. You can grab the plugin here: Yanfly.moe: http://yanfly.moe/2016/12/17/yep-122-extended-doodad-pack-1-rpg-maker-mv/
  6. Follow the bug reporting guidelines that are shown on the front post, the top post of each thread, and the post linked to from Yanfly.moe: NOTE: Read this before submitting a bug report on this thread: I will only support my own plugins and code that I, myself have provided. If there are bugs with other people's plugins and/or bugs with the RPG Maker MV base code itself, I am not responsible for it. Report it in their own threads if it is a bug for their plugin or the official bug report forum if it is a bug with the RPG Maker MV base code. I am not responsible for bugs created by plugins created by other makers. There will be no compatibility patches made between my plugins and non-YEP plugins. This is not because I disrespect other plugin makers. If I did, I wouldn't go so far as to maximize compatibility with my plugins when possible. The reason behind this is because of my lack of time, and I'd like to put my undivided attention to errors caused by my own plugins. I am not responsible for any Lunatic Mode that you, yourself, have made. If you have created your own Lunatic Mode code that isn't running, go visit the JavaScript Support Forum instead. I am not obligated to explain to you how to code in JavaScript. There are plenty places online to learn it but this thread is not that place. I am not obligated to explain to you how to use all the various functions inside of my plugins. If a function added by my plugins is not listed in the Help File, it means I do not deem that function to be used for script calls. Therefore, if you choose a function outside of the ones listed in the help files to use in a script call, I am NOT responsible for it not working properly for you. No script call support will be provided for functions not listed within the help file. I am not going to "fix" my plugins to work with the Exclude unused files feature that comes with RPG Maker MV. The feature exists primarily for games that don't use plugins or games that use plugins that do not reference other game files. Read about it here in detail. ALL bug reports MUST follow these guidelines and use this template: Plugin Name: (What is the name of the plugin?) Do you have all the latest updates for the plugins in question? (Click here for all of the latest updates and install them. If you do not have the latest updates, I will ask you to remake the bug report) Plugin Parameter Changes: (Mention ALL of the changes you've made to the plugin's parameters. Otherwise, I will revert every single plugin's settings to the default setting) Bug Explanation: (What is the bug in your own words? Keep this detailed. "It isn't working right" is not a valid bug report.) Create a Sample Project Reproducing the bug: The sample project MUST follow all of these guidelines: Create a new project. Do NOT just copy over your game project folders. This should be just a stock, empty, new RPG Maker MV project. If I do not see an empty project with Harold, Therese, Marsha, and Lucius, I will not look any further. The project's file size must be 200 MB or LESS. Remove unnecessary audio and image files until you reach that size or use MV Stripper if you need help doing so. Install -only- the affected plugins. Do NOT copy/paste them over from your project's Plugin Manager. If you're using non-YEP plugins, do NOT include them. That said, I apologize that both ATB and CTB are no longer supported by Yanfly, so if you're using them, please remove them from the project used for the bug report. Do -NOT- rename the plugins' filenames. They will not work if you do so. MAKE SURE you DO NOT change the filename from the file downloaded from the website. Make sure they're in the EXACT order listed on Yanfly.moe. The correct ordering of plugins is important. Some plugins will not work if they aren't in the right order. Do -NOT- deploy the project through File > Deployment. Do -NOT- box the sample project. If I cannot open up the sample project when I get it, you will have to redo it all. Error Report: (If you received an error message, press F8 when the message is received to open up the debug console, then copy/paste the entire error log and paste it here). Exact Steps on How to Replicate Bug: (Write out IN DETAIL, a step-by-step guide on how to replicate the bug.) Did you recreate the bug on the sample project? (If not, do so. MAKE SURE you are using notetags in the right place and haven't misspelled anything. DO NOT USE SAVES. I need to know exactly how to recreate the problem from start to finish. Simply giving me a save file tells me nothing.) Upload the sample project and share the link (ABSOLUTELY REQUIRED): Use WinZip or WinRAR to archive the project. Do -NOT- archive it multiple times. Upload it on a website like Mediafire.com or Dropbox. Do -NOT- use a website that involves timers like 4shared, RapidShare, etc. If I am time-gated from downloading the project, I will ask you to reupload it somewhere else. Post the link here. If you do not include a sample project that meets these guidelines, the bug report will be invalid. There are NO exceptions. --- Unfortunately, this is an issue with Wordpress that I use for the site. :/ They auto convert the ' into a different quote type. Thanks for bringing it up though! --- If it's performance related, be sure to check the MV source code differences to see if everything matches up. Also, try disabling other non-Yanfly plugins to see if they're conflicting. --- Lunatic Mode support isn't helped here, I'm sorry. From the front post, the top post of each thread, and the post linked to from Yanfly.moe: I am not responsible for any Lunatic Mode that you, yourself, have made. If you have created your own Lunatic Mode code that isn't running, go visit the JavaScript Support Forum instead.
  7. Thanks, for the reupload. This appears to be a loading issue as the weapon sheet sizes are rather big. I'll have to work in a way to get these assets loaded early. --- From the front page, the bug report page, and everything else NOTE: Read this before submitting a bug report on this thread: I will only support my own plugins and code that I, myself have provided. If there are bugs with other people's plugins and/or bugs with the RPG Maker MV base code itself, I am not responsible for it. Report it in their own threads if it is a bug for their plugin or the official bug report forum if it is a bug with the RPG Maker MV base code. I am not responsible for bugs created by plugins created by other makers. There will be no compatibility patches made between my plugins and non-YEP plugins. This is not because I disrespect other plugin makers. If I did, I wouldn't go so far as to maximize compatibility with my plugins when possible. The reason behind this is because of my lack of time, and I'd like to put my undivided attention to errors caused by my own plugins. I am not responsible for any Lunatic Mode that you, yourself, have made. If you have created your own Lunatic Mode code that isn't running, go visit the JavaScript Support Forum instead. I am not obligated to explain to you how to code in JavaScript. There are plenty places online to learn it but this thread is not that place. I am not obligated to explain to you how to use all the various functions inside of my plugins. If a function added by my plugins is not listed in the Help File, it means I do not deem that function to be used for script calls. Therefore, if you choose a function outside of the ones listed in the help files to use in a script call, I am NOT responsible for it not working properly for you. No script call support will be provided for functions not listed within the help file. I am not going to "fix" my plugins to work with the Exclude unused files feature that comes with RPG Maker MV. The feature exists primarily for games that don't use plugins or games that use plugins that do not reference other game files. Read about it here in detail. ALL bug reports MUST follow these guidelines and use this template: Plugin Name: (What is the name of the plugin?) Do you have all the latest updates for the plugins in question? (Click here for all of the latest updates and install them. If you do not have the latest updates, I will ask you to remake the bug report) Plugin Parameter Changes: (Mention ALL of the changes you've made to the plugin's parameters. Otherwise, I will revert every single plugin's settings to the default setting) Bug Explanation: (What is the bug in your own words? Keep this detailed. "It isn't working right" is not a valid bug report.) Create a Sample Project Reproducing the bug: The sample project MUST follow all of these guidelines: Create a new project. Do NOT just copy over your game project folders. This should be just a stock, empty, new RPG Maker MV project. If I do not see an empty project with Harold, Therese, Marsha, and Lucius, I will not look any further. The project's file size must be 200 MB or LESS. Remove unnecessary audio and image files until you reach that size or use MV Stripper if you need help doing so. Install -only- the affected plugins. Do NOT copy/paste them over from your project's Plugin Manager. If you're using non-YEP plugins, do NOT include them. That said, I apologize that both ATB and CTB are no longer supported by Yanfly, so if you're using them, please remove them from the project used for the bug report. Do -NOT- rename the plugins' filenames. They will not work if you do so. MAKE SURE you DO NOT change the filename from the file downloaded from the website. Make sure they're in the EXACT order listed on Yanfly.moe. The correct ordering of plugins is important. Some plugins will not work if they aren't in the right order. Do -NOT- deploy the project through File > Deployment. Do -NOT- box the sample project. If I cannot open up the sample project when I get it, you will have to redo it all. Error Report: (If you received an error message, press F8 when the message is received to open up the debug console, then copy/paste the entire error log and paste it here). Exact Steps on How to Replicate Bug: (Write out IN DETAIL, a step-by-step guide on how to replicate the bug.) Did you recreate the bug on the sample project? (If not, do so. MAKE SURE you are using notetags in the right place and haven't misspelled anything. DO NOT USE SAVES. I need to know exactly how to recreate the problem from start to finish. Simply giving me a save file tells me nothing.) Upload the sample project and share the link (ABSOLUTELY REQUIRED): Use WinZip or WinRAR to archive the project. Do -NOT- archive it multiple times. Upload it on a website like Mediafire.com or Dropbox. Do -NOT- use a website that involves timers like 4shared, RapidShare, etc. If I am time-gated from downloading the project, I will ask you to reupload it somewhere else. Post the link here. If you do not include a sample project that meets these guidelines, the bug report will be invalid. There are NO exceptions. WHY I NEED A CLEAN SAMPLE PROJECT FOR BUG REPORTS: If you're wondering why I make it an absolute requirement for sample projects containing to be made, it's because in the past, I've chased and hunted bugs that do not exist either because a user had a conflicting error with a non-Yanfly plugin, has not updated the plugins, using the plugin incorrectly, or think something is a bug when it really isn't. The amount of time I've wasted chasing these "bugs" is unfathomable as that time could have been spent developing new content. To mitigate this issue, I made it an absolute requirement for bugs to be reported in such a manner because of the following: It makes the user go through all of the troubleshooting steps to reduce the amount of user errors. If the user identifies it as a user error, then the user would also have gained troubleshooting skills, which are essential for game development. If you cannot be bothered to learn how to troubleshoot, I'm afraid RPG Maker will be giving you a whole lot more stress later on. Isolate the bugs caused by Yanfly plugins away from non-Yanfly plugins. As stated above, I do not provide support for non-Yanfly plugins due to my lack of time to create compatibility patches for non-Yanfly plugins. Having over 100+ plugins, making a compatibility patch for each one of those with every other plugin out there is absolute insanity. It shows that the user is serious about getting the bug fixed as I am. Being able to put out time to isolate a problem so it can be fixed means the user is serious about getting their game made. If you are not serious about getting a bug fixed for your game, then I have no reason to be serious about getting it fixed for you. As a user's time is important to them, my time is also important to me, and this is our mutual agreement to get things done cooperatively. Thank you for understanding. --- Sorry, but you're on your own for that one. You'll have to keep track of everything you use yourself. There's no tool currently that keeps track of everything. You'll have to go through each and everything facet of your game one by one and see what's needed. It will take time, but it will have to be done. --- That's something you have to keep track of yourself. You're the one who needs to manage your own game's assets and everything. Go through each and everything facet of your game one by one and see what's needed. It will take time, but it will have to be done.
  8. FREQUENTLY ASKED QUESTION Q: How come when I deploy my game, files are missing? A: See below: To everybody who's using this feature and telling me my plugins aren't working after putting them online or whatever, stop using it. That is the cause of all those problems for your deployment/export/whatever you call it. The feature exists primarily for games that don't use plugins or games that use plugins that do not reference other game files. If you plan to use that "feature" while using my plugins that alter or reference files, then you will encounter problems. If you absolutely have to use it for whatever reason, then I'm afraid it's better for you to not use my plugins or any plugins that require flexible referencing. --- Also, yes, I'm aware that in RPG Maker MV's help file, there's a [Exclude unused files] Plugin Configuration option. Guess what? If you read through it indepth, you'll realize that not everything will work properly because I choose to give you, as the users, flexibility over what folders and file types can and can't be used. For plugin parameters: * @param ME * @desc The ME name for sample music effect. * @default Organ * @require 1 * @dir audio/me/ * @type file That does not accommodate for flexible directory referencing. For notetags: * @noteParam sampleImage * @noteRequire 1 * @noteDir img/sample/ * @noteType file * @noteData items That does not allow for flexible notetag creation. It is only usable with the default system of notetags, which are inflexible, case sensitive, and not user friendly. --- This is not a matter of me being lazy to fix the problems it has with my plugins. This is a matter of the fact that the "exclusion rules" they add do not comply with the way I create plugins that are made to be user-friendly.
  9. Thanks for finding these! I'll get them fixed for the next patch update! --- I'm missing the sprite sheet to test this properly. --- From the various pages: NOTE: Read this before submitting a bug report on this thread: I will only support my own plugins and code that I, myself have provided. If there are bugs with other people's plugins and/or bugs with the RPG Maker MV base code itself, I am not responsible for it. Report it in their own threads if it is a bug for their plugin or the official bug report forum if it is a bug with the RPG Maker MV base code. I am not responsible for bugs created by plugins created by other makers. There will be no compatibility patches made between my plugins and non-YEP plugins. This is not because I disrespect other plugin makers. If I did, I wouldn't go so far as to maximize compatibility with my plugins when possible. The reason behind this is because of my lack of time, and I'd like to put my undivided attention to errors caused by my own plugins. I am not responsible for any Lunatic Mode that you, yourself, have made. If you have created your own Lunatic Mode code that isn't running, go visit the JavaScript Support Forum instead. I am not obligated to explain to you how to code in JavaScript. There are plenty places online to learn it but this thread is not that place. I am not obligated to explain to you how to use all the various functions inside of my plugins. If a function added by my plugins is not listed in the Help File, it means I do not deem that function to be used for script calls. Therefore, if you choose a function outside of the ones listed in the help files to use in a script call, I am NOT responsible for it not working properly for you. No script call support will be provided for functions not listed within the help file. --- There is nothing my plugins can do to fix this. You have to fix this issue yourself after you've deployed your game and modify the json file signifying what window resolution you want it to use. --- ...I need to seriously add this to the FAQ: Stop using the exclude unused files when exporting.
  10. I'll have to take a look at this in depth. It'll have to be a fix I'll have to get into for the following week. --- Please don't initiate with this kind of attitude. Especially since I've stated at the very first post of this thread: THIS THREAD WILL BE USED FOR PLUGIN UPDATES, NEW YEP VIDEOS, AND BUG REPORTS! This thread is NOT a request thread. Requests include new plugins, new features for existing plugins, and features that you personally think should exist but currently do not. If you want requests, visit the proper subforum for it; this thread is not the place to do so. I do not take requests. Nobody gets a special service here. This goes for regular users, patrons, moderators, and even friends. The request forum is for other people to take on the requests. I am not the only person who is capable of creating plugins. There are plenty of people who are as capable and more capable than me for plugin creation.
  11. Can you place this into a ZIP or RAR and the upload it? I'm not going to download each and every single file individually. --- This is not a bug. However, I'm glad you figured it out for your project.
  12. YEP.121 - Map Select Equip - RPG Maker MV The Select Item event in RPG Maker MV does what it's supposed to: selects an item and then binds the value to a variable. However, it lacks the ability to allow the player to select weapons, armors, or both. This plugin gives you the functionality of selecting an equip and binding the ID of the equip to a variable. You can grab the plugin here: Yanfly.moe: http://yanfly.moe/2016/12/03/yep-121-map-select-equip-rpg-maker-mv/
  13. If you don't save immediately after you make plugin settings and go straight to battle test, nothing changes. This is explained here: BASIC TROUBLE SHOOTING 1. Are all your plugins up to date? If they're not, download the updated versions from here: http://yanfly.moe/yep/changelog/ 2. Did you rename any of their plugins from their default filenames? If you did, then the plugins won't work. Do NOT rename them. 3. Did you make sure all of the plugins are placed in order as http://yanfly.moe/yep/ inside of the Plugin Manager? 4. When you updated the plugin, did you /open up/ the plugin within the Plugin Manager? You are getting the error because you updated the plugin and did not go into the plugin itself like the instructions here in the first video: http://yanfly.moe/yep/changelog/ Why is this important? Because whenever new parameters are added to a plugin upon a new update, you have to enter the plugin in order for the Plugin Manager to add those new parameters into your game. Otherwise, you will get undefined errors and "random" crashes. Skipping that step is not optional and is very crucial to getting updated plugins to work. 5. If you are using non-Yanfly plugins, turn off ALL of the non-Yanfly plugins to see if there are any conflicts. 6. If you are testing your project in Battle Test and aren't seeing any changes made after updating your plugin, make sure you -save- your project. RPG Maker MV does not carry over changes to Battle Test until you save your project.
  14. New arrangements have been made to the bug report guidelines. Too many people have been omitting too many steps far too many times. NOTE: Read this before submitting a bug report on this thread: I will only support my own plugins and code that I, myself have provided. If there are bugs with other people's plugins and/or bugs with the RPG Maker MV base code itself, I am not responsible for it. Report it in their own threads if it is a bug for their plugin or the official bug report forum if it is a bug with the RPG Maker MV base code. I am not responsible for bugs created by plugins created by other makers. There will be no compatibility patches made between my plugins and non-YEP plugins. This is not because I disrespect other plugin makers. If I did, I wouldn't go so far as to maximize compatibility with my plugins when possible. The reason behind this is because of my lack of time, and I'd like to put my undivided attention to errors caused by my own plugins. I am not responsible for any Lunatic Mode that you, yourself, have made. If you have created your own Lunatic Mode code that isn't running, go visit the JavaScript Support Forum instead. I am not obligated to explain to you how to code in JavaScript. There are plenty places online to learn it but this thread is not that place. I am not obligated to explain to you how to use all the various functions inside of my plugins. If a function added by my plugins is not listed in the Help File, it means I do not deem that function to be used for script calls. Therefore, if you choose a function outside of the ones listed in the help files to use in a script call, I am NOT responsible for it not working properly for you. No script call support will be provided for functions not listed within the help file. ALL bug reports MUST follow these guidelines and use this template: Plugin Name: (What is the name of the plugin?) Do you have all the latest updates for the plugins in question? (Click here for all of the latest updates and install them. If you do not have the latest updates, I will ask you to remake the bug report) Plugin Parameter Changes: (Mention ALL of the changes you've made to the plugin's parameters. Otherwise, I will revert every single plugin's settings to the default setting) Bug Explanation: (What is the bug in your own words? Keep this detailed. "It isn't working right" is not a valid bug report.) Create a Sample Project Reproducing the bug: The sample project MUST follow all of these guidelines: Create a new project. Do NOT just copy over your game project folders. This should be just a stock, empty, new RPG Maker MV project. If I do not see an empty project with Harold, Therese, Marsha, and Lucius, I will not look any further. The project's file size must be 200 MB or LESS. Remove unnecessary audio and image files until you reach that size or use MV Stripper if you need help doing so. Install -only- the affected plugins. Do NOT copy/paste them over from your project's Plugin Manager. If you're using non-YEP plugins, do NOT include them. That said, I apologize that both ATB and CTB are no longer supported by Yanfly, so if you're using them, please remove them from the project used for the bug report. Do -NOT- rename the plugins' filenames. They will not work if you do so. MAKE SURE you DO NOT change the filename from the file downloaded from the website. Make sure they're in the EXACT order listed on Yanfly.moe. The correct ordering of plugins is important. Some plugins will not work if they aren't in the right order. Do -NOT- deploy the project through File > Deployment. Do -NOT- box the sample project. If I cannot open up the sample project when I get it, you will have to redo it all. Error Report: (If you received an error message, press F8 when the message is received to open up the debug console, then copy/paste the entire error log and paste it here). Exact Steps on How to Replicate Bug: (Write out IN DETAIL, a step-by-step guide on how to replicate the bug.) Did you recreate the bug on the sample project? (If not, do so. MAKE SURE you are using notetags in the right place and haven't misspelled anything. DO NOT USE SAVES. I need to know exactly how to recreate the problem from start to finish. Simply giving me a save file tells me nothing.) Upload the sample project and share the link (ABSOLUTELY REQUIRED): Use WinZip or WinRAR to archive the project. Do -NOT- archive it multiple times. Upload it on a website like Mediafire.com or Dropbox. Do -NOT- use a website that involves timers like 4shared, RapidShare, etc. If I am time-gated from downloading the project, I will ask you to reupload it somewhere else. Post the link here. If you do not include a sample project that meets these guidelines, the bug report will be invalid. There are NO exceptions. WHY I NEED A CLEAN SAMPLE PROJECT FOR BUG REPORTS: If you're wondering why I make it an absolute requirement for sample projects containing to be made, it's because in the past, I've chased and hunted bugs that do not exist either because a user had a conflicting error with a non-Yanfly plugin, has not updated the plugins, using the plugin incorrectly, or think something is a bug when it really isn't. The amount of time I've wasted chasing these "bugs" is unfathomable as that time could have been spent developing new content. To mitigate this issue, I made it an absolute requirement for bugs to be reported in such a manner because of the following: It makes the user go through all of the troubleshooting steps to reduce the amount of user errors. If the user identifies it as a user error, then the user would also have gained troubleshooting skills, which are essential for game development. If you cannot be bothered to learn how to troubleshoot, I'm afraid RPG Maker will be giving you a whole lot more stress later on. Isolate the bugs caused by Yanfly plugins away from non-Yanfly plugins. As stated above, I do not provide support for non-Yanfly plugins due to my lack of time to create compatibility patches for non-Yanfly plugins. Having over 100+ plugins, making a compatibility patch for each one of those with every other plugin out there is absolute insanity. It shows that the user is serious about getting the bug fixed as I am. Being able to put out time to isolate a problem so it can be fixed means the user is serious about getting their game made. If you are not serious about getting a bug fixed for your game, then I have no reason to be serious about getting it fixed for you. As a user's time is important to them, my time is also important to me, and this is our mutual agreement to get things done cooperatively. Thank you for understanding. BASIC TROUBLE SHOOTING 1. Are all your plugins up to date? If they're not, download the updated versions from here: http://yanfly.moe/yep/changelog/ 2. Did you rename any of their plugins from their default filenames? If you did, then the plugins won't work. Do NOT rename them. 3. Did you make sure all of the plugins are placed in order as http://yanfly.moe/yep/ inside of the Plugin Manager? 4. When you updated the plugin, did you /open up/ the plugin within the Plugin Manager? You are getting the error because you updated the plugin and did not go into the plugin itself like the instructions here in the first video: http://yanfly.moe/yep/changelog/ Why is this important? Because whenever new parameters are added to a plugin upon a new update, you have to enter the plugin in order for the Plugin Manager to add those new parameters into your game. Otherwise, you will get undefined errors and "random" crashes. Skipping that step is not optional and is very crucial to getting updated plugins to work. 5. If you are using non-Yanfly plugins, turn off ALL of the non-Yanfly plugins to see if there are any conflicts. 6. If you are testing your project in Battle Test and aren't seeing any changes made after updating your plugin, make sure you -save- your project. RPG Maker MV does not carry over changes to Battle Test until you save your project. F.A.Q. ABOUT ATB AND CTB PLUGINS The ATB and CTB plugins are custom battle systems that do NOT involve a turn-based system that you're used to with the default turn-based battle system (DTB). They function off of a tick-based system, which means it does not work off standard means. This also means you have to adjust either the plugin or your game to fit these means. Here are some frequently reported "issues" with the system. None of these are bugs so do not report them as bugs. If ATB bars are taking too long to fill up, then change your battlers' AGI values to higher or change the plugin parameters to fit your game. If ATB states are dropping in turns too quickly, this is because you didn't adjust the proper state turn settings within the Battle Engine Core to fit your game. For ATB, no, I will NOT make Active Mode. It's not because I can't (I've made it before in VX's Yanfly Engine Melody). It's because RPG Maker MV's code structure for the battle system makes it more likely to break everything if it does so. If this is something you absolutely need, the Plugin Request Forum is your place to visit, if DoubleX RMMV Popularized ATB Core(which is at least compatible with my Battle Engine Core with the compatibility fix) can't meet your demands already. If there is "lag" between CTB turns, this isn't because of the plugin. This is because your low AGI values is making the game go through hundreds to thousands of CTB updates per tick. Once again, either you increase the AGI values or change the plugin parameters to fit your In CTB, States "skipping" multiple turns when updating isn't a bug. It is because in between the previous battler next battler, there was a huge gap in time, enough to go through two state turn cycles. Adjust the state turn settings within the Battle Engine Core to fit your game. For CTB, no, I will NOT make multiple instances of turn icons appearing for multiple actors. If you want something like that made, you can request it in the Plugin Request Forum. If all of these issues are beyond you, then I'm afraid the ATB and CTB plugins aren't for you. As a developer, it is your responsibility to understand the plugins and systems you are using. You are not doing your players any favor by using a system that you, yourself, do not fully comprehend. I will not educate anyone how ATB and CTB systems work. My plugins work based on the ATB and CTB systems of existing Final Fantasy games with slight tweaks to fit RPG Maker MV's system. Please study them on your own accord.