blancharke
Member
- Joined
- Jan 15, 2010
- Messages
- 225
That is weird. You know how WoW leaves you in 'combat' mode sometimes when you're not really in combat? I would continually get the message 'I don't have a target'. 'That requires a target.' when it happened, so I added that bit in there to disable the voice spam.
The only difference between that, and the old one, is the addition of 'target != null' and 'target.isvalidunit'. Try adding the new code back in, but leave off the 'isvalidunit' check - just make it the 'not null' check. Does it still work for you on autoattack? If so, that's what I'll keep.
BTW - what was your new toon class/spec? I could check this out myself if I knew what class was failing.
I'm busy on making my own class spec files because I'm leveling 5 toons in dungeons fighting as a group. When I'm done adding stuff + tweaking I'll publish it.
Will download the latest version now and test it on a lvl 1 toon again. (all meleeclasses I tested had this problem)
For the people who are interested about the 5 man dungeon project using FTW: 3 warriors all specs, frostmage, holy paladin.
EDIT:
I tested with the suggestions like you said. Removing the null part but this doesnt help. He didn't wanted to attack Kresh - NPC - World of Warcraft with this
Code:
private bool On_AutoAttack() {
string fnname = "MBC.On_AutoAttack";
MyTimer.Start(fnname);
if (!StyxWoW.Me.IsAutoAttacking && StyxWoW.Me.IsValidUnit())
{
log(" AutoAttack");
Lua.DoString("StartAttack()");
}
MyTimer.Stop(fnname);
return false;
}
Will use the old method again untill you find a solution.
Last edited: