pokemon-rogue-battle
    Preparing search index...

    Variable MoveUseModeConst

    MoveUseMode: {
        DELAYED_ATTACK: 6;
        FOLLOW_UP: 4;
        IGNORE_PP: 2;
        INDIRECT: 3;
        NORMAL: 1;
        REFLECTED: 5;
    } = ...

    Enum representing all the possible means through which a given move can be executed. Each one inherits the properties (or exclusions) of all types preceding it. Properties newly found on a given use mode will be bolded, while oddities breaking a previous trend will be listed in italics.

    Callers should refrain from performing non-equality checks on MoveUseModes directly, instead using the available helper functions (isVirtual, isIgnoreStatus, isIgnorePP and isReflected).

    Type declaration

    • ReadonlyDELAYED_ATTACK: 6

      This "move" was created by a transparent effect that does not count as using a move, such as Future Sight/Doom Desire.

      In addition to inheriting the cancellation ignores and copy prevention from MoveUseMode.REFLECTED, transparent moves are ignored by all forms of move usage checks due to not pushing to move history.

      Consider other means of implementing FS/DD than this - we currently only use it to prevent pushing to move history and avoid re-delaying the attack portion

    • ReadonlyFOLLOW_UP: 4

      This move was called as part of another move's effect (such as for most Move-calling moves).

      Follow-up moves bypass cancellation from all non-volatile status conditions and BattlerTagLapseType.MOVE-type effects (having been checked already on the calling move).

      They are not ignored by other move-calling moves and abilities (unlike MoveUseMode.FOLLOW_UP and MoveUseMode.REFLECTED), but still inherit the former's disregard for moveset-related effects.

    • ReadonlyIGNORE_PP: 2

      This move was called by an effect that ignores PP, such as a consecutively executed move (e.g. Outrage).

      PP-ignoring moves (as their name implies) do not consume PP when used and will not fail if none is left prior to execution. All other effects remain identical to MoveUseMode.NORMAL.

      PP can still be reduced by other effects (such as Spite or Eerie Spell).

    • ReadonlyINDIRECT: 3

      This move was called indirectly by an out-of-turn effect other than Instruct or the user's previous move. Currently only used by Dancer.

      Indirect moves ignore PP checks similar to MoveUseMode.IGNORE_PP, but additionally cannot be copied by all move-copying effects (barring reflection). They are also "skipped over" by most moveset and move history-related effects (PP reduction, Last Resort, etc).

      They still respect the user's volatile status conditions and confusion (though will uniquely cure freeze and sleep before use).

    • ReadonlyNORMAL: 1

      This move was used normally (i.e. clicking on the button) or called via Instruct. It deducts PP from the user's moveset (failing if out of PP), and interacts normally with other moves and abilities.

    • ReadonlyREFLECTED: 5

      This move was reflected by Magic Coat or Magic Bounce.

      Reflected moves ignore all the same cancellation checks as MoveUseMode.INDIRECT and retain the same copy prevention as MoveUseMode.FOLLOW_UP, but additionally cannot be reflected by other reflecting effects.

    Settings

    Member Visibility