[H - Quest] Hellfire 60+ WIP

My druid was getting a steady 110k/hr from 58-70
Mage was a little lower -- around 75-80k/hr
Fury warrior was the same as the mage until I got him some decent gear around level 64, then he shot up to about 120k/hr

 

I'm stuck at level 66. I know the profile has more quests to do, but it won't do them. It won't even grind the rest of the way.

Log is attached. The problem starts @ 4:58:13 AM:912

 

Update this profile please

 

Does this work from 58?

 

It is up todate and Yes it will work from 58 it will just grind to 60. Now next time your post something think first ask questions later, It doesn't take a genius to open the profile and see what's going on.


Great profile btw

 

My priest fails to pick up "Forward Base: Reaver's Fall".

 

Good profile! I used it all the way to Blade's Edge. There were a few problems.
1. Lack of mailboxes. I added one in Nagrand, but there are plenty more that need added.
2. There was one quest in Terokkar that I had to do by hand. I don't remember which one.
3. Also, two quests in Nagrand weren't working (Vile Idolatry and Stealing from thieves) so I added hotspots to your profile and that fixed em up.
4. Last problem I noticed was that the PVP area in Nagrand wasn't blacklisted. My lil guy decided it was okay to trot on through there with the Alliance in control.

 

Came back an hour later only to see that my bot had died 23 times inside Honor Hold, all red armour and kept ressing ontop of guards.

Why would it even go in there?

 

I have to sit near the computer while this profile is on.. When I go - my char stucks, dies...

 

First off, thanks for putting all the effort/time into this profile. Is there anything special we have to do to Blacklist Honor Hold, as far as quest tagging goes? Or is it the typical Blacklist same for both grind and quest? Second, which is related to Avoid Mobs, anything special we need to do there to make sure we decide not to pull "Fel Reaver"? The huge elite that roams everywhere. I came in the room last night to my toon pulling him, made me chuckle Thanks again.

 

Stopped at 66

 

The only 2 things I notice wrong and were due to level to low :
<PickUp QuestName="Proving Your Strength" QuestId="10479" GiverName="Warden Bullrok" GiverId="18407" GiverType="NPC" />
<Objective QuestName="Proving Your Strength" QuestId="10479" Type="CollectItem" ItemId="25433" ItemName="Obsidian Warbeads" CollectCount="10" />
<PickUp QuestName="He Called Himself Altruis..." QuestId="9983" GiverName="Matron Celestine" GiverId="18301" />
<TurnIn QuestName="He Called Himself Altruis..." QuestId="9983" TurnInName="Altruis the Sufferer" TurnInId="18417" />

Other than that, this profile was perfect. There was a couple hotspots in Shat. from getting stuck on sections of bridge, but HB got unstuck after 2 attempts.

 

This profile is broke for me. Does 1 quest then just breaks. I have tried every edit I know and nothing will make it work. Going to chalk it up as a HB problem.

 

Not an HB problem, the profile works just fine A few edits are necessary to make it perfect, but you'll find those throughout the thread.
What quest is it failing on?

 

I had some Mesh issues earlier today and I also noticed people having issues. Have you tried the real basic.. erase everything in the mesh folder and try again?

 

<PickUp QuestName="Forward Base: Reaver's Fall" QuestId="10124" GiverName="Sergeant Shatterskull" GiverId="19256" />

It will get that far, pick that up and then the bot stops itself. I went and did that quest by hand and it moves to the next but stops, saying it cant create quest.

 

where is the grind area fr 58-60? my character dosen't move
[1:16:51 PM:780] StyxWoW.AreaManager.CurrentGrindArea is null

im at the legion front but still currentgrindarea is null

does it have to be at a certain point?

 

I started from ThrallMart and it went right to the correct grinding area?

 

...have no idea wat ur talking about

is that a question?...

 

Well, I decided to give it a go again, ran 2 quest by hand and turned it on... working great now.

Guess it was just 1 or 2 quests that had an issue.