Başar BallıözProduct Engineer
← All posts

Quest pacing: measuring where a 150-level game goes flat

Tibblo's road from level 1 to 150 is about 763 days of play. Making sure a player always has a quest was the easy half. The hard half was making them want to know what happens next. Here is how I measured where the story stopped pulling, and what changed.

By Başar Ballıöz · · 4 min read

Always a quest is not the same as a story

The first round of quest work made one promise: from level 1 to 150, the quest tracker is never empty. A test walks a pet through every level and fails if there is a single moment without a quest. That worked. But a tracker that always says "Play 3 games" is not a reason to come back.

So the second question was: how long does a player wait between two moments where the story moves?

Measure in days, not levels

Levels are the wrong unit. Level 10 to 11 takes a few hours; level 140 to 141 takes days. The game's balance file already says how many engaged days (days a player actually plays) each level takes, so I put the story steps on that timeline:

ChapterLevelsDaysStory stepsDays per stepLongest gap
1 The Bay1–2025122.04.1
2 Whisperwood20–4054114.96.9
3 Frostpeak38–608098.813.9
4 Sunsand Isles59–901491410.613.9
5 Cloudtop88–1202001711.814.0
6 Crystal Deep118–150256318.38.8

The table made the problem obvious. In the first two chapters the story moves every two to five days. From chapter 3 on, a player can go two weeks between story moments, and the chapters are long.

Why the middle went flat

Looking at what filled those two weeks gave four reasons:

  1. Region tasks were single, unconnected chores. 74 templates, the same set in every region under a new name, with no daily limit. A keen player saw each one again within a day or two.
  2. The neighbours left the story at level 40. The six friends from the starting town finished their quests between levels 23 and 39. After that, the town you started in went quiet.
  3. Nothing pulled you back after a break. A child returning after three days saw a tracker line, not where the story was.
  4. Chapter 1 had no face. Its quests came from a notice board; the first character with a voice appeared at level 21.

Five small phases

Each phase shipped on its own, kept old saves working and stayed inside the XP plan (quests give about 110 XP a day, so levelling speed does not change):

  • The neighbours come along. Each of the six friends gets one quest in every later region, tied to who they are: the baker wants a mountain cocoa recipe, the robot builder's sensors pick up crystals in the Deep. 24 quests, levels 42 to 148.
  • Small stories between the big steps. The 74 single chores became 48 three-step arcs, eight per region giver, each with a beginning, a middle and an end: look for the lost mitten, follow the tracks, give it back. The tracker shows "Step 2/3", and the last step has its own thanks line. Each pet draws arcs in its own order from a seed, with no repeat until the pool is used.
  • Three a day. After the third region task, the giver says "Come back tomorrow" and the tracker points at the next story step and its level. A full day of tasks pays at most 84 XP, under the quest share, and a test checks it.
  • "Last time…" and "Next…". After two days or more away, the room opens with a small card: the last story step and its thanks line, then the next step's title and level. Once per return, never over a sheet or the tutorial.
  • A face for chapter 1. A neighbour called Max now gives the notice board's quests and waits beside it while it has one. He later builds the mountain pass, so the face from chapter 1 opens the road to the first far region.

Old saves still load

A quest id in a save looks like task:<template>:<n>:<level>. The old single-task templates stay in the code only so those ids still parse and can be handed in; the next task a player gets starts an arc. No new save fields were needed. (How Tibblo keeps every old save loading is its own post: save file versioning.)

Tests that guard the pacing

  • The walk from level 1 to 150 is never without a quest and finishes the whole story.
  • Every story gap stays within its limit in engaged days.
  • Every neighbour has a quest open in every chapter.
  • Arcs run in order; two pets get different orders; nothing repeats inside the pool.
  • Days per level stay near the balance plan.
  • The "Last time…" card shows after two days but not after one, and fits the screen in English and Turkish.

One more test caught a real bug on the way: the map and the walkable town both show where Max stands, and a first version only moved him in the town. A test that checks "the map and the town agree" failed before any player saw it.

What I would reuse

  1. Put story moments on a timeline of real play days. Levels hide the gaps.
  2. Turn chores into short arcs. Three steps with an ending feel like a story; three unrelated tasks feel like a list.
  3. Cap the filler, point at the story. "Come back tomorrow" is better than the same chore again.
  4. Greet the returning player. One line of "where we were" does more than any reward.

More posts

Godot on iOS: from an uneven 60 fps to 120 Hz with MetalA Godot 4 game stuck near 60 fps on an iPhone 14 Pro with a main thread busy only 4 ms a frame. How a phone bench and Instruments found the cause, and how switching iOS to Metal gave 119 fps. Smooth scrolling in Godot when every card's art is drawn from codeA Godot 4 tray of 230 cards with art drawn from code stuttered on every scroll. How a picture cache, a limit of two new pictures a frame and drawing only cards near the view made it smooth.