ArenaNet talk:AI bugs/AI Issues Archive 1

Control Panel issues

Hero -- All

Issue: Targeting AI: Hero's do not follow specific targets set by them via the hero panel when a party flag is setup
How to fix: Update AI Code or remove your party flag as a work around
Additional info: When you plant a Party Flag and set a hero on guard mode, and then select a specific target enemy for a hero using the hero panel, they will not attack that specific target as they should when the party flag is not set. Instead they will target whatever they feel like generally and ignore the hero panel specific target

Chik En 23:48, 18 October 2007 (UTC)

I've never had this problem, can you provide more details on how to reproduce this bug? They do switch targets to spread hexes like Parasitic Bond around and will also attack any target that blocks them, but otherwise they seem to follow their target just fine with or without a party flag. --Draikin 16:47, 19 October 2007 (UTC)

I specifically noticed this with Koss. If I set the All party flag (keystroke 9) and he is on guard mode and then I select an enemy and set him to target that enemy ONLY till it is dead. He will ignore this directive unless I remove the all party flag. This has happened with him as well as other Hero's but mostly I have seen him do it because I usually bring him. Chik En 20:55, 19 October 2007 (UTC)

Even if I set the all party flag and give a hero a specific target like you said, he still never attacked other targets. Unless someone can verify that this bug really exists, I think this should be moved to the Unconfirmed issues. --Draikin 23:18, 6 January 2008 (UTC)

Hero Control Panel -- Interrupted skills

Issue: When you manually click a skill on the Hero Control Panel and the hero gets interrupted while trying to use it, the checkmark will remain on that skill and the hero will not use any other skills until it is recharged.
How to fix: Update the Hero Control Panel so that manually checked skills that get interrupted are automatically unchecked so that the hero can continue to use other skills.
Additional info: none

--Draikin 12:08, 23 September 2007 (UTC)

This is intended functionality. It may not makes sense for more competitive play, but the intent is to make it so that if a skill is selected, that it will eventually be used. I personally have a hard time trying to track the actions of all my heroes, while playing my character. If I manually select to use a hero skill, it means I really want it used. The fix described seems like it would cause more frustration if the player was not aware that the hero was interrupted, the hero would seem to just fail to cast. Let me know if you think the majority of players would want this change. We can look into it more. Ben Kirsch 19:04, 25 January 2008 (UTC)

I'll ask the community about this. I guess another solution would be to somehow alert the player that the skill was interrupted, perhaps by displaying a certain effect on the skill icon. With the current implementation it can be very annoying when you order a hero monk to use a skill and he gets interrupted, since by the time you realize the skill was interrupted he could already be dead because he stopped using skills. --Draikin 16:57, 26 January 2008 (UTC)

I'm going to archive this since I assume this mechanic is here to stay. --18:35, 3 January 2009 (UTC)

Hero Control Panel -- Energy bar displays incorrect value

Issue: When heroes are resurrected at the base in Hero Battles, their energy bar will sometimes appear to be empty although they do in fact have full energy.
How to fix: Fix the bug that causes this problem.
Additional info: none

--Draikin 23:24, 27 November 2007 (UTC)

Are you still seeing this? I tried to reproduce the issue, but haven't had any luck. Ben Kirsch 22:06, 28 January 2008 (UTC)

It doesn't happen all that often so I have no idea exactly what triggers it. I'll ask around and see if anyone encountered this bug recently. --Draikin 01:15, 29 January 2008 (UTC)

Going to archive this since it probably doesn't occur anymore. --Draikin 18:35, 3 January 2009 (UTC)

Hero Control Panel -- Heroes not canceling skills which were manually disabled

Issue: When a player manually disables a skill on the Hero Control Panel and the hero happens to be activating that skill at the same time, the hero continues to use the skill until he has activated it. This causes them to unnecessarily lose energy and use a potentially undesired skill.
How to fix: When a hero is ordered to disable a skill which he’s already activating, the hero should cancel it right away.
Additional info: This is ironic in light of the bug reported above where heroes cancel skills that are manually clicked

--Ronduwil 00:46, 4 January 2008 (UTC)

Just like a player, the hero will still lose the energy if the skill is canceled mid cast. In most cases, the player will benefit more from casting the spell then simply losing the energy. For long casts, or skills that have a particular disadvantage against a given foe I could see this being an issue, but for the majority of skills the benefits of completing the cast seem to outweigh having the skill canceled. Ben Kirsch 20:02, 25 January 2008 (UTC)

