1
edit
m (y?) |
(Fixed an error on the Accuracy section, related to the scale, after checking the values in the actual game.) |
||
Line 37: | Line 37: | ||
* '''Accuracy''' | * '''Accuracy''' determines move's accuracy. Divide this value by 100 to get the actual accuracy. In RGBY Games, this value was 0-255 and divided by 256, which explains why sometimes attacks like Swift missed. This no longer happens in RSE/LGFR. This value is also set to 0 to reach 100% accuracy. | ||
* '''Effect accuracy''' determines probability that the effect associated with a given move will happen. Divide this value by 100 to get the actual effect's accuracy. So that, for instance, a value of 100 gives you 100% chances for the effect to trigger. For yet-unknowned reasons, some moves have this value set to 0 which results in 100% accuracy as well. | * '''Effect accuracy''' determines probability that the effect associated with a given move will happen. Divide this value by 100 to get the actual effect's accuracy. So that, for instance, a value of 100 gives you 100% chances for the effect to trigger. For yet-unknowned reasons, some moves have this value set to 0 which results in 100% accuracy as well. | ||
* '''Affects whom''' determines who the move will hit on a 2 on 2 battle. It can be selected target, user, both foes, random foe, both foes and partner, field, opponent field (Spikes) and last opponent who moved. The following table indicates which value matches a certain target type. | * '''Affects whom''' determines who the move will hit on a 2 on 2 battle. It can be selected target, user, both foes, random foe, both foes and partner, field, opponent field (Spikes) and last opponent who moved. The following table indicates which value matches a certain target type. |
edit