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!

[PAID] GarrisonButler

I still have the issue where if I start the bot inside the mine, it loops to infinity with "found garrison cache" and "found mine". There needs to be some sort of POI lockout between your Tasks. It shouldn't be finding a new task until the current task is done. You said you couldn't reproduce on the last version ... but it's still an issue.

When the bot finds a POI to go do, it should lock out all other POIs from being done.
 
justinr1234 said:
I still have the issue where if I start the bot inside the mine, it loops to infinity with "found garrison cache" and "found mine". There needs to be some sort of POI lockout between your Tasks. It shouldn't be finding a new task until the current task is done. You said you couldn't reproduce on the last version ... but it's still an issue.

When the bot finds a POI to go do, it should lock out all other POIs from being done.
Click to expand...
I was able to reproduce it, should be fixed in next release.
 
Enchanting:

Bot tries to interact with Yunis Sonnenstaub(79821) but he has to interact with Gara

Information about Garra
Name = Garra
Wowhead Id = 79820
Faction = 1734 [Horde, Standard]
Location = <5645.052, 4507.231, 120.0704>
<Vendor Name="Garra" Entry="79820" Type="Repair" X="5645.052" Y="4507.231" Z="120.0704" />
 
Not sure if this is just me, but this seems to ping pong all over the mine when collecting nodes, rather than just do them as it passes them.

Is there any way to skip some work orders? For example I don't want to waste resources at the Bunker since I get enough follower upgrades from Salvage.
 
Noticed the bot was failing to reach a node that was underwater in the mine, and it said blacklisting but it just kept trying to attempt grabbing it. Here's a small log of how it was behaving, not sure if it's helpful. :X
 

Attachments

Pathing for Warmill level 3 is completely off for Horde.
Bot tries to go into the warmill to start Work Order but gets stuck outside.
 
razer86 said:
Not sure if this is just me, but this seems to ping pong all over the mine when collecting nodes, rather than just do them as it passes them.

Is there any way to skip some work orders? For example I don't want to waste resources at the Bunker since I get enough follower upgrades from Salvage.
Click to expand...

it's not just you. as some other poster said, it's choosing nodes based on z axis or something.

Also, the "that item is already being used" issue is not totally fixed.
 
Last edited:
Awesome job. I'll donate when I get home.

Only one issue I've found with the latest version:
Bot keeps running to Yukla Greenshadow and open's the Enchanting window. Then the bot keeps spamming:
[GarrisonBuddy] 0.5.4: Moving to start work order:Enchanter's Study
[GarrisonBuddy] 0.5.4: Failed to open Work order frame.
[GarrisonBuddy] 0.5.4: Failed to open Work order frame.

I've turned off Enchanting in the settings (I just have the building, don't actually have enchanting) but it keeps running to her.

--

Believe I found the problem. The Horde version is looking for the wrong NPC. The NPC that handles work orders for Horde is Garra (79820 instead of 79821). Yukla does the enchanting.

--

Problem solved. Changing the NPC ID to 79820 in Building.cs from 79821 now correctly goes to Garra to drop off work orders.
 
Last edited:
Found another issue. We're constantly drinking coffee even if we have the buff.

I'll look later to figure out why, but here's my temp fix:

WoWItem coffee = Me.BagItems.Where(o => o.Entry == MinersCofeeItemId).ToList().FirstOrDefault();
if (coffee != null && coffee.Usable &&
!Me.HasAura(MinersCofeeAura))

Something after the || is causing it to think the coffee buff needs to be cast again, even if we already have it.

--

Also, can you please add an option to disable work orders for War Mill. Just got rid of all my resources on it. :(

--

Stopping outside of the Salvage Yard but can't actually salvage the item (since we're not standing inside). Level 2 Salvage Yard - Horde.
 
Last edited:
Slight problem. sometimes when mining it gets an error that "i can't do that yet" upon looting. usually solved by moving closer.

Also, having the zig zag problem where the bot goes to nodes on the other side of the mine before mining a node closer
 
Last edited:
Thanks for all the feedback!
Unfortunately I was a bit too busy IRL tonight to take a look, but will dedicate tomorrow to it.
The fixes won't take long thanks to you, and I should have the time to enhance the navigation.
I was hoping for an official fix for the nav system but they must have a lot of other things to take care of than dynamic meshes for the Garrison.
Once everything is stable, might throw myself into it to fix it once and for all.

In the meantime, keep posting feedbag/bugs/ideas! :)
I'll do my best to get you a stable enough version to run with a relogger asap.
 
Hey deams, great job on your progress with this man, very nice so far. I just wanted to add for some reason my bot will not redo my missions. It started up and did its normal routine and started missions and I set it to grind and it would not return there. Even when I hearth I reset the bot to see if it would redo my mission and it went straight to grind. If I can help with a log or anything let me know! thanks again!
 
Is there anyway you could have each building have its own on/off switch for work orders? I want the bot to collect and start work orders everywhere except dwarven bunker. I cant afford to use garrison resources on work orders, only reason I built the bunker is for the free raid bonus roll.
 
deams said:
What do you think about the rest of the behavior?
Click to expand...

Really loving it dude, runs really well. You have done fantastic work in a very short period.

An idea for possible future development: Allow the bot to log to different characters or have it indicate to HBrelog that it has completed its current run. This would be incredibly useful for leveling multiple alts followers or collecting work orders.

Another idea: allow the bot to start upgrades in the garrison, tier 2 to tier 3 for exmaple.
 
Hey dude seems there is still a minor problem with getting close enough to nodes.