That makes sense. If you really don't want them to use the skill you can always flag them to a new location to force them to cancel it before disabling the skill. --Draikin 16:57, 26 January 2008 (UTC)

I went ahead an put a check mark next to this issue since it has been discussed. If anyone thinks a change is still needed, feel free to remove the check, and leave a note describing what you think needs to be changed. Ben Kirsch 22:10, 28 January 2008 (UTC)

I used a different check mark icon for this kind of problem so people know it can still be debated. --Draikin 16:29, 14 March 2008 (UTC)

Going to archive this since there's been no response for a while now. --Draikin 18:35, 3 January 2009 (UTC)

Flagging and Movement Issues

Heroes -- Warriors

Issue: Warrior heroes will pursue their chosen target even when an individual flag is set and when in defensive combat mode.
How to fix: Fix the AI so that warrior heroes will absolutely not move from the location of their indvidual flag when in defensive mode uless they begin taking more than X dps, in this way, make the warrior heros viable tanks in PvE.
Additional info: When the party flag is set, allow the warrior heroes to move about as they currently do, only when they have an individual flag, warrior heroes will not move.

This is intended behavior and not a bug. Changing it to your version would make the game completely unplayable with heroes. --Draikin 18:27, 20 November 2007 (UTC)

Hero -- Ogden Stonehealer

Issue: From my observations Ogden tends to disobey flagging commands and will run way ahead into where the tank is working even though he has no touch skills on his skill bar. Ogden was doing this even while set to defensive mode.
How to fix: Make him obey his flagging commands.
Additional info: Sometimes other EoTN heroes will undergo this behaviour but it is only more apparent in Ogden's case.

Hero -- Razah

Issue: Razah runs away in one direction and does not stop...ever(NOT flagged)
How to fix: Make Razah not run away
Additional info: He literally runs to the edge of the map and tries to walk into the wall

Razah doesn't have a special AI, whatever caused this would have happened to any hero. --Draikin 13:00, 2 October 2007 (UTC)

Hero -- All Heroes

Issue: When attacked by AOE, they spend an extended amount of time standing in it before running away, IF they run away..
How to fix: Make them like enemies that instantly flee from the slightest AoE
Additional info: none

Henchman -- Henchman

Issue: When a melee player, leading Henchman & Heroes attacks a group of enemies, the Henchman & Heroes tend to lag behind, out of projectile/casting range. Sometimes they don't even move. This is without setting a flag.
How to fix: Heroes & Henchman should act the same way they did in Previous installments of Guild Wars. Only staying back when they are told to. Heroes & Henchmen should always follow the player when not flagged.
Additional info: This does not mean all NPCs should be within melee range.

Hey, I put the "not considered an issue but up for discussion" icon on this one because I'm not seeing this problem myself. Is there some specific situation where your melee henchmen and heroes aren't running up to attack an enemy? What do you mean by previous installments of Guild Wars? Is this only happening in a specific campaign? If someone could please respond with a little more information I would be glad to look into this further. Thanks. -Kim Chase 22:37, 10 July 2008 (UTC)

Sounds like the (resolved) bug that used to cause henchmen and heroes to stop moving when they encountered spirits. --Draikin 00:25, 12 July 2008 (UTC)

I think this can be archived. --Draikin 22:04, 3 January 2009 (UTC)

Heroes -- All

Issue: If a hero is flagged individually -and then the All NPC flag is set -removing the specific Hero's flag makes it so that hero follows the player and does not respond to the All NPC flag. (Specifcally: Set a Hero's Flag. Set the All NPC Flag. Remove Hero's Flag.)
How to fix: Have the heroes check and respond to the All NPC flag if one is set after their specific flag is removed.
Additional info: none

Yukiko 05:17, 8 September 2007 (UTC)

Actually a lot of Hero Battle players use this to their advantage, once you get used to it this really isn't a problem. Changing it to the "correct" behavior would actually make it more difficult to control heroes (once you set the main flag you can't have one hero follow you around anymore). --Draikin 02:19, 26 November 2007 (UTC)

I think this can be archived. --Draikin 22:04, 3 January 2009 (UTC)

Skill Usage Issues

Assassin

Hero & Henchmen skill usage -- Shroud of Silence

Issue: The AI doesn't use this skill on monks.
How to fix: Update the AI so that is does use the skill on monks.
Additional info: none

--Draikin 23:24, 27 November 2007 (UTC)

