Not much on the side of updates today. Most of them are performance updates with the exception of the Action Sequence Pack 2 to allow enemies to display weapons while making attack motions.
Yanfly Engine Plugins is a plugin library made for RPG Maker MV, a wonderful piece of software to help you make that role playing game of your dreams. You can find out more about RPG Maker MV here.
Yanfly Engine Plugins is a plugin library made for RPG Maker MV, a wonderful piece of software to help you make that role playing game of your dreams. You can find out more about RPG Maker MV here.
This plugin requires Battle Engine Core. This extension plugin allows you to animate enemies in a number of ways, from giving static enemies breathing, floating, and scaled attributes to utilizing animated sideview actors as potential battlers for your enemies instead of static graphics to help make your enemies appear more lively!
And as promised, here is the animated slime in all its glory!
Yanfly Engine Plugins is a plugin library made for RPG Maker MV, a wonderful piece of software to help you make that role playing game of your dreams. You can find out more about RPG Maker MV here.
This plugin requires Skill Core. Now you can set costs for skills using items. The item costs will appear next to the other skill costs displaying the icons of the items needed and the amount of the items to be used. Item costs using this plugin can be altered by set and percentile amounts in addition to being replaced altogether by a substitute item.
And so, I’ve made a few plugin updates today that have been placed under a stress test. With 999 events on a map, the goal is to have 60 FPS or more. Although I’m aware this is hardware-dependant to some degree, it is code-dependent, too. Previously, two of the plugins (Event Mini Window and Stop Map Movement) in my test map of 999 events would drop the FPS down to 30 FPS, even on my computer. While it’s an extreme case that people should almost never use 999 events on a single map, the fact remains is that as long as 999 events can be put down, it will be put down at some point in the future, whether or not it should or shouldn’t be done. And so, with all the Yanfly Engine Plugins installed, doing some tests today brought up the performance from 30 FPS to 60 FPS~
Yanfly Engine Plugins is a plugin library made for RPG Maker MV, a wonderful piece of software to help you make that role playing game of your dreams. You can find out more about RPG Maker MV here.
I’d like to give a very big THANK YOU to Eivind Teig for making a video clip for updating plugins on MacOS. You’re awesome! ❤
There’s been a pretty major update to the Battle Engine Core today (and the battle systems for ATB and CTB).
Previously in the past, performing a Force Action would cancel out the Current Action and the Forced Action would take over. This was an effect of the Battle Engine Core. While this may seem like a bad idea, this was selected over what RPG Maker MV did by default. RPG Maker MV originally had it so that Common Events can only be ran at the end of an action. This would include Forced Actions as Forced Actions can only occur during events. The Battle Engine Core, however, changed it so that Common Events can be ran at any time during an action and not just the end of it. This decision was made knowing full well that Forced Actions would override the Current Action because I valued the pros and cons of allowing Common Events to be ran mid-action versus end-of-an-action-only and the pros weighed way more. The Forced Action overriding the Current Action was then documented within the Battle Engine Core.
Now, after revisiting the Forced Action event, I’ve came up with a queue system that would save the Current Action’s instance as an object. Whenever Forced Actions would occur, the Current Action instead, gets queued up minus whatever it’s already performed, and after the Forced Action is done, the Current Action would continue after. Though this hasn’t been tested extensively, it should theoretically work for the most part. So now, the Battle Engine Core contains the ability to perform Common Events mid-action in addition to allowing Forced Actions occur without sacrificing the remaining actions of the Current Action.
Actor Variables also got a small update to allow hiding and showing of certain variables midgame.
Yanfly Engine Plugins is a plugin library made for RPG Maker MV, a wonderful piece of software to help you make that role playing game of your dreams. You can find out more about RPG Maker MV here.
This plugin requires the Status Menu Core. Ever wanted to display unique Game Variables into the status menu to portray your actors? Now you can! These variables can come from a global or individual source per actor. Variables listed in the Global Columns found in the parameters will be listed for all actors. Variables defined in the actor noteboxes will be listed for that actor when displayed.
Yanfly Engine Plugins is a plugin library made for RPG Maker MV, a wonderful piece of software to help you make that role playing game of your dreams. You can find out more about RPG Maker MV here.
You can find the copy and paste version of the code here:
<Post-Damage Eval>
if (target.isActor() && target._classId === 20) {
if (!target.isLearnedSkill(item.id)) {
target.learnSkill(item.id);
var text = target.name() + ' has learned '
text = text + item.name + '!';
$gameMessage.add(text);
}
}
</Post-Damage Eval>
Ever wanted to recreate the Blue Magic system found in Final Fantasy? It’s a system where characters are able to learn enemy skills once they are struck by them! Well, now you can using the aid of the Skill Core plugin!
Today’s update is an update which leaves me to make an unfortunate decision to cut off the ‘Turn Structure’ parameter from both the ATB and CTB. For those wondering, the ‘Turn Structure’ parameter allowed you to change the ATB/CTB from a Tick-Based battle system to a Turn-Based battle system. While this does work for the most part, it’s not what an ATB/CTB battle system is supposed to do. And with that combination, I’d then have to factor in native turn-based, native and current tick-based, native-changed tick-based into turn-based, tick-based that was functioning with a turn-based state turn system, and turn-based that was functioning with a tick-based origin that uses turn-based state counters on a tick-based setting. This causes confusion for users who don’t really understand how a tick-based system works, and suddenly changing it over to a turn-based system while maintaining tick-based system traits can end up becoming a huge mess in understanding. So, for that reason alone, the ‘Turn Structure’ parameter is getting sacked for a more standard setting.
Yanfly Engine Plugins is a plugin library made for RPG Maker MV, a wonderful piece of software to help you make that role playing game of your dreams. You can find out more about RPG Maker MV here.
This plugin lets you place text above the heads of various events using a miniature label through a comment tag. The text used can also use text codes so text, icons, colors, etc. whatever it is, you can use it as a label! Continue reading →
Whew, going to push the updates early today. Apparently, the update for the Action Sequence Pack 3 last night broke the panning aspect of the battle camera with me attempting to use the updated changes to the function. So instead, I reverted it back to the old method but just gave it a different name as to not overwrite anything. Action Sequence Pack 3 should be working the same as before. 🙂
For the scripters out there who like to make changes or write plugins around my stuff, the Status Menu Core is now a Window_Selectable instead of a Window_Base. Have fun! 😀
Yanfly Engine Plugins is a plugin library made for RPG Maker MV, a wonderful piece of software to help you make that role playing game of your dreams. You can find out more about RPG Maker MV here.
I’ve added a CAPTCHA requirement to the polls because I’ve been aware and have been alerted by multiple users that there’s potential abuse going on due to the numbers I’m getting. However, I’m going to let the results main as is since there was no telling how many of the votes were abused. I’m aware that CAPTCHA doesn’t prevent abuse, but it should at least slow the abuse down. Still, I insist that we all vote fairly here. After all, is this not a nice community of friends working together to create their dream RPG’s?
