Kickz Questing Profile - Uldum

[tumbum]

Quest: Gnomebliteration - Quest - World of Warcraft

Got this Error from the QB

[17:15:56.140 D] Cleared POI - Reason Exception in Root.Tick()
[17:15:56.140 D] Cleared POI
[17:15:56.332 D] System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at System.Collections.Generic.List`1.get_Item(Int32 index)
   at Styx.Bot.Quest_Behaviors.KillGnomes.<get_RunEmOver>b__b(Object r) in f:\TNS\Honorbuddy\Quest Behaviors\SpecificQuests\27779-Uldum-Gnomebliteration.cs:line 181
   at Styx.TreeSharp.Action.RunAction(Object context)
   at Styx.TreeSharp.Action.
.
()
   at Styx.TreeSharp.Composite.Tick(Object context)
   at Styx.TreeSharp.Decorator.
.
()
   at Styx.TreeSharp.Composite.Tick(Object context)
   at Styx.TreeSharp.PrioritySelector.
.
()
   at Styx.TreeSharp.Composite.Tick(Object context)
   at Styx.TreeSharp.Decorator.
.
()
   at Styx.TreeSharp.Composite.Tick(Object context)
   at Styx.TreeSharp.PrioritySelector.
.
()
   at Styx.TreeSharp.Composite.Tick(Object context)
   at Styx.CommonBot.TreeRoot.()

Quest starts normal. Toon fly to the Fireball and use it. Jump down and start to move. After some Seconds the Fireball turn endless in a circle and the Fireball Animation is lost. If i try to move the Fireball by Hand over the Gnomes doesnt work, they dont die. I have to jump out of the Fireball so the Toon gets a new one ... and so on.

 

[Tony]

hmm,i will have CJ take a look on this

 

[chinajade]

hmm,i will have CJ take a look on this

Hi, Tumbum, and thanks for all the awesome feedback you're constantly providing!

I looked at the behavior and captured the issue to the TODO list. Here's the captured note:

* 27779-Uldum-Gnomebliteration.cs:

+ Ref post: Kickz Questing Profile - Uldum
+ The behavior can kill all the Gnomes in the immediate area, then run out of things to kill. Since there
are distance limits on the range of ObjectManager.GetObjectsOfType(), the 'target list' goes empty
and causes this problem. We need to rewrite the behavior to have the ball follow a particular path when there
are no more targets in the immediate area. The path should take us to more targets so
ObjectManager.GetObjectsOfType() can be re-populated.​

Its not a quick fix, as the behavior will need a new capability (to follow a path if no targets in area). Will prioritize it into all the other work remaining to do.

Thanks again for the report!

cheers,
chinajade

 

[Crowley]

No, i know exactly what he is talking about and i am pretty sure it's also a legit player issue. Even if there are gnomes in the immediate area so not sure it is an Objectmanager for targets issue, could be wrong ofc

The actual ball your in disappears. The shadow is on the ground but the ball has gone and gnomes don't die when you roll the shadow over them, which i guess could cause the system.ArgumentOutOfRangeException since the gnomes aren't actually targets at this point. Only way to fix it, like Tum says, is to leave vehicle and the bot takes over and flies back up to get another ball fine. Not really sure what causes the disappearing ball issue. Haven't looked into it too much.

 

[tumbum]

No, i know exactly what he is talking about and i am pretty sure it's also a legit player issue. Even if there are gnomes in the immediate area so not sure it is an Objectmanager for targets issue, could be wrong ofc

The actual ball your in disappears. The shadow is on the ground but the ball has gone and gnomes don't die when you roll the shadow over them, which i guess could cause the system.ArgumentOutOfRangeException since the gnomes aren't actually targets at this point. Only way to fix it, like Tum says, is to leave vehicle and the bot takes over and flies back up to get another ball fine. Not really sure what causes the disappearing ball issue. Haven't looked into it too much.

Thats 100% correct!

 

[CodenameG]

so the solution is to complete the quest manually, then restart the bot, because the issue is ether something we have to work around, or wait for blizzard to fix. both of these are going to take longer then if you would complete the quest manually and move on.

 

[Crowley]

so the solution is to complete the quest manually, then restart the bot, because the issue is ether something we have to work around, or wait for blizzard to fix. both of these are going to take longer then if you would complete the quest manually and move on.

That or make is so that if the bot reads there are no targets in the immediate area for say 30 seconds then use leavevehicle code. He will just fly back and get another ball if that's the case.

 

[Kickazz006]

we'll figure out something guys ... notes added to qb list.

thanks