A LifeQuest focus session uses elapsed server time as the source of truth for full XP. The countdown on your phone shows your progress, but changing the device clock, closing the screen, or leaving the app does not rewrite the time recorded by the server.
At 10:38 p.m., Theo sat at a scratched library desk with a chemistry workbook open beside a cold vending-machine coffee. The first-year student had one chapter left to review before a morning quiz, and he had started a 25-minute Mind quest to keep himself in the chair long enough to finish it.
With seven minutes showing, a message pulled him into another app. He answered, checked one more notification, then locked his phone. By the time he returned, the library was preparing to close. If those minutes had quietly paused, his session would remain unfinished, leaving him without the full-XP completion he expected and without enough time to restart before packing up.
The countdown shows progress, while the server records it
A device-side countdown can appear authoritative because it is the number directly in front of you. Yet a counter controlled entirely by the phone can become unreliable when the app moves into the background, the operating system limits activity, or the device clock changes.
LifeQuest starts a focus session on the server and records its start time there. The phone then displays a countdown derived from that server-issued timestamp. When you finish, the server calculates how much time has actually elapsed using its own clock.
That distinction matters because full XP represents a completed verification method. The reward should follow the recorded session, rather than whichever number the device happens to display after interruptions.
The visible timer still has a useful job. It tells you where you are in the session and helps turn “study chemistry” into a bounded block of work. The server has a different job: deciding whether enough elapsed time has passed to support full XP.
This separation follows the same principle described in LifeQuest Focus Sessions: How Server Time Protects Full XP From Phone Clock Changes. The interface guides the effort. The reward depends on the underlying record.
Leaving the screen does not create imaginary paused time
When Theo unlocked his phone, LifeQuest did not pretend the interruption had paused. The session showed how long he had been away, based on the same server start time.
That message changed his decision. He had enough elapsed time to finish the session, so he reopened his notes and used the remaining library minutes to check the questions he had marked earlier. The interruption remained part of the session. No hidden pause protected his streak, and no device-side counter erased the time that had passed.
This is an important constraint to understand before pressing start. A LifeQuest focus session measures elapsed time, not continuous attention. It cannot know whether you spent every second reading, writing, or staring through a window. The verification supports a narrower, honest claim: the server-timed block ran for the required duration.
That makes the timer useful without pretending it can inspect your intentions. If you need to leave for a reason that should not count, finish your current work before starting a session or begin a fresh one later. There is currently no cancel endpoint, and an abandoned session clears after 12 hours.
For a closer look at what happens when the screen locks, see Does Locking Your Phone Pause a LifeQuest Focus Session or Cost You Full XP?.
Full XP depends on the proof method you choose
A focus timer fits quests where elapsed time is meaningful: studying a chapter, drafting an essay, practicing a skill, or working through a set of problems. Other quests call for different evidence.
A coding quest may qualify for GitHub push verification. A visible real-world result may suit an in-app camera photo reviewed for plausibility. When objective proof is impractical, honest self-report remains available for half XP.
The choice matters because LifeQuest does not apply one generic completion checkbox to every kind of effort. You select a verification method that genuinely fits the quest. Form-coaching videos also stay separate from completion and XP, so feedback about exercise or craft technique cannot masquerade as evidence that a quest was completed.
Server timing follows the same boundary. It can verify elapsed time. It cannot verify perfect concentration, the quality of the work, or what happened outside the recorded session. Clear limits make the earned reward easier to trust.
Start the timer when the work starts
Theo closed his workbook with two minutes left before he needed to leave. The chapter had pencil marks in the margins, three corrected answers, and one question circled for the morning.
His phone displayed the completed focus session, and LifeQuest awarded full XP from the server-recorded elapsed time. The reward did not depend on keeping the app open or preserving a fragile local countdown.
For your next focus quest, make the start moment literal. Put the material in front of you, remove the obvious distraction, then start the session. Let the phone show the minutes. Let the server keep the record. When the timer finishes, leave one visible trace of the work behind: a solved problem, a paragraph drafted, or a page covered in notes.
Comments
No comments yet.