Game Development Reference
In-Depth Information
Figure 3-16.
The States tab of the RMVXA Database
As previously noted, using
.add_state
requires that you set which state you actually want to add, and it looks at
the database value to determine what to add. So, Death is 1, while HP Regen is 14, for example. States have one or two
new things, but not much that we haven't seen in a similar form already.
•
Restriction
defines what happens to someone affected by the state. Most of them are more forced
actions than restrictions. In the case of Death, the actor or enemy
cannot move
(logically, as they
are dead!). However, you also have
None
,
Attack an enemy
,
Attack anyone
, and
Attack an ally
.
•
Removal Conditions
define when a state is removed. This is more important for actors, given
that enemies cease to be after you are done battling with them. If you don't define any removal
conditions, the only way to remove the state would be to have an item or event that does just that.
1.
Remove at Battle End
is self-explanatory. Once the battle ends, so does the state.
2.
Remove by Restriction
, on the other hand, is downright misleading. The RMVXA tool
tip says: “Automatically remove a restriction if [Restriction] has been set to anything
other than [None]”. That's a bald-faced lie. The tool tip contradicts what Remove by
Restriction implies. How it actually works is that a state with that condition will be
removed if its owner is affected by another state that causes a restriction. For example,
you can have a Rage state that is affected by restrictions so that, if your actor affected
by Rage is stunned or otherwise hindered, he/she loses the state.
