HB ARCHIVES: Feedback for Honorbuddy Improvements--DO NOT DELETE!

Hello. Have mentioned this before here, but esp. now, think it is worth mentioning again.

HB is a good program; this is why so many use it. IMO however, it used to be a great program.

I am all for 'fixing' the issues denoted throughout this thread, but please, please do not make HB any bigger or bulkier than it is already getting.

Before adding anything TO the bot, I think that the most important thing is going through it and streamlining what is already available.

Thanks.

 

I agree 100% I mean it's called Honorbuddy but I can't do bg's with dc after 5-10 maps. But I can quest,father,grind,do dungeons,etc

Honorbuddy is staying to feel like a Jack of all trades and a master of none.

 

This summed up my response perfectly.

 

I think the best thing for them to improve is

1st : Full 1-90 Full AFK profile.
2nd : Update Dungeon Buddy, Works for all classes and race and fractions.
3rd : BGBuddy

 

Is there any way to change routine while running honorbuddy ? like switching from singular to purerotation and so on without closing honorbuddy and reopen it ?

 

i feel if you make option for us to change HB name in tasks and active missione to reduce detection lvl coz some time wow got some but and when send the debug for blizzard it'll include all task in the try working

 

My suggestions are for dungeonbuddy or forums related to dungeonbuddy.

- When an instance is complete, check if there are quests to turn in (and turn them in) before porting out to repair.
- Make it possible to hit start on leader when inside an instance without any instance/raid selected to run. (Bot config/dungeon/type set to None)
- Make it possible to run dungeonbuddy at level 10 when inside an instance and noqueuing is needed. (eg. when you're inside Deadmines with a group and you aren't 15 yet)

Give dungeonbuddy some more love in the forums and add some sections for it:
- General/support section, basically what the thread is now
- Custom profiles section where people can release custom scripts, so they aren't burried somewhere in a single thread
- Custom profiles development and suggestions where the community can work together on custom scripts. A scripting guide would also be really good to put in this section.

Right now the learning curve is pretty steep for the scripts. If people have a place where they can work together on some scripts it would probably get us some really nice scripts.

 

Good day! I have some suggestions on BGBuddy logic improvements that I'd really like to share with developers. And first of all, sorry if my English is bad, I hope you will get the point of my suggestions.

The biggest problem of BGBuddy is that on the beginning of the battle, the bot idle at the base waiting for the biggest fight to start moving somewhere. From my point of view, this should be changed for each battleground.

I think that it really doen't matter how many times bot dies in battleground, it's more important to not look suspicious to other players and don't get your account banned. And add some small random factors to the routine.

WSG
- As soon as the battleground starts, bot should immediately start moving to enemy base, ignoring everything. On WSG there are 3 "routes" to the enemy base - left side, center and right side. That would be really great if side could be chosen randomly, so it just rolls from 1 to 3 and pick the route, so there will be no lines of bots moving the same route. It doesn't matter how fast the bot will die, after death it should start moving to biggest fight as it doing right now. Enemy flag room should be just first important route point of this bg untill the bots death. If bot didn't die in the enemy flag room, it should switch to normal 'biggest fight' searching. If bot is attacked while moving, ofc it should start fighting.
- No flag defence at own base. This is really a problem when 3-4 bots are just standing at base near the flag or their teammates with enemy flag. The enemy team member with flag should be the highest priority to kill, so it should be just searching and trying to kill enemy flag carrier all the time, just like normal a little noobish player would do.
- During the fight bot should randomly go to one of the building with berserker buff and switch back to the 'biggest fight', dont wait for buff if its not there, just run in and run back to fight. There are 2 buildings with buff and bot could alo roll 1-2 to pick the room number, this should happend after some number of deaths, for example after each 5th death, the bot goes to try pick the buff. This will not improve bot fighting skill, but it adds additional random factor.
- 'Biggest fight' doensn't work well for WSG, so flag carrier should be always in prio to the biggest fight.

Arathi Basin
- As soon as the battleground starts, bot should immediately start moving to one of 3 central bases (mines, blacksmith, timberwood), ignoring everything. Base number should be also randomly rolled from 1 to 3. If bot succesfully captures the base, stay there and defend it. If bot dies, it goes to 'biggest fight'.
- Attacked base defence mechanism. If bot is not defending captured base and is moving somewhere searching the 'biggest fight', it should move to the attacked by other team base. Attacked base should be in prio to the biggest fight.

