The official VisuStella notetag help thread

I'm not at home currently but when I get back I'll have a look at this if you haven't had an answer yet. I need to go through the thread at some point and find any unanswered questions, too.

I'm not sure this is actually needed as target.isDead seems to only be correctly calculated much later than post-damage

Hmmm, it says that notetag just runs code after the executedamage function. So doesn't it add that to all your stuff? The way I understand it is that it uses that function for gaining hp too, it just changes the sign of the value depending what the damage type is (disclaimer: I might be wrong LOL).

If you want it only to work with normal attack, I think it's:
this.item().id === 1
If you want it to work with hp damage causing skills, I think it's:
this.item().damage.type === 1

I don't understand your point.
The code - which is and not is making sure that the target is alive before determining if the random roll is going to inflict the state. There is no other time for that to happen, as far as I am aware.

@rpgLord69 The honest answer to your question is: I don't know. The intention for this item is that the chance to inflict state 65 was only applied to the straightforward attack skill. This is the first time that the state has turned up with another skill.

That's not correct. The isDead() method checks for the target to be affected with the death state.

That doesn't happen until the entire skill has finished resolving and the target battler is refreshed - this will never return true unless you manually applied state 1 someplace else.

If you look at Yanfly's Tips & Tricks, or any of the threads on the forum with skill/state notetags, what you want to check for is target.hp<=0 e.g. the target will die.

So there's nothing in the description of the notetag you're using (JS Post-Damage as User) that says it only is evaluated when the attack skill is used. I'm not sure where you got that impression.

The plugin documentation says:


which is the function that every skill with anything entered in the damage formula will call.

If you want to check the target is dead:

To check that it is an attack skill (targets an enemy):

If you only want it to function with the user's Attack skill:

@ATT_Turan Thank you for explaining that in a way that I can understand.
I assume that in this instance, as I will be specifying that the skill is Attack, I don't also need to check that this is an enemy. The only time Attack might be used against an ally is if the user has Confusion, and then it is logical that the ally might get inflicted as well.

Putting it all together I came up with this:

<JS Post-Damage as User>
if (target.hp<=0 && this.isAttack() && Math.random()<.4)
target.addState(65);
</JS Post-Damage as User>

Should I split the 3 conditions into separate lines?
Testing these doesn't produce a crash, but neither has State 65 been inflicted. This is difficult to test for, because it's only a 40% chance, but in 10 fights it's not come up once. Even putting it to 90% it didn't happen.

@Kes

I believe to fix it you need to put a ! in front of 'target.hp' so that it's


Because right now it's only going to activate if the target has 0 or less, and I assume you want the opposite when it's still alive, correct? Which will explain why nothing is triggering right now.

@FrigidGaze How right you are. Enemy now being nicely splatted with the state.
Thank you.

@Kes Right, that's just a mathematical operator. HP is less than or equal to zero - so you were only trying to do it when your target was dead.

You can reverse it as @FrigidGaze showed, with the NOT operator, or just reverse the math - target.hp > 0, is greater than zero, is still alive.

I did word it confusingly in my prior post.

posted in the wrong thread before so:

I’m using Visustella MZ and is there a way to create a passive state that prevents other states from expiring?

For example, if the actor has that passive state, a buff that last only 3 turns would never expire, nor would an ailment that lasted 4 turns.

Bonus points if it could only apply to certain state categories!

Hey all,

For STB Turn Display. Is there a way to have a gap between non subjects? I hate how on top of each other each frame is.

You could give it a turn/action end tag that loops through states, checks for category X, and adds 1 to the duration of each one that meets the condition.

I actually figured out a little snippet that prevents the state turn from incrementing when that state was applied:


It's been working so far.

A quick question (hopefully)


Do i have to alter anything to have Action Sequences accepts variables in place of numbers? I want to set motions and just do something like actor ID $gameVariables.value(20) here:

Unless the documentation explicitly says someplace you can do that, there's no way that would work.

You can't just provide anything code-related - whether it's a script call or a plugin command that interfaces with one - something different from what it's written to work with.

Good call. Actually dawned on me after that any Summoned Pet (since I'm only using one at a time) would be "friend index 4" (basically party index 4) in action sequences. So I can just use that.

Hi there, I'm scratching my head over something that should be simple... I want to swap out sprite sheets based on the weapon equipped, and to prototype this I have the following note in the state 'EqShortSword':


The console.log entry I added because it didn't seem to do anything, and lo and behold, no log is being added. The state itself is applied correctly when equipping a Short Sword, but it seems to ignore the note? I suspect I'm overlooking something very basic here, but need a second set of eyes...

EDIT: for clarification, the icon for the passive state (in this case EqShortSword and EqLongSword) are showing up in the actor status menu correctly. It just seems like the whole <JS On Add State> notetag is ignored.

@werzaque Passive states are neither added nor removed, they are only toggled on and off. This is in the plugin documentation:

Thanks, you are absolutely correct. However, now I'm a little puzzled how to implement this mechanic... I saw that the MV-equivalent of these plugins did allow for sprite sheet swapping through this mechanic. But if passive states are not states, I'd need a something to add a "normal" state upon equipping...

Will try asking their discord for clarification.

Maybe you can link to what you're looking at, because that's not correct. I can't think of any combination of Yanfly plugins/notetags that would let you change an actor's spritesheet by equipping a weapon.

I would've used waynee95's On Equip Eval, which runs code when you equip and unequip items (in fact, that is what I'm using in my project).

You could check, see if that plugin is compatible with MZ - the equip/unequip methods may well be the same between engines.