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!

Question?

Using the QuestHelper version would make this super easy! See the Questing Pack in my signature for access to QuestHelper!

HTML: 
<Profile Name="QH Basic Grind Profile" Author="Deathdisguise" Version="1">
    <Kill X="123" Y="123" Z="123" />
</Profile>

The following profile will kill everything within a 200m radius of the (123,123,123) coordinate, and not actively engage primes, or flying mobs. :)

EDIT: Should probably include the name/author/version attributes too, just in case. ;)
 
Last edited:
Dagravit0598 said:
How do i make a grinding profile?
Click to expand...


In game with wildbuddy open just select a mob or your self using ATL+CTRL+H that will make a hotspot. It set to a basic radius and if you want to make it larger you can. You can have more hot spots or less. WB will scans 500 x objects around radius.


Template
<Profile Name="NAME OF GRIND" Author="Walter" Version="0.1">
<Grind>
<Repair PreferClosest="true" PreferFirst="false">
<RepairNPCs>
<RepairNPC Name="Provisioner Omnichron" CreatureId="56657" X="-22479.49" Y="-942.8369" Z="-27812.71" MapId="2997" /> <----- Alt+Shift+D when selecting vendor how you dump.
</RepairNPCs>
</Repair>

<Vendor>
<VendorNPCs>
<VendorNPC Name="Provisioner Omnichron" CreatureId="56657" X="-22479.49" Y="-942.8369" Z="-27812.71" MapId="2997"/> <----- Alt+Shift+D when selecting vendor how you dump.
</VendorNPCs>
</Vendor>
<GrindArea>
<Hotspot X="-532424.5513" Y="-982349.8234737" Z="-42342238.72" Timeout="60" Range="60" Name="New Hotspot" />
</GrindArea>
</Grind>
</Profile>
Click to expand...


If you need more help don't be afraid to ask.
 
I cant get the grind profile to work. This is whats inside:

<Profile Name="NAME OF GRIND" Author="Walter" Version="0.1">
<Grind>
<Repair PreferClosest="true" PreferFirst="false">
<RepairNPCs>
</RepairNPCs>
</Repair>

<Vendor>
<VendorNPCs>
</Vendor>
<GrindArea>
<Hotspot X="-1402.85449" Y="-925.8044" Z="-2007.2428" Timeout="60" Range="40" Name="New Hotspot" />
<Hotspot X="-1390.29065" Y="-918.47876" Z="-2063.13721" Timeout="60" Range="40" Name="New Hotspot" />
<Hotspot X="-1346.9165" Y="-916.7501" Z="-2031.183" Timeout="60" Range="40" Name="New Hotspot" />
</GrindArea>
</Grind>
</Profile>
 
HTML: 
<Profile Name="NAME OF GRIND" Author="Walter" Version="0.1">
    <Grind Condition="1==1">

        <CreatureIds></CreatureIds>

        <Repair PreferClosest="true" PreferFirst="false">
            <RepairNPCs>
            </RepairNPCs>
        </Repair>

        <Vendor>
            <VendorNPCs>
        </Vendor>

        <GrindArea>
            <Hotspot X="-1402.85449" Y="-925.8044" Z="-2007.2428" Timeout="60" Range="40" Name="New Hotspot" />
            <Hotspot X="-1390.29065" Y="-918.47876" Z="-2063.13721" Timeout="60" Range="40" Name="New Hotspot" />
            <Hotspot X="-1346.9165" Y="-916.7501" Z="-2031.183" Timeout="60" Range="40" Name="New Hotspot" />
        </GrindArea>
    </Grind>
</Profile>

Added in a CreatureId tag in case you want reference to it, for killing specific actors (it's likely still broken, so we just leave that blank for now)

A Condition attribute of "1==1" returns true always, so it will always loop through the grind tag until the bot is stopped.


And to toot my own horn, this same profile using QuestHelper :cool: :

HTML: 
<Profile Name="Potato" Author="DD" />
    <Kill X="-1390.29065" Y="-918.47876" Z="-2063.13721" />
</Profile>
 
Deathdisguise said:
Using the QuestHelper version would make this super easy! See the Questing Pack in my signature for access to QuestHelper!

HTML: 
<Profile Name="QH Basic Grind Profile" Author="Deathdisguise" Version="1">
    <Kill X="123" Y="123" Z="123" />
</Profile>

The following profile will kill everything within a 200m radius of the (123,123,123) coordinate, and not actively engage primes, or flying mobs. :)

EDIT: Should probably include the name/author/version attributes too, just in case. ;)
Click to expand...

Hey champ, just tried this, subbing in my coordinates. It still seems to be going after the elites, the ones that have that red glow about them. Should it be doing that?

EDIT: Yeah even doing it with the one Walter posted, goes after champions/elites whatever they are, dies too often as I cannot find a spot around where I am at which does not have them, too squishy at my level to take them on solo
 
Last edited:
lyvewyre said:
Hey champ, just tried this, subbing in my coordinates. It still seems to be going after the elites, the ones that have that red glow about them. Should it be doing that?

EDIT: Yeah even doing it with the one Walter posted, goes after champions/elites whatever they are, dies too often as I cannot find a spot around where I am at which does not have them, too squishy at my level to take them on solo
Click to expand...


Best advice I can give you is to make more hotspots that are smaller. That way you can dodge elite for now. Avoid tag code is something that's in progress. Never was "turned" on due to nav server needing some tweaks to make it work correctly. Hope this helps.


Walter
 
lyvewyre said:
Hey champ, just tried this, subbing in my coordinates. It still seems to be going after the elites, the ones that have that red glow about them. Should it be doing that?
Click to expand...

It shouldn't be engaging Superior/Primes directly, if it unfortunately paths into one, it'll end up attempting to kill it (and usually losing), I have my own implementation of avoidance, but unfortunately it's still being tested as it's buggy at times. :(

It's possible it's attacking a champion or elite, as there's two different ranks that glow red (I think?) I can look into it if I find a rare spawn to see which one it is. :)

To give you more control, here's the full syntax:

HTML: 
<Kill Condition="" Quest="-1" Objective="-1" Creature="" X="" Y="" Z="" Radius="200" PullRange="24" />
 
Last edited:
lyvewyre said:
Hey champ, just tried this, subbing in my coordinates. It still seems to be going after the elites, the ones that have that red glow about them. Should it be doing that?
Click to expand...

I looked into it further, and you were correct! The WB enum is incomplete, and I was misguided in my implementation! The SVN now has an updated version that should correctly ignore all Primes and above. :)
 
With all of the above profiles i get this error, any idea why?

Thanks in advance.


xception during execution of profile tag <Kill /> (Line #2)System.AggregateException: Si sono verificati uno o più errori. ---> Buddy.Wildstar.BotCommon.Navigation.PathfindingException: Did not receive valid pathfind response in the last 5 seconds.
in *
‎
‎*‬*​**‫‪‎‫‫‏‬​‏*‫‪**.r26!IPi!L885beL\\_Oj;Ju\*f.()
--- Fine della traccia dello stack dell'eccezione interna ---
in System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
in System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout)
in Buddy.Coroutines.Coroutine.v(6lX\,=%<)9fM_B(!vMO~R22.()
--- Fine traccia dello stack da posizione precedente dove è stata generata l'eccezione ---
in System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
in System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
in Buddy.Coroutines.Coroutine.n0-_D8%ODIqAD52\,g;EwrH\&".()
--- Fine traccia dello stack da posizione precedente dove è stata generata l'eccezione ---
in System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
in System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
in System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
in Buddy.Wildstar.BotCommon.Navigator.bmKE} 0tkHrLXPJJ\\Fvw!7DT.()
--- Fine traccia dello stack da posizione precedente dove è stata generata l'eccezione ---
in System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
in System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
in Buddy.Wildstar.BotCommon.CommonBehaviors.ir1eYvNGYKya}\\\]gXQ~ELKG#.()
--- Fine traccia dello stack da posizione precedente dove è stata generata l'eccezione ---
in System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
in System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
in System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
in Buddy.Wildstar.BotCommon.CommonBehaviors.QLF#T\,!\,-'!_\]9uT)KC`Wjda.()
--- Fine traccia dello stack da posizione precedente dove è stata generata l'eccezione ---
in System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
in System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
in Buddy.Wildstar.BotCommon.CommonBehaviors.=4I`^_=JZ=a$m7y(3H\&E\.LN?.()
--- Fine traccia dello stack da posizione precedente dove è stata generata l'eccezione ---
in System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
in System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
in System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
in Buddy.Wildstar.Engine.Profiles.KillTag.<ProfileTagLogic>d__8.MoveNext() in c:\Users\Federico\Documents\Wildbuddy\Plugins\QuestHelper\ProfileTags\KillTag.cs:riga 167
--- Fine traccia dello stack da posizione precedente dove è stata generata l'eccezione ---
in System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
in System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
in Buddy.ProfileBot.ProfileBot.JnYAY>BLef\]E\.6(=)Q\\TZ@V\..MoveNext()
---> (Eccezione interna 0) Buddy.Wildstar.BotCommon.Navigation.PathfindingException: Did not receive valid pathfind response in the last 5 seconds.
in *
‎
‎*‬*​**‫‪‎‫‫‏‬​‏*‫‪**.r26!IPi!L885beL\\_Oj;Ju\*f.()<---
 
I think the navigation servers are actually down, as it's happening even in "supported" regions...

So is this a just temporary issue? The only thing I can do is wait, right? xD
Any other way to check the nav-server status?

Thanks for your help
 
Last edited:
You must log in or register to reply here.
Back
Top