[SOLVED] YEP_EquipCore working flawlessly, but...

[MORINGA]

Hello! First post here, sorry if it's not in the right place (I searched for YEP_EquipCore, read many, many posts/topics until I decided to create this one)

Spoiler: Objective

To make it so, that an equipment (say, a weapon, in this example):
-has a base 'str' requirement value of 25;
-'punishes' the character using it, if their 'str' value is below 35, by subtracting the difference between 35 and 'str' from current 'dex'

I'm using YEP_EquipCore and YEP_X_EquipRequirements, along with some other non-Yanfly plugins:

No issues so far using custom parameters (QuasiParamsPlus), here's a notetag for a weapon:

Yes, it reads that _cParamPlus[0] and checks, all fine. No conflicts so far.

Spoiler

This solved a little question I had where I wanted the base value of a custom attribute. Instead of using "user.xyz", I used "user._cParamPlus".
So, no more "equip-this-one-to-equip-that-one" thing...

Now, I need to write another conditional notetag, which applies some kind of a "punishment", after the said weapon is equipped.


And this is where YEP_EquipCore comes into scene: it allows me - through Lunatic Mode - to customize this weapon effect, by checking the above condition.
So it would theoretically apply an effect of subtracting, say, 10 to 0 from 'dex'.

Again, it reads all of the above, checks and etc (I checked the console by adding the 'console.log()' thing).
But it does not write to 'user.dex'.

I'm pretty sure I'm doing something wrong here, just can't find out what...
I'd appreciate any help, hint, link, guidance.
Thanks in advance!

 

[mlogan]

I've moved this thread to Plugin Support. Please be sure to post your threads in the correct forum next time. Thank you.

 

[Andar]

But it does not write to 'user.dex'.

What is user.dex and where did you define it?
Most likely you defined it in a different context where the plugin can't access.

The engine itself doesn't have strength or dexterity or any values for it, so most probably you're using a plugin to create those values - which one?

Please give links to the websites of all plugins you're using in this context, people will have to check the exact code where is what in order to help.

 

[MORINGA]

[move]Plugin Support[/move]

Thanks!

What is user.dex and where did you define it?
Most likely you defined it in a different context where the plugin can't access.

The engine itself doesn't have strength or dexterity or any values for it, so most probably you're using a plugin to create those values - which one?

Please give links to the websites of all plugins you're using in this context, people will have to check the exact code where is what in order to help.

Thanks for the reply!
'user.dex', as well as 'user.str' are custom parameters¹ I defined using QPP plugin (QuasiParamsPlus):
These can be altered via notetags or plugin code, once they become properties of the 'actor' object (or Game_Actors. prototype.actor? Or $gameActors.actor()? )

I'm also using Yanfly's YEP_EquipCore and YEP_X_EquipRequirements (actually, versions 1.16 and 1.06, respectively)

There's an implementation of Alistair's AP_StatDistribution, which I copied and altered to make it so that the player can manually change custom parameters on level up (just added entries, and yes, I know it's not recommended, but I see it as a temporary solution so that I can make any progress into developing this one, until I find something more...."by the book"/suitable).
Disabling it doesn't change anything, so I'm assuming it has nothing to do with the property not being set.

Other plugins I'm currently using:

Spoiler

• YEP_CoreEngine ("or die", meaning "mandatory");
• QPP, for custom parameters;
• Two ICFSoft I'd rather not use - and probably will no longer use, QPP does the trick, although a little bit limited;
• YEP_BaseParamControl - needed to link MaxHP to a custom attribute ('user.vit', for instance - works perfectly!);
• Will soon use YEP_ExtraParamFormula/YEP_SpecialParamFormula. It'll solve many issues with xparams/sparams;
• YEP_EnhancedTP - makes it so that TP now works as Stamina. Again, works perfectly;
• YEP_MainMenuManager and YEP_StatusMenuCore - disabled cause I'd have to copy/alter one of them to show custom attributes. Or I'd have to disable some menus and create new ones - which I feel not yet skilled enough to do so;
• JAH_StatusMenuCore - solved the above issue (disabling it does not solve the issue related to this topic);
• YEP_X_ActorVariables - useful, initially for debugging/developing purposes;
• AP_StatDistribution (disabled to check if it causes the issue related to this topic);
• AP_AbilityDistribution - will most probably not be used as intended. Possibly not used at all (we need Skill Distribution - not Ability - limited to a certain custom parameter. Things are getting complicated, hehe, no prob.);
• YEP_SkillCore - needed to customize skill/spell costs (i.e: costs MP and TP). Works as intended;
• YEP_MapGoldWindow, BOB_CustomStats, MOR_RecoverOnLevelUp: the first two, I was still learning how to use plugins. The last one, I was learning how to make plugins (aaand...boss/manager (the person) did not want its implementation. Players may suffer a little bit more.)
• ShowConsoleOnBoot - as I'm *expecting* some crashes-on-load, this might be useful. Anyway, I use console so often it comes in handy...

Thinking a little bit more (after finally sleeping, lol), I noticed that, with the exception of AP_StatDistribution and QuasiParamsPlus, all other plugins that deal with custom parameters only read from them.
I guess I'll have to check the codes that write values to them².

(btw: I'm having some difficulty getting the actor's ID and making it work in a notetag formula. I thought I'd never have to get the actor's ID in such situation because and item equipped by 'actor(x)' is supposedly related to that 'actor(x)')

¹(usually, I first check the plugin to see if it uses 'user' within notetags, because...well, QPP, for instance, does not)
²(addCParam(paramId, value) and setCParam(paramId, value) within QPP. Not sure if it's available to be used by other plugins, though the said plugin help says it is)

 

[waynee95]

@MORINGA
The 'dex' param is read only. Use user.addCParam(CParamId, value) and replace CParamId with the id of the dex param. To substract from the
param use a negative value.
Normally, there should be no problem with using it in the notetags.

You get the actorId by calling user.actorId() if user is an actor.

 

[MORINGA]

@MORINGA
The 'dex' param is read only. Use user.addCParam(CParamId, value) and replace CParamId with the id of the dex param. To substract from the
param use a negative value.
Normally, there should be no problem with using it in the notetags.

You get the actorId by calling user.actorId() if user is an actor.

Er...hum...it crashes (so I get nothing from console) when I use either addCParam() or setCParam().
Thing is: I'm not allowed to use it within YEP_EquipCore's notetags (I'm inclined to actually prefer it that way! Since it's a QPP implementation, there should be a "QPP-like" solution for this - if I'm not mistaken! But that would require another way to call those functions, since I may not use 'user', nor 'actor' for QPP...)

(Thinking and testing before posting) Good news! [SOLVED]

Spoiler: From QPP's Help section:

Fixed Params allows you to add a fixed param value to states and equipment.
With this you can create states that will add a constant value to a param.
Or create a poison / regeneration state that ticks a fixed number.
( You can also add these in Actors, Classes and Enemies Notes)

Setting up <note tag>

<params>
Param: Value
</params>

Where Param can be: MHP, MMP, ATK, DEF, MAT, MDF, AGI, LUK and new Params

Value can be any number or even a formula. Can use a and v[] but not b!

I did miss a single letter - a statement, actually - that made all the difference: "can use a."
Which means the following is now working:

<params>
DEX: if (a._cParamPlus[0] >= 35) { 0; } else { a._cParamPlus[0] - 35; }
</params>

I'll remember this from now on: if plugin X implements feature Y, it's up to X's resources to deal with said features.
In the end, it was all about proper use of QPP and nothing to do with YEP_EquipCore.
Thanks!

(Word to the wise: drink about 3/4 of a gallon of water per day. Be grateful. Eat veggies. And do not code without proper sleeping...)