Editing Artificial intelligence

{{ArticleIcons|series=y}}
'''Artificial intelligence''', abbreviated as '''AI''',  in the [[Super Smash Bros. (series)|''Super Smash Bros.'' series]] refers to the intelligence of any computer-controlled (CPU) character (called '''computer players''' in-game) in the single-player and [[Versus Mode]]s. In Versus Mode, players can preset the AI of a computer player. In [[Adventure Mode]], [[All-Star Mode]], and [[Classic Mode]], players can still set it to some degree.

Artificial intelligence levels range from 1-9, with 1 being the weakest and 9 the strongest. Certain [[event]]s in ''Melee'' give opponents a level of 0, which results in them not attacking at all (but still following whatever movement behaviour they would normally have).

==Training against CPUs==
Players commonly fight against CPUs to train when there aren't other players around to play. This is a practise that is criticised by some, as besides even the highest level CPUs being of a lower level than a typical casual player, CPUs do things that human players never do (and will never do things that are common for human players to do), as well as having several exploitable flaws and being completely incapable of [[mindgames|mind gaming]]. Training against CPUs does not adequately train one's cerebral skills (such as the ability to read and bait opponents), and it is often argued that excessive training against CPUs may cause a player to develop habits that work against CPUs but will be heavily exploited by human players.

However, training against CPUs does have its merits. CPUs can be used to effectively practise [[combo]]s and [[chain throw]]s, as well as [[spacing]], [[punish]]ing attacks, and other [[tech skill]] related things. CPUs can be more effective than human players in this regard, as they're always available and won't refuse a match where a player just want to practise the aforementioned things. Many top professional smashers have reported using CPUs to train, such as {{Sm|Nairo}} and {{Sm|Vinnie}}.

There is no consensus though on what level CPU is best to train against, with players mostly having their own personal opinion on what level is most effective. Some say level 1 CPUs are the best, as they won't have inhuman perfect shielding abilities and won't disrupt the player's training. Some say level 9 CPUs are the best, as they will actively try to fight the player and can punish mistakes the player makes. Some others say level 5 CPUs are the best for being a middle ground between the two extremes. Another camp maintains what level is best is dependent on what a player is trying to practise.

==Flaws in the AI==
While it is notable that high level CPUs are precise with their reflexes, such as being able to [[power shield]] almost any attack, reflect projectiles with little hesitation, counterattack out of knockback the instant they can act, and land or control attacks that human players would find difficult such as Yoshi's [[Egg Throw]] and Pikachu's [[Volt Tackle]], all three games are known for having AI that can be extremely flawed in most scenarios. There are many complaints surrounding the poor artificial intelligence of computer players in ''[[Super Smash Bros.]]'' and ''[[Super Smash Bros. Melee]]'', though ''[[Super Smash Bros. Brawl]]'' also received attention to its flawed AI system; in all three games, particularly noteworthy and amusing AI flaws have been uploaded to YouTube, often by saying that the AI in the games is "just too good".

===''[[Super Smash Bros.]]''===
<!-- READ THE FOLLOWING GUIDELINES BEFORE ADDING ANY EXAMPLES:
1. Avoid adding very specific, situational instances that rarely, if ever, show up, where a computer player may not perform optimally. If you have to specify what level the CPU is, the character, the stage, what the CPU is attempting, and even the exact location on the stage, do not add it. Also do not add examples that require nonstandard gameplay, and do not add examples that you have to write a small guide to replicate.
2. Suboptimal play by the CPU in general does not constitute an AI flaw. For something to be considered an AI flaw, it has to be a repeated behavior by the AI that directly hinders a CPU's performance regardless of outside circumstances.
3. Per the previous guideline, a potential example must be a behavior by the CPU that it will nearly always repeat when the circumstances leading to the example occurs. 
4. Examples are ordered, so when putting down an example, make sure it fits the order. The order goes; general flaws > character specific flaws > item related flaws > stage related flaws > character + specific stage flaw.-->

