
15. July 2010, 16:31
|
|
|
We are *Premium*
Join Date: Aug 2009
Posts: 162
Thanks: 1
Thanked 0x in 0 Posts
Pirox Award(s): 0
I speak: English
 
|
|
Not pvpTool related except I'm wanting to RAF 2 characters running pvpTool to assist my main during runs through instances. I downloaded KeepFollowing and have the profile posted in another thread that does '/kfollow leader' and an antiafk - I removed the antiafk and set a target macro to assist the main only. The logs show the target spamming, the targets change properly....so it should not be pvpTool causing my problem:
The point of this post then is that this works great for my warlock...he follows and attacks just fine, but the shaman will just stand there. She won't follow at all, but the pvpTool targeting function and macro appears to be working. The WoW directory is shared between all three accounts. The shaman will enter the /kfollow command from the profile but not even budge or turn to face, but the text is on her screen saying 'Following Xxxx'! Arg, I was working on this for almost an hour, just standing in an instance. If I go to her screen and type /kfollow leader, she will absolutely not do a thing when pvpTool is running. On a fresh relog before running pvptool, she will follow to the leader and stop following once she gets to him.
I'm absolutely confused!
Am I missing something in my setting up of KeepFollowing? Should I try running WoW from different folders? Baby crying and it was getting late so I quit debugging so I figured I would post about this at work to see if anyone has seen a similar issue before...
I can still just run them through using /follow and an after combat macro but this addon is supposed to make it easier!
Any ideas?
---------- Post added at 11:31 ---------- Previous post was at 10:43 ----------
I thought I posted this in WoW->General...could be moved to the appropriate forum if a mod so desired.
|
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
|
|
|
|
|
 |