• IS THIS SITE UGLY? Click "RG3" at the very bottom-left of this page to change it. To dismiss this notice, click the X --->

Problem - Kissassist Syntax Error - /DQuery

Joined
Aug 10, 2019
RedCents
90¢
Started getting a syntax error on my SK today.

When running Kissassist I am getting the following Syntax error over and over.

Syntax: /dquery <name> [-q <query>][-o <result>][-t <timeout>] --execute query on name and store return in result

It stops when I end KA or pause it. Anyone have this error before?
 
Joined
Mar 19, 2019
RedCents
604¢
Started getting a syntax error on my SK today.

When running Kissassist I am getting the following Syntax error over and over.

Syntax: /dquery <name> [-q <query>][-o <result>][-t <timeout>] --execute query on name and store return in result

It stops when I end KA or pause it. Anyone have this error before?
Is it connecting to your dannet group ok? Does actually affect anything?
 

ctaylor22

Moderator
Joined
Mar 21, 2014
RedCents
10,633¢
I have seen that error happen when the character trying to be queried is not in the all peers group. This was an issue in an earlier version of kiss when using the cure routine, but it was fixed. Make sure you have the latest kissassist.
 
Joined
Jul 22, 2018
RedCents
2,692¢
Had this last night on my warrior during a raid. The raid leader decided to split up my box group because reasons, so the War was grouped with non-boxed players. Didn't appear to have an impact on performance.
 

ctaylor22

Moderator
Joined
Mar 21, 2014
RedCents
10,633¢
No. The message won't hurt anything, just annoying spam. May have to add a few extra checks to get this to stop spamming.
 

ctaylor22

Moderator
Joined
Mar 21, 2014
RedCents
10,633¢
KissAssist assumes that your MainAssist is in the DanNet Peers[all] group. So I will have to add code to check if the MA is in the group or not.
 

ctaylor22

Moderator
Joined
Mar 21, 2014
RedCents
10,633¢
I think this should fix the issue. I added a check for the MainAssist in the Peers all group before using the /dquery command. Just replace the } else { line with the } else /if (${DanNet.Peers[all].Find[${MainAssist}|]}) {. The section of code in the CheckBuffs Routine is listed below

INI:
                    /if (${MainAssist.NotEqual[${Me}]}) {
                        /if (!${DanNetOn}) {
                            /if (${Ini["KissAssist_Buffs.ini",${Spawn[${MainAssistType} ${MainAssist}].ID},"Blockedbuffs"].Find[${BuffToCheck}]}) /continue
                            /if (${Ini["KissAssist_Buffs.ini",${Spawn[${MainAssistType} ${MainAssist}].ID},"Buffs"].Find[${BuffToCheck}]}) /continue
                        |} else {
                        } else /if (${DanNet.Peers[all].Find[${MainAssist}|]}) {
                            /dquery ${MainAssist} -q "Me.BlockedBuff[${BuffToCheck}].ID" -o DNout
                            /delay ${DanNetDelay} ${DanNet.Query.Received}
                            /if (${Bool[${DNout}]}) /continue
                            /dquery ${MainAssist} -q "Me.Buff[${BuffToCheck}].ID" -o DNout
                            /delay ${DanNetDelay} ${DanNet.Query.Received}
                            /if (${Bool[${DNout}]}) /continue
                        }
                    } else {
                        /if (${Me.BlockedBuff[${BuffToCheck}].ID}) /continue
                        /if (${Me.Buff[${BuffToCheck}].ID}) /continue
                    }
FYI, This still needs to be tested, but it should work fine.
 

ctaylor22

Moderator
Joined
Mar 21, 2014
RedCents
10,633¢
@sl968 reports that if there's a masterlooter set for the group, the message stops spamming
Would need a Debug log from @sl968 when the message is being spammed. To figure out exactly where in the code the /dquery is being used to generate the spam. From what I can see in the AssignLooter routine, only peers in the all group and checked and even then there is an additional check for the Peer to be a member of your group, before using the /dquery command. When you set LootOn=1 then that code gets bypassed.
 
Top