After editing an arcade, a successful save does not immediately tell a user how many experience points the contribution earned. Opening a profile to check adds another trip between the action and its reward. In Delta, we connected reward information to action responses so document edits and participation in fault information can show XP and level changes where the work finishes. This did not introduce new award rules.

Contribution results and experience points

Experience points, or XP, accumulate through participation; a level describes the user’s current stage in that progression. A save message confirms the document update but does not explain the awarded XP. Showing the reward alongside the completed action makes that relationship easier to follow.

The interface cannot calculate awards simply by counting button presses. Activities have different conditions, and the actual increase depends on server processing. For example, even when saving the same kind of edit, the screen needs the returned result before announcing a reward.

flowchart TD
    accTitle: Passing reward results to the interface
    accDescr: Pass reward information from the server’s action response to a shared interface handler.
    A["Document edits, reports, and other actions"] --> B
    B["Server processing and XP result"] --> C
    C["Reward feedback from response"]

Reward data in action responses

The response carries reward information in xp_feedback: previous and resulting XP, the increase, and previous and resulting levels. It also includes remaining XP and progress toward the next level, avoiding a separate calculation of those rules in the interface. Shared handling checks that the numeric values are valid before using them.

An XP notification appears only for a positive increase. Responses without an increase or without reward information produce no reward toast. Inferring a reward from the user’s action could disagree with the actual award, so a server-confirmed increase determines whether to display it.

flowchart TD
    accTitle: Conditions for displaying feedback
    accDescr: Validate reward numbers and show XP and level progress when the increase is positive.
    A["Validate reward data and numbers"] --> B
    B["Check for a positive XP increase"] --> C
    C["XP, level, and progress toast"]

XP and levels in a toast

A toast is a brief notice over the current screen. Its title shows XP gained and its description the current level. If the level changed, it shows the previous and new values as well. Remaining XP and progress toward the next level come from the response.

Successful document edits, fault reports and reactions use this shared handling. Authenticated attendance processing can also pass through reward results. Instead of duplicating calculations and wording in each feature, actions deliver their results to the same toast presentation.

Feedback and the reward record

Users can now see gained XP and their current level where they complete an action. A consistent presentation across features reduces the need to leave that screen to check rewards. The document-save result and XP result can each be understood.

A short notice can still be missed. Not seeing a toast does not mean no XP was awarded, and showing it again must not recalculate the reward. The server remains responsible for awarding and retaining the record; the toast communicates an already processed result.

Reference: XP feedback in action responses.