Another great plugin, and with that, now Yanfly has more MV plugins in his library that VX Ace scripts! Great job!
P.S. : Are you still planning to port the
Skill Cost Gold script in Ace as a plugin? Because the poor plugin was always left last in the polls...
Perhaps in the future. I'm withholding from that plugin though, since it was pretty clear a lot of people didn't want it.
---
Hello!
I have a question about yanfly's "Equip Battle Skill" plugin.
Is there a way (with a script call i guess) to check if a specific skill is actually equiped in a specific slot?
For example : if Actor1 has Skill3 equiped in slot2, it will activate Switch5?
I've provided a list of functions in the help file. How you use it is entirely up to you.
---
Love the new plugin yanfly, especially the ability to augment the strength of specific elements very useful.
One thing I noticed though,
if I set the element to none in the skill tab then use that skill in battle it results in 0. No matter what, it ignore the formula box. If I assign any element other than none to the skill it works just fine. Not sure if its a bug or that's how its intended just figured I mention it to see if anyone else runs into that small problem.
From the front page and the bug report 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