There are two variables in KissAssist that are set with /noparse
These two variables are used in many places throughout Kiss... but they are only /varset this one time, and this section of the code is only read on initialization. From the looks of it, it seems that the /noparse command seems to set the variable and it is somehow continuously updated per the logic in the line.
Is that correct? I can't seem to find a longer explanation of the /noparse command that illuminates the issue.
Thanks!
JJB
Rich (BB code):
/noparse /varset AggroTargetID ${If[${Me.XTarget[${XTSlot}].ID},${Me.XTarget[${XTSlot}].ID},${If[${AggroTargetID2},${AggroTargetID2},0]}]}
/noparse /varset PullAggroTargetID ${If[${ChainPull}==0,${Me.XTarget[${XTSlot}].ID},${If[${Me.XTarget[${XTSlot}].ID} && (${Me.XTarget[${XTSlot}].ID}==${MyTargetID} || ${Me.XTarget[${XTSlot}].ID}!=${BeginMobID} || ${Me.XTarget[${XTSlot2}].ID}),${MyTargetID},0]}]}
These two variables are used in many places throughout Kiss... but they are only /varset this one time, and this section of the code is only read on initialization. From the looks of it, it seems that the /noparse command seems to set the variable and it is somehow continuously updated per the logic in the line.
Is that correct? I can't seem to find a longer explanation of the /noparse command that illuminates the issue.
Thanks!
JJB