• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver

Question - Attack auto targets my Mage and stops attacking.

Joined
Dec 28, 2019
RedCents
4,627¢
I have no idea what is happening right now but it is getting me killed.. :(

I am using mq2monk for my monk and KA11 for my Mage. This is a group of six but the issue seems to be with my Monk and Mage. At first it was just my Mage not auto following 50% of the time when I hit the "follow me" button, after some research I switched to EQBCS2 and this seemed to resolved the issue. So tonight I am running down through Kunark, hit Chardok and start fighting my way down when I notice that every time after I pull a mod to me (echo of Dup), I hit "a" to start auto-attack and the monk targets my mage and does nothing... I switch windows and start attacking with my War and Zerker and flip back to the monk. I check the chat keys and "a" is only assigned to auto-attack. So I click on the mob that we are fighting and hit "a" and boom, the monk auto targets the mage and does nothing. Does this sound like anything anyone has dealt with or has a solution for?

Here is my set up:

Monk set to Puller
Warrior set to Main Assist & Main Tank

Camp ON
/bcg //camphere on
/noparse /bcg //if (${Me.Class.ShortName.Equal[BER]}) /zerk mode 1
/noparse /bcg //if (${Me.Class.ShortName.Equal[WAR]}) /war mode 4
/noparse /bcg //if (${Me.Class.ShortName.Equal[MNK]}) /monk mode 0 (I play my monk)

KISS start
/noparse /bcg //if (!${Select[${Me.Class.ShortName},BER,WAR,MNK]}) /mac kissassist assist ${Group.MainTank} 98
 
Last edited:
Ok, I have made sure that my old KA INI for the monk is no longer preset in the MQ2/Test/Release/Macros folder. I have also insured that his INI file does exist in the MQ2/Test/Release folder. I went through my mages INI file and found a few things that were not filled out and completed there values (though this would probably not be part of my original issue), so this will help in a different way. Going to test this out again, I can not reproduce this behavior in the GH against the combat dummies so going to find something that I can kill.
 
Ok, ran to a zone and starting killing stuff, everything looks like it is acting the way its should. Though the mage is still trying to cast Giant Modulation Shard over and over, even though its lore

My buff line looks like:
Buffs5=Summon Modulation Shard|Summon|Summoned: Glowing Modulation Shard|1
 
Buffs5=Summon Modulation Shard|Summon|Summoned: Glowing Modulation Shard|1

you will need to look up the proper aa level for your skill and the item it summons changes based on level:
here is the list of shards it can summon:

INI:
Summoned: Giant Modulation Shard
Summoned: Glowing Modulation Shard
Summoned: Large Modulation Shard
Summoned: Medium Modulation Shard
Summoned: Radiant Modulation Shard
Summoned: Small Modulation Shard

ad for the monk attacking the mage, that i have no answer for, other than the xtended target window coulda been bugged, it sometimes happens that eq sets the autohater wrong or something, or a macro or plugin does it, i dont know, i know the bug atleast made the kissassist people put in a fix for it, to ensure that xtarget1 was set proper.

so i am thinking that you might have had one of those sessions where the eq windows just mess up things
 
Thank you for that @kaen01 this has resolved the mage issue with the repeated casting. I was unaware of the AA levels.

As far as the Monk selected the Mage. After I removed the old KA INI from the KA INI path, the issue has seemed to go away, at least it has not happened since. I sat in the Overthere for about two hours killing trash mobs and had no more issues.
 
Wow... here is something interesting that I came across today, My issue with the Summoning: Glowing Modulation Shard over and over again came back. I was trying to think of what I did since the last fix. Then it dawned on me, last night I was cleaning out my bags and I started placing any of the "left over from battle" summoned objects on to the walls of my house..... This started causing issues later on with duplicate lore items, EVEN when I was not in the same zone as my house. I have since gone back and destroyed all of the summoned items that were on the walls of my house and GH. Now I am no longer repeatedly casting Glowing Modulation Shard again and getting the duplicate lore error message.

Hope this also helps someone.

TL;DR: Make sure your casting/summoning the item that matches your current AA and don't stick left over summoned items in your GH or house.
 
Last edited:
Question - Attack auto targets my Mage and stops attacking.

Users who are viewing this thread

Back
Top
Cart