RMMV Yanfly's Auto Passive States conditions not working?

[Gargoyle77]

Hello. My problem is the following. I'm trying to give a passive state to actors, but the passive will only be present if the actor has 100 TP. Without the condition, the passive state works as intented; it automatically is applied to the actors as soon as the game starts. Now, when I put the condition on it it's when nothing happens. The state is not applied even if the conditions are met. Why is this? I'll attach many images that show that I'm doing everything right as far as I know. Can you please help me with this?

 

[Andar]

Are your yanfly plugins in the correct order?
Some of them look as if they are not, and all of them have to be in the order of the main list, top to bottom, or they are known for strange effects and bugs.

 

[Gargoyle77]

Are your yanfly plugins in the correct order?
Some of them look as if they are not, and all of them have to be in the order of the main list, top to bottom, or they are known for strange effects and bugs.

Yes, I double checked yanfly's engine plugins page and I put them in the same order they appear there.

 

[ATT_Turan]

I know it's not supremely helpful, but that state with that condition works in my test project.

Does it change anything if you disable the extra conditions pack? Does it work if you use the custom condition instead of the default one? e.g.

<Custom Passive Condition>
condition=user.tp>99;
</Custom Passive Condition>

But, like I said, what you have works for me, so I feel like something else must be mixed up on your side.

 

[Gargoyle77]

I tested the what I wanted to do in battle and it works. Is it possible that this whole thing doesn't work outside battle?

 

[ATT_Turan]

My test was outside of battle.

 

[Gargoyle77]

My test was outside of battle.

I testes it by putting the notetags you gave, but nothing happens outside battle. However, in battle it works as intended.

 

[ShadowDragon]

@Gargoyle77 there was a bug inside that plugin I believe, so you should
check @ATT_Turan terrific fixes on the yanfly plugins.

if it is the condition bug, add that fix and it should work as it should.
he made alot of fixes for serveral plugins, some minor, some unoticed,
so its a nice list , so I think he tested it on a modified version with the fix
inside it

 

[ATT_Turan]

@ShadowDragon Thanks for the recommendation, but the fix in my thread is for conditions with switches.

The parameter conditions work correctly with the plugin as written, as far as I've seen - I tested with Yanfly's original file using the condition that the OP wrote and it works for me out of battle.

 

[GeneralIroh]

Hmm. I've been having this same exact problem, except I want it to activate when the actor's TP is equal to 0. I'll take a look st my plugins and upload some photos here to see if we csn figure out the issue both for myself and the OP.

 

[GeneralIroh]

Okay, I took some snapshots. I have a Monk class that is supposed to have an automatic passive state called exhaustion that only triggers when the actor's TP is less than 1%. NOTE: While my photo shows that I have tags for both the TP and HP being under 1%, normally I just have the TP note tag.

The passive conditions do not work. The auto-passive state does work, my monk characters are always 'exhausted.' But they have the state even when the conditions for the state are not met. I tried using Yanfly's 'Passive COndition Cases' plugin extension to see if that could be a work around, but it doesn't fix the problem either. In the spoiler below you will find my plugin list and the auto-passive state note tags I am using.

It would be nice to get a fix for this, but mostly I just want the original poster to know that they aren't alone in having this particular issue.

Spoiler: Plugin order and the non-working state conditions

 

[AphoticAmaranth]

@SarcasticSloth the notetags for the passive conditions are for states, not for classes

 

[GeneralIroh]

Well I'll be. Nice catch! Unfortunately, even after I moved the note tag to the state itself, the problem persists.

@SarcasticSloth the notetags for the passive conditions are for states, not for classes

 

[ATT_Turan]

As a general rule, you can't duplicate notetags unless the instructions explicitly say you can. Only one of those notetags will function on the state - to have either one work, you'd need to put them into a Custom condition tag using JavaScript.

e.g.:

<Custom Passive Condition>
condition=user.hpRate()<.01 || user.tpRate()<0.1;
</Custom Passive Condition>

That's presuming you wanted it to activate under either condition. If you want both, the state only turns on when both HP and TP are below 1%, change the || to a &&

 

[GeneralIroh]

Thanks! While my photo showed that I was trying to do both HP and TP as conditions, I never actually ran the game that way. I always only did one or the other. So the duplicate note tags isn't the problem but my photo was misleading.

I'll try your code and report back.

As a general rule, you can't duplicate notetags unless the instructions explicitly say you can. Only one of those notetags will function on the state - to have either one work, you'd need to put them into a Custom condition tag using JavaScript.

e.g.:

<Custom Passive Condition>
condition=user.hpRate()<.01 || user.tpRate()<0.1;
</Custom Passive Condition>

That's presuming you wanted it to activate under either condition. If you want both, the state only turns on when both HP and TP are below 1%, change the || to a &&