2 questions about States

[Kes]

Slightly confused here, as the script returned a printout even when damage had been done - though not consistently.  Here is an example of when it gave a message despite damage being done.

And here is a shot of when it printed out when NULL was shown on screen.

To my untutored eye, there appears to be no difference between them.  What I did notice is that according to the printout, 108HP damage should have been dealt, but it came up on screen as NULL and the enemy HP bar showed no reduction, so indeed no damage had been suffered.

Colour me bewildered.

 

[Another Fen]

That's indeed funny. Normally the guard correction is the last step of the damage calculation, so its result should match the damage caused (at least when the item does not have any recovery effects, which I forgot to track).

The next suggestion of mine would be that another script modifies the damage calculation or overwrites the action result before it is displayed. A list of your used scripts (e.g. a copy of the Scripts.rvdata2 - file from your project folder) would be helpful to check that.

A list of the stats/features of both battlers and the item wouldn't be a bad thing too.

I don't know if the enemy was paralyzed, but the printout still shows a 5% evasion chance (Evasion rate = 0.05) for any reason.

 

[Kes]

I'll pm you the scripts file.

The enemy wasn't paralyzed, so the EVA rate is correct.

This isn't being done by an item.  I have given this character a passive ability of 50% counter attack.  It is applying the default counter attack state.  That state is applying the default attack, and the default attack has the modified damage formula.

 

[Kes]

The query has been resolved with the help of Another Fen.  I needed to re-order my scripts.  As it seems no one has any ideas about why a paralyzed enemy is still evading with EVA set at -100% on that state, I shall ask to have this topic closed.  If anyone reading this does have a suggestion, please let me know.

thanks.

 

[Andar]

This thread is being closed, due to being solved. If for some reason you would like this thread re-opened, please report this post and leave a message why. Thank you.