Hero & Henchmen skill usage -- Siphon Speed

Issue: This skill is only used when the hero/hench is on the run and chasing a target. If the assassin is attacking a non-moving target he won't use the skill even if he has a combo that depends on the opponent being hexed.
How to fix: Update the AI so that the skill is used even when the target is not moving.
Additional info: none

--Draikin 23:47, 17 September 2007 (UTC)

Now that the functionality of the skill itself has changed this is no longer a problem so I'll archive it. --Draikin 21:48, 5 April 2008 (UTC)

Assassin Skill Issue -- Endure Pain

Issue: Assassin heroes will not use Endure Pain, even if they also have health boosters such as Death's Charge, Heart of Shadow, or Shadow Refuge available to take advantage of it.
How to fix: Make her activate Endure Pain then augment her Health with any Skills which would give her a boost to her current Health.
Additional info: If the AI has access to boosts in Health, they should not wait until their Health is low before activating this Skill. Having a sudden boost to maximum Health and the means to access it should be a priority for an AI.

--Tashiro 07:58, 4 October 2008 (UTC)

Duplicate issue that only needs to be posted in the warrior skill section, so I'm archiving this. --Draikin 17:32, 4 October 2008 (UTC)

Hero & Henchmen skill usage -- Recall

Issue: Despite being a maintained enchantment the AI will still maintain Recall on a random ally.
How to fix: Like most other maintained enchantments, the AI should simply not use this skill and let the player use it manually.
Additional info: This behavior isn't really a problem since the player can still disable the skill.

--Draikin 13:00, 2 October 2007 (UTC)

This issue has been reported. --Andrew Patrick 23:19, 14 May 2008 (UTC)

In the end this really is a non-issue, unless anyone objects I think this can be archived. --Draikin 18:45, 8 August 2008 (UTC)

Dervish

Hero & Henchmen skill usage -- Reaper's Sweep

Issue: The AI only uses this skill on foes with less than 50% health, despite the fact that it deals a considerable amount of armor-ignoring damage.
How to fix: Update the AI so that is does use the skill on foes with more than 50% health.
Additional info: none

--Draikin 19:20, 28 November 2007 (UTC)

The problem here is the 8 sec recharge time. If you use it too soon, it may not recharge in time to cause the DW when the target gets to <50% health. Overall, I think it's okay. -- Hong 01:29, 15 January 2008 (UTC)

That's a good point, you can't really expect the AI to use it more effectively than they do now. I think I'll just archive this. --Draikin 19:24, 17 January 2008 (UTC)

Monk

Heroes & Henchies -- Monks

