Issues with UseItemOn running between a target to use item on, and XYZ coords

[Inferno]

When trying to create a behaviour that would allow the completion of

War is Hell - Quest - World of Warcraft

Where you have to use a torch to burn either alliance or forsaken corpses, the custom behaviour

CustomBehavior File="UseItemOn" QuestId="11270" MobId="24009" ItemId="12886" NumOfTimes="1" WaitTime="4000" Range="5" CollectionDistance="100" X="1764.727" Y="-5913.021" Z="7.546279"

Travels to the XYZ coordinates, finds a nearby alliance corpse, runs to it, and then tries to run back to the xyz coords, gets about half way, then runs back to the corpse, loops a few times then decides it's spent too long in one place and logs out.

Any idea what would be causing it to run back to the xyz coords after finding a valid target?

Cheers

 

[Kickazz006]

1st, use php instead of code brackets in the dev forum

<CustomBehavior File="UseItemOn" QuestId="11270" MobId="24009" ItemId="12886" NumOfTimes="1" WaitTime="4000" Range="5" CollectionDistance="200" X="1764.727" Y="-5913.021" Z="7.546279" />

second, can you attach the log

 

[vlad0327]

You have provided a wrong ItemId. You need to use ItemId="33278"

 

[Kickazz006]

You have provided a wrong ItemId. You need to use ItemId="33278"

that was my next guess =) i just wanted to make sure that the bot wasn't acting up (the behavior)

 

[Inferno]

Oops.

>< Well now I just feel stupid. The item id change fixed it. I swear I had that in there before...

Log attached anyway.

Interestingly it doesn't appear to have thrown an error when it didn't have an item of that id in the bots inventory.

Also, is there a simple way to get it to pick mobid's out of a list when doing the custom behaviour? It seems that you can only specify one mobid to use the item on.

It would be handy to be able to do both forsaken and alliance corpses in this instance.

EDIT: Since the mobs are in the same location, I just used a while loop to swap between doing an alliance corpse and a forsaken corpse, it looks a bit odd when there are a few alliance/horde corpses next to each other, but it's a workable solution.