QB: UseItemTargetLocation seems to be broken

[Thumped]

Running a quest Profile and when it calls for the UseItemTargetLocation quest behavior, it just hangs

Tried 3 times, this one is at the bottom of the log...
[00:43:04.005 D] Goal: UseItemTargetLocation: In Progress


Thanks

 

[chinajade]

Running a quest Profile and when it calls for the UseItemTargetLocation quest behavior, it just hangs

Tried 3 times, this one is at the bottom of the log...
[00:43:04.005 D] Goal: UseItemTargetLocation: In Progress


Thanks

Hi, Thumped,

I've captured your report to the "to look at" list. I'm not familiar with the Sharecropper profile, and it could also be misusing the behavior. Could you point me to a copy of it?

thanks!
chinajade

 

[Thumped]

Hi, Thumped,

I've captured your report to the "to look at" list. I'm not familiar with the Sharecropper profile, and it could also be misusing the behavior. Could you point me to a copy of it?

thanks!
chinajade

It is in my sig china... Thanks

 

[chinajade]

It is in my sig china... Thanks

Hi again, Thumped. Doh! ty

I looked in your thread, and you must be working on a new profile that is not in your thread, yet. Alas, I'm also unfamiliar with the content you are trying to address.

But...
I did give a look at the UseItemTargetLocation code, and it will silently fail as you observe if the proper item is not in your bag. Are you certain you specified the correct ItemId in the profile invocation?

Either way it goes, UseItemTargetLocation needs some work--silently failing is not an acceptable situation.


cheers,
chinajade

 

[Thumped]

Line 543 of the Enigma file and Line 542 of the Songbell file. Both files worked great until the last patch...

 

[chinajade]

Line 543 of the Enigma file and Line 542 of the Songbell file. Both files worked great until the last patch...

Hi again, Thumped,

I think I see where the problem may lie. We've been having some real issues with correct "Cooldown" information being returned from the WoWclient since the last patch. I've been talking to the developers responsible for that area, but nothing has been resolved yet.

I've modified a copy of UseItemTargetLocation.cs to confirm this is the problem. It won't fix the problem, but just confirm it. Would you be so kind as to give this a test, and show me a fresh log with it?

View attachment UseItemTargetLocation.cs​

thanks!
chinajade

 

[Thumped]

I will give a try tonight...

Thanks again Chinajade

 

[Thumped]

Works like it's supposed too..

 

[Dare932]

That is not just questing targetting...the entire bots targetting is not working....when I use BGBuddy my toon is just running up to people and following them around.

 

[CodenameG]

so your good now?

 

[chinajade]

Works like it's supposed too..

Hi, Thumped,

Can you show me the log please? If it actually repaired the issue, I will check in the change to the QB. But, I'd like to make certain first (with a log), as it wasn't supposed to actually fix your problem.

cheers,
chinajade

P.S. - In the future, issues like this should probably be discussed in the Developer forum instead of the Support forum.

 

[Thumped]

Yes'm I will get you a log this afternoon, at work...bah.

 

[Thumped]

Hi, Thumped,

Can you show me the log please? If it actually repaired the issue, I will check in the change to the QB. But, I'd like to make certain first (with a log), as it wasn't supposed to actually fix your problem.

cheers,
chinajade

P.S. - In the future, issues like this should probably be discussed in the Developer forum instead of the Support forum.

Here you go Chinajade
Shorten up the profile so it would only test the Custom Behavior...log and profile are attached

View attachment 6280 2013-03-28 17.09.txt
View attachment PlantSongbellTest.xml

 

[Thumped]

so your good now?

Yeap!

 

[chinajade]

Here you go Chinajade
Shorten up the profile so it would only test the Custom Behavior...log and profile are attached

View attachment 86551
View attachment 86552

Hi, Thumped, and many thanks for the log.

For the life of me, I don't see how the changes could've affected the outcome. I just altered the code to print messages if the item could not be found, or the item was on cooldown (which neither show up in the log). Previously, the behavior would just lock up with a silent failure.

I'll check the changes in, but this lack of understanding why it now works bothers the fool out of me.

Thanks again!
chinajade