After contributing, a user needs to know what changed in their experience points. Musecat added response-based XP and level toasts on June 27, followed by a level-up modal on July 4. The August improvement extends that immediate feedback into guidance about future goals and ways to participate.

XP feedback and future goals

An immediate toast explains a reward just earned, but says less about what comes next. For example, a contributor may want to know when profile features or a supporter application become relevant. An experience total alone cannot explain those conditions.

flowchart TD
    accTitle: Immediate rewards and progression guidance
    accDescr: Immediate rewards and longer-term goals use separate guidance.
    A["XP change in an action response"] --> B
    B["Level-up feedback"] --> C
    C["Next goals and contribution guide"]

Document edits, photos, fault information, attendance and visits happen across different screens. Scattered participation and reward information makes goals harder to find. A progression guide provides somewhere to review progress and available activities alongside immediate feedback.

A policy table explaining XP by activity and when another reward becomes available. Original English capture.

Level progress and feature guidance

The progression view calculates the current level and next goal from experience points, displaying remaining XP and progress. Milestones link to relevant features such as profile backgrounds and supporter applications. It also handles reaching a point with no further goal.

flowchart TD
    accTitle: Calculating the next goal
    accDescr: Calculate the level and next target from current XP, then show remaining experience.
    A["Current experience"] --> B
    B["Calculate level and next goal"] --> C
    C["Progress and remaining XP"]

Showing a milestone does not itself authorize an application. Supporter applications check existing supporter status and the eligibility and application state returned by the server. Progression provides guidance; the feature still applies its own conditions.

When a contribution raises the level, the dialog shows the previous and next levels and progress. Original English capture.

Reward conditions and metric rankings

The guide gathers XP-earning activities and their conditions. The server determines whether an activity has already been recognized and what reward is actually issued; browser copy is not the authority for payment.

flowchart TD
    accTitle: Growth and participation metrics
    accDescr: Personal progress and relative rank answer different questions.
    A["Recorded contributions"] --> B
    B["Level progression and metric aggregates"] --> C
    C["Personal goals and rankings"]

Rankings are provided by measures such as level and visits. Long-term accumulation and activity within a period answer different questions. Users can see their own position as well as leading entries, with the selected metric supplying the meaning of the comparison.

Using progression and reviewing contributions

Rewards, future goals and participation options become easier to follow together. Levels describe personal progression, while rankings describe relative positions within a chosen measure. Different activities need not become a single competition simply because they award XP.

Neither measure proves the accuracy of an individual edit. Reward processing prevents duplicate awards; change history, review and restoration address incorrect content. Progression feedback supports participation without replacing that review.

Related articles and sources: Level progression and supporter guide implementation

Related updates

• 2026 H1 Initial Supporter Applications End