A LifeQuest focus quest earns full XP from elapsed server time. Changing the clock on a phone cannot create extra minutes because the server records when the session starts and decides how much time has passed.
At 11:42 p.m. in a quiet apartment near Glasgow, Eli has one section left in a portfolio project due the next morning. His coffee has gone cold, his phone is at 9 percent, and the unfinished page still holds three placeholder images.
Eli creates a Craft quest, chooses a focus session, and starts the timer. If he quits early, the portfolio stays incomplete. If his phone dies before he understands what LifeQuest is measuring, he may assume the session disappears with it.
This is an illustrative scene, but the mechanics are real. The timestamp that matters has already left Eli’s phone.
The session begins with a server-issued time
When Eli taps Start, LifeQuest creates a focus session on the server. The server issues the session’s `started_at` time, and the countdown shown on his screen is derived from that value.
The number on the phone helps Eli see where he is in the session. It does not control the evidence.
That distinction matters because a device-side timer lives in an environment the device owner can change. A phone clock can jump forward. An app can move into the background. The operating system can suspend work to save battery. If XP depended on a local counter alone, the counter would be carrying more trust than it deserved.
LifeQuest keeps the source of elapsed time on the server instead. Eli can set his phone clock to tomorrow, but the server has not traveled with it. Ten real minutes still count as ten real minutes.
The idea is simple: put the measurement closest to the fact it needs to establish. The same lesson appears in the pound-seconds mistake that lost a Mars orbiter. A measurement only helps when everyone agrees what produced it and what it means.
Leaving the screen does not pause reality
At 11:55 p.m., Eli’s battery warning appears. He plugs in the phone across the room and returns to his laptop. The screen locks while he replaces the placeholders, checks the mobile layout, and fixes a heading that wraps badly.
The focus session continues.
LifeQuest does not pretend the timer paused when Eli stopped looking at it. When he returns, the app can show how long he was away because the displayed countdown still traces back to the server-issued start time. The server remains the authority when the session is finished.
That creates an honest boundary. LifeQuest can establish that the timed interval elapsed. It cannot see every thought Eli had during it, and it does not claim to. He could stare at the wall for part of the session. A server-timed focus quest provides stronger evidence than tapping a generic completion checkbox, while stopping short of surveillance.
There is another edge case worth saying plainly: only one focus session can run at a time. An abandoned session has no cancel control yet and clears after 12 hours. Those constraints keep the mechanic understandable, even when the session goes wrong.
For a closer look at what the app communicates after someone leaves the screen, see the away-time message LifeQuest shows.
Full XP arrives after the server checks elapsed time
Just after midnight, Eli opens LifeQuest again. The portfolio now has real project images, the final heading sits correctly, and the submission page is ready.
He finishes the focus session.
This is the moment when the outcome is still uncertain. If the required interval has not elapsed according to the server, changing the phone clock cannot rescue it. Finishing too early will not manufacture full XP, even if the display was altered locally.
The server compares its own timing information, then accepts or rejects the completion. When the elapsed time qualifies, LifeQuest awards full XP and records the focus timer as the verification method. The celebration sting can play for that verified completion if Eli has music enabled.
The XP reflects the evidence available for this kind of quest. A photo might show a finished page, but it cannot establish a sustained work interval. A GitHub push may fit a coding quest, yet it does not fit every study or creative task. Self-report remains available for half XP when objective proof is impractical. Focus timing earns full XP because it matches the claim being made: a defined period passed after the quest session began.
Build the quest around what can be established
The useful question comes before pressing Start: what would count as honest evidence for this particular task?
Choose focus timing when the commitment itself is a period of concentrated work. Set a quest such as “Work on the portfolio for 25 minutes,” rather than “Finish my entire portfolio.” The first promise matches what the timer can establish. The second depends on a result the timer cannot inspect.
Eli’s phone is still charging across the room when he submits the portfolio. LifeQuest did not certify the quality of every image or prove that distraction never entered his head. It recorded something narrower and defensible: the session began on the server, enough real time elapsed, and the completion earned full XP without trusting the phone’s clock.
Comments
No comments yet.