For the Jormonger issue were you testing with an alliance toon? I noticed that there were different mobs for both factions and added the other mobs in an update yesterday. I've noticed that for ranged dps that it would sometimes not attack the constrictor tentacle, I still need to look into what's causing the issue. Were you using singular as your routine? There will be an all in one profile, once all the profiles are completed. There's quite a few complexities with looting every boss e.g. having to deal with vendoring epic quality gear and not vendoring raiding or pvp gear, making sure the bot knows how to get to the vendor after each boss, players starting with not much free bag space, etc. Adding support for the faceless horror before General Vezax is still on my todo list. Good to see there's no issues with icc.
1. Which boss did you die on and what was it trying to do once it respawned? 1.1. Looks like Kologarn was blacklisted because the bot was unable to generate a path to the boss. 1.2. It wasn't moving towards Sara? 2. When you start the profile outside of Ulduar it will set it to 10 man since it's faster and then set it back to 25 man once up to Yogg-Saron. Looks like I need to do some more testing for this boss. 3. The dowhen hook for this seems to sometimes not execute and since the bot can't navigate to the entrance it will just take rez sickness. I'll make a request to have honorbuddy support flying when moving back to it's corpse. 4. Singular considers the mobs and even the boss to be trivial, so it will not use cooldowns by default. You can try checking singulars settings for something that will let you use cooldowns all the time. 5. This was answered in the above post. 1. I added support for ranged dps in yesterdays update for Kologarn, but it looks like it needs some more work. You will get stone gripped if you have a pet or you're outside of melee range. I haven't added support for dismissing pets first into the profile yet, but it should be moving into melee range if you're a ranged dps. 2. What were you getting stuck on? 3.1. It should be switching to portals as soon as they spawned, I made a lot of changes to the Yogg-Saron yesterday so i'll have to look into that. 3.2. This might happen in certain situations and still needs some work done on it.
Actually, I got the same issue with faceless horror since the voidlord summoned would not join the battle unless the toons attack it. If the voidlord has a higher priority to be killed, it should be fine.
1: 1.1 and 1.2 gives the scenarios I met with this problem. 1.2. It wasn't move towards Sara but a corner in the room. 2. I am not sure about how the progress is recorded for Ulduar now. Originally, 10-people raid and 25 have different record on the boss killed. Based on your reply, it seems that 10 and 25 share the same record now (and this matches with what I saw in the raid info). If this is the case, then what you have done is the best way. 3. For this one, it does not take the sickness. Actually, the toon just stays on the ground instead of flying. And it stuck in a corner near the entrance. But I think this is more related to the honorbuddy itself rather than this profile. 4. I will try to find this and apply it in the later test. With specific boss, 2. With respect to Hodir, the battle was fine at the beginning, and then the toon start to run toward the entrance and keep running as the door is closed. This happens in the 25 mode. The raid was changed to 10-people mode then (as I mentioned above) and it was all fine to kill Hodir. I did not play Ulduar in the WLK and not quite sure about the mechanism on every fight. When I solo, I always choose to rush the boss if possible and find a proper solution if failed. So what I proposed is as strait-forward as possible. As the other tester may know the mechanism better, they may have some suggestions better for specific boss.
*Yes Alliance. *Singular as I wasnt going to test this week with Tuanha as most profiles support singular as a primary routine. *NO rush for optional looting, just a suggestion. *Will corpse runs be implemented? I know technically they shouldnt be needed but sometimes accidents happen.
If you want to use a combat routine other than singular, then you'll have to ask the author of that routine to add support for capability flags. Corpse runs is already implemented in the profiles.
Test with my 660 lvl Boomkin. Everything is perfect except Yogg-Saron. After gripped by the tenctale, the toon cannot get off it. (It has charges of starsurge/starfall as well as moonfire but did not cast it). Then I stop the bot and finish the battle manually. This is also the tricky part when I solo the raid. Further, I start the script outside the raid. It is 10 -people first and turned into 25 just before Yogg-Saron. This works well as well as reduce the possible flaws in previous boss. I'll let you know when I test the other characters.
I still need to look into what's causing that issue, but i'm guessing it's an issue with singular for ranged dps. If you are able to test with a ranged dps with a different routine and see if that issue still happens.
Two more tests were done: Fury Warrior: I use singular to test melee dps. It failed in P2 of YS. In detail, when the warrior was gripped, it tries to attack another tentacle instead of the on it should attack. Ele Sham: I tried to use a routine other than singular at first. So I chose TuanHA Shaman(free edition). However, with this routine, it did not work even with the second boss. (And there was no combat in the first one actually). So I switched back to singular. It also stuck in P2 of YS. When sham was gripped, it tries to cast tremor totem.... Then it also failed. Besides Ulduar, I test ICC for the warrior. Everything is fine except for some tiny problem. After enter the raid, there was a spider mob stays in the air. (I guess that's a but of the game). Then the warrior stuck since it tries to kill the mob while the distance is too large. That's the only issue I met.
did you ever manage to add the pureblood firehawk ? im looking to farm this so i will test it fully if you have it
Firelands is the next raid that I plan on doing after I finish adding world navigation and fixing current issues.
Downloaded a fresh install of HB for this. Here are some results from yesterday. Combat Rogue ICC run: Was not able to take out the boat first time and the cannons froze before the enemy boat was killed. The rogue just stood there for a while and then kept trying to run off the edge of the boat as if the boat was docked until it finally wiped. Stopped the bot right after starting the event on Saurfang and restarted bot, after I did this, the bot just stood there and it said No viable mobs in area. Would not engage Deathbringer. Had to do it manually. After these issues, the bot finished ICC 100% Afk. BM Hunter ICC run: Smooth run except for LK, when the hunter got the LK down to 1%, there was still a Shambling Horror up. The bot would not attack it. Since LK was down to 1% he started his RP and Tirion came out, instead of Tirion hitting LK to finish the encounter, he actually aggroed the Shambling Horror and the encounter would have never ended because the thing heals itself each time it enrages or something, or it would take Tirion a very, very long time to kill it. I would think it should be prioritized over LK after phase 1 has ended. Ret Paladin ICC run: 100% Afk'd and finished. Destruction Warlock ICC run: 100% Afk'd and finished. Destruction Warlock Ulduar run: 100% Afk up until Mimiron, kills him but then runs to the shattered walkway portal and just sits there, the honorbuddy message states, No viable mobs in area. Frost DK Ulduar run: Exact same as warlock. I actually would continue the run to test Yogg, but I forgot how to manually get there haha, its been a while...I'll try to figure it out though, will post results later. One observation I made was that if the bot choose to use the zep to get to ICC, it takes an eternity. It would be much faster if the bot would use the pandaland portal and then go to vale and use the dalaran portal. I'll report more results as I continue to test.
