What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Bug Report - Bot Stuck Spamming Traveler's Tundra Mammoth Trying to Vendor Run

skuld

New Member
Joined
Apr 24, 2011
Messages
21
Reaction score
0
I have an alliance toon that just hit 68 so I moved them to Valiance Keep in Borean Tundra. I have the Traveler's Tundra Mammoth. I loaded Kick's questing profile [Fly][A - Quest] LK 68-80 [Kick]. I start the Questing bot (using Singular DK routine) while I am standing outside on the docks, right next to the ship that brings you from Stormwind (around position 2231.82, 5135.42, 5.34 in Developer Tools).

According to the logs, the toon seems to want to do a vendor run. It summons the Traveler's Tundra Mammoth, pauses, takes 3 steps forward, and then hops off. Then summons the mammoth again, and takes 3 steps, then hops off. This continues over and over. It makes questing impossible plus makes it super-obvious to anyone watching that you're probably a bot.
 

Attachments

Hi, Skuld, and many thanks for that log!

We've opened HB-2079 ("Honorbuddy's use of mobile repair vendor sends it into an infinite loop") against this issue. There is no work-around for the problem at this time. You'll just need to keep an eye on the toon, and send it to a permanent vendor when it needs to sell or repair, or either use the mobile repair mount manually.

Sorry for the inconvenience.

cheers,
chinajade
 
Could you bump up the priority on this bug? There are times when the toon is fully repaired and has nothing to sell in the inventory, yet the questing profile is forcing the mount to be summoned over and over. Using the mobile repair mount manually does not help. The only way to fix this is to move the toon to the vendor that it is trying to get to and then it will continue the profile.

Is there an easy way to just simply remove mobile repair usage from HB until this issue is resolved?

Edit: For the benefit of anyone else running into this problem, I was able to workaround the issue above. I edited the questing profile I was using (one of Kick's) to remove all repair vendors and repair custom behavior lines.

So in the questing profile, for vendor lines that start like:
Code:
<Vendor Name="Markus Scylan" Id="22227" Type="Repair" Nav="Fly" X="-707.8071" Y="2716.121" Z="94.7371" />

replace with:
Code:
<!--<Vendor Name="Markus Scylan" Id="22227" Type="Repair" Nav="Fly" X="-707.8071" Y="2716.121" Z="94.7371" />-->

Also any lines that look like:
Code:
<CustomBehavior File="ForceSetVendor" DoSell="true" DoRepair="true" DoMail="true" />

replace with:
Code:
<!--<CustomBehavior File="ForceSetVendor" DoSell="true" DoRepair="true" DoMail="true" />-->
 
Last edited:
Some more information, I was able to get around the issue above by buying the Grand Expedition Yak. Now instead of Traveler's Tundra Mammoth being summon, it uses the Yak and the error loop is not triggered when using the Yak.

Just a guess, but it looks like this may be an issue with the vendor id being wrong? I originally purchased the Traveler's Tundra Mammoth on Horde side and I'm seeing issues on Alliance side. I had read that originally the Traveler's Tundra Mammoth was specific to each faction, so you had to buy it twice to get it on both factions. But Blizz changed it so that you only need to buy it once.

The repair guy on the Traveler's Tundra Mammoth is Gnimo ID=32639
 
i wouldnt even begin to know if that is or is not the issue concerning this particular issue. all we can do is submit it to the devs and let them work it out.
 
Back
Top