Mastery Tracking
Progression System Guide
Learn how Avalanche Trivia measures mastery, keeps questions rotating, and blends inventory-based events into the climb from tile 0 to tile 100.
Question order that never stalls
- Each player receives a personalised question order stored in `questionProgress.order`. The list is randomised with Fisher-Yates whenever the set changes or the game starts fresh.
- When a player reaches the end of their list, `firstPassIndex` wraps back to zero automatically. There is no “all questions answered” dead-end—the client keeps cycling without host intervention.
- The active question pointer lives on the player document. If someone disconnects or refreshes, they rejoin right where the cycle left off.
Mastery-driven movement
- Every correct answer advances the climber by `totalPositions / totalQuestions` (default 100 ÷ question count). The movement engine tracks carry-over steps so danger zones can halt mid-jump and finish the remainder later.
- Unique correct answers are recorded in `questionProgress.correctlyAnsweredIds`. That list powers scoreboards and mastery logging while repeated clears still grant the reinforcement step forward.
- Movement strategy defaults to `fixed`, but hosts can store `movementStrategy: 'proportional'` on the player document for experiments where position equals mastery percentage exactly.
Inventory-aware events
- The Map & Compass event spawns between positions 1-15 and marks its tile in `eventFlags.mapCompassPos`. Solving the prompt stores the tool in `inventory.map_compass` for the rest of the match.
- Fork decisions reuse the same inventory data: carrying the Map & Compass unlocks a safe-path reveal or the sliding puzzle route instead of a blind coin flip.
- Tunnel shortcuts read from the same progression state, using a deficit-aware calculation so players who are behind receive the biggest jumps without overshooting tile 100.
Event synergy
Fork side quest outcomes
Missing the fork guess no longer means an instant penalty. The side quest tracks hermit quizzes, solo attempts, and sliding puzzle timers, then applies the resulting position delta while logging telemetry for the host feed.
Tunnel momentum
Up to three tunnel offers can appear between tiles 51-70 by default. Each success advances 8-24 spaces depending on the player’s deficit, while failures keep the normal question cadence intact.
Shield integration
Shield prompts continue to override the question view when an avalanche is pending. The countdowns reuse the updated timer cleanup logic so modals close reliably once the choice is made.
Best practices
For hosts
- Monitor the events feed for Map & Compass pickups and fork resolutions. Those entries confirm the inventory state without needing to open each player document.
- If you tweak question sets mid-series, remind players that their order re-randomises on the next sync—they should expect fresh sequencing after the update.
- Use voice or chat callouts when someone approaches tile 15, 40, or 55 so the group is ready for the Map & Compass, fork, or tunnel prompts as they appear.
For players
- Treat the Map & Compass question like a prerequisite—it makes the fork decision trivial and opens an alternate success path even after a wrong guess.
- When the question list loops, keep answering. Repeats still move you forward and provide extra chances to trigger tunnels or shield streaks.
- During fork side quests, focus on the timer at the top of the modal. If it expires, the stored outcome applies immediately (usually a -10 or -15 setback).