For when the AI is used, see Battle round.

This page describes the battle AI (artificial intelligence). That is, how computer-controlled opponents in battle (both wild Pokémon and enemy/ally trainers) choose which moves to use and which items to use when. This page assumes the AI controlling an enemy trainer, although it applies for wild Pokémon and partner trainers too.

This is a complicated topic, and unnecessary for most users. Do not attempt to modify the AI unless you have decent scripting knowledge.

Levels of AI

The basic principle of AI in Essentials is that better trainers should be cleverer than worse trainers. A cleverer AI has access to more information about the battle and is more informed about various effects of moves/abilities/items/other effects.

When defining a trainer type, one of the properties that can be defined is a skill level. This is usually the same as the trainer type's base money payout. A higher skill level represents a better AI.

By default, there are 5 tiers of AI in Essentials:

  • Skill level 0 - Used by wild Pokémon, which have an equal chance of choosing each move they know.
  • Skill level 1-31 - Known as PBTrainerAI.minimumSkill. Trainers are assumed to be at least this tier.
  • Skill level 32-47 - Known as PBTrainerAI.mediumSkill.
  • Skill level 48-99 - Known as PBTrainerAI.highSkill.
  • Skill level 100+ - Known as PBTrainerAI.bestSkill.

All trainer types within a given tier will behave exactly the same. The only differences are between different AI tiers, where higher tiers have access to more information and improved calculations.

AI overview

The first thing the AI needs to do each turn is decide whether to use an attack, use an item, or switch their Pokémon with another one. This decision starts in the script section PokeBattle_Battle, in def pbDefaultChooseEnemyCommand.

Firstly, the AI decides whether it should use an item (PokeBattle_Battledef pbEnemyItemToUse). This method goes through each item the AI has, and decides whether to use it. There are separate clauses in this decision for each item the AI has been programmed to recognise - it can recognise (and therefore use) only the basic battle items. Note the order in which each recognised item is checked, e.g. Full Restore takes priority over Full Heal.

If the AI decides not to use an item, then it decides whether it can/should withdraw the Pokémon instead (PokeBattle_AIdef pbEnemyShouldWithdrawEx?). This method looks at several factors in turn, including how good the player's Pokémon's moves will do against it, whether it can use any moves itself, whether it is about to faint because of toxic poisoning or Perish Song, and so forth. This decision can flip-flop as it runs through each factor. Finally, if it has decided to switch Pokémon, the method decides which other Pokémon in the AI trainer's party is the best choice to switch in with, and does so.

If the AI won't switch Pokémon either, then it needs to choose a move to use (PokeBattle_AIdef pbChooseMoves). For each known move in turn, it calculates a score depending on various factors, including the function code and effectiveness of that move, the currently active abilities, move effects and weather, the user's held item and status, and how many Pokémon the player has left. It then compares the scores for each move, and chooses which move to use depending on these scores. If there are no good moves to choose from, there is another opportunity to switch the Pokémon out instead.

Just before it chooses a move to use, the AI will decide if it should Mega Evolve their Pokémon. By default, it will always choose to do so if possible.

Item recognition and effects

The AI needs to be programmed to recognise particular items. Currently it only recognises the basic Potions, Heal items and X stat raisers. This recognition is done in the script section PokeBattle_Battle, in def pbEnemyItemToUse.

Items used by the AI also need code describing their effects - this code is separate from the code used when the player uses the item. These effects are listed in def pbEnemyUseItem, just below the above method. These effects should be the same as if the player had used them, for fairness.

Community content is available under CC-BY-SA unless otherwise noted.