Question - View Lockout Timers

[Jetanroth]

Is there a way to view your toons lockout timers anywhere?

 

[Sic]

/tasktimers


I also check alt-z window for places like Fan the Flames as that actually has a loot lockout timer as well - and you can end up doing the mission and not get loot because your loot timer wasn't back

 

[tarquinn]

Alt+Z pulls up expedition window with lockouts as well

 

[zuesizgod]

/taskt if you wanna shorten it. I also have it hotkeyed

 

[Jetanroth]

Fantastic, thank you!

 

[Rare Spawn]

Is there a TLO for this? Not to be confused with the amount of time remaining on an active task, which I believe is all we have here: https://www.redguides.com/docs/projects/macroquest/reference/data-types/datatype-task/

 

[wired420]

Is there a TLO for this? Not to be confused with the amount of time remaining on an active task, which I believe is all we have here: https://www.redguides.com/docs/projects/macroquest/reference/data-types/datatype-task/

Yeah its in here https://www.redguides.com/docs/projects/macroquest/reference/data-types/datatype-dynamiczone/

 

[Rare Spawn]

Yeah its in here https://www.redguides.com/docs/projects/macroquest/reference/data-types/datatype-dynamiczone/

Thanks Wired!

 

[Rare Spawn]

Does not seem to be working as intended. Mission cooldowns visible with /taskt do not show up for completed missions in the TLO .

/taskt confirms i have one timer with hours left cooldown.
${DynamicZone.MaxTimers} has a value of 0.
Also searching for the timer by name returns NULL.

Perhaps related, the inactive missions on cooldown do not show in the EQ expedition window either, only the /taskt command, to my knowledge

Has someone else gotten this to work for missions (not raids)? There's a good chance my problem is between the chair and the keyboard, so asking for a 2nd set of eyes.

 

[ChatWithThisName]

Taskt is 100% text based. No other way to get the information that I'm aware of. To my knowledge the information is stored serverside and doing a /taskt requests the results and therefore it isn't locally accessible.

If you're willing to look at some old code I did I had parsed it at one point. But it's been a while and the results of these may no longer be accurate as it done in MQ2 times.

#Event TaskTimer "'#1#' replay timer: #2#d:#3#h:#4#m remaining."
#Event TaskTimer2 "You may not request this shared task because you must wait #1#d:#2#h:#3#m before you can do another task of this type."

Sub Event_TaskTimer(string line, string taskname, string days, string hours, string mins)
    |/echo TaskTimer: ${taskname} - ${days}d - ${hours}h - ${mins}m Timer: ${Math.Calc[${Math.Calc[${hours}*6000]}+${Math.Calc[${mins}*100]}].Int}
    /if (!${Defined[${taskname}timer]}) {
        /declare "${taskname}timer" timer outer ${Math.Calc[${Math.Calc[${hours}*36000]}+${Math.Calc[${mins}*600]}+600].Int}
    } else {
        /varset "${taskname}timer" ${Math.Calc[${Math.Calc[${hours}*36000]}+${Math.Calc[${mins}*600]}+600].Int}
    }
/return

Sub Event_TaskTimer2(string line, string days, string hours, string mins)
    |/echo TaskTimer2 ${TaskGetName} - ${days}d - ${hours}h - ${mins}m Timer: ${Math.Calc[${Math.Calc[${hours}*6000]}+${Math.Calc[${mins}*100]}].Int}
    /if (!${Defined[${TaskGetName}timer]}) {
        /declare "${TaskGetName}timer" timer outer ${Math.Calc[${Math.Calc[${hours}*36000]}+${Math.Calc[${mins}*600]}+600].Int}
    } else {
        /varset "${TaskGetName}timer" ${Math.Calc[${Math.Calc[${hours}*36000]}+${Math.Calc[${mins}*600]}+600].Int}
    }
    /varset GetMissionFailed TRUE
    /echo NewTimer: ${${TaskGetName}timer}
/return

These required a /doevents for each task there was a result for. This required you know how many different tasks you planned to do, otherwise there was no way for them all to be parsed. The logic will need to be altered to suit your situation/uses.