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!

[QB][N] Voidtalon of the Dark Star

can someone tell ?

the Camp only one does it move when it detects an Portal or do i have to stay next to the portal?
 
When it detects the portal it will move towards it and click it (in theory). Camp only won't navigate to any spawn spots.
 
Only an idea:

Is it possible to make an Radar Only one?
so i move around kill some mobs and when he found an Portal i get an notify or something else?
 
havoc874 said:
Only an idea:

Is it possible to make an Radar Only one?
so i move around kill some mobs and when he found an Portal i get an notify or something else?
Click to expand...

That would require a plugin, well beyond the scope of this profile.
 
I still get disconnected if I leave it by it's self for to long, anyone else having this issue?
 
I managed to fix the out of memory issue, I added a few extra seconds onto the portal check timer and now it runs for at least 9 hours with no issues, as long as I close and reopen the program every 9 hours or so there's no issues at all.
 
Kesmarkidavid,

Collection Distance is set to 100. So fairly good distance. Easy enough to increase.

Noct157,

How long is too long? My max so far is about 6 hours. I'm hearing now the respawn thing on this might be 48 hours, had no idea it was so long when I started this. =(

Exystredofar,

So it was just too much activity? or too much logging? I've thought maybe I don't need to message every single time it moves. I can't imagine any particular line of code is causing a memory leak its all standard profile stuff.
 
ajziegle said:
Do not trust this profile, it does not work. It found a void portal and did not interact with it. Talk about a waste of time and chance at a very rare mount.
Click to expand...

You did see the repeated comments about untested right? How well do you think anyone can test a profile for something that pops up randomly every 2 days and you can only click once per account? Help me make it better if you can, if not, well you got your moneys worth. (ie free.)
 
Already sent you a log in private message and yes you can actually test this by having it run on a portal thats in a city or another object. Interaction with objects with a stand alone profile and others woudl be a simple checking for the same ID, aka SW portal or IF Portal. Something similar. Testing the script to accept a scenario would be to queue a scenario yourself and test it that way. I understand Beta, but also understand that you don't require the exact item to interact with to test your code.
 
You gave me a tiny excerpt that showed my profile attempting to interact with the portal correctly. And yes, I have of course tested with other portals, as I have lots of private profiles I don't share that use a wide variety of portals. It's very simple code that's extremely well used.

HTML: 
<While Condition="Object(239828) != null ">
  <CustomBehavior File="Message" Text="Portal Found, Interacting!!" LogColor="Orange" />
  <CustomBehavior File="InteractWith" WaitForNpcs="false" WaitTime="3000" MobId="239828" NumTimes="2" Range="1" CollectionDistance="100" PreInteractMountStrategy="DismountOrCancelShapeshift" />
  <If Condition="Me.ZoneId != 7519">
    <CustomBehavior File="RunMacro" Macro="/click LFGDungeonReadyDialogEnterDungeonButton" />
    <CustomBehavior File="WaitTimer" WaitTime="2000" />				
  </If>
</While>

Walking through it it enters a while loop ONLY if the object with that ID is detected. It bypasses this as long as the object is not found. (that part works fine.)

Then a message. Then InteractWith. (Which is used in a gazillion places in quest scripts).

Going through the options. Waitfornpc=false means it won't stand there waiting, it'll continue to loop (meaning instead of trying once, we'll try every time it loops (as long as the we haven't changed zones (ie entered the scenario, and the object still exists (someone else clicks it).

Mobid is what we click. Numtimes the number of times it "clicks". One is probably sufficient, 2 was just in case since I haven't to lay eyes on it. Range is how close your character moves before "clicking" Collection distance is how far away it can be from where we're standing before we consider it a valid object to intearct with. Preinteract just tells it to dismount and drop shapeshift prior to clicking. That's it. Nothing all that special there. Nothing that hasn't been tested with other portals a zillion times. Nothing I uniquely wrote for just this specific situation.

The part I am more concerned about is the clicking the scenario button.
 
ajziegle said:
[QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[InteractWith-v1963(warning) @line 38]: Attribute 'NumTimes' is not recognized by this behavior--ignoring it.

Is also in the logs, which tells me NumTimes isn't recognized. I understanding the coding you did as I went through it and the only reason I even ran it is because i thought it might be sound as it was sound in principle. Looks like the interaction with the object turned out to be an issue?
Click to expand...

That's just a warning, it doesn't stop it from continuing the interact. Nothing in your log shows an error. It found it started moving towards it, got sidetracked by a monster, then the log ends.
 
Vengent said:
Exystredofar,

So it was just too much activity? or too much logging? I've thought maybe I don't need to message every single time it moves. I can't imagine any particular line of code is causing a memory leak its all standard profile stuff.
Click to expand...

Honestly I'm not sure, keeping log files rotating didn't seem to fix it, it seemed almost as though the program itself ran out of memory from scanning the WoW client too much, closing and restarting honorbuddy would fix the entire issue. I have no idea why this would happen.
 
Vengent said:
The part I am more concerned about is the clicking the scenario button.
Click to expand...
Hopefully we just need it to click on the portal and then it will send it to us in the mail. People who are relam hopping and click on the portal get an error saying they cannot que for scenario while in group and then it gets mailed to them. I hope that if you click on the portal and the timer for the scenario runs out it that it will just mail it. People have stated it taking up to half an hour to get it in the mail so idk how the mailing works
 
ajziegle said:
Do not trust this profile, it does not work. It found a void portal and did not interact with it. Talk about a waste of time and chance at a very rare mount.
Click to expand...


ajziegle,

Given what we found in your logs, would you like to amend this statement?
 
You must log in or register to reply here.
Back
Top