just my opinion, but make this if possible: 1) enable combat while low hp 2) enable combat if umnounted ( happened to me 2 times, random dismount to kill dogs -> then dismouted walked to get packs )
Did you just push an update to this? Just started experiencing a bunch of new problems I hadn't seen before. Transfer Failed: Instance transfer aborted: This is a wow side problem, but I think you need to include some kind of "load through" detection using vendors or something to verify it successfully loaded. If it does this, fails to load, gets kicked back outside, it goes into a very bottish looking routine running into walls etc outside. It doesn't seem to be able to recover from this on it's own. Death sequence -> ran to entrance then spammed "clicking corpse popup..." instead of just running into instance to revive. Gets stuck until I intervene and stop/start. Also noticed one champion completely left instance, alive, flew to where the spirit healer is, and then flew around in circles. Also stuck until I stop/start. I've only seen this once so I'll pass it off as a fluke.
ummm you dont download anytthing it should be streamed to you bud if you dont see the new file structure please get ahold of us on skype username reviir
Talk to your CR sorry bud that is PURE CR issues nothin i can do from my end for you check your class config button
Yea the new Update is called you updated honorbuddy I didnt do anything but i do know that i have heard ALOT of people having MASSIVE problems from the new HB update.
[InstanceTimer-v2005(info)] Started. [Singular] info: botbase disabled BehaviorFlags.Combat MoveTo failed to move to the location: <-370.5505, 161.2445, 50.68102> MoveTo failed to move to the location: <-341.2198, 168.0296, 50.01959> MoveTo failed to move to the location: <-317.5022, 126.7723, 44.92214> MoveTo failed to move to the location: <-305.551, 118.2663, 44.79093> MoveTo failed to move to the location: <-305.551, 118.2663, 44.79093> MoveTo failed to move to the location: <-297.0278, 98.69031, 44.76669> MoveTo failed to move to the location: <-273.7947, 45.03028, 45.43379> MoveTo failed to move to the location: <-322.6329, 64.39885, 46.15767> MoveTo failed to move to the location: <-342.1133, 87.80555, 46.15767> Every Time the same... I allready deleted firelands1 in meshes...
Get me on skype u have 2 mesh folders it would seem. Becauuuussss3eeee that is a mesh error Username reviir
I'm still on 784. I usually don't take updates until I see what the support forum looks like afterwards. I'm continuing to have: Won't enter instance to revive - Tries to click corpse instead. If, for some reason, instance ever fails to load the script breaks. It can't handle expecting to zone in and then not doing so. This should be easy to add checks for, no? It's weird that this happens for zoning in, because it handles failing to zone OUT just fine. It just tries to walk back into the portal. If it fails to go into Firelands from outside though it just can't recover.
Just wanted to say, the biggest issue I've noticed that could help prevent at least the needing to resurrect part is that two of your stop and fight locations are just too close to the lava river (on the normal profile at least). If you have a core hound or molten lord in the pull, you WILL get thrown in. I sit there and watch my bots with this profile and it just happens too often for being such a simple thing to fix. Just pull those mobs close to the river, and then run inland 20 yards before you stop to fight. It would literally take adding 2-3 hotspots added and add maybe 5 seconds to the run, at the benefit of preventing needing to res and stopping the profile from erroring out or wasting 10 minutes on a death. You would never get kicked in again because A) distance and B) the hounds/lords would be kicking you away from the river at that point.
I'm using the trial with a feral druid. Using the normal farm. It gathers a few packs of mobs while mounted and doesn't dismount, it will sit there and just wait to die and it seems like it will only dismount if a mob dismounts me. Then it waits till its really low health, then goes into bear form and finally attacks them. I'm using Taunha's CR. I've also fallen in the lava at least a few times so far and died.
I have noticed that the bot gathers up all of the mobs, then there is a long delay for the CR to kick in and start attacking, in the meantime im pushed down to 25% HP and almost die every pull. How can this be avoided?
appear to be having the same issue, also using tuanha rogue in full mythic gear. also, the bot vendors lockboxes, as a rogue this mildly frustrating.
Shouldnt be doing that guys pelase check your cr its not picking up right away it looks like. Else get me some logs and i will look it over also. BUT i will say that ALOT of people have had issues while using Tuhana CR... once i get them to switch to singular problem solved Far as lockbox's go yes i am aware it vendors this is a generic High end GPH run i am working on a new verstion that will handle Rogues and mailing of lockbox to your blacksmith / rogue... once i can get time
yah first thing i checked. Good to hear about inc lockbox version, id say lockboxes can boost GPH significantly.
also now using prot pally 620ilvl instead of rogue 695ilvl because it seems to survive better with the delay in CR kicking in.
OMFG NICE WORK! the Savage Leather was sold for 22G each in my server i can easily make 10K+/hour TY!!!! and the demand is SUPER SUPER HIGH!