Examples of flawed AI in ''Super Smash Bros.'' (''SSB'') include:
*Level 9 CPU players which [[roll]] incredibly often compared to their later ''Melee'' and ''[[Super Smash Bros. Brawl]]'' counterparts.
*The general poor [[recovery]] abilities of CPUs -  e.g if the player jumps into a level 9 [[Captain Falcon (SSB)|Captain Falcon's]] [[Falcon Dive]], he will not attempt to recover. The same thing occurs if the player attacks any CPU character out of their [[up special]].
**A CPU {{SSB|Ness}} will always aim his [[PK Thunder]] as a recovery sideways, even if the ledge is above him.
**A CPU Kirby and {{SSB|Jigglypuff}} will immediately use up all their jumps after getting knocked off the stage.
**CPU Jigglypuffs never use [[Pound]] to recover. At high levels, however, they may still use it if characters approach them from the side, in an attempt to attack.
*CPUs have poor shielding abilities. Sometimes, if a player attacks a high-level CPU with a consecutive-hitting [[jab]] (such as Kirby's), the CPU may shield and stay in place until the shield eventually breaks, without even attempting to escape the attack by rolling.
*A tendency toward [[projectile]]/charge move [[spam]]ming (such as a level 9 {{SSB|Pikachu}} consistently using [[Thunder Jolt]] or a level 9 {{SSB|Donkey Kong}} using [[Giant Punch]] cancels).
*A level 9 {{SSB|Link}} CPU will always use [[Boomerang]] as its first attack. Similarly, a level 3 Link will use [[Bomb]] as its first attack.
*A {{SSB|Fox}} fighting a human player who runs to the edge of a stage such as [[Dream Land]] will cause Fox to follow and aim his [[Fire Fox]] off of the stage - resulting in a self-destruct.<ref>{{cite web| url = http://www.youtube.com/watch?v=OGPMxhH5Zss | title = Super Smash Bros 64 - Tricking Fox's AI | accessmonthday = Jan 2| accessyear = 2011| author = [http://www.youtube.com/user/JetlagJad JetlagJad]| date = 2007-05-23| format = video| work = | publisher = YouTube| quote = }}</ref>
**Similarly, if a character is far away from it, a high-level Fox CPU may repeatedly use [[Blaster]], even if the enemy is shielding or protecting. As a result, a player using [[Ness]] can easily trick Fox's AI by standing far away from it and using [[PSI Magnet]] to absorb the shots.
*On the [[Kirby Team]] in the [[1P Game]] mode, when the Kirbys are knocked off the stage, they tend to [[fast fall]] as soon as they run out of mid-air jumps, without even using [[Final Cutter]] to recover. This makes easy for players to KO them, even at Very Hard [[difficulty]].
*When an [[item]] appears, a level 9 CPU will cease all fighting to get the item. This may cause them to walk into stage hazards (such as the tornado on [[Hyrule Castle]]) or other traps (such as a [[Motion-Sensor Bomb]]). However, they will ignore items dropped on clouds in the {{SSB|Yoshi's Island}}, and under normal conditions they won't run into wandering [[Bob-omb]]s.
*A CPU player who picks up a throwing item when another player is below their platform will repeatedly throw the item to the ground until it disappears - even if the item is a [[Bob-omb]], which often leads to the CPU self-destructing.
*If there is a player on the right side of the [[Saffron City]] stage, CPUs will walk into the doors of the Pokémon trap.
*On [[Peach's Castle]], if a human player stands on the bottom [[platform]], a CPU on one of the moving platforms will run into the wall repeatedly.
*In [[Hyrule Castle]], a level 9 {{SSB|Kirby}} may repeatedly use [[Stone]] on the left side of the stage, causing him to slide down, resulting in a [[self-destruct]].


===''[[Super Smash Bros. Melee]]''===
The AI in ''Super Smash Bros. Melee'' is notorious for how flawed it is. Computer players, regardless of level, primarily fight by constantly [[approach]]ing to then [[spam]] their [[neutral attack]] and [[dash grab]]s when close to opponents, while using any projectiles they have periodically when opponents are out of the [[range]] of their jab and grab. In {{SSBM|Kirby}}'s case, CPUs repeteadly use [[Final Cutter]] to attack. Though the exact rates of usage vary depending on the character, the AI will generally avoid using their [[tilt]]s and [[smash]]es outside certain situations, and will almost never use [[aerial]]s to attack unless they were already in the air from trying to reach an opponent's position (such as if they were jumping up to an opponent on an upper [[platform]]) or from being hit into the air from a prior attack. Specific CPUs also have a tendency to overuse one move aside from the aforementioned, such as {{SSBM|Ganondorf}} constantly using [[Dark Dive]] when a character is in front of and above him, and {{SSBM|Zelda}} constantly using her [[down tilt]] to "lock" opponents. The AI is additionally notorious for how terrible it is at [[recover]]ing. While the AI won't give up during recoveries like in ''Smash 64'', the AI still has significant problems with its recovery skills. The AI always recovers in a basic and predictable pattern (which itself causes them to fail many recoveries that were possible), while making no effort at all to fight off [[edge-guard]]ers. This results in computer players being extremely easy to edge-guard, which is exacerbated by ''Melee'''s edge-guarding friendly [[:Category:Game Physics|physics]]. 

The AI in ''Melee'' also make poor use of their [[shield]]s and defensive maneuvers in general. Computer players, even at level nine, will often not use their shields to block attacks, and will often not use [[rolling dodge]]s, [[sidestep]]s, and [[air dodge]]s to dodge attacks. As such, computer players will often take whatever attack is thrown their way, expending no effort to dodge it, and when combined with their constant approaching, will often lead to them just walking into a player's charged attack. There is an exception to this though with a few attacks that the AI was programmed to dodge at all costs (such as {{SSBM|Bowser}}'s [[up smash]] and [[Bowser Bomb]]), where computer players will always [[roll dodge]] away or [[air dodge]] if the attack is being used in their vicinity (this can be observed by charging Bowser's up smash below a CPU on a platform, who will then roll back and forth until Bowser unleashes his smash). Additionally, despite minimal use of their shields, CPUs are very precise with [[power shield]]ing, so when they do shield an attack, it is usually a power shield. On top of this, while the AI will often not shield physical attacks, higher level CPUs will always shield any projectile if they are not in [[lag]]; level nine CPUs will usually perfect shield to reflect projectiles. They do this to a fault however, which can be exploited with rapid projectiles like [[Blaster]], as when under projectile fire, CPUs will prioritise shielding against all projectiles over all else, leading to the CPU just standing there and shielding against rapid projectiles until the opponent ceases fire or they [[shield break|break their shield]]. 

Certain stages are notorious for exploiting poor AI, such as stages with pits like [[Jungle Japes]], where the AI does not properly recognise these pits and will often fall into them to [[self-destruct]] while trying to attack a player near them. The AI also plays especially poorly on moving stages such as [[Icicle Mountain]], where computer players will move up one platform at a time, which is too slow to escape the lower blast line when the stage speeds up.

The AI is also extremely incompetent with handling [[item]]s and their effects. When their size and physic changes, the AI ignores it and will play as if they were normal, which leads to [[giant]] CPUs inadvertently walking off stages, and [[metal]] CPUs plummeting to their death as they attempt to attack an offstage player. When an item appears, CPUs will never pick them up, only picking them up accidentally when trying to attack an opponent next to the item; additionally, they have poor concepts of knowing what items are in front of them, frequently causing them to walk into set [[Motion-Sensor Bomb]]s, walking [[Bob-omb]]s, and into hostile [[Poké Ball]] Pokémon. There is an exception to this when there are healing items, [[Poké Ball]]s, [[Cloaking Device]]s, or [[Hammer]]s present; CPUs will usually immediately cease all fighting against the player and will instead flee to pick up these items. They will often put themselves in harm's way while trying to do so, just to obtain said item.

<!-- READ THE FOLLOWING GUIDELINES BEFORE ADDING ANY EXAMPLES:
1. Avoid adding very specific, situational instances that rarely, if ever, show up, where a computer player may not perform optimally. If you have to specify what level the CPU is, the character, the stage, what the CPU is attempting, and even the exact location on the stage, do not add it. Also do not add examples that require nonstandard gameplay, and do not add examples that you have to write a small guide to replicate.
2. Suboptimal play by the CPU in general does not constitute an AI flaw. For something to be considered an AI flaw, it has to be a repeated behavior by the AI that directly hinders a CPU's performance regardless of outside circumstances.
3. Per the previous guideline, a potential example must be a behavior by the CPU that it will nearly always repeat when the circumstances leading to the example occurs. 
4. Examples are ordered, so when putting down an example, make sure it fits the order. The order goes; general flaws > character specific flaws > item related flaws > stage related flaws > character + specific stage flaw.-->

Specific examples of poor AI include:
*Computer players have generally poor recovery abilities:
**They will never attempt to fight off or evade edge-guarders.
**They will only use their midair jumps and [[up special]] move to recover - never any alternate recovery methods such as [[side special]] moves, [[Air dodge]]s or [[wall-grapple]]s.
***{{SSBM|Luigi}} acts as an exception; he will instead always use the [[Green Missile]] and never use [[Super Jump Punch]] to recover (even when necessary). 
**CPU {{SSBM|Fox}}, {{SSBM|Falco}}, {{SSBM|Marth}}, {{SSBM|Roy}}, {{SSBM|Zelda}}, and {{SSBM|Mewtwo}} will always aim in the same upward diagonal trajectory when recovering, even if using such a trajectory will result in them failing to make it back to the stage while a more desirable trajectory would allow them to recover successfully.
**If a CPU {{SSBM|Jigglypuff}} runs out of midair jumps when recovering, it will use [[Sing]], instead of using [[Pound]] or an air dodge, guaranteeing a failed recovery.
**A CPU {{SSBM|Ness}} will only utilise [[PK Thunder]] when recovering if they are set to level nine, and will always aim it in the same upward diagonal trajectory. A lower level CPU Ness will fall and self destruct if their midair jump is not enough to make it back to the stage.
**CPU {{SSBM|Peach}}es will never [[float]]. Also, when they use Peach Parasol, they will follow the player even if they are near a pit, making Peach approach it and then, depending on the stage, not be able to reach a platform or ledge, resulting in a self-destruct.
*Computer players have poor concept of continuous attacks:
**They never charge attacks that require button holding, including: [[smash attack]]s (with the exception of the {{SSBM|Ice Climbers}}, who occasionally charge their [[forward smash]]), [[Shield Breaker]], [[Hero's Bow]], [[Skull Bash]], [[Green Missile]], [[Rollout]], and the [[Super Scope]], among others. [[Fire Breath]] also applies; it will never be held past the minimum length. 
**They never use the second hit of {{SSBM|Link}}'s or {{SSBM|Young Link}}'s forward smash; as a result, CPUs cannot KO effectively as either character, as Link's forward smash is relatively weak when the first hit connects, while Young Link's first hit deals low, set knockback to set up the second, more powerful attack.
**CPU {{SSBM|Fox}}es and {{SSBM|Falco}}s will never hold their [[Reflector]] past the minimum length. The same goes for {{SSBM|Kirby}}'s [[Inhale]], and {{SSBM|Ness}}'s [[PSI Magnet]].
**A CPU Kirby under the effect of [[Stone]] will never end the transformation early. Besides allowing players to easily punish a CPU Kirby with powerful attacks, this will cause him to self destruct on some stages, if he hits a breakable platform above the lower blast line or is on a slope that ends offstage, cause him to slide down and off to the lower blast line. 
*CPUs will never initiate a [[fast fall]].
*AI have poor taunting habits. After the CPU respawns, if the player jumps for a distance while the CPU is walking toward them, the CPU may eventually taunt for no apparent reason.
**Upon KOing a character, CPUs will usually taunt, regardless of what is occurring around them.
*CPUs will never initiate a [[dash]] outside [[dash grab]]s and/or [[dash attack]]s.
*Upon returning on a [[Revival platform]], CPUs will immediately reenter the fight again regardless of what is happening.
*CPUs will still shield attacks when [[invincible]].
*CPUs will never [[sidestep]] intentionally; the only time they will sidestep is when they are trying to both shield and fall through a soft platform.
*When an opponent is knocked down or hanging on a ledge, CPUs will only use [[down tilt]]s and [[down smash]]es to attack them.
*CPUs cannot properly recognise the height differences that occur when standing on slopes, which will lead to things like a CPU flailing above an opponent with their jab when higher up on a slope.
*CPUs do not recognise pits as if they were an offstage area, leading to the CPU just walking into them and falling into them as the CPU attempts to carelessly attack an opponent near the pit, which often results in the CPU self-destructing.
*A CPU Jigglypuff never uses [[Rollout]] or [[Rest]]. Strangely, a Kirby with Jigglypuff absorbed will attempt to use Rollout, but will never charge it when using it (as noted above).
*A CPU {{SSBM|Marth}} and {{SSBM|Roy}} will never use [[Counter]].
*CPU Kirbys have unusual behavior dealing with [[Inhale]]. When they first use Inhale, they will constantly use it until they can copy a character. Additionally, they will heavily [[spam]] the move they copied. They will also never utilise the option to just spit a character out.
*As they approach the player, CPU {{SSBM|Captain Falcon}}s and {{SSBM|Ganondorf}}s will periodically use [[Falcon Punch|Falcon]]/[[Warlock Punch]], [[Raptor Boost]]/[[Gerudo Dragon]], and up tilt in the case of Ganondorf, like how other CPUs use projectiles while approaching. They do this despite the opponent being completely out of their range, and the very long [[lag]] of these attacks making it easy for opponents to punish them. They will occasionally use [[Falcon Kick]]/[[Wizard's Foot]] instead, however.
**CPU Captain Falcons will additionally always use Raptor Boost after using forward throw on someone, even if it would cause them to go offstage and self-destruct. They may also use Raptor Boost if the player is near the ledge offstage, attempting to hit them, but usually falling off the stage. CPU Ganondorfs however do not exhibit this behavior with Gerudo Dragon.
**CPU Ganondorfs will also nearly always use Dark Dive when someone is near above them, even if they're near the edge of the stage, which can cause him to use Dark Dive and then fall offstage, self-destructing. CPU Falcons however do not exhibit their behavior with Falcon Dive.
*CPU Kirbys and Bowsers will use their down specials (Stone and Bowser Bomb respectively) on foes below them when they are in midair, regardless of what is below them. Similarly, some grounded CPUs will spam a special attack if a player is above them: a CPU Ness will spam [[PK Flash]], a CPU Pikachu or Pichu will spam [[Thunder]], and a CPU Peach mostly uses [[Peach Parasol]] if the player is at a close range.
*A high level CPU {{SSBM|Mario}} and {{SSBM|Dr. Mario}} will often jump off the stage and attempt to use their [[forward aerial]] to edgeguard against recovering opponents, which depending on the stage, frequently leads to self destructs. CPU {{SSBM|Captain Falcon}}s exhibit similar behavior with their [[down aerial]], but rarely self destruct when they do so.
*Despite the AI's tendency to shield any projectile as noted earlier, CPU Bowsers will never shield projectiles when approaching the player, even at level nine. <ref>http://www.youtube.com/watch?v=gW7lnHpTzhU</ref>
*CPUs will usually air dodge upon being hit by Luigi's sourspotted Super Jump Punch, even if it results in falling off the stage. 
*Picking up either a Hammer or a Starman will cause all the CPUs to run to the opposite side of the stage and stand there until the effect wears off; they will not use any defensive maneuvers whatsoever.
*If a CPU grabs a [[Warp Star]], they will never change the trajectory of the attack.
*If a CPU grabs a Hammer, it will chase opponents until they reach a wall and continually jump in place even if the obstacle can be jumped over. They will also jump offstage to chase opponents that have jumped off the stage, and self destruct in the process.
*If they are next to the radius of [[Venusaur]]'s earthquake or near [[Wobbuffet]], the CPUs may shield even though they are not in the Pokémon's damage radius.
*When the player stands still on certain locations in stages, all opposing CPUs will cease all movement and action if the player is not in attack range, until the player moves or one of the aforementioned desired items appears. A notable example of this is the right edge of the middle right platform in {{SSBM|Battlefield}}, which can be exploited in [[Cruel Melee]].
*In [[Princess Peach's Castle]], CPUs will always run to the opposite side of the castle when [[Banzai Bill]] appears. During this, the CPU will ignore opponents, and will not attack nor defend themselves unless an opponent comes near. When this does happen, it disrupts their normal behavior pattern and they will sometimes stay on the side of the castle where the Banzai Bill is and get KO'd by its explosion.
**Also, CPUs may run straight into the Banzai Bill in order to reach the other side.
*In [[Brinstar]], CPUs will always go to the hovering metallic platform in the centre when acid rises from the bottom. During this, the CPU will ignore opponents, and will not attack nor defend themselves unless an opponent comes near.
*When at a stop on [[Mute City]] and the stage is about to move again, they will not jump back on the main moving platform unless a player or item provokes them to go on it, leading to them sustaining avoidable damage when the stage moves.
*In Jungle Japes when the player is Player 1 while a CPU Ness is Player 2, if the player does not move, Ness will try to jump over to the player, but will fall into the river and self destruct his first stock. Similar behavior occurs against level nine {{SSBM|Yoshi}} on [[Fourside]], who will air dodge into the first pit and SD.
*In Jungle Japes, if the player stands still on the right platform as a CPU Fox comes off the [[revival platform]], Fox will repeatedly jump into the river and fail to recover until he runs out of stocks or time runs out. A CPU Roy will also exhibit this behavior in this situation.

===''[[Super Smash Bros. Brawl]]''===
In ''Super Smash Bros. Brawl'', the AI is generally more proficient with character recoveries (most prominently {{SSBB|Luigi}}). If a human player gets an [[item]] like a [[Starman (item)|Starman]], rather than just trying to avoid that character, they'll also use the opportunity to attack any stragglers. When a [[Smash Ball]] appears, computer players will aggressively attack it at opportune times, while repelling anyone who tries to get it as well. Another significant change in AI from ''Melee'' is that computer players have a preference to targeting human players before other computer players.

Another new feature is that the computer's level in [[Training Mode]] can now be selected. The AI is also improved greatly, as opponents set to Attack mode will actively fight the player, rather than walking towards them and rarely throwing an attack like in previous installments.

Also, for each CPU level, the game gives a word to describe the CPU's skill level:
#Puny-1
#Wimpy-2
#Weak-3 (the default level)
#Normal-4
#Hardy-5
#Strong-6
#Burly-7
#Mighty-8
#Nasty-9

Many rumors have circulated about the AI of ''Brawl''. One claims that level 9 CPUs read button commands the player inputs, thereby allowing them to perfect shield more often. This sparked general dislike among the community, many of whom labelled the idea as "cheating". [[SLAPAHO]] tested this to see if this were true; no definitive results were returned, however, and they admitted that more experimentation and tests were needed. 

Another rumor claims that there's a system in ''Brawl'' that enables AI players to "learn" from human players.<ref name="CECPUexpBlog">{{cite web| url = http://allisbrawl.com/blogpost.aspx?id=8848| title = The Wonders of Brawl's CPU Experience System| accessmonthday = Jan 2| accessyear = 2011| author = [http://allisbrawl.com/blog.aspx?id=10347 ChurroEmiliano]| date = 2008-12-31| format = blogpost| work = | publisher = [http://allisbrawl.com/ AllIsBrawl.com]| quote = When developing Super Smash Bros. Brawl, Sakurai integrated an experience system in which CPUs (mostly level 9/nasty) would actually learn from other players and try to mimic such strategies.  This experience system is subject to all characters. / The way you and others play on your save data, the way they will intend to play, keeping several of their own ways of playing as well. You can tell a huge difference, by comparing...a new fresh save data of Brawl, to a very much used save data.}}</ref><ref name="CECPUexpVideo">{{cite web
| url = http://www.youtube.com/watch?v=g4HvhIPOz4I| title = The Wonders of Brawl's CPU Experience System| accessmonthday = Jan 2| accessyear = 2011| author = [http://www.youtube.com/user/ChurroEmiliano ChurroEmiliano]| date = 2008-12-29| format = video| work = | publisher = YouTube| quote = Churro (Snake) vs. Lvl 9 Link}}</ref><ref name="CEFalconPunch">{{cite web
| url = http://www.youtube.com/watch?v=YMcEUsMd9Cw| title = Falcon Punch Much? 0_0| accessmonthday = Jan 2| accessyear = 2011| author = [http://www.youtube.com/user/ChurroEmiliano ChurroEmiliano]| date = 2008-12-31| format = video | work = | publisher = YouTube| quote = After having several Falcon Punch free-for-alls, the CPU wanted to fit in.
}}</ref> [[All is Brawl]] blogger Churro Emiliano documented much of this widely for the first time in a blog post made at the end of 2008. Aside from some advanced techniques and play-styles, the AI have also been reported to "learn" to [[taunt]] a KO by crouch-spamming,<ref name="jerkette">{{cite web| url = http://www.youtube.com/watch?v=diJX703iC0A| title = ...jerkette| accessmonthday = Jan 2| accessyear = 2011| author = [http://www.youtube.com/user/Hoidsa Hoidsa]| date = 2009-05-13| format = video| work = | publisher = YouTube| quote = }}</ref> and to overuse Falcon Punches after humans play several Falcon Punch free-for-alls.<ref name="CEFalconPunch" /> It is currently not confirmed if there is a learning mechanism or not.

The flaws in ''Brawl''’s artificial intelligence are considerably lesser and less recurrent than in ''Melee'', but they can still be potent. Computer players still tend to be easier to KO and [[edgeguard]] than the average human player, even when set at level 9, due to not utilising survival techniques such as [[DI]] and usually not fighting back when being edgeguarded. CPUs do, however, [[air dodge]] when sent flying, which provides minimal cushioning for knockback although usually not enough to save them. Computer players sometimes have difficulty avoiding certain stage hazards (most notable on [[Halberd]]), and are prone to self destructing in scrolling stages, such as the [[Past and Melee Stages|Melee Stages]] [[Rainbow Cruise]] and [[Big Blue]]. They have generally poor edgeguarding abilities (though unlike the previous two games, self destructing while attempting to edgeguard is very rare), and will usually stand on the ledge and spam projectiles when the player is recovering; they will only attack offstage with certain characters such as [[Meta Knight (SSBB)|Meta Knight]]. And while they are better at recovering than in previous game, computer players still under utilise recoveries, such as by not making use of alternate recovery options with some characters, or always recovering in the same direction with a recovery move. A computer player (regardless of level) will also always aim for solid platforms that can be [[edge sweet spot|sweetspotted]] when recovering, even when there are "soft" platforms off the stage.

Computer players also tend to play strangely in complex custom stages, and in overly large complex stages like [[New Pork City]] and [[75 m]].

Aside from being flawed as stated above, in [[Free-for-all]]s, CPUs will target the human player even if they aren't [[team]]ed. They will also target the character that has the highest damage to earn a KO, and in doing so will not attack other CPUs, which results in them following each other in lockstep.

Specific examples of poor AI include:
<!-- READ THE FOLLOWING GUIDELINES BEFORE ADDING ANY EXAMPLES:
1. Avoid adding very specific, situational instances that rarely, if ever, show up, where a computer player may not perform optimally. If you have to specify what level the CPU is, the character, the stage, what the CPU is attempting, and even the exact location on the stage, do not add it. Also do not add examples that require nonstandard gameplay, and do not add examples that you have to write a small guide to replicate.
2. Suboptimal play by the CPU in general does not constitute an AI flaw. For something to be considered an AI flaw, it has to be a repeated behavior by the AI that directly hinders a CPU's performance regardless of outside circumstances.
3. Per the previous guideline, a potential example must be a behavior by the CPU that it will nearly always repeat when the circumstances leading to the example occurs. 
4. Examples are ordered, so when putting down an example, make sure it fits the order. The order goes; general flaws > character specific flaws > item related flaws > stage related flaws > character + specific stage flaw.-->

*CPUs still underutilise the recoveries of several characters:
**A CPU {{SSBB|Ness}} and {{SSBB|Lucas}} will always hit themselves with [[PK Thunder]] in the same upward diagonal trajectory when recovering, even if using such a trajectory will result in them failing to make it back to the stage while a more desirable trajectory would allow them to recover successfully. This is especially noticeable on {{SSBB|Final Destination}}, as Ness will often not make it back to the stage when using PK Thunder to recover (when recovery is possible), while a Lucas will often launch himself underneath the stage lips.
**A CPU {{SSBB|Ike}} will not use [[Aether]] unless he is directly underneath a ledge. This causes him to self destruct without trying to recover, or waiting too long to use Aether and failing a recovery that was possible. CPU Snakes exhibits similar behavior using [[Cypher]], often choosing to use it too late and self destructing.
**A CPU {{SSBB|Yoshi}} will never use Egg Throw for recovery.
**A CPU Luigi will never use [[Luigi Cyclone]] for recovery.
**A CPU {{SSBB|Meta Knight}} will never use [[Mach Tornado]] nor [[Drill Rush]] for recovery, and will often use [[Dimensional Cape]] to recover instead of Meta Knight's other superior recovery options.
**A CPU {{SSBB|R.O.B.}} will not input any actions after using [[Robo Burner]] until it reaches the ground, grabs a ledge, or is hit by an attack.
**If an opponent jumps into a {{SSBB|Fox}} or {{SSBB|Falco}} using their up specials during the charge up phase of their move, they will angle the recovery horizontally and self-destruct.
**If a CPU {{SSBB|Mr. Game & Watch}} uses [[Fire]] and fails to recover, he will repeatedly use [[Judge]] until the bottom blast line is crossed. While not necessarily problematic, there are instances where if a CPU Mr. Game & Watch reaches the apex of Fire and ends up short of the stage but in distance of reaching the ledge, the CPU will decide to use Judge too soon, causing him to miss the ledge and self destruct.
*If a CPU KOs a player, while the player has invincibility frames after respawning, the CPU will run away from the player and jump onto a platform if there is one nearby, without trying to dodge the player's attacks.
*When players grab the [[ledge]], CPUs will stand still a safe distance from the ledge for some seconds before pursuing the ledge hanging player.
*If a CPU, regardless of level, is hit near the upper [[blast line]] while above an elevated platform, they'll fall straight down until reaching the ground after knockback is finished, while making no attempt to dodge or counterattack a pursuing player.<ref>http://www.youtube.com/watch?v=D9nursdpKIw</ref>
*When hit by an electric hitbox, a CPU may randomly DI up or down, more often DIing down, which can result in instances of an attack with an electric hitbox KOing them when the computer player would have survived otherwise.
*While CPUs in ''Melee'' could [[meteor cancel]] to a moderate degree, CPUs will never meteor cancel in ''Brawl'', sustaining the meteor smash's full knockback before attempting recovery. This results in meteor smashes KOing computer players at much lower percentages than they KO human players.
*CPUs have [http://www.youtube.com/watch?v=qryrf87N5OQ difficulty recognising walls].
*A CPU {{SSBB|Bowser}} will never hold Fire Breath past its minimum length. CPU {{SSBB|Charizard}} replicate equivalent behavior with [[Flamethrower]].
*When {{SSBB|Snake}} uses his [[down throw]] near an edge on a CPU, the CPU will always roll toward the nearest edge the instant they can make a move.
*When {{SSBB|Ganondorf}} uses [[Flame Choke]] on a CPU, they will never act the soonest they can.
*A low leveled Fox, Falco and Wolf will mostly self-destruct when using Landmaster, especially if the target is hanging on a ledge or so. A high level CPU will stay in place and repeatedly perform barrel rolls against opponents grabbing the ledge. 
*When a CPU Luigi uses [[Negative Zone]], he will almost always spam [[Fireball]] repeatedly, even when set to level nine.
**Similarly, a CPU Pit using [[Palutena's Army]] will spam [[Palutena's Arrow]].
*CPUs with a [[Gooey Bomb]] or [[C4]] stuck on them will constantly shield and dodge until it falls off or explodes.
*CPUs holding a [[Cracker Launcher]] will not turn around, and will shoot at a slow rate in their current trajectory while repeatedly stepping back if their targeted player is not in front of them.
*In the underground version of [[Mushroomy Kingdom]], CPUs will sometimes repeatedly attack the blocks, ignoring the player even if items aren't on.

==External links==
*http://www.youtube.com/watch?v=rk_EhpxKu8Q - Abusing DK's AI in training mode
*http://www.youtube.com/watch?v=71yUbTsR54E&feature=related - The majority of [[TAS]] videos by Andtgar show off abusing ''SSB'' AI while perfectly comboing.
*[http://youtube.com/watch?feature=related&v=EZwg37tu6B0 A video showing an AI flaw of Falco in ''Melee'']

==References==
<references/>

[[Category:Gameplay]]
	You aren't logged in. While it's not a requirement to create an account, doing so makes it a lot easier to keep track of your edits and a lot harder to confuse you with someone else. If you edit without being logged in, your IP address will be recorded in the page's edit history.
	Log in	Create account
Insert common text
Signature	~~~~
Symbols	£ ¥ ° ± × ÷ € ≈ ≠ ≤ ≥
Diacritics	À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï Ð Ñ Ò Ó Ô Õ Ö Ø Œ Ù Ú Û Ü Ý Þ ß à á â ã ä å æ ç è é ê ë ì í î ï ð ñ ò ó ô õ ö ø œ ù ú û ü ý þ ÿ
Wikitext	[] [[]] \| [[Category:]] [[File:]] #REDIRECT: [[]] {\| \|- \|\| \|}
Templates	{{cleanup}} {{image}} {{reflist}} {{stub}} {{d}} {{delete}}
Formatting	<!----> <br> <code></code> <gallery></gallery> <nowiki></nowiki> <ref></ref> <references/> {{#widget:YouTube\|id=}}
Substitution	<includeonly></includeonly> <noinclude></noinclude>