Feedback talk:Bug reports/AI bugs

Vizunah Square

This happens if the party runs off before Togo and Mehnlo have their dialogue, especially if there is an MM in the party as Mehnlo gets very caught up in healing the minions rather than playing his part in the story. If the party slows down and allows the dialogue to complete, Togo will follow without incident. -- Wyn talk 18:12, 5 October 2009 (UTC)

This happens at every closed door in the mission if you're unlucky. Mhenlo will always keep healing minions if they are in range instead of saying his lines. Sometimes he even walks up to them and sticks with them in the second part of the mission. --Golgarit Raven 04:09, 30 October 2009 (UTC)

Signing

Is there a reason that no one is signing their posts any more? Or is this a poolicy that I skimmed over on the new "rules"? -- Timeoffire45 rawr 18:10, 5 October 2009 (UTC)

No clue why no one is signing. -- Wyn talk 18:14, 5 October 2009 (UTC)

It's a recursive effect. I didn't sign because nobody else was, and there was nothing on the page that said "sign your comments" explicitly. I'll put a notice at the top of the page. —Jette 03:34, 6 October 2009 (UTC)

Oh, I was supposed to sign, my bad. Misery 11:58, 6 October 2009 (UTC)

Thanks Jette :) -- Timeoffire45 rawr 23:29, 6 October 2009 (UTC)

Misery

Thanks for all the great input :> --The preceding unsigned comment was added by User:Moo Kitty (talk).

Yes, I appreciate you taking the time to actual document the bugs that are apparently widely known, yet not in the bug database.   — Tennessee Ernie Ford (TEF) 03:33, 7 October 2009 (UTC)

Thanks for the thanks TEF. I suspect some people who appreciate my work have ulterior motives for thanking me, but that's ok because I have ulterior motives too. Hi Moo Kitty. Misery 08:02, 7 October 2009 (UTC)

guildwars 2

im a nobody my hobby is gw i would like to be a tester for gw2 if you need pleas i would like to try it so if and only if you wont i would like to help fan of G.W Roy Kluth e.mell <email address removed> thank you --The preceding unsigned comment was added by User:Cook (talk).

Hi, don't post your address here please, spammers read it. Also I doubt they're selecting people for the beta test yet. — Why 18:45, 4 September 2010 (UTC)

Turtle Bug

In FA, I've noticed that it's not only the turtles that are bugged. On rare occassions, the warriors also get stuck at the gate (after the turtle is dead and dissappeared) and don't move forward. They would get stuck where the turtles normally get stuck (meaning they're unobstructed yet don't move). Not sure if that's relevant to figuring out what's wrong with the turtles. P.S. Please move FA turtles/bugs up on your list of bugs to fix. It's one of the very few active PvP places left in Guild Wars where people of all experience levels can play together. (HA and GvG aren't easy to setup for most players, I personally don't do Codex much, RA is fine for the most part, I personally think JQ is boring/repetitive, and AB tends to be a little empty at times (plus it's in kurzick territory most of the time which doesn't help, but that's not Anet's fault)) = 7 PvP types, 3 of which (HA,GvG,CA) aren't necessarily rookie friendly. 152.7.14.158 03:04, 20 November 2010 (UTC)Nova

Issue: Heroes and henchmen might become relocated to an incorrect position while being flagged off-compass.

One possibility is that your heroes are running away from the threat and attempting to heal themselves.

During Unspeakable, Unknowable I've never had the problem of the heroes (or hench) running away while off-compass; a problem only occurs if my toon is close enough to the flags that the heroes/hench attempt to follow. I think something else is going on. If you want more insight (and have the time to spare), you could try letting your character die off-compass and then clicking on the names of one of the flagged heroes to see what they actually do.  — Tennessee Ernie Ford (TEF) 18:09, 7 January 2011 (UTC)

The Bugs are hindering the game

FA: Siege turtles stop to attack an enemy through a wall through the FIRST doors....they will not move to get a better vantage point, and players exploit this to distract the turtle so the turtle refuses to move through the door. The Obstructions Kill it.

Jade Quarry: The Juggernaut refuses to move from the base even if the shrine is recapped at times, Ditto for the Turtles.

Hero AI/Melee AI: its kind of frustrating to see Snakebite and other Melee refuse to attack(and only use Your All Alone) an enemy im wanding to death instead of helping out...which quite frankly is BULL. an ALLY is a friend...friend is there for you...this isnt the case.

The Random Arena Bug:lately Code 015....no one can get a consecutive win to gain Gladiator points...its stopping the title, and if they do get consecutive wins...its only up to about 3.

The Development team(s) need to worry either about 2 things:

1. The Urgency of Guild Wars 2 being produced and released...the players can wait, they have seen enough to draw them in already.

2. Fixing The Bugs in the original Guild Wars to keep the interest in the content, which we realize is happening in upcoming updates, however these bugs...hinder most players ability to enjoy the content and are forced to either rezone,resign or move on to a close related game such as Aion or the dreaded Runescape...These bugs being fixed will increase the players interests in certain pvp and pve areas as complications won't drive them away...

seeing as a few developers from the development team took time off their own schedule while working on guild wars 2 to make that fancy page of the commando, how much time can it honestly take to fix a few tiny bugs..do it on your spare time...just as long as somethings being done....even news.

The Synchronizing In RA kind of eliminates the "random" does it not?

Lithril 23:13, 6 April 2011 (UTC)

Removal of Obvious not bugs

Can we just remove things that people have labeled as bugs but aren't? Such as "my summon attacks stuff through wall but won't follow me" - since they act as minions anyway.. --File:User Chieftain Alex Chieftain Signature.pngChieftain Alex 11:00, 17 May 2011 (UTC)

What we've been doing (that seems to be okay) is:

1. Tagging the posts with if it's the community agrees it's not a bug and if, based on the description, it might be a bug, but there's not enough info.
   • In both cases, add an appropriate note (in addition to an edit summary).
2. After a period of time, moving to the not a bug archives those that have been labeled .

It might also be worth re-ordering some of the bugs so that: the headers better summarize the issue and to group similar reports together.

On the whole, it's up to ANet to decide what is/isn't a bug; our job here is to make sure that it's as easy as possible for the QA/live teams to read the bug reports (not just this one), without interfering too much with the community's ability to communicate. There's a lot of eye-of-beholder disagreement about what constitutes a bug and, whenever possible, we should make sure that any small fraction of us doesn't impose our definition on the rest of the community. — Tennessee Ernie Ford (TEF) 16:26, 17 May 2011 (UTC)