Kaelhoel
New Member
- Joined
- Sep 15, 2013
- Messages
- 175
- Reaction score
- 1
Did you copied the quest behaviours to the behaviours folder inside HB? This solved same issue for me...
Oh bloody doh... Thanks mate!
Did you copied the quest behaviours to the behaviours folder inside HB? This solved same issue for me...
It loots the bos and then jumps of the edge so that I get teleported to the start. When I get to the start of the instance, my character just keeps jumping of the edge. Sometimes (but rarely) he goes out the way he should. It loots the boss as I said but it still won't work.
Really awesome work. Tried it today, first time in Black Temple with my Monk and the Glaive dropped...thanks m8![]()
Oh bloody doh... Thanks mate!
That profile is Frostfever's territory.I'm running through the Black Temple farm now. Fury warrior ilvl480
On High Warlod Naj'entus, my character only starts attacking the boss when his shield is up. When the boss removes his water shield, my dude stops attacking again. Which means that he does 0 damage and dies, horribly.I've tried with lvl85 DK, lvl90 prot paladin and lvl90 Fury warrior now, same thing happens.
On Supremus my Fury Warrior stands in blue fire and does not use any special attacks. Not sure if this is only a Singular issue, or whether its profile based..
On Shade of Akama the bot at first doesn't attack, because it's out of range after killing the lesser mobs. I didn't wait to see if Akama would be killed.
On Teron Gorefiend the bot jumps bravely in and starts auto-attacking the boss with an occasional Heroic Strike, so I need to step in again to save his butt.
On Reliquary of Souls the character starts using special attacks! First head goes down. Adds are easily killed. 2nd head spawns and special attacks are still being used, but not quickly enough. Bot dies, even after using a healing potion... Will continue later.
You'd just have to add a code in the profile to switch the dungeon to Heroic before starting.Is there any way of running the Northerend instance grinds in heroic instead of normal ?
Things like this are completely unpredictable and aren't always as global as you think. 7/10 the issue is specific to your configurations, that's why profile developers typically ask for a log, that way we can see how the code is being executed on a technical level rather than a visual level.Hi echo! sorry to bother you, a few months back i told you about a blackspot when flying to vortex pinnacle, where the screen turned black. It seems that you made the bot so it can't reach that spot but for some reason he doesn't continues, he gets crazy spinning on the spot trying to reach the blacklisted spot or something like that. haha pretty funny but completely broken! just letting you know.
Skipping mobs that are out of the way, attack mobs in the way: Normal run pulls intentionally skip mob packs, it's designed to run the dungeon how a typical dungeon group would.BTW, the grim batol normal pull is leaving a lot of mobs unnatacked and it seems a waste since he already wastes so much time running, spending a few more secs to pull some mobs that are already on the way could net better results. I have yet to try the lite gold run, that could work.
Singular seems to underperform with this profile for some reason, something that doesn't happen with other profiles. i mean, its a slower and a lot of the times after pulling he just stays iddle getting pwned when he should easily wipe them, this from a 511 frost mage. He does the job most of the time in normal, but forget about gold run for this very reason... i can pull 3 times what he pulls in gold run manually and clear it without any problem, which could mean i have enough gear.
Things like this are completely unpredictable and aren't always as global as you think. 7/10 the issue is specific to your configurations, that's why profile developers typically ask for a log, that way we can see how the code is being executed on a technical level rather than a visual level.
I've ran at least 14 testers through that profile, all different classes - factions - mount speeds and none have been able to emulate any sort of issue while navigating.
Skipping mobs that are out of the way, attack mobs in the way: Normal run pulls intentionally skip mob packs, it's designed to run the dungeon how a typical dungeon group would.
At least a optimized run would, Grim Batol is still undergoing tweaks considering every run-type was coded in less than an hour.
As far as Singular combat optimization - I know what you mean.
My geared Monk that was botted wasn't able to even come close to 10% the efficiency of my under-geared Monk that was human controlled.
Singular is a VERY choppy combat behavior. The only reason we recommend it for our profiles is it's one of the only behaviors (that I know of) that not only supports every class, but is able to navigate while in a dungeon properly.
I was able to Tweak my Singular's code a bit for Monks so that it spams Spinning Crane Kick at 2 or higher mob pulls while rotating small healing spells / cooldown buffs. It did increase the efficiency, but not to human-ability.
For now, with the limitations of Singular - the Grim Batol run won't be the instance-of-choice for demanding gold farmers.
However, once our gear standards rise so to will the ability and profits.
I didn't "get you wrong" at all.You got me wrong, i don't mean the coding, i have a modified singular profile that does a reasonably good job, at least in every other profile.. but he underperforms greatly when doing grim batol, after body pulling he just goes idle for a few seconds sometimes, the reactions are a lot slower and it only happens here. The human controlled was meant to kinda show that gear is more than enough nothing more, sorry for that misunderstanding, never meant the bot to perform to my level.
That's a CTM error. In order to get the bot to jump off the edge, the bot has to be told to go to a specific coordinate that's mid-air off the ledges.About the vortex pinnacle pathing, i'll try to get you another log later. Alsot when finishing the instance, sometimes he fails to complete the path to the exit resulting in the bot getting stucked trying to get back, this was already reported i think, i can the a log of this if you want, it happened a few minutes ago.
I didn't "get you wrong" at all.
I was just agreeing with you by giving my own experience as an example while adding a few little details to go along with it.
It's no mystery that the bot .. as you say .. "underperforms" while running this dungeon but like I said, there's nothing we can do about that aside from modifying a little bit of Singular's code and waiting for Blizzard to "simplify" the game further as they tend to overdo..
That's a CTM error. In order to get the bot to jump off the edge, the bot has to be told to go to a specific coordinate that's mid-air off the ledges.
However, it can be a hit-or-miss situation because when the bot jumps off the edge, it could easily overshoot the coordinate causing the bot to never finish its navigation to it.
Speed increases/decreases can cause this more frequently. But at the same time.. it can be completely natural given the millions of variables.
So, given that - when the bot is teleported back to the beginning of the instance, navigation fails because the bot still wants to navigate to that coordinate - which it obviously cannot anymore.
I'm looking into fixing this - after I get some sleep.![]()
You may want to consider buying the bot... Or at least hiding the fact that you're using a modified version before submitting your log.ahh, ok, sorry for the missunderstanding and hoping you can fix the pathing.
Here is a log of the black screen [19:01:43.672 N] Honorbuddy v2.5.8179.697 started. [19:31:13.229 N] Logging in. - Pastebin.com
Hope you can get something out of it.
Thanks for all the support! You are doing a great job!
You may want to consider buying the bot... Or at least hiding the fact that you're using a modified version before submitting your log.
The BlaSOD (black screen of death) happens when the bot forcibly navigates directly up from it's current position - while spinning.
This happens rarely, but can easily be fixed.
<CustomBehavior File="UserSettings" LootMobs="True" PullDistance="1" KillBetweenHotspots="True" LogoutForInactivity="False" />
<RunTo X="XXXXX" Y="YYYYYY" Z="ZZZZZZ" /> <!-- Kill (Boss Name)-->
<CustomBehavior File="UserSettings" LootMobs="False" PullDistance="15" KillBetweenHotspots="True" LogoutForInactivity="False" />
I'd like to request the Lawbringer Recolor plate set
Lawbringer Armor (Recolor) - Transmog Set - World of Warcraft
I recommend including an option to only loot bosses too, as soloing an instance and looting every enemy fills up bags quickly.
Code:<CustomBehavior File="UserSettings" LootMobs="True" PullDistance="1" KillBetweenHotspots="True" LogoutForInactivity="False" /> <RunTo X="XXXXX" Y="YYYYYY" Z="ZZZZZZ" /> <!-- Kill (Boss Name)--> <CustomBehavior File="UserSettings" LootMobs="False" PullDistance="15" KillBetweenHotspots="True" LogoutForInactivity="False" />
I cant farming![]()
Ilove you echo gdfgsfdgsda workingDelete your "Quest Behaviors" folder located in the root of your Honorbuddy folder.
After you do that, copy a new Quest Behavior folder from a fresh Honorbuddy download.
[InstanceTimer]: Your instance run took 04m:20s
[InstanceTimer]: Waiting for 08m:10s
Hey! I've just tarted using your profiles and I must say that they are great! However there's one thing I dont understand about the profiles logic.
I'm currently running the transmog profile for the Assassination Armor. Every time the bot is done with the instance it usually waits around for 8 or 9 minutes. Why is that? Cant just the bot go out and reset the instance, like it does?
This is what HB usually does.
Code:[InstanceTimer]: Your instance run took 04m:20s [InstanceTimer]: Waiting for 08m:10s
Also attached the log not sure if that helps.
Thanks for your amazing profiles and keep up the awesome work!
Cheers,
Khemist
View attachment 107538