Stuck at: Goal: Turning in Quest - Foolish Endeavors : QuestID - 11705 : To - Garrosh Hellscream : ID - 25237
Hi,
Kasia,
Your Honorbuddy appears to be seriously damaged.
Several hundred consecutive lines of this:
[06:58:28.220 D] [InteractWith-v719(debug)] Navigator unable to move to destination(interact with Nerub'ar Egg Sac (id: 187655, dist: 19.5, noLoS, TtB: 49s), <2517.565, 6107.762, 76.96187>) on ground--try MovementBy="FlightorPreferred".
Several hundred consecutive lines of this:
[07:03:05.995 D] (Singular) EnsureMovementStoppedWithinMelee: stopping because target at 3.7 yds
[07:03:05.995 D] (Singular) StopMoving: Now, unit == null, method:
[07:03:06.187 D] (Singular) EnsureMovementStoppedWithinMelee: stopping because target at 3.7 yds
[07:03:06.187 D] (Singular) StopMoving: Now, unit == null, method:
Several hundred consecutive lines of this:
[07:25:54.423 N] [Singular] Casting Nimble Brew on Me @ 100.0%
[07:25:54.872 N] [Singular] STUNNED! (loss of control)
[07:25:55.916 N] [Singular] STUNNED! (loss of control)
[07:25:56.947 N] [Singular] STUNNED! (loss of control)
[07:25:57.901 D] (Singular) [CombatLog] SPELL_CAST_FAILED Nimble Brew#137562 failure: 'Can't do that while stunned'
Several hundred consecutive lines of this:
[07:26:11.799 D] Cleared POI
[07:26:11.867 D] Changed POI to: Type: Kill, Name: Varidus the Flenser
[07:26:11.867 D] Cleared POI - Reason No targets in target list - POI.Kill Sanity Checks
A schizophrenic Honrbuddy that can't figure out whether to turn in or kill mobs (several hundred lines of this):
[07:30:32.046 D] Changed POI to: Type: QuestTurnIn
[07:30:32.079 D] Changed POI to: Type: Kill, Name: Varidus the Flenser
[07:30:32.176 N] [Singular] invalid attack unit Varidus the Flenser.DBF4 cannot be Attacked
[07:30:32.176 D] Cleared POI - Reason Singular detected invalid mob as BotPoi
More schizophrenia with a behavior that is not even running (it terminated at
[07:28:15.596 D]) vs Quest TurnIn:
[07:32:55.478 N] [EscortGroup-v594(info) @line 1945]: Moving to nearest escorted unit
[07:32:56.888 N] Moving to Type: QuestTurnIn
[07:32:58.436 N] [EscortGroup-v594(info) @line 1945]: Moving to nearest escorted unit
[07:32:59.818 N] Moving to Type: QuestTurnIn
[07:33:01.606 N] [EscortGroup-v594(info) @line 1945]: Moving to nearest escorted unit
[07:33:02.957 N] Moving to Type: QuestTurnIn
In short, these are not profile issues. Worse, I wouldn't even know how to begin repair other than with a 'clean install'.
[post=1120664]HelpDesk: "Clean installing" Honorbuddy[/post]
cheers,
chinajade
[EDITED 17-Nov-2013 by
chinajade]: We've seen a second instance of this issue. It looks like the
EscortGroup behavior may have been damaged in some fashion by the Honorbuddy re-architecture. (I.e., the
EscortGroup behavior has not been modified in a very very long time). We've captured this issue to our internal tracking system, but no ETA on when it will be repaired.)
[size=-2]Ref:
[post=1325006]Kasia's original post w/log[/post][/size]