The Full XP Jonah Didn’t Earn, and What It Would Have Cost His Skill Tree

A focus quest should be settled by elapsed server time, not by a reflexive tap on “done.” LifeQuest uses the server-issued start time to determine whether a focus session earns full XP, so the record follows the time you actually spent in session.

A familiar button can hide an unfinished session

At 9:38 p.m., Jonah is in the back corner of a library in Lisbon, a cold coffee beside his laptop and three scratched-out calculus problems on his notebook. He started a LifeQuest focus quest for an hour of practice, then got pulled into a call from his sister and left his phone face down while he talked.

When he comes back, the screen is still there. So is the temptation: tap a completion box, take the reward, move on.

That reflex is familiar because most task lists treat completion as a declaration. You did it, you say you did it, the item disappears. That can be useful for errands and quick reminders. It says very little about a focused block of work, especially when the reward is meant to reflect the time the quest asked for.

Jonah knows he did not get the full hour. If LifeQuest counted only his final tap, he could turn an interrupted session into full XP. The immediate bad ending is smaller than a missed train or a lost deposit, but it still matters: his skill tree would record progress he had not actually earned, and the next rank would mean less to him.

Server time keeps the focus record honest

A LifeQuest focus session begins with a server-timed start. The countdown on the device helps you see where you are, but the server measures elapsed time independently. Leaving the app does not pause the session. Returning later can show how long you were away, rather than creating the comforting fiction that the clock stopped because the screen did.

For Jonah, that changes the finish line. He can finish the session, but the result depends on the recorded time, not how confidently he presses a button. Full XP comes from completing the required focus time. If the session falls short, self-report remains available for half XP.

That fallback matters. It gives people a way to acknowledge real work without forcing a false full-credit outcome. A half-XP self-report says, in effect: I made progress, but this was not the verified focus block I planned.

The distinction is part of LifeQuest’s evidence-weighted approach. Different quests can call for different kinds of evidence. A coding quest may qualify for GitHub verification. A workout can use a photo where appropriate. A focus quest has a form of proof already built into its structure: a start time and elapsed server time.

For a closer look at what happens when a session gets interrupted, read What Happens When You Forget the Timer but Finish the Work?.

The goal is a record you can trust later

The next morning, Jonah opens LifeQuest before class. His focus quest shows the result it actually earned. He does not have to reconstruct the evening from memory or wonder whether he gave himself credit for a session that drifted away.

That clarity becomes more valuable as quests stack up. XP, streaks, ranks, titles, and badges are more motivating when they point back to work you can recognize. The point is never to punish an interrupted evening. Life happens. The point is to keep “full XP” tied to the kind of completion the quest promised.

A generic checkbox makes every task look identical at the finish line. LifeQuest gives the finish line context. A self-report can recognize effort. A photo can support a visible result. GitHub can verify a qualifying push created after the quest. Server time can support a focus block.

Build focus quests around time you intend to protect

Before Jonah starts his next session, he makes the quest smaller: 30 minutes of problem sets, one topic, phone on silent. He starts it after he has cleared the things most likely to pull him away. The focus timer does not create concentration for him, but it makes the agreement concrete.

That is a useful way to treat any focus quest. Choose a duration you can realistically protect. Start when you are ready to work. If you leave, let the session reflect that. If you still made progress, record it honestly and keep going.

Full XP is more satisfying when the record behind it can answer a simple question: how did this quest actually get done?