What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

my bot is havin trouble interacting with a portal it needs to click

cgw-1991 said:
View attachment 24889the bots not clicking the portal it needs to click to go turn in a quest here is a log
Click to expand...

I just ran two toons through that section of Kick's Classic profile, and had the same problem.

The problem is that the mage spawns the portal (its not a permanent object, unlike all other portals). And for some reason, Honorbuddy cannot 'see' it when it pops.
Code: 
[1:58:46 AM:467] Goal: Interacting with Portal to Andorhal
[1:58:46 AM:981] Activity: Moving towards - <-14471.73, 469.4871, 30.7543>
[1:58:47 AM:791] Activity: Waiting for object to spawn
[1:59:05 AM:455] Activity: Moving towards - <-14471.73, 469.4871, 30.7543>
[1:59:06 AM:194] Activity: Waiting for object to spawn
[1:59:24 AM:698] Activity: Moving towards - <-14471.73, 469.4871, 30.7543>

Just 1) stop the bot, 2) click on the portal, 3) turn the quest in when you arrive on the other side, and 4) restart the bot. All will be good after that.


I'll bring this thread to Kick's attention to see if he's got any clever rabbits in his back pocket. Its clear that he's made a serious attempt to address the shortcoming by the WaitTimer behavior he's used in the profile. Alas, that doesn't seem to be enough to get the job done.


cheers,
chinajade
 
Actually i remember that quest as i tested Azenius, it's not a profile issue as far as i know. As i ran it, i needed to get the portal id, and somehow neither Honorbuddy nor Profile Helper could find it. The only way to get the id was targeting it and getting target info (seeming odd as it wasn't in the list of objects)
 
shakazara said:
Actually i remember that quest as i tested Azenius, it's not a profile issue as far as i know. As i ran it, i needed to get the portal id, and somehow neither Honorbuddy nor Profile Helper could find it. The only way to get the id was targeting it and getting target info (seeming odd as it wasn't in the list of objects)
Click to expand...

unless blizz changed it, the portal was actually an npcid when i originally wrote the script.

now, blizz probably changed it to a temp gameobject, but who knows?

CJ or someone else who runs this again and gets stuck. please open profile helper and look in the gameobjects and npc's tabs and see what it says. Currently it says 49637 (npc id)

Portal to Andorhal - NPC - World of Warcraft
 
up to classic 1-60 alliance human

im up to the quest where u have to kill 20 wild life, but the issue is the profile is looking for one type of unit and their are several mobs you can kill.
 
Kickazz006 said:
unless blizz changed it, the portal was actually an npcid when i originally wrote the script.

now, blizz probably changed it to a temp gameobject, but who knows?

CJ or someone else who runs this again and gets stuck. please open profile helper and look in the gameobjects and npc's tabs and see what it says. Currently it says 49637 (npc id)

Portal to Andorhal - NPC - World of Warcraft
Click to expand...

Kick, I had another toon run through this segment. I can confirm:
  • The portal is an NPC
  • The portal id you have in the profile is correct (49637)
I couldn't make InteractWith work. Out of desperation, I switched to CollectThings (that's a serious abuse of that behavior), since some of their functionality overlaps. The CollectThings succeeded where the InteractWith fails. It probably has to do with how WoWUnit vs WoWObject are handled in the two different behaviors. (CollectThings treats Mobs/Objects as generically as possible, InteractWith is more particular in the use of each.)

If you feel like abusing it too, I replace line 5494-5495:
Code: 
<CustomBehavior File="WaitTimer" WaitTime="2000" />
<CustomBehavior File="InteractWith"  MobId="49637" NumOfTimes="1"
    WaitTime="1000" CollectionDistance="50"
    X="-14471.73" Y="469.4871" Z="30.7543" />

with this...
Code: 
<CustomBehavior File="WaitTimer" WaitTime="[COLOR="red"]4000[/COLOR]" />
<CustomBehavior File="[COLOR="red"]CollectThings[/COLOR]"  [COLOR="red"]MobId="49637"
    CollectUntil="NoTargetsInArea" CollectItemCount="1" CollectItemId="49637"
    X="-14471.73" Y="469.4871" Z="30.7543"[/COLOR] />


I tested the change several times (dropped the quest, and restarted the profile), and its a loooong flight back to BootyBay. :D Its a solid fix, even if a bit goofy.


Edit: BasicInteractWith also works. I always make things harder than they need to be (i.e., CollectThings) :) :
Code: 
<CustomBehavior File="WaitTimer" WaitTime="[COLOR="red"]4000[/COLOR]" />
<CustomBehavior File="[COLOR="red"]BasicInteractWith[/COLOR]" [COLOR="red"]MobId="49637"[/COLOR] />

cheers,
chinajade
 
Last edited:
You must log in or register to reply here.
Back
Top