Issue: Heros and hench treat protection spells as heals, as an example they waste energy between fights throwing prot spirit or rof on minions - they'll prot spirit minions during a fight instead of casting prot on the guy(s) taking damage
How to fix: Fix the AI to only use prot in relevant circumstances (party member/ally is taking lots of damage per second, cast some prot), party member is taking damage (not degen'ing) cast rof, etc.
Additional info: none

Hero & Henchmen skill usage -- Guardian

Issue: The AI doesn't use this skill enough, this is especially noticeable when compared to how often they use Shield of Absorption.
How to fix: Update the AI so that Guardian is used more often, similar to how they use Shield of Absorption.
Additional info: none

--Draikin 00:36, 13 September 2007 (UTC)

After testing this again it seems they do use Guardian just as often as Shield of Absorption so I archived it. --Draikin 18:02, 24 January 2008 (UTC)

Heroes & Henchies -- Monks

Issue: Monk heroes waste energy healing and prot-ing necromancer minions.
How to fix: I would guess (but I'm not positive) That the AI as it is now would act in the same manner with ritualist and ranger spirits, so have them not target any summoned creature.
Additional info: none

Spirits are not affected by Monk heals, or Enchantments, so there shouldn't be an issue here. As far as Monk heroes healing minions, I personally like this functionality. I generally have a minion master hero, and have found that they are much better when assisted in healing the minions. I can see how in certain party setups where there wasn't enough healing this could be an issue, but a change here really doesn't seem warranted. The negative impact to players currently counting on Monk Heroes healing Minions seems like it would outweigh the current complaint with how Monk AI functions. Ben Kirsch 22:56, 28 January 2008 (UTC)

The issue here is that a minion master is always going to bring Blood of the Master to heal his minions, and it's far more efficient for the monks to heal the necro instead of healing minions individually. Since minions constantly need to be healed, the monks often won't be at full energy when the team goes into battle again. The ideal solution here is to not let the monks heal the minions anymore and simply let the AI use Blood of the Master more often than they do now. That way the minions won't die and the monks don't have to spend nearly as much energy healing the necromancer. --Draikin 00:14, 29 January 2008 (UTC)

Another issue is that some of us use minions as nova bombs. In that scenario, healing the minions is not simply a waste of energy; it's counterproductive to boot. I also second Draikin's statement. It is much easier for the MM to use Blood of the Master to heal all the minions in the area at once than it is for the healer to spam his bar down to zero in a vain attempt to keep a group of 10 minions at max health.--Ronduwil 07:10, 2 February 2008 (UTC)

We can't assume that someone with minions is "always" going to bring Blood of the Master or Veratas Sacrifice, or that they will never want to use monk heals on their minions. Some players use skills like Heal Area to keep their minions alive, and they should be free to make a N/Mo MM with Heal Area if they want to. If we force the AI to not heal minions, we remove these kinds of options entirely. -Kim Chase 17:58, 10 July 2008 (UTC)

Hero & Henchmen skill usage -- Unyielding Aura

Issue: While they are maintaining Unyielding Aura, I've noticed that heroes treat its ressurection ability as having the range it formerly did; that is to say, they they attempt to ressurect fallen players from wherever they may be by repeatedly cancelling and reapplying UA from wherever they happen to be standing.
How to fix: Teach the AI that they need to be in cast range for UA to actually resurrect a player.
Additional info: The hero will attempt to move about one step every time they recast UA in an attempt-it seems-to resurrect the party member, but after they cast and then cancel they do not move closer for the interim ten seconds. I don't know if it was just a bad night when this happened to me, but I'm hoping that-if it wasn't a fluke-it can be fixed.

-- Timeoffire45 22:25, 18 June 2009 (UTC)

I tried for about an hour now in PvE and PvP, but could not get this to reproduce. Do you have any more details as to how you noticed that? --Golgarit Raven 19:45, 25 June 2009 (UTC)

Sadly, no >_< It wasn't my hero, so I can't be sure of too much, but the player MAY have had the hero flagged. In fact, after doing testing of my own, I can't get the hero to cancel UA until they get fairly close in the first place...ugh.... So, my original bug is a dud, I suppose >_< I feel pretty stupid now....

As a side note, a hero will not resurrect a player when they are flagged just barely outside of cast range and, even when not flagged, will not resureect a player until they move well into cast range (as in, move within agro range of the corpse as opposed to the edge of agro/cast range). If that made sense, I will do a little jig...and, again, sorry for the basic waste of time >_<

No problem, I'll just x it out for now. --Golgarit Raven 18:26, 26 June 2009 (UTC)

Elementalist

Hero & Henchmen skill usage -- Blinding Flash

Issue: This skill is only used to blind opponents from a certain profession instead of all professions. For instance the skill is not used on monks and ritualists even if they are attacking with a sword and have 12 swordsmanship.
How to fix: Update the AI so that any opponents using ranged or melee attacks are blinded regardless of their profession.
Additional info: none

--Draikin 23:49, 9 September 2007 (UTC)

I've been noticing that the Ai choose their attacks for blindness, dazing, anti-spell and attack hexes etc based on the weapon their target is carrying, I've tested this with heroes and enemy ai, with myself and just watchem them attack each other, it appears to be the case. --Ckal Ktak 14:09, 5 December 2007 (UTC)

Hero & Henchmen skill usage -- Rodgort's Invocation

Issue: The AI uses this skill only on foes who have 0.25¼ of they health remaining. This is a poor way of using this skill destructive power, there are many ways to paliate its high cost now that heroes use Glowing Gaze and Mind Blast much better.
How to fix: Change the hero AI so that it uses the skill more often and regardless of the current health of their target.
Additional info: none

--FunnyUsername 14:16, 26 August 2008 (UTC)

I think the current AI behavior for this skill isn't that bad: when they can only hit one target, they'll use it when it's at 10% health. When they can hit multiple targets, they'll use it normally (on recharge if it's their only skill). I guess they could change it so that the skill is "less likely" used on single targets, that would basically make them use the skill more on single targets if they have no other attack skills available. --Draikin 18:46, 26 August 2008 (UTC)

It doesnt matter how many enemies are around the main target, the hero will only use this skill if his target has less than 0.25¼ of their health left. I tested it on the Isle of the Nameless, locked Saousuke on the Practice target, wich has 5 more tagets Nearby that can be hit by Rodgort's Invocation, and he didnt use it unless its main target health was less than 25%. Go and try if u dont belive me :). --FunnyUsername 19:48, 26 August 2008 (UTC)

I believe you, but heroes won't use AoE skills correctly on the Practice targets for some reason. They do use the skill correctly against normal targets, you can verify this in PvE. --Draikin 21:42, 26 August 2008 (UTC)

That same thing applies to many tests of AI behaviour. Who really cares how the AI responds to practice targets. What matters is how it responds to hostiles that fight back; unfortunately, that currently remains fairly screwed up. -- Inspired to ____ 21:51, 26 August 2008 (UTC)

Yep, just checked with "real" foes and they use it properly, kind of strange that they use their skills in a different way with a barrel ...--FunnyUsername 22:21, 26 August 2008 (UTC)

To be clear...I am not a fan of the AI and am as near to quitting playing this game as I have ever been since the recent changes seem to have helped the HM enemies and hurt heroes & henches; however, the AI has always seemed to take into account the threat level, etc. when deciding what to cast or if to cast helpful enchantments vs damage causing spells as talked about below and this is not a bad thing. So it's only obvious that a barrel would be dealt with differently then an attacking foe, or that whether to reenchant would be based on the threat level, nearness to death of the enemy, etc. -- Inspired to ____ 00:51, 27 August 2008 (UTC)

The below issue is a different case, it happens regardless of what kind of enemy or number of enemies, the AI will simply spam some spells before refresh the attunement and it doesnt matter if its target is either an Oni, a Warden, a Barrel or a Spirit, at least of what i experienced. Im aware that in some situations, it may be more usefull for example to use an Eruption to blind a bunch of meleers foes rather than refreshing an attunement, but that happened to me on counted situations while playing the game compared to the amount of times that left me with a burden elementalist with almost no energy.

Its just that i think that energy management is quite important, and that its best to spend 2 seconds casting an enchantment so they dont run out of energy during a combat. Anyway, heroes already use Glyph of Lesser Energy over an offensive skill, why not apply the same to attunements?. --FunnyUsername 09:44, 27 August 2008 (UTC)

Mesmer

Hero & Henchmen skill usage -- Backfire

Issue: The AI doesn't use this skill on monks.
How to fix: Update the AI so that it does use the skill on monks.
Additional info: none

--Draikin 23:24, 27 November 2007 (UTC)

Hero -- Gwen

Issue: Does not use Power spike if another interrupt skill is present(recharging or not)
How to fix: Update her (and possibly other) AI(s) to use this skill
Additional info: Tested with builds OQNDAjwDLXwoDAAAAAAAwOB, OQNDAjwDHXAAAAAAAAAYnA, and OQNDAjwDPAVu2FIDM6yBShdC.

I wasn't able to reproduce this issue. Has anyone noticed this problem recently? Leah Rivera 19:53, 28 May 2009 (UTC)

Will check on this today, would ruin my build for her if true. --Golgarit Raven 08:03, 17 June 2009 (UTC)

I have Power Spike on Gwen more or less constantly along with other interrupts and I have never noticed this problem. The AI does sometimes prefer other interrupts such as Cry of Frustration, but I'd think that is for logical reasons. Vili 点 12:01, 17 June 2009 (UTC)

Agreed. Seems to run just fine, as intended. Even on the Isle she uses it perfectly. Can be closed. --Golgarit Raven 14:04, 17 June 2009 (UTC)

Agreed that the AI uses this equally often as other interrupts, I'll go ahead and close it. --Draikin 17:09, 17 June 2009 (UTC)

Necromancer

Hero & Henchmen skill usage -- Vampiric Spirit

Issue: The AI doesn't use this skill often enough and therefore fails to maintain the enchantment.
How to fix: The AI should maintain this enchantment 100% of the time, in the same way they use enchantments like Masochism.
Additional info: none

--Draikin 21:29, 18 November 2007 (UTC)

Hero & Henchmen skill usage -- Soul Leech

Issue: The AI doesn't use this skill on monks.
How to fix: Update the AI so that it does use the skill on monks.
Additional info: none

--Draikin 23:24, 27 November 2007 (UTC)

Hero & Henchmen skill usage -- Wail of Doom

Issue: This skill is used on recharge against any opponent.
How to fix: This skill should primarily be used on melee opponents who are attacking (in the same way they use Insidious Parasite), and if there are no targets who are attacking or if the player locked the hero on a specific target who isn't attacking then it should be used as a normal interrupt (like leech signet).
Additional info: none

--Draikin 13:00, 2 October 2007 (UTC)

Now that the functionality of the skill itself has changed this is no longer a problem so it can be archived. --Draikin 22:03, 11 April 2008 (UTC)

Hero & Henchmen skill usage -- Blood of the Master, Death Nova, and Jagged Bones

Issue: Necro heroes hang back out of range and putz around with these skills even if the rest of the party has engaged in fighting.
How to fix: If a battle begins, necro heroes should lower the priority on these skills until the minions have been brought into fighting range.
Additional info: You can work around this by flagging the necromancer hero into the fray, but it gets annoying to have to do that every time. Once the minions have entered combat, the current behavior is fine as is.

--Ronduwil 02:32, 4 January 2008 (UTC)

This is something that is working as intended. All of these skills are useful in a Minion Master build and if it causes the Necromancer Hero to fall behind some, or force us to manually flag them where we want them to be located, its because the Ai is doing its job attempting to keep a minion pack going. You could disable the skills when you are on the run as an alternate to flagging the hero though. Elijah Miller 19:24, 9 July 2008 (UTC)

Hero -- Livia

Issue: Does not cast Mark of Pain
How to fix: Not sure if any heroes do, but make them use it appropriately
Additional info: None.

The AI does use the skill. --Draikin 15:54, 2 January 2009 (UTC)

Hero -- Livia

Issue: Does not cast Jagged Bones on Jagged Horrors.
How to fix: Make her cast it more often, she could keep up a 10 minion army, if using the build I have for her properly.
Additional info: None.

The AI does use the skill on Jagged Horrors. --Draikin 15:54, 2 January 2009 (UTC)

Ranger

Hero -- Concussion Shot

Issue: For some odd reason when ever I give a ranger the skill Concussion Shot they will never use it. 99 times out of 100 they will use another skill or they will use no skill at all. Ex. Jin uses Savage Shot on Flare. Flare is casted again and she lets it cast even though she has the energy for Concussion Shot.
How to fix: Is there something wrong with the code that tells the AI when it is to use this skill?
Additional info: none

After doing some testing they don't seem to prefer using other interrupts, so I'm not sure what's causing them to ignore the skill in your case. --Draikin 17:25, 15 December 2007 (UTC)

My Jin has no issue with this skill, but it seems you have to put it on the far left on your skill bar. Mine is on slot 2, next to Archer's Signet. The use of this elite might also be the reason for which she tends to use it more frequently. -- 81.246.250.214 20:45, 27 April 2008 (UTC)

My hero was actually using this skill quite well. I tried it with the skill on the far left and far right, and he always did a good job of determining when to use this skill vs another skill. I'm going to mark this as won't fix, but if someone can give a specific circumstance where their hero uses (or doesn't use) this skill in a less-than-ideal manner, I will take another look. --Andrew Patrick 21:51, 10 July 2008 (UTC)

Common skill issues

Hero & Henchmen skill usage -- Spirits

Issue: The AI uses a lot of spirits regardless of whether or not there are enemies around. Basically as soon as you zone they start putting down spirits even if you don't want them to, and you have to disable the skill altogether and manually control them to prevent them from placing spirits in the wrong area. Also when the hero/hench is following you or running towards you after they were resurrected and you did not set a flag, they will simply stop to put down spirits first leaving an entire trail of spirits behind. The spirits in question where this behavior occurs are every ranger spirit expect for Favorable Winds and Muddy Terrain, and the following binding rituals: Life, Preservation and Restoration (Gaze of Fury also belongs to the list, but for this particular skill it does seem to make sense that they use it wherever possible).
How to fix: Let the AI put down all the spirits only during combat, in other situations where players still want to place spirits they can simply manually click them.
Additional info: none

--Draikin 23:49, 9 September 2007 (UTC)

You cannot assume that you will never want a hero to cast a spirit or binding ritual outside of combat. In fact, it is common that you will want to stack spirits before the enemy reaches you, or so that you can pull enemies into an area. -Kim Chase 18:49, 10 July 2008 (UTC)

Hero & Henchmen skill usage -- AoE attacks and Target Lock

Issue: Heroes will use AoE attacks like Searing Flames and Savannah Heat on a target of their choice even when they are specifically locked on a different target.
How to fix: When the player locks a hero onto a target, heroes should only use AoE attacks on that particular target.
Additional info: none

--Draikin 21:29, 18 November 2007 (UTC)

On second thought this probably isn't such a good idea after all, the main reason I asked for this change was because I was tired of seeing my elementalist heroes ignore their target lock and attack pets, but that's a different problem altogether.

Hero -- All of them, I assume.

Issue: They use all target-enemy skills on your target, even if they are locked on different ones.
How to fix: Make them use skills on THEIR target, not yours.
Additional info: None

frvwfr2 (talk · contributions) 00:40, 17 June 2008 (UTC)

They do use their skills on their target, they'll only end up attacking your target when using skills designed to ignore target lock (Like Parasitic Bond). --Draikin 22:50, 2 July 2008 (UTC)

Well then blackout needs to have its ignore-lock removed. ~~ frvwfr2 (talk · contributions) 15:30, 25 July 2008 (UTC)

Skills like blackout are just too complex for the AI to handle correctly, I always disable it. You could argue that the ignore-lock should be removed for this skill but they'd still be doing more harm than good when spamming it. --Draikin 16:22, 25 July 2008 (UTC)

I was using it in spikes in hB, till I realized that they target your spike, instead of their target... ~~ frvwfr2 (talk · contributions) 21:25, 25 July 2008 (UTC)

That's basically a common problem with the AI, skills that ignore target lock don't prioritize locked targets (I don't think I actually posted that issue here yet). That means they might end up using Parasitic Bond and Faintheartedness on a pet while you actually locked the R/P instead. On the topic of Blackout, you'd actually have a strong case to argue that it should only be used on the locked or otherwise called target. It's not a skill that can be spammed on multiple enemies and there's no conditional effect that would warrant this behavior either. Currently the AI doesn't use it on non-caster targets while the skill is actually a solid counter to adrenaline based builds. --Draikin 20:57, 28 July 2008 (UTC)

Combat and Behaviour Issues

Hero & Henchmen -- Hero & Henchmen

Issue: Sometimes, they will stop attacking an enemy if we do not continue to attack said enemy.
How to fix: Prevent them from stopping to attack enemies?
Additional info: Here's the long version: this is something I have noticed often, but I managed to get a good screenshot this time. I went AFK, and a boss group walked into range of my party. The heroes and henchmen killed most of the group, but they did not kill the monk boss...Instead, they would attack, then stop attacking when the boss got at low health, then the boss would heal himself, then they would attack again, stop attacking again once the boss was at low health, and so on. Here are some screenshots:

Here the enemy is within range, but the henchmen and heroes are standing still.

Then they go attack.

Then they decide to just stand still and let the enemy heal again.

This feels very similar to how the heroes and henchmen will stop attacking an enemy who has just used Call to the Torment.

—The preceding unsigned comment was added by Erasculio (talk • contribs) 15:02, 8 September 2007 (UTC).

Unless someone disagrees I think this problem should be archived as well. This is basically intended behaviour, since (in PvE at least) heroes will only attack when you order them to attack or when they are under attack. If you don't call a target or lock them onto one, they will not attack unless something attacks your team. In this case the monk boss probably wasn't attacking your team because he was low on health, causing your team to stop attacking as well. --Draikin 23:18, 6 January 2008 (UTC)

Hero -- Heroes won't attack creatures in aggro range until a human attacks

Issue: When a called target dies, the heroes will not select new targets; instead they stop attacking. Worse, melee heroes will literally run back to the party's location. They snap out of this state if another target is called or if a human-controlled player attacks something.
How to fix: Heroes in attack or guard mode should automatically fight anything that enters the aggro bubble. If a target dies they should automatically switch targets if there are still hostile creatures in aggro range.
Additional info: This is not as noticeable in bigger parties because one or more human players is usually attacking at a given time. I mostly notice this behavior when I am by myself and I'm in the middle of using 'non-hostile' (summon, healing, or protection) spells. This issue may be related to the Hero & Henchmen issue reported by Erasculio.

--Ronduwil 01:11, 4 January 2008 (UTC)

Actually they'll only stop attacking (as far as I know) when nobody is attacking the team, which is probably why Erasculio's heroes stopped attacking that monk boss since it didn't attack when it was low on health. As long as somebody is attacking your team, your heroes will continue to select their own targets and you don't need to call anything. Of course if your heroes stop attacking while your team is still taking damage then that would be a problem, but I've never actually seen them do that. --Draikin 03:43, 4 January 2008 (UTC)

Here's why I might be confused: I almost always bring a minion master, so if my minions are engaged, I consider my party to be in battle. It could very well be that none of my party members were directly under attack, but my minions were. My perception, however, was that Talon Silverwing was running back to my side in the middle of a fight. I didn't even notice the problem until I started trying to work my monk through Eye of the North. I generally don't attack while I'm monking, so the problem becomes more pronounced. This could be a sticky issue. On one hand I don't want my party to attack distant targets that are attacking my minions because the minions are brain-dead and I often leave them to die while they run off to attack something I have no intention of engaging. However, I do want my party to attack targets in their aggro bubble even if they are only beating on the minions. --Ronduwil 07:42, 4 January 2008 (UTC)

That would explain the problem. Minions attack whatever enters their aggro bubble but heroes don't consider them as part of the team. The problem here is that the heroes' "attack" status is triggered slightly beyond their aggro bubble (it's about 1.2 x aggro bubble range). Any ally under attack within that range will cause them to attack as well, except for minions. It's really up to the player to call targets in this case, because otherwise the AI just doesn't know whether you want to abandon your minions or attack instead. --Draikin 12:38, 4 January 2008 (UTC)

I'm going to archive this, I don't think this behavior is actually a problem at this point. --Draikin 22:39, 3 January 2009 (UTC)

Independent NPC issues

NPC -- Ebon Vanguard Assassin

Issue: Sometimes attacks the wrong target when two targets are close together.
How to fix: Alter the Ebon Vanguard Assassin's AI so that he "locks on" to the target he shadow steps to.
Additional info: On Isle of the Nameless, if Ebon Vanguard Assassin Support is used on the Master of Damage, the assassin will attack the western adjacent target.

By selecting a target you are simply chosing where he will shadow step to. he Ebon Vanguard Assasin is not intended to lock onto the target, and it can choose to select a new target. -Kim Chase 18:57, 10 July 2008 (UTC)

General & Miscellaneous issues

NCP's In Alliance Battles -- All NCP's in there

Issue: People take them with them
How to fix: No idea
Additional info: None

If you're referring to the Saltspray Dragon Hatchlings and the elite warriors, rangers and elementalists, it's not a bug, they're supposed to follow players. -- Gordon Ecker 08:31, 17 May 2008 (UTC)

Monster -- Scarab Nest Builder AI bug

Issue: when surrounding the Monk Queen Boss, will not aggro if attacked long ranged (ie, outside aggro bubble)
How to fix: make them less on guard and more aggressive
Additional info: spotted this while doing the Zquest to kill Kepkhet Marrowfest

Katherinezoltin 06:06, 1 May 2009 (UTC)

I think this is intentional. They're ranger trappers, it makes sense for them to hold their position and force melee attackers to walk into their traps. The Brooding Thorns in Urgoz's Warren are another example of stationary trapper monsters. -- Gordon Ecker (talk) 06:13, 1 May 2009 (UTC)

Like Gordon explained, this is intentional. I think this can be archived. --Draikin 22:51, 19 July 2009 (UTC)

→ moved from ArenaNet:AI_bugs

Hero -- Zhed Shadowhoof AI Bug

Issue: Will always rush in to the battle frontline.
How to fix: Make him stay at the backline with the other casters.
Additional info: This happens regardless to his build.

--The preceding unsigned comment was added by 89.139.108.169 (talk).

This I have noticed with Vekk today. When I don't call target he will cast from the back line, but once I call target Vekk will run in as if I smack them with his face. It's really annoying. 000.00.00.00 22:04, 9 April 2009 (UTC)

If anyone wants to see I used Xfire to capture footage of him running in after calling target. I have all ranged skills and a staff on him. 000.00.00.00 22:09, 9 April 2009 (UTC)

I'll check on this today, it would be helpful if you posted your skillbar code in here. I only noticed this behaviour with melee skills and skills like Phoenix, who is ranged and melee at the same time. But we'll see. Wanted to test Phoenix more anyway. --Golgarit Raven 09:25, 18 June 2009 (UTC)

Tested with and without calling, using all 3 Ele heroes. Does not happen when skilled correctly. In case of using Phoenix I'll have to check more thoroughly, as Sousoke did not use it at all. This one can be closed. --Golgarit Raven 17:33, 18 June 2009 (UTC)