RMMV Yanfly Class Base Parameters & Hime Parameter Tables

[Tenebre]

Hello all,

I use many Yanfly plugins, for example Yep_X_Class Base Parameters. Unfortunately I have no experience with scripting, and from this point of view I think it's not possible to add decreasing curves again (example: HP gain +10 per level until Lv. 20, then +20 until Lv. 60, then +5 until Lv. 99).

That's why I use Hime's Parameter Tables. Between these plugins everything seems to be fine, it took over all the stats from Hime's plugin and used the EXP curve from Yanfly. However, Hime's parameters do not work together with Yanfly's "Buffs and States Core". I don't know if this is due to that alone, or if this plugin collides with other plugins, which in turn collide with Hime's parameters. But I've got no other issues than that if I activate Buffs and States Core.

Can you help me with a solution for Yanfly's Buffs and States Core and Hime's Parameter Tables? Or do you know how to integrate wave curves (I hope this name is right in English) within Yep_X_Class Base Parameters? With a little adjusting, that should work too.

I've done all the balancing work in Excel, so each character can take X hits from X Enemy at Level X, from Lv. 1-99. And after this, this issue breaks it all .

Thanks a lot for your answers!

 

[Sword_of_Dusk]

What exactly isn't working between Parameter Tables and Buffs and States Core?

 

[Tenebre]

If Buffs and States Core is deactivated, all stats are taken from Hime's "Parameter Tables", what is correct. But if I activate B&S Core, it simply doesn't take over these stats from Hime's Tables.