Eye of the Storm
- As soon as the battleground starts, bot should immediately start moving to opposite team bases.
- Bot should be randomly moving betwen bases. The are 4 bases and bot can roll 1 to 4 to pick the base. On each base he should wait for lets say 20 seconds and start moving to another one if he is not attacked by enemy players. If in combat, pick the base after leaving combat.

Alterac Valley
- This is big battleground and current logic works fine here.

Stand of the Ancients
- Current logic is fine. I really doubt it is possible to prevent bot from fighting on the beach, so it's ok.

Isle of Conquest
- Make bot to always use portals from the base. Sometimes bot is getting stuck with closed gates. Everything else is fine here, another big battleground, hard to detect bot players.

Twin Peaks
- Everything same as for WSG. Moving to enemy base at the beginning, flag carrier prio to biggest fight, no own flag or friendly flag carrier defence.

The Battle for Gilneas
- Current logic is fine, but some random base movement would be nice, same as with the Eye of the Storm.

Temple of Kotmogu
- Current logic is fine, simple battleground with fighting in the center.

Silvershand Mines
- Current logic is fine, but making the bot to always fight close to the cart would be great.

Deepwind Gorge
- 3 bases and cart carrier. Randomly run to capture on of the bases rolling 1 to 3. If the base if already captured, wait there 20 seconds and move to another random one. Enemy player with cart is highest prio to bases and biggest fight.

So main idea is adding randomness factor with adding 3 to 5 main points to each battleground and making bot to randomly pick one of them and move among them when there are no flag carriers to kill or bases to capture. And of course, adding forced movement at the beginning of the fight and removing defending logic for most battlegrounds. Bot should be acting more like random noobish player, who is just fooling around and less like a machine controlled character.

I know nothing about programming and I'll never be able to modify existing routines or create the new ones, so I hope one of the developers would find some suggestions useful and will try to bring them to life. Thx for reading and sry for long post

 

Here is how Honorbuddy should be ABLE to look, like a "small"-mode
I'm sick of the Chaos... or is there any way or tool already ? Just make it small and sticky to the instance it is hooked to when in "small"-mode.

 

Please allow for Mailboxes to be loaded remotely from another file, so you can simply have a big list of mailboxes.

 

Small request - as part of the gatherbuddy profile when you go into the node selection tab under bot config there is no option for golden lotus - ideally id like to farm just ores, but have have herb gathering turned on (with all MoP herbs except golden lotus turned off) so as not to miss out on the few that do spawn around my route. Helpful for the transmutes!

Cheers for a great program.

 

It would be great if grindbot also used randomize hotspots, just like gatherbuddy does. This would thwart blizzard's LCP detection easily.

 

About a year ago you added the ability to hit the "Enter" key on your keyboard to press Honorbuddy's "Login" button on the "Honorbuddy Login" screen.

I loved this feature because it meant I didn't have to fumble around on my trackpad to manually click "Login."

Any chance you could also add the ability to hit the "Enter" key to press the "Launch" button on the "Honorbuddy Launcher" screen?

Thank you and keep up the amazing work.

 

Hello.

Can you make an option for displaying timestamps in HB window log?

Best regards.

 

Please add GossipOptions parameter to the CollectThings quest behaviour for quests such as these which require you to Gossip with the gameObject/unit which is underwater - Spirits Watch Over Us - Quest - World of Warcraft

 

It would be nice if BG buddy would read chat before start. IOC for example. BG Buddy Knows its only going Docks,Hangar,Workshop. People will be spamming in BG channel Docks! Or Hangar. BG Buddy collects them, counts them, takes highest key word and makes decision with 10 seconds to spare before BG Starts.

 

It's a good idea but the highest count wouldn't necessarily be where everyone else is going. People could spam Docks and at the last second someone can make a good plan for Waterworks and everyone goes there.

I'd like for the info section in the Honorbuddy client to be more informative. It can show you honor points gained per hour, levels gained in the current session, gold looted/acquired from vendoring items, current BG objective such as defending FC, capping base etc...

 

Gatherbuddy:
Add a speed scale on how fast you mine ores, because for me it goes to fast and forgets to collect the ore cause it goes to fast

Dungeonbuddy:
Add a auto-greed button so instead of loosing all the loot you get some.

 

Question :

Would it be possible to add a sub-option to the "Settings->Kill between Hotspots" in HB, where you can tick whether HB should indeed kill between hotspots, but only when the MOB level is such that it yields XP? As it is now, HB kills everything in its path, potentially wasting a lot of time.

Similar question for the gathering options ..

 

Add <RandomizeHotspots>True</RandomizeHotspots> to the <Grindarea> section within the script.
But a more "hard-wired" option would be very convenient indeed.

Happy Botting