[YEP] Yanfly Engine Plugins

Don't forget to check if there is still a problem first...

Plugin Name: YEP.1 Core Engine & YEP.14 Main Menu Manager


Bug Explanation: The error appeared after updating to 1.3.2. When I put a resolution bigger than 816x624 (1104x624 for example), part of the command window in the main menu seems cut (and the gold window too). I don't know what of the two plugins have the bug, but only appears with the combination of those two. I adressed an image of it:


Error Report: No error message.


Exact Steps on How to Replicate Bug: Open the game, then open the main menu and see the command window.


Sample Project (REQUIRED): YEP Bug report

This seems to be a new bug introduced by 1.3.2's changes to the WindowLayer. -_-


For this one, it's better if you reported it to the devs. There's nothing to really replicate with it by default, but the window mask layer is extending past where it should be.

Thanks, Yanfly. I already reported the issue in the support forums. I hope the devs can fix this without more problems.


@Yanfly I have found another issue, this one related to the fullscreen and the Core Engine (maybe it's related with the bug above).


Plugin Name: YEP.1 Core Engine


Bug Explanation: If you try to put the game in fullscreen with the YEP Core Engine enabled, the resolution of the game will be the same as in windowed mode, and the F3 key (to toggle stretch mode) don't work too.


Error Report: No error message.


Exact Steps on How to Replicate Bug: Open the game, and then try to put it in fullscreen mode with the F4 key.


Sample Project (REQUIRED): Fullscreen bug report (it's the same demo as above).

Thanks, Yanfly. I already reported the issue in the support forums. I hope the devs can fix this without more problems.


@Yanfly I have found another issue, this one related to the fullscreen and the Core Engine (maybe it's related with the bug above).


Plugin Name: YEP.1 Core Engine


Bug Explanation: If you try to put the game in fullscreen with the YEP Core Engine enabled, the resolution of the game will be the same as in windowed mode, and the F3 key (to toggle stretch mode) don't work too.


Error Report: No error message.


Exact Steps on How to Replicate Bug: Open the game, and then try to put it in fullscreen mode with the F4 key.


Sample Project (REQUIRED): Fullscreen bug report (it's the same demo as above).

I'm having no problems. The only change I made to your map is made it 50x50 tiles and filled it with grass to show the borders of the screen.

EDIT: Ah wait, I see the problem. I'll explain.


The problem here is due to the new changes made to the Pixi engine.


The way my screen resolution plugin works is, it takes the difference of the screen sizes and extends the window of the game to whatever size you declared in the plugin itself. However, JavaScript will not allow windows to extend past a size that based on your desktop resolution AFTER subtracting the Start Menu bar's height and AFTER subtracting the heights of the window title and borders themselves.


This means, if you are running a 1280x720 resolution game, on your desktop with resolution of 1366x768, with a 40 pixel tall, a window title height of 30 pixels tall, then extra border padding of 2 pixels wide minimum (accounting for both sides with the default theme), you have actually roughly 72 pixels left of space meaning you'll have only 696 pixels of room to display your game. Looking at your screenshot, the height of the image is 691 pixels tall, which means the calculations are in the ballpark area given the theme you're probably running for Windows.


That said, this is something that should have been accounted for by main MV engine itself.


My suggestion? Revert back to MV 1.3.1 for the time being. http://yanfly.moe/beta/BackToMV1.3.1.rar


I'll have to figure out yet another way to fix these oversights.

Thanks, Yanfly. It's a bit difficult to understand all the process of how the fullscreen works, but I'll do what you suggest me and revert my project to 1.3.1 version of the engine. By the way... Should I report this bug too in the RPG Maker MV Support forums too? Maybe the devs can do something about this.

I don't know if this was already reported but with the YEP_CoreEngine v1.20 I have still the battleback scaling issue with a resolution of 1280x720. When I change to default or 1366x1280 it works fine.

To make a bug report, simply report it in this thread. Chances are, I will find out about the bug in this thread than by making one in the JS Support forum.


ALL bug reports MUST follow these guidelines and use this template: 


Plugin Name: (What is the name of the plugin?)


Bug Explanation: (What is the bug in your own words? Keep this detailed. "It isn't working right" is not a valid bug report.)


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.)


Sample Project (REQUIRED): A sample project MUST be attached to the bug report. All steps MUST be followed. If a single step is ignored, the bug report is invalid and I will move on to the next bug report. If you do not attach a sample project to the bug report, your bug report WILL BE ignored. There are NO exceptions.


Follow these Instructions. All steps MUST be followed or I will require you to redo it.


1. Download all the newest updates of the plugin.2. 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.3. If the project's file size is above 200 MB, remove unnecessary audio and image files until you reach that size. Usehttp://forums.rpgmakerweb.com/index.php?/topic/47985-mvstripper-remove-unused-assets-from-your-mv-project/ if you need some help doing so.4. Install -only- the affected plugins. If you're using non-YEP plugins, do NOT include them. That said, 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.5. Do -NOT- rename the plugins' filenames. They cease to work if you do so.6. Make sure they're in the EXACT order listed on http://yanfly.moe/yep/. The ordering of plugins is important.7. Recreate the error in the sample project. 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.8. Archive the project with WinZip or WinRAR. Do not archive it multiple times. It does not compress it further.9. Do -NOT- deploy the project through File > Deployment. Upload the project online to a website like MediaFire.com or or Dropbox. Please 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 to somewhere else.10. Post the link here and I'll take a look at it.


NOTE: I'll only provide support for my own plugins and code that I, myself, have provided. This isn't because I disrespect other plugin makers or anything of the sort. If I did, I wouldn't go so far as to maximize compatibility with my plugins when possible. The reason behind is because of my lack of time, and I'd like to put my undivided attention to errors caused by my own plugins. That said, any modifications you've made to the plugins itself, any custom Lunatic Mode code you've made yourself that isn't provided by me, or problems with the source code will not be supported by me either.


NOTE2: As I've stated before in the previous note, I'll only provide support for my own codes that I, myself, have provided. To make this clear, this means strictly the plugins I've made and any code for Lunatic Mode that I, personally, have provided through Tips & Tricks. I am not responsible for any coding errors, coding roadblocks, or code questions that you come across within your own Lunatic Mode code. Unless the Lunatic Mode notetag itself has a bug, you are to ask your questions here.


NOTE3: However, as an exception to NOTE2, this does not mean I am going 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.





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:

1. It makes the player 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.
   
2. 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.
   
3. 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. 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.





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.