- Mar 15, 2012
- Reaction score
Common Event - DisableCommonEventMenuConfirm
how to reenable with plugin. after using disable common event menu confirm all common event become unselectable.
Whenever you use ClearCommonEventMenu, it will clear the settings.
Man I read your requirements for bug reporting and to be honest it's a little much for the bug I want to report. If you don't want to look into it that's fine.
With your YEP_X_ClassBaseParam (latest version is what I have as of this post) I'm using the script:
<Custom Class Parameters>
exp = level * 10;
</Custom Class Parameters>
and it works except it doesn't take the current level into account. It is only using level "1" when calculating the exp. So essentially the formula above will never require more or less than 10 exp to level up, forever. I've tried a few things to rectify the situation. If Yanfly doesn't want to test it, if somebody else can corroborate so I know I'm not alone in this error that'd be cool.
From the first post of this thread and this post that appears at the start of each new page:
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.
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.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.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.
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 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.
- 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. 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.
Plugin Name: Party Limit Gauge
Bug Explanation: Party's Gauge isn't showing when "Per Party Member" is set to 0 while "Party Max Bonus" is set higher than 0 (I set mine at 100 with the "Gauge Increments" is set to 100. Troops aren't having this problem with their Guage, just the party.
Exact Steps on How to Replicate Bug: Enter battle and you'll see the party has no visible Guage.
Sample Project (REQUIRED): https://www.dropbox.com/s/8r8hhtloz1bci2v/Party%20Limit%20Gauge%20not%20showing%20up.zip?dl=0
Thanks, I'll check it out.