Problem - New Target Switching Problem

[Grrizz]

I am having issues with my toons not switching tagets. I have all neccasary toons with target switching =1. I also have used this before and was always able to switch targets. The mission I am currently doing is Trial of the Eternal Cyclone in The Burning Lands. I have my wizard located at the top and kissassist is off so can manually burn it down when adds are down. I also use dannet. My main tank will not switch fron the main Boss even when I continually press on new target it switches right back to main boss. not sure why as wizard is running manuallyso main tank should not be using its target. would hate to have to setup hotkeys as time is a big factor is this quest and my toons constantlly try to climb to the top instead of burning down adds so wizard can burn down boss. Any and all help appreciated.
Thank You
Grrizz

 

[Sic]

howdy grrizz, I moved your kiss support question to the kiss support section

the target switching option is so you can swap with your MA, and it sounds like you know that, and know how it should work.

I would make sure you're not using mq2melee and your kissassist isn't set to use it either

 

[Grrizz]

Ty Sic and ouble checked and all toons including rogue which uses maui still are all set to 0 on mq2melee.

 

[B_I_G__D_A_D_D_Y]

I am having issues with my toons not switching tagets.

Only the MA (your tank) needs the setting:

[Melee]
TargetSwitchingOn=1

... but then your tank also needs a button made to send the command to each assisting character to actually follow the MA's lead and change their targets. That command is /switchnow and you need to transmit that to your group/raid via EQBC or Dannet.

I use an EQ hotbutton and EQBC so mine looks like /bcg //switchnow. I usually spam it a few times.

My "driver" is an SK also running KissAssist and I manually change the target on him. Sometimes I have to do this a couple times but eventually the SK will stay fixed on the new target and then I click the button to get the rest of the crew to follow his lead.

Note that most pets will NOT change targets unless you actually /pet stop them. I usually don't bother and have never made a button to do that. It's only been an issue on a few events like Avatar of War. In that case I actually just bag all my pets ahead of time.

 

[Sic]

can you also make sure that none of your toons (that you don't want to be) are using mq2afnuke?

 

[Grrizz]

I was not sure what it would be under so pulled up each ini file and looked for mq2afnuke and it is not even listed on any of them.

 

[Sic]

I was not sure what it would be under so pulled up each ini file and looked for mq2afnuke and it is not even listed on any of them.

mq2afnuke wouldn't be in your kiss (and shouldn't)

it is a stand alone plugin

/plugin mq2afnuke unload just in case, was my point

 

[Grrizz]

I typed into all 6 toons and said it was not found also checked under plugins to make sure it is with the program. It is listed under plugins.

 

[Grrizz]

ok just typed in ///////plugin mq2melee unload and found it was loaded on my mag but no other toons

 

[ctaylor22]

Make sure your using MQ2EQBC or MQ2DanNet on all your players. The Tank/MA will broadcast when his target changes, when manually changed, causing the Assist characters to trigger an event that will switch their Targets.

 

[Grrizz]

All my toons are dannet so no problem there

 

[ctaylor22]

When you switch targets with your MA, you should see the MA broadcast a message using Dannet. Should be something like. "I am MA, and I switched to new Target." and then "TANKING-> MobName Here <- ID####". What you want to check for, is the other group members getting the "TANKING-> MobName Here <- ID####" message. If they are not then they won't switch targets, If they are getting the message, Then you should see the assist character /echo a message "Attack Called: TankNamehere MobID". The MobID should be the same number as sent by the Tank in their TANKING-> message(ID####). If you are not seeing the assist character /echoing the message, then the Dannet message event is NOT getting triggered.

If your Dannet message format differs from the default, that could be the issue.