RMMZ Passive Sate Help

[Furiousfox]

Hey I just tried Yanflys passive state plugin for MZ (link: http://www.yanfly.moe/wiki/Auto_Passive_States_(YEP)) and cant seem to get it to work.
I am trying to make it so when a party member has 0 MP (changed the name to 'Sanity' if that matters) they gain the 'Insane' state. In the character notebox I put:
<Passive State: 52>
<Passive Condition: MP Below 1>

52 being the insane state and it doesnt seem to work.

 

[AphoticAmaranth]

That plugin is for MV. It wouldn't work with MZ.

 

[Furiousfox]

That plugin is for MV. It wouldn't work with MZ.

Dang, is there any way to get what im trying to do with common events, states and skills or something?
I just want actors to gain a specific state at 0MP.

 

[slimmmeiske2]

Passive States can be done with Visustella's Skill and State Core.

 

[ShadowDragon]

or if you dont have the Visustella's, you can use FOSSIL which works
for most YEP's plugins to work in MZ.

but ported version from MV to MZ and improved with tons of features,
are working better in MZ.

 

[ATT_Turan]

In the character notebox I put:
<Passive State: 52>
<Passive Condition: MP Below 1>

Aside from the issues mentioned by other replies, that's incorrect usage.

According to the documentation, "Passive Condition" is a state notetag - you would put that in the notetags for state 52, telling it when to turn on and off. It doesn't go on the actor.

 

[Furiousfox]

Passive States can be done with Visustella's Skill and State Core.

What exactly do I put in the notetag for the state? I just want to apply the state when MP is 0. I tried Visu plugin with <Passive Condition: MP Below 1> in the state notetag and it did nothing

 

[ATT_Turan]

What exactly do I put in the notetag for the state? I just want to apply the state when MP is 0. I tried Visu plugin with <Passive Condition: MP Below 1> in the state notetag and it did nothing

Well...where did you get that syntax from? I'm looking at the notetags in the documentation of the Skills and States Core and I don't see anything like that - so why would you think it should work?

There doesn't appear to be any built-in support for conditions based on parameters, so you would do:

<JS Passive Condition>
condition=user.mp==0;
</JS Passive Condition>

 

[Furiousfox]

Well...where did you get that syntax from? I'm looking at the notetags in the documentation of the Skills and States Core and I don't see anything like that - so why would you think it should work?

There doesn't appear to be any built-in support for conditions based on parameters, so you would do:

<JS Passive Condition>
condition=user.mp==0;
</JS Passive Condition>

I put that in the states notetag and it doesnt seem to work. Do I have to replace anything specifically?

(and I viewed the visu documents and couldnt seem to find what I needed so I decided to use the syntax for the old yanfly one in the 0.5% it would be the same from plugin to plugin).

 

[ATT_Turan]

I put that in the states notetag and it doesnt seem to work. Do I have to replace anything specifically?

Please provide screenshots of the actor and the state. Between posts 6 and 8, I've given you all of the instructions you should need for this to work correctly.

(and I viewed the visu documents and couldnt seem to find what I needed so I decided to use the syntax for the old yanfly one in the 0.5% it would be the same from plugin to plugin).

When it comes to coding, there's really no point in guessing. It doesn't hurt anything, per se, but it's almost guaranteed to waste your time If that were valid syntax, it would be in the extensive documentation by VisuStella.

 

[Furiousfox]

Please provide screenshots of the actor and the state. Between posts 6 and 8, I've given you all of the instructions you should need for this to work correctly.

When it comes to coding, there's really no point in guessing. It doesn't hurt anything, per se, but it's almost guaranteed to waste your time If that were valid syntax, it would be in the extensive documentation by VisuStella.

Heres a screenshot of both.
Thank you for the help/advice and your patients.

 

[eomereolsson]

Directly contradicting what @ATT_Turan said, I'm going to go ahead and take a guess based on my knowledge of the Yanfly plugin for MV (because I personally don't have MZ)
You currently only have a notetag telling the plugin under which conditions to apply a passive state. You don't actually tell the plugin which state to apply, when the condition is met.
With the yanfly plugin you had to specify the state with a notetag for the actor

<Passive State: x>

(which seems to be the same for the Visustella plugin, telling from its documentation).
Then you had to add a notetag to that state x where you specify under which conditions to actually apply this state. This would be where you would put the condition notetag

<JS Passive Condition>
condition=user.mp==0;
</JS Passive Condition>

 

[ATT_Turan]

Directly contradicting what ATT_Turan said...

...that's not contradicting anything I said.

Aside from the issues mentioned by other replies, that's incorrect usage.

According to the documentation, "Passive Condition" is a state notetag - you would put that in the notetags for state 52, telling it when to turn on and off. It doesn't go on the actor.

I even told the OP to read that post again in my last response ¯\_(ツ)_/¯

 

[Sword_of_Dusk]

Actually, he was talking about contradicting this bit:

When it comes to coding, there's really no point in guessing. It doesn't hurt anything, per se, but it's almost guaranteed to waste your time If that were valid syntax, it would be in the extensive documentation by VisuStella.

However, there's not actually any contradiction because you already noted that it would be in the documentation, and a cursory look tells me that <Passive State: x> is indeed in the help file. @ATT_Turan

 

[eomereolsson]

@ATT_Turan , yes, @Sword_of_Dusk got my meaning. It was meant as a bit tongue in cheek, because I generally agree with you that people should just read the manual instead of guessing and hoping to achieve the correct result through pure chance. (Seriously it astounds me, how often I have seen threads asking for help with script commands where they try to call functions that straight up don't exist.)

However I saw @Furiousfox 's screenshot and just thought: "No way that this will work without telling the plugin which state to apply." I looked at the documentation for Visustella's plugin, but couldn't find the exact correct way by a quick glance. And since I personally don't use the plugin I didn't want to spend more time digging deeper into it. So I answered based on guesswork, hoping this would be enough of a hint, so Furiousfox could figure the rest out for themselves.

 

[ATT_Turan]

So I answered based on guesswork, hoping this would be enough of a hint, so Furiousfox could figure the rest out for themselves.

I get your meaning. It's just a bit ironic, as aside from that being in the documentation I told the OP to read, I in fact already gave that answer last week...and referenced it again in my post on Saturday. So he'd already been told 3 ways before your post, and just isn't reading something (or the translation issues are really that bad).