LifeQuest focus sessions measure elapsed time on the server, so briefly locking your phone does not pause or erase the session. When you return, the displayed countdown is rebuilt from the server-issued start time rather than trusted to a fragile device-side counter.
Imagine Lena, a first-year engineering student in Manchester, studying at 9:18 p.m. with a cold mug of tea beside her keyboard. She had started a LifeQuest focus session for a Mind quest, then turned her phone face down to work through a stubborn set of calculus problems.
Twenty minutes later, her screen lit up with a message from her project partner. Lena unlocked the phone, replied, and locked it again before the temptation to scroll could take over.
Then doubt arrived. Had opening another app interrupted the timer? If the phone had suspended LifeQuest in the background, the session might finish short of the required duration. Full XP was on the line, along with the streak she had kept through a week of early lectures and late study sessions.
The timer continued somewhere the phone could not interrupt
Lena reopened LifeQuest with only a few minutes left. The timer had moved forward.
The app had not depended on a counter running continuously on her phone. LifeQuest had recorded the session start on the server. When Lena returned, the app calculated the display from that server-issued time, including the period when her phone was locked.
A note also made the behavior clear: she had been away, and nothing had paused.
That distinction matters because phones routinely suspend background activity. People lock screens, switch apps, answer calls, lose focus, or let battery-saving rules take over. A counter that lives only on the device can freeze, drift, or restart. It may show a clean number while recording an unreliable session.
LifeQuest uses elapsed server time for the XP decision. The countdown you see is a useful display, but the server provides the timing record that determines whether the focus session qualifies for full XP.
Server timing protects the meaning of full XP
A focus quest carries a simple claim: you committed a defined block of elapsed time to the task. The verification method should measure that claim directly.
Server timing does that without pretending to know more than it can. It cannot prove Lena understood every equation or resisted every distraction. It can verify that the session ran for the required elapsed time according to the server’s clock.
That boundary keeps the system honest. Full XP reflects the evidence available for the quest, not a claim of perfect concentration. If Lena leaves the app, the clock continues because real time continues. There is no hidden pause that turns a longer break into a shorter recorded session.
An abandoned session also cannot remain open forever. LifeQuest allows only one active focus session at a time, and an unfinished session clears after 12 hours. The focus screen states this plainly so the rule does not surprise someone returning later.
This approach follows the same principle behind LifeQuest’s other verification methods: choose evidence that genuinely fits the quest. A qualifying GitHub push can support a coding quest. An accepted camera photo can support a visible real-world result. Honest self-report remains available for half XP when objective proof is impractical. The half-XP option preserves progress without pretending every claim carries the same evidence.
Locking the screen does not pause the commitment
Lena watched the final minutes pass, finished the last problem she had planned to attempt, and submitted the focus session. The server confirmed enough elapsed time, so the quest earned full XP.
The useful lesson was larger than one completed quest. She no longer needed to keep her screen awake as if the glowing display itself proved she was studying. She could lock the phone, put it out of reach, and return when the work was done.
There is still an important caveat. Leaving the focus screen does not create a background service, and the optional focus music stops when the screen is gone. The timing record continues because it lives on the server; the audio does not follow you outside the screen.
That separation gives each part one clear job. The phone displays the session. The server measures elapsed time. Lena does the work.
For a related failure case, a premature zero can reveal why the visible countdown and the server’s timing record must remain distinct.
Put the phone down and let the evidence match the task
On her next study night, Lena started another Mind quest, checked the server-issued session had begun, and placed her phone inside her backpack. No screen stayed glowing beside the textbook. No anxious unlock was needed to keep a local counter alive.
Her practical routine became simple: start the session, note that leaving will not pause it, do the planned work, then return to finish. If the session ends too early, LifeQuest will not award full XP. If enough server-measured time has elapsed, a locked screen will not erase it.
At 10:07 p.m., Lena zipped the backpack shut and turned back to the next equation.
Comments
No comments yet.