EQL Source / Tools / Lockout tracker
Lockout tracker.
Every other tracker here tells you what you have done. This one tells you what is still open — which is the question you have at the start of an evening. It reads your own combat log, in the browser. Nothing is uploaded; there is no server to upload to.
Reads your logYour log never leavesNo install
All “not looked”?
Start with the log. The game writes one only when asked:
/log on begins it. Anything earlier is invisible, which is what the
grid is telling you.
It says “not looked” rather than guessing
This is why it is promoted here, and it is a correctness property rather than a feature.
A cell it has no history for reads not looked. It does not read open. The two are different claims and only one of them is true: an empty log says nothing about whether a boss is available, and the guess that looks most useful is wrong in the one direction that costs you a night.
The same discipline runs through the rest of it. It will only report a lockout as refused where a positive control is present in the log to prove a refusal would have been visible; otherwise it degrades to unknown rather than inventing a lock. And repeat kills of one boss at one tier are recorded but never counted twice — a kill proves the fight happened, not that a second completion was consumed.
514e9ebb, read 2026-09-04.Three timers, and it refuses to merge them
Most of what is said about lockouts in this game is one of these three mistaken for another.
- Weekly taskTurns over on a Tuesday, and this is the only weekday
anywhere in the model. It governs the weekly task and its Void-Touched
Potential token — not instance loot.stated, not measured
The hour is not recorded, so on the turnover day itself the tool evaluates both
possibilities and marks the cells that disagree
unknown. - Instance lockoutA rolling timer. No weekday, no boundary, and not a weekly reset. This is the one people describe as resetting on Tuesday, and it does not.rolling
- Replay timerAlso rolling, about an hour, and it governs re-entry rather than loot. The tool records it so it can be kept out of the lockout cells; it is the likely origin of the community “rolling 18 hours” claim.re-entry only
What is measured, and what only follows from it
The distinction is the whole subtlety, and it is easy to state one as the other.
The measured figure is a difference, not a duration. Between the replay timer and the boss timer there are exactly 5 days 23 hours — 514,800 seconds. It is arrived at by subtracting one from the other, and the subtraction cancels how long ago the lock was taken, which is why it holds whatever that elapsed time was. That is the part that does not depend on an assumption.
A 6-day lockout is what follows if the replay
period is exactly one hour. The tool marks that figure conditional and
names the condition, rather than publishing it as a measurement. This page does the same:
it is a reasonable reading, it is not a thing anyone has timed, and the difference between
those two sentences is the reason this site exists.
Every figure carries where it came from
Nothing leaves the module as a bare number. Each value carries its own
provenance — observed, inferred, or not recorded — and the labels are
attached per figure rather than per object, so a measured quantity and an assumed
one sitting in the same record do not inherit one another's standing. The difference above
is marked observed and the period beside it conditional,
in the same constant.
That is the rule this site had to learn the expensive way, on the Plane of Sky dataset, where one verified flag covered thirty-odd claims read from different pages on different days. It was reached here independently, in another repository, and it is the strongest single reason to trust the output.