Problem - I broke KA Toons named xxmm, xxmma, xxmme, xxmmi, xxmmo, xxmmu

[Sifter228]

When /mac kissassist xxmm is used or even when /mac kissassist ${Group.MainAssist} is used the toons assist xxmma instead of xxmm.

Dang!

 

[Sifter228]

Sucks all that effort to create six accounts and level them to 10 just to find out the group will never work due to how I named them. Probably should be in the FAQ.

Names that are identical in the first four letters will not work with KA. Avoid acdd, acdda, acdde, acddi, acddo, and acddu names. Man what a waste of tme.

 

[ABDon]

Untested, but try /mac kissassist "xxmm"

Or just physically target xxmm and do /mac kissassist

 

[Sifter228]

Nothing works. I've tried everything I can think of. Six hours wasted. I don't have a free six hours to give away.
Nice it'll take six hours to create and build a new level 10 tank. /sigh

 

[Sustained]

Name changes fixed it for me :P was instant fix

 

[Sifter228]

Name changes fixed it for me :P was instant fix

No DB coins so that's not happening. Someone clue me in on what it is that i wrong with names like abdd, abdda, abdde, abddim abddo, abddu?

 

[jande]

Its not mq/kiss is a known everquest problem.
Same letters actually as a character name, then using the name as a prefix is a bad idea. so xxmm or abdd won't work. EQ name matching is a stuffup.

What you can do is rename that one character xxmm to something like xxmmt

 

[Sic]

No DB coins so that's not happening. Someone clue me in on what it is that i wrong with names like abdd, abdda, abdde, abddim abddo, abddu?

it is likely finding the closest first match it finds

 

[AmericanNero]

That doesn't make sense... KA just takes the name and opens the file. There is no trimming.

 

[Wild Beagle]

I would guess that you would have issues within the game itself with those names.

 

[ABDon]

There used to be a similar problem in game (not MQ specific) - I have toons with the same name but just an 'e' or 'ie' on the end - which prevented "/invite toonname" from working.

That was fixed, but seems to be in the same vein

 

[Maskoi]

Take xxmma out of the group and try starting it with the other toons and see if that works.
Also check the name as kiss starts up as well in the mq2 windows.

 

[vandersl]

This will probably turn out to be a good thing in the long run. Nothing screams "Hey, look at my 6-box bot team!" quite like having them named like that. Whatever the reason for the current suspension waves, making the team a bit less conspicuous wouldn't hurt.

Also, if you have any higher level help available, or at least a few K pp, can get to level 10 on all 6 new toons in 15 minutes. Skip the tutorial, head to WFP and do the Red Wine for Lady Shae quest for 10 minutes.

 

[Sifter228]

This will probably turn out to be a good thing in the long run. Nothing screams "Hey, look at my 6-box bot team!" quite like having them named like that. Whatever the reason for the current suspension waves, making the team a bit less conspicuous wouldn't hurt.

Also, if you have any higher level help available, or at least a few K pp, can get to level 10 on all 6 new toons in 15 minutes. Skip the tutorial, head to WFP and do the Red Wine for Lady Shae quest for 10 minutes.

I know i was keeping the tanks as A but changed it with my last group. I now have 54 toons humming along.

 

[Kasino7]

To get around it, on the tank, couldn't you broadcast a spawn id?

/bcg //mac kissassist assist ${Spawn[${Me.ID}].CleanName}

Otherwise, any option in kiss to start up based on ids? If you can /tar id 0124 technically should be able to (maybe withn a recoding of the startup) do the same based on id?

 

[Sifter228]

I tried that as well and it doesn't work consistently. At some point the macro breaks without an error given. It doesn't take very long for the toons to just stop "recognizing" the MA as the MA, often, before the first mob hits camp..

 

[Sifter228]

I tried that as well and it doesn't work consistently. At some point the macro breaks without an error given. It doesn't take very long for the toons to just stop "recognizing" the MA as the MA, often, before the first mob hits camp..

I've gotten it to work now by assigning the tank/ma as just an assist and i'm having melee "tank/ma" for now. It's strange however as all targeting and attempts to work with ABDD in vv in a 6 group of ABDDvowels ends up everything intended for ABDD actually goes to ABDDa. Kinda neat.

 

[Knightly]

EQ itself would target whoever is closest. MQ probably targets whatever is first match in the list. Can fix that in KA though by doing an exact match.

 

[ctaylor22]

@Sifter228

Here is the fix:

In the AssignMainAssist routine find these lines:


[CODE title="Old Code"]
/if (${Spawn[pc ${MainAssist}].ID}) {
/tar pc ${MainAssist}
/delay 10 ${Target.ID}==${Spawn[${MainAssist} pc].ID}
} else {

[/CODE]

and change to this:


[CODE title="New Code"] /if (${Spawn[=${MainAssist} pc].ID}) {
/tar id ${Spawn[=${MainAssist} pc].ID}
/delay 10 ${Target.ID}==${Spawn[=${MainAssist} pc].ID}
} else {

[/CODE]

I will make this change in the production copy as well.

 

[Sifter228]

@Sifter228

Here is the fix:

In the AssignMainAssist routine find there lines:


[CODE title="Old Code"]
/if (${Spawn[pc ${MainAssist}].ID}) {
/tar pc ${MainAssist}
/delay 10 ${Target.ID}==${Spawn[${MainAssist} pc].ID}
} else {

[/CODE]

and change to this:


[CODE title="New Code"] /if (${Spawn[=${MainAssist} pc].ID}) {
/tar id ${Spawn[=${MainAssist} pc].ID}
/delay 10 ${Target.ID}==${Spawn[=${MainAssist} pc].ID}
} else {

[/CODE]

I will make this change in the production copy as well.

Thank you!

This will probably turn out to be a good thing in the long run. Nothing screams "Hey, look at my 6-box bot team!" quite like having them named like that. Whatever the reason for the current suspension waves, making the team a bit less conspicuous wouldn't hurt.

It was more about file ini being in order for making mass copy and pastes. When you have a couple three dozen ini files to update at one time alphabetical was the easiest choice.