I tried to put Hime's Plugin before + after B&S Core, but it makes no difference.
Oh, and the plugins are up to date btw (B&S Core v1.16 / Hime's v1.3).

 

[Andar]

and what happens if you place tsukihimes plugin after every other plugin?

 

[Tenebre]

Nothing :-D

 

[Sword_of_Dusk]

If Buffs and States Core is deactivated, all stats are taken from Hime's "Parameter Tables", what is correct. But if I activate B&S Core, it simply doesn't take over these stats from Hime's Tables.

I tried to put Hime's Plugin before + after B&S Core, but it makes no difference.
Oh, and the plugins are up to date btw (B&S Core v1.16 / Hime's v1.3).

That's odd. I don't think I encountered this problem during my early testing of Parameter Tables, and I had Buffs and States Core active. What other plugins do you have?

 

[Tenebre]

Bump

Edit:
Oh man ... I had the tab open and the page never refreshed, so I saw your post just now after the bump. Sorry, I'm a total noob at forums. Honestly, this is the first forum I've ever posted .

Tomorrow I start a business trip. I'll put together a list once I get back, 1-2 weeks depending.

Sorry again, now I know and it won't happen to me again. Thanks for your efforts anyway.

 

[Tenebre]

Here’s my plugin list. The final section seems a bit chaotic, but earlier I had to experiment with the plugin order for all plugins to work. I have no issues other than that (Hime’s and Yanfly’s BuffsStatesCore).



SRD_MenuBackgrounds v2.05

SRD_SuperToolsEngine v1.31

MBS_MapZoom v?

SpeedManager v1.1

LNM_GameEditorCore v1.2.2

LNM_GameTime v1.5.1

VE_BasicModule v1.23

VE_CounterActions v1.10

VE_DualWield v1.04

VE_FogAndOverlay v1.07

FROG_Core v1.0.3

---------------------------

YEP_CoreEngine v1.31

YEP_SaveEventLocations v1.00

YEP_BaseParamControl v1.04

YEP_X_ClassBaseParam v1.05

YEP_SaveCore v1.06

YEP_ClassChangeCore v1.13

YEP_X_Subclass v1.11

FROG_SignatureSkill v2.1

----------------------------

YEP_BattleEngineCore v1.50

YEP_X_ActSeqPack1 v1.13

YEP_X_ActSeqPack2 v1.13

YEP_X_ActSeqPack3 v1.05

YEP_X_BattleSysSTB v1.05

YEP_X_TurnOrderDisplay v1.03

YEP_X_VisualHpGauge v1.07

YEP_BattleAICore v1.15

YEP_AbsorptionBarrier v1.08

YEP_BuffsStatesCore v1.16 (when turned ON, Hime’s Parameter Tables won’t work)

YEP_AutoPassiveStates v1.17

YEP_X_PassiveAuras v1.08

YEP_DamageCore v1.08

YEP_X_CriticalControl v1.06

YEP_ForceAdvantage v1.01

----------------------------------

YEP_ElementCore v1.02

YEP_SkillCore v1.13

YEP_StatusMenuCore v1.04

YEP_OptionsCore v1.02

YEP_X_SkillCooldowns v1.12

YEP_InstantCast v1.12

YEP_VictoryAftermath v1.07

YEP_X_AftermathLevelUp v1.01

YEP_X_AnimatedSVEnemies v1.04

YEP_Taunt v1.02

YEP_RegionBattlebacks v1.01

YEP_RegionRestrictions v1.00

YEP_MessageCore v1.19

YEP_X_ExtMesPack1 v1.12

YEP_X_MessageSpeedOpt v1.00

YEP_BaseTroopEvents v1.00

YEP_StealSnatch v1.10

YEP_EquipCore v1.11

YEP_ItemCore v1.12

YEP_TargetCore v1.05

YEP_X_SelectionControl v1.15

YEP_X_AttachAugments v1.11

YEP_ItemSynthesis v1.11

YEP_ShopMenuCore v1.05

YEP_WeaponAnimation v1.05

YEP_WeaponUnleash v1.05

------------------------------

CommunityBasic

MadeWithMv

SAN_ShaderFilter v1.0.0

SAN_ShaderFilterCharaRipple v1.0.0

SAN_ShaderFilterCharaHeatHaze v1.0.0

SAN_ShaderFilterScanLine v1.0.0

Galv_RandEncounterConditions v1.2

YEP_BattleAniSpeedOpt v1.01

BattleResultsPopup

EnemyBook

SRD_SkillExtender v1.04

CGMV_Core v1.6

CGMV_Encyclopedia v1.7

LNM_LightingTool v1.7.4

HIME_ParameterTables v1.3 (Works as intended if BuffsStatesCore is turned OFF)

 

[Sword_of_Dusk]

Have you checked to make sure that Buff and States and Parameter Tables work together even if everything else is turned off? Because I was just tweaking my game's tables about two hours ago, and they work perfectly fine. I'd guess that Class Base Parameters ain't playing nice with Hime's plugin.

 

[Tenebre]

Do you mean I should turn off anything other than this two plugins? That's a way I didn't think about, thanks!

I will then turn on 10 more plugins. So if this bug occures, i know in which 10 plugins it must be.

I'll give an update here as soon as I know.

EDIT:
I've disabled all plugins, but even if I turn YEP CoreEngine off (or if I put Himes plugin before Yanfly's plugins), it doesn't take the parameters from Hime :-(

As soon as I turn Buffs & States Core off, it works as intended.

It doesn't do any sense to me ...

 

[Sword_of_Dusk]

@Tenebre Is that your exact plugin order above? If not, could you post a picture of your plugin manager so I can see the order you have them in? It might make a difference, especially considering that I use both of the clashing plugins myself.

 

[Frostorm]

I use many Yanfly plugins, for example Yep_X_Class Base Parameters. Unfortunately I have no experience with scripting, and from this point of view I think it's not possible to add decreasing curves again (example: HP gain +10 per level until Lv. 20, then +20 until Lv. 60, then +5 until Lv. 99).

<Custom maxhp Formula>
if (level < 20) {
  value = level * 10 + n; //replace "n" w/ any value you wish
} else if (level < 60) {
  value = (level - 19) * 20 + 190 + n;
} else {
  value = (level - 59) * 5 + 990 + n;
}
</Custom maxhp Formula>

 

[Tenebre]

@sword of Dusk: Yes, it's the correct order.

@Frostorm: Decreasing curves are important for me (because of HP and the "Monk" class' ATK).
I use your mentioned plugin for the EXP curve. Stats like DEF raises 0.41865 per Level for another Class, for example, so that's not a problem.

 

[Tenebre]

Wtf I've found the issue finally! I post it for people that may get the same issue:

It was the setting inside Yanfly's Buffs and States Core that alters the buff rate formula. I tried it to alter this formula inside rpg_objects.js and got the same error.

All I have to do now is not to use buffs but states.

Does someone see a mistake in the formula itself? Otherwise, they are different reasons that I can live with. The purpose was 1 buff = 10% increase, 2nd buff = 25% total increase

Original: this._buffs[paramId] * 0.25 + 1
Altered: this._buffs[paramId] * 0.1 + 1.15


Thanks for all your help.

 

[eomereolsson]

Well, your alteration of the formula does not accomplish what you wish to accomplish.
this._buffs[paramId] is the number of buffs the character has.

In the original this means the following:
No buff: 0 * 0.25 + 1 = 1 multiplier => 100% of the parameter
1 buff: 1 * 0.25 + 1 = 1.25 multiplier => 125% of the parameter
2 buffs: 2 * 0.25 + 1 = 1.5 multiplier => 150% of the parameter

Your alteration does the following:
No buff: 0 * 0.1 + 1.15 = 1.15 multiplier => 115% of the parameter
1 buff: 1 * 0.1 + 1.15 = 1.25 multiplier => 125% of the parameter
2 buffs: 2 * 0.1 + 1.15 = 1.35 multiplier => 135% of the parameter

I think there is not actually an incompatibility between these two plugins, but because of your configuration of Buffs & States Core, the value you configured in the param tables got multiplied by 1.15 even when no buff was present.

 

[Tenebre]

Sry, I indeed need 115% and 125% :-D. These two plugins worked as intended as soon as I've set the settings to standard.

After I altered this wrong formula in rpg_objects.js, my project crashed. So it's imaginable that the bug has occured because "No Buff" has to be 100%.

I'll try: X * 0.125 + 1 (or maybe X * 0.12)

Then it should be 100%, 113%, 125% or 100%, 112%, 124%

If that isn't possible too, the bug seems to have other reasons.

Thanks

EDIT: Yes, 0.125 worked! It seems that you have to keep "+ 1".
Very well! 3 months of demotivation are gone!