+1 The last version was an improvement but it still bothers me, that it tries to step a few steps backwards even when you are in a party / raid...
Is it possible to use the Item ID for Conjure Refreshment (Mage) because i run into Problems with German WoW
Hello there bersacker, unfortunately I do not support the other game clients. It is enough of a challenge to keep it working with one client. Tested FTW in a raid, no major lag. Small lag spike right after starting, nothing else for me. Your machine might need more memory, or maybe you were running it in diagnostic mode, which slows it down in order to print to the console. Will look into making FTW not antistuck with scroll lock on.
Kamilche, here is the exact error I get. Code: [19:33:57.010 D] System.AccessViolationException: Could not read bytes from 01599EFA [299]! Full log attached.
I have a quick question if i set the value of "Death Grip Target.IsFleeing = 1" and change it to "0" then DeathGrip would not be cast at all correct? only when i click on it ?
No, with this you are turning off death gripping target that is fleeing from you, like humanoid NPC's that are trying to run away from you when they have low health. I found a small bug. Issue is bandaging your self, it instantly stops bandaging when you hit certain point of HP (for instance i have 49% of HP, routine will use Bandages, and on 50% of HP continue to move). It will not use complete "channel" of bandaging, it will just interrupt it at certain point, even if you need to heal 1% of HP.
Updated paladins, they should no longer try to emancipate every time they have forbearance on. Fixed bear rotations, latest patch messed with thrash. About the crashing with the deathknight, you might be running too many plugins, or maybe you don't have enough memory on your machine. You might also want to try running HB as administrator if you feel it isn't either of those. Is it doing the bandage movement in grind bot? If it is, we might be able to fix that, otherwise I don't know what the problem is. Could you post a log if it does it in grind bot.
Sorry, my bad, havent provide much info to you.. Well.. log would be.. insanely big since HB is running for.. 4(?) days now without interrupts so.. going trough all that would be.. A bit more info: Honorbuddy .518 Botbase "Questingbot" with "killing between hotspots" enabled. Profile "Kick's Mega profile pack" Horde flying version for Outland. (i know that profile has nothing to do with this, but just in case) So basically what is happening.. Bot is on route from point A to point B, at some point it pulls larger pack and get below certain amount of HP. In combat, as does out of it, no matter how low im on HP, bot will use bandages to certain amount of HP and continue moving, interrupting bandage channel. This can happen even if you are 200hp below that limit where bot continues to move.
Have a good CC for mage ( Arcane, fire or frost) ??, nobody have a good CC that make a good dps. I have 490 item level and i cant get more that 100k in a boss
Yes the endless move back is fixed. In regards to the bandaging, questing bot sends move signals constantly which interrupt the cast before it can cancel the move order. This breaks the cast, and then it sees its not casting anything, and it moves on. There is nothing that can be done about that from my end.
Would this work for "IsBoss": HTML: Level = ?? I don't want to waste my long CDs on trash mobs so something that will only take place on boss fights would be great.
i treat everything in my cc's as a boss, if: "target.,maxhp >= groupsize*4m" so every mob over 4m hp is a boss while solo every mob over 20m hp is a boss while grp(5) every mob over 40m hp is a boss while in raid(10) every mob over 100m hp is a boss while in raid(25) might not be 100% true for all and everything, but at least i dont feel like wasting cooldowns. also, my CC got a list with all the "mighty boss names" so i could doublecheck - but mostly i just check hp.
that was pseudocode - it does not work this way with FTW. if kamilche adds some syntax like that, it will. But thats up to him!
