MV - Variable Level Params

Description:

This plugin adds two degrees of randomness to parameters gained when actors level up in your project. The first level of randomness is facilitated via 'Growth Ranks' which are set via note tags on your actor classes. 

These ranks range from F rank, all the way to S rank spanning a total of 10 different ranks. Whenever an actor levels up, the growth rank of their current class is used to determine how their base parameters will increase for that level. The amount of a parameter gained at each level, for each rank is configured in the plugin manager.

Additionally, bonus ranks can be assigned to equipment, states, or actors. These ranks can also be negative (effectively acting as a penalty), allowing you to make heavy equipment lower your agility gain, or something similar. The combined total of the class growth rank, and all bonus ranks is the actor's Effective Growth Rank in that parameter. Bonus or penalty ranks cannot cause an actor to exceed an effective rank of S, or drop below an effective rank of F.

Each growth rank for each parameter is configured as a range between two numbers, a minimum and a maximum value. When an actor levels up, a random roll between the minimum and maximum for each parameter is performed, and the result is granted to the actor as a bonus parameter for leveling up. This happens at every level up, for every actor. The system works best if each rank provides a slightly higher average value, but not so much as to become unbalancing.

The second degree of randomness is introduced via a random variance plugin parameter. Each base parameter is assigned a random variance range, which is also checked on each level up, and granted to the actor as well. This feature works best if the range is small, default is 0-1. The purpose of this is to allow actors belonging to a class that has F rank in a parameter to still occasionally see some growth, but not so much as to make it possible for someone with a poor growth in a parameter to accidentally gain more on a level up than someone with a higher growth who rolled poorly.

This system is designed for projects which have a class changing mechanic in them, as the growth ranks provide permanent parameter bonuses to actors when they level up as a specific class. These bonuses are not removed when changing class (even if the level is reset), meaning that an actor who spends a long time as a melee character before changing to a mage type character will not be as good at being a mage as an actor who had been a mage all along.

Additionally, while not a hard requirement, this plugin also works best if the stat curve growth of all classes is the same, or very similar, this way, changing class does not immediately invalid all training done as a previous class. If your fighter class has 400 attack value at level 30 and he class changes into a wizard who only has 12, it's not going to matter how many levels he spent as that fighter, as the bonus params for leveling up are never going to make that difference. Likewise, spending all of your time as a fighter class, with low magic attack growth doesn't matter at all when switching into the mage class sets your m.attack to the same value as someone who'd been a mage the whole time.

Features:

• Grants a bonus value to each base parameter on level up, determined by a combination of class, bonus values from equipment, states, or on the actor, and random variance
• Bonus parameters granted in this way are not removed when changes classes, even if levels are rest on doing so.
• A window is shown on actor level up that displays all parameter changes from all sources. (can be turned off)
• Note tags allow two actors who share the same class to still have different effective growth ranks
• Bonus ranks granted on equipment or states can be used by players to target growth in specific parameters for specific actors. 
• Projects with a class change system will see further character customization options, especially if the default class param curves are all the same (or very similar).
  • As the params granted in this way are permanent, actors who spend many levels in a class with high growth in certain params will see those params remain high when changing to a different class with lower growth ranks
• No required plugin dependencies.
  • Tested and works* with YEP_VictoryAftermath and YEP_X_Aftermath_LevelUp
• Version 1.10+:

  
  

  • YEP_X_Subclass plugin compatibility.
  • Add bonus ranks based on the equipped subclass' parameter ranks, or take the higher, lower, or average of the ranks of the base class and subclass.
  • The class change scene now shows growth rank changes when changing classes.

Compatibility Note:

This plugin works in a base RPG Maker project without any require plugins. If you are using the yanfly plugin suite (which many users are), specifically the YEP_VictoryAftermath plugin, the param change popup window display does not function in battle. This is due to the way that level ups are handled in the aftermath window. A compatibility patch is planned for the future. In the mean time the YEP_X_Aftermath_LevelUp plugin actually handles the variable param changes just fine without the popup window at all. If you are using one or both of these plugins, it is recommended you turn the popup display plugin parameter off for now, as it doesn't function correctly, and may cause some weird behavior if a level up is called from the map scene via event after levels are gained in battle.

Terms of Use:

• You may:
  • Use this plugin in any commercial or non-commercial projects you like.
  • Make changes to the plugin, to add/remove or improve features, or add compatibility with other plugins, or fix bugs, for personal use only.
  • Share these changes only as extensions to the original plugin, and not for profit.
• You may not:
  • Share this plugin, or the demo project with anyone else.
  • Claim full ownership of, or profit from modifications to this plugin
  • Modify the header, or claim ownership of this plugin.
  • Share modified versions of this plugin directly, any extensions need to be standalone, in that the end user must have this plugin to use them.