• 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 - TLO for target HPs, the number of, not the %

Rare Spawn

Well-known member
Joined
Oct 10, 2022
RedCents
3,282¢
Hello all, is there a TLO for the total HPs a target has? Is seems the default answer to these is "100"

${Target.MaxHPs}
${Target.CurrentHPs}

Thanks.
 
I don't believe that information is available to the client. We only get a percent
 
Any suggestions for logic to help decide if a target is worth long duration DOTs? Trying to figure our something to help skip 120 second long dots on trash that dies in 16 seconds.
 
Any suggestions for logic to help decide if a target is worth long duration DOTs? Trying to figure our something to help skip 120 second long dots on trash that dies in 16 seconds.
This is very much a play by ear situation. You could look for ${Target.Named} and try to only used it if the target is a named mob. Generally speaking everything I fight is 16 second trash mobs. But there is no easybutton for this situation because there just isn't enough information available. May just be a case of turning it off when you don't want it to do the thing. Then manually casting when you do, or turning it on if that's an option.
 
Keep a database of encounters and fight lengths. Then next time around, when you start the fight, you can check your notes and if the recorded fight is > than x time, then you know, "Hey I should use long-duration DOTs on this sucka!"
 
My end goal is to create a true/false condition for a KissAssist.ini. What I am thinking so far is something like this:

(!${Target.MyBuff[Name Of DOT].ID} && ${Target.PctHPs} > 70) && (${Target.ConColor.Equal[RED]} || ${Target.ConColor.Equal[YELLOW]} || ${Target.ConColor.Equal[WHITE]})

I wondering if the Target.ConColor checks can be further collapsed into something cleaner.... like (${Target.ConColor.Equal[RED|YELLOW|WHITE]}) but this does not work, I assume its looking for an exact match of "RED|YELLOW|WHITE" and not the intended function of "RED" or "YELLOW" or "WHITE". Is there way to fix that? My thinking is that querying the TLO Target.ConColor once, instead of 3 times, would be cleaner and less work.
 
My end goal is to create a true/false condition for a KissAssist.ini. What I am thinking so far is something like this:

(!${Target.MyBuff[Name Of DOT].ID} && ${Target.PctHPs} > 70) && (${Target.ConColor.Equal[RED]} || ${Target.ConColor.Equal[YELLOW]} || ${Target.ConColor.Equal[WHITE]})

I wondering if the Target.ConColor checks can be further collapsed into something cleaner.... like (${Target.ConColor.Equal[RED|YELLOW|WHITE]}) but this does not work, I assume its looking for an exact match of "RED|YELLOW|WHITE" and not the intended function of "RED" or "YELLOW" or "WHITE". Is there way to fix that? My thinking is that querying the TLO Target.ConColor once, instead of 3 times, would be cleaner and less work.
${Select[${Target.ConColor},RED,YELLOW,WHITE]}
 
Question - TLO for target HPs, the number of, not the %

Users who are viewing this thread

Back
Top
Cart