SPECIAL STATUSES [2K3]

They're all possible.

You need a common event to check for each status, some variables to hold the "real" health values for the diseased characters so you can restore it when the condition is lifted, and a couple of "remove battle command" calls to get your disable one working.

EDIT - One of the class skills in my game is actually similar to Disease. I think it would be EASIER to do it to party members than it was to do it to enemies actually!

For auto-life, you just have your common event turn on a switch for each character that has it active. Then in the battle events, just have a page that activates with that switch, and have a condition fork for that party member's hp<1. Restore them to life in the event, and you're good.

Since my game allows the player to select which battle commands they want to arm the character with, I use variables to store the order. I strip them all off and re-apply them in a pre-battle common event. That keeps the order right.

You can remove the Disease condition via a common event if it persists after battle. Just make sure that you keep everyone's possible Diseased Max HP variables separate, and that you don't accidentally overwrite that value after it has already been set. Have a fork condition for each character that triggers when their condition is NOT Disease, and use the variable to set their max hp numbers back. Now, a potential bug here is that if the character gains a level while Diseased, their old MAX hp wouldn't reflect this new number. You COULD fix this by checking their current Max HP against half of the value of the Max HP stored in their Variable. If it is higher, add the difference to a variable, apply it to the Max HP variable, and then add it back in to the character.

Bubble would work the same way as Disease, just in reverse.

Reverse would almost be more trouble than it was worth, unless you were going to handle all skills and attacks via battle events. It is doable, but it will probably get very time consuming.

It all depends on how you structure the skill. If you make Auto-Life a party wide buff, you could just make the skill into a switch.

Also, there is no reason you couldn't put the auto-life code in one event page you call every round. The common event still has to check to see who has it on, and turn on a switch for them (you could also use variables). You'll just get something that looks like this -

TRIGGER: Turn 1X
Call Common Event : Event_Name_Here

Branch: If Switch (Char1-AutoLife) = On
Variable Oper: Set Character1 HP
Branch: If <= 0
*Your resurrection stuff goes here. You bring them back with 1 hp, a Full Restore, or anything in between. You could even haste characters who were auto-life'd if you wanted.*
End
End

Just repeat the above for every character what can carry the Auto-Life effect.


Or-

If you just make the skill a switch, you can have a battle event triggered by that switch. Whenever it runs, check the hp of everyone in the party. You can do it in sequence and re-use one set of variables. Any time the hp for a character comes back <1, resurrect them and move on to the next check.

I always try to get as much of the event code for the battles into common events as possible. It makes it easier to make changes in one place, instead of every single battle, but some things WILL have to be done within the battle event pages themselves.

Since you're worried about running low on switches, we'll use a variable this time.
You could use one variable for both Burn and Heat, provided they can't be stacked on a character at the same time. Again, you'll need one for each character.

We'll call the variable BurnFreeze. 1 = Burn, -1 = Freeze. 0 = Null

Freeze - In your common event, where you check for the Freeze status, you could record the character's hp value into a variable. Repeat this for every character that can be effected by the status. (I'm going to shorthand the pseudo-code here a little bit for expediency)


If Hero1 Condition = Freeze
If Variable:Hero1BurnFreeze =/= -1
Set Hero1FreezeHp = Hero HP
Change Variable:Hero1BurnFreeze = -1
End
Set TempFreezeHPVariable = Hero HP
If TempFreezeHPVariable =/= Hero1FreezeHP
Change Hero1Hp - 99999
With Hp Reduction can kill target checked.
End if
End

That will check to see if the character has the status, and if so will set a variable to their HP at that time. Any time their HP is different from the value set when the BurnFreeze variable is first changed, they die.


Burn/Heat -

In your master common event, or in one of your common events if you end up with more than one to help keep track of everything, check for the Burn status.

This one will require some in battle eventing as well as the regular common work.

Common Event-
If Hero1 Condition = Burn/Heat
Change Variable:Hero1BurnFreeze = 1
End if


Battle Event-
Trigger : Variable:Hero1BurnFreeze = 1

Condition Hero1 uses FIGHT command.
Change Hero1Hp - 99999
With Hp Reduction can kill target checked.
End If

End If

You just need to repeat the above for each of the party member's possible skills.

This should be right, or at least close enough to help get you there. This is also just how I would probably do these status types, and not necessarily the best way.

To conserve Battle Event Pages, which I believe top out at 99/100, you could nest multiple characters together in a single event. I try to avoid that when possible, due to how easy it gets to make mistakes when you're copy-pasting the events for each party member, but again, that is just me.

This worked perfectly for me.

Death sentence would be easy with the architecture already in place. Check to see if the character has the status and turn on a switch. When the switch is on, use a battle event to check for all actions the player can take. When player uses FIGHT command, ITEM, DEFEND, etc. Whenever the player acts, add one to a variable. When the variable reaches the turn limit for Doom/Death Sentence, kill the character.

Checking it when the character acts is better then checking it in your 1x turn event, since THAT would count the turns of every unit in battle. If you have 4 enemies and 3 player characters, a 5 turn death sentence might as well be an automatic kill.