Code: 
Can't generate a path to the lootable. Blacklisting it for 15 minutes.Blacklisting 28309890E0E3174000502F0001850626 for 00:15:00 [Type: Loot, Node, Skin] - Reason: Couldn't generate a path to the target.
Clearing POI - Reason Can't generate a path to lootable
Interacting with Mine Cart (GameObject Id: 232541)
Changed POI to: Type: Harvest
Can't generate a path to the lootable. Blacklisting it for 15 minutes.
Blacklisting 28309890E0E3174000502F0001850626 for 00:15:00 [Type: Loot, Node, Skin] - Reason: Couldn't generate a path to the target.
Clearing POI - Reason Can't generate a path to lootable
Changed POI to: Type: Harvest
Can't generate a path to the lootable. Blacklisting it for 15 minutes.
Blacklisting 28309890E0E3174000502F0001850626 for 00:15:00 [Type: Loot, Node, Skin] - Reason: Couldn't generate a path to the target.
Clearing POI - Reason Can't generate a path to lootable
Changed POI to: Type: Harvest
Can't generate a path to the lootable. Blacklisting it for 15 minutes.
Blacklisting 28309890E0E3174000502F0001850626 for 00:15:00 [Type: Loot, Node, Skin] - Reason: Couldn't generate a path to the target.
Clearing POI - Reason Can't generate a path to lootable
[GarrisonBuddy] 0.5.4: Found ore to gather, moving to ore at:<1876.241, 184.0847, 9.92889>
Changed POI to: Type: Harvest
Can't generate a path to the lootable. Blacklisting it for 15 minutes.
Blacklisting 28309890E0E3174000502F0001850626 for 00:15:00 [Type: Loot, Node, Skin] - Reason: Couldn't generate a path to the target.
Clearing POI - Reason Can't generate a path to lootable
Interacting with Mine Cart (GameObject Id: 232541)
Changed POI to: Type: Harvest
Can't generate a path to the lootable. Blacklisting it for 15 minutes.
Blacklisting 28309890E0E3174000502F0001850626 for 00:15:00 [Type: Loot, Node, Skin] - Reason: Couldn't generate a path to the target.
Clearing POI - Reason Can't generate a path to lootable
Changed POI to: Type: Harvest

Getting stuck in this loop on some of the nodes. If I manually move forward one step it goes like normal. Weirdly getting the message "this is already in use" from WoW.

Also seems to be a bit of confusion with which node to go to? Just running back and forth between two nodes.

Code: 
[GarrisonBuddy] 0.5.4: Found ore to gather, moving to ore at:<1954.37, 215.046, 16.34472>[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1902.333, 170.3187, 21.47897>
[GarrisonBuddy] 0.5.4: Detected garrison cache available, moving to collect.
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Starting path generation.
[GarrisonBuddy] 0.5.4: Found ClosestToNodes in 0ms.
[GarrisonBuddy] 0.5.4: Found Any in 0ms.
[GarrisonBuddy] 0.5.4: Found InitialiseGraph in 0ms.
[GarrisonBuddy] 0.5.4: Found ProcessGraph in 1344ms.
[GarrisonBuddy] 0.5.4: Found ExtractPath in 1345ms.
[GarrisonBuddy] 0.5.4: Path generated in 1345ms with 199 waypoints.
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1901.414, 164.3811, 22.50824>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1901.178, 161.7993, 22.96655>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1900.738, 160.4414, 23.16304>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1898.841, 158.5372, 23.2271>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1896.486, 155.3561, 23.35583>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1896.253, 153.9473, 23.43627>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1895.897, 151.079, 23.34438>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1895.739, 149.6526, 23.2529>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1895.473, 146.8023, 23.12257>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1895.372, 145.3989, 23.06863>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1895.34, 141.5682, 23.02039>
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Detected garrison cache available, moving to collect.
[GarrisonBuddy] 0.5.4: Shipment Garrison Cache - 236916 - 23775: <1947.616, 286.6389, 88.96585>
[GarrisonBuddy] 0.5.4: Found ore to gather, moving to ore at:<1954.37, 215.046, 16.34472>
[GarrisonBuddy] 0.5.4: Starting path generation.
[GarrisonBuddy] 0.5.4: Found ClosestToNodes in 0ms.
[GarrisonBuddy] 0.5.4: Found ClosestToNodes in 5ms.
[GarrisonBuddy] 0.5.4: Found Any in 5ms.
[GarrisonBuddy] 0.5.4: Found InitialiseGraph in 5ms.
[GarrisonBuddy] 0.5.4: Found ProcessGraph in 1315ms.
[GarrisonBuddy] 0.5.4: Found ExtractPath in 1315ms.
[GarrisonBuddy] 0.5.4: Path generated in 1315ms with 39 waypoints.
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1895.473, 146.8023, 23.12257>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1895.739, 149.6526, 23.2529>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1895.897, 151.079, 23.34438>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1896.253, 153.9473, 23.43627>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1896.486, 155.3561, 23.35583>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1898.841, 158.5372, 23.2271>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1900.738, 160.4414, 23.16304>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1901.178, 161.7993, 22.96655>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1901.414, 164.3811, 22.50824>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1901.894, 167.4876, 21.98334>
[GarrisonBuddy] 0.5.4: Loading next waypoint to : <1902.333, 170.3187, 21.47897>
[GarrisonBuddy] 0.5.4: Found ore to gather, moving to ore at:<1954.37, 215.046, 16.34472>
[GarrisonBuddy] 0.5.4: Detected garrison cache available, moving to collect.
 
You must log in or register to reply here.
Back
Top