The official VisuStella notetag help thread

If it's limited to 1 you can just take out the loops.

Since you're using visustella, you might look at their "javascript snippets" or quick functions.
They're in the Core...down near the bottom, I think.
They're basically js functions that can be used globally.
There are a few random type functions. The one I use a lot of is "randomfrom" which
let's you give a list of numbers from which it will pull one out at random.
So like "randomfrom(10,20,30,40)" will randomly give you 10,20,30 or 40.

Hey, just 1 question about the BTB system and chain battles... is there anyway for BP amount to carry over to next chain. each chain reset BP back to 0, I wanna stop that.

If there isn't a parameter or notetag for it, you'd have to override it with a plugin.

Looking at the docs, it might be possible, but it will be a pain in the butt.
You can use VS battle core to run a "post battle" common event.
In that event you could make note of the BP value for each party member and
then stick it in a variable for each actor.

Then...you could use the chain battle "Next Victory Queue Common event" command, and have a common event that then assigns those variables to each actor's BP. However, that might not work, since I expect they'll get re-initialized when the battle actually commences.

So, you might have to put it in the very first Troop Event page...

In any case, it would be a pain, and getting the timing right from an eventing/plugin running commands standpoint will take some effort.

A better option would be to put in a feature request to the VZ team via their website. They already maintain hp, mp, tp, etc as part of the plugin. You might ask them to make BP carry over one of the options.

Okay, so the way the armor scaling calculation works is this:

First of all, it replaces each instance of b.def, b.mdf, b.agi or b.luk with
Math.max(this.applyArmorModifiers(b, %1), 1), where %1 is the replaced parameter. This applies armour modifiers to b and returns the maximum between that value and 1 (meaning modifiers can't cause the value to be 0 or negative).

It then calculates the damage value as normal, taking the max value between the evaluated formula and 0.

If the action deals HP or MP damage and is not certain hit, the defender's armor is applied:

If the action is a physical attack, we start with target's def, or mdf if it's magical.
We then apply armor modifiers to the target using the relevant parameter.

If armor is greater than or equal to 0, we multiply value by 100 / (100 + armor). Otherwise we multiply value by 2 - (100 / (100 - armor)).

Applying armour modifiers just bundles up all the armor reduction/penetration notetags and reduces them into a final value. For example, let's say you attacked an enemy with 101 def and a 20 flat armour reduction state while equipped with a weapon that has 5% armour penetration.

First the flat value will be subtracted from the enemy's def, giving 81. Then that will be reduced by 5% for the weapon, resulting in the enemy having 76.95 def.

Let's say your weapon attack damage calculation was 50. Ordinarily with no modifiers the enemy's 101 def would reduce that to: 50 * 100 / (100 + 101) = 25. With the armour reduction and penetration, the attack will deal: 50 * 100 / (100 + 76.95) = 28 instead.


Yep, absolutely. You could incorporate target.gainTp(-value) into a pre-damage as user notetag on the skill.

Theoretically you could do

enabled = $gameActors.actor(3).isTpbCharged();

If you put that in the skill notetag, it should make it so that the skill can only be used when actor 3's ATB is full.

I'm curious as to why you need to do that on a skill when you can define the element of it in either the damage settings or a multi-element notetag and that rate will be calculated for you. Or are you trying to incorporate additional elemental damage beyond what the skill already deals?

1. Yes you can, with the script
SceneManager._scene._lightContainer.children.find(child => child instanceof Sprite_LightSpawn && child._source.eventId === {id of the event the light was spawned on}).destroy();

2. It seems that only one light can be attached via notetags, but the first solution should sort out your problem.

If only we could get "random target" in this menu, it would be easier for me

@Kazuo Would it make a difference if the scope on the actual skill in the database were set to 'Enemy & Ally'? But perhaps you already have that.

I recall a thread trying to get a random target in action sequences and @Arthran wrote a plugin extension to add that functionality.

But I don't recall what thread that was, so hopefully they'll be able to chime in and repost it.