- Joined
- Sep 11, 2019
- Messages
- 4
- Reaction score
- 1
- First Language
- English
- Primarily Uses
- RMVXA
Hi, so I'm using Yanfly's Lunatic States for VX Ace, found here.
https://yanflychannel.wordpress.com/rmvxa/battle-scripts/lunatic-states/
My goal is to create the state Flames, such that when the main character attacks an enemy who has Flames the main character is inflicted with a seperate state, Burning.
I tried to implement State A by making a state with the following notes:
and in Yanfly's script, I edited COMMON SHOCK like this.
The problem is that when the enemy attacks the main character, COMMON SHOCK is also triggered for some reason.
I thought shock was supposed to trigger when the holder of the state takes damage, but it's triggering when the holder of the state deals damage as well.
How can I prevent this?
Side notes:
I reproduced the bug in a new project by adding the same notetag to a new state and giving it to a slime, and replacing the common shock script to poison the actor. So I'm pretty sure the issue is what I think it is.
I'm aware of the double looping bug in yanfly's lunatic states. the bug occured when I left the double loop in, and the bug still occurs as described when I take the two instances of the double loop out.
https://yanflychannel.wordpress.com/rmvxa/battle-scripts/lunatic-states/
My goal is to create the state Flames, such that when the main character attacks an enemy who has Flames the main character is inflicted with a seperate state, Burning.
I tried to implement State A by making a state with the following notes:
Code:
<shock effect: COMMON SHOCK>
Code:
when /COMMON SHOCK/i
$game_actors[32].add_state(57)
I thought shock was supposed to trigger when the holder of the state takes damage, but it's triggering when the holder of the state deals damage as well.
How can I prevent this?
Side notes:
I reproduced the bug in a new project by adding the same notetag to a new state and giving it to a slime, and replacing the common shock script to poison the actor. So I'm pretty sure the issue is what I think it is.
I'm aware of the double looping bug in yanfly's lunatic states. the bug occured when I left the double loop in, and the bug still occurs as described when I take the two instances of the double loop out.

