Entering Results Manually

Manual entry is best for a small number of verified results or a targeted correction. Use screenshot or spreadsheet import for a full leaderboard, but keep the same review discipline.

Before entry

Confirm the kingdom or alliance, event instance, event date, result mode, and stage. Search for the player before creating one. If the instance is locked, archived, or outside your assignment, the form can be unavailable even when you can read the event.

Enter a row

1. Open the dated event instance or Manual Input workflow.
2. Select the existing player in the correct scope.
3. Set participation and the score or stage fields supported by the event.
4. Compare the row with the source.
5. Choose the visible Save action and wait for success feedback.

A manual row writes directly to saved event data; it does not pass through screenshot recognition. Review before Save. For a cumulative event, enter the intended total. For a multi-stage event, select the intended stage. A same-player, same-event, same-date correction may update the effective result rather than create an independent duplicate.

Edit a saved result

Open the instance detail, record batch, player history, or import review that exposes the result. Change only the incorrect fields and save. If the source was an import, the corrected saved result can differ from the original extracted proposal while import history still records the source.

What happens next

The result appears in instance and player history. Eligible analytics and reward status recalculate from the current saved data. Reload those views after the save. A successful save does not publish a Castle Position schedule or modify an account profile.

Manual result entry landmarks

Verify context before choosing the player or entering values.

• Active kingdom or alliance and selected event instance with date.
• Player selector and event-specific participation, score, stage, or position controls.
• Existing-value or duplicate feedback when editing the same effective result.
• Save result and visible success or validation message.

If the player is missing, use Player Directory and Profiles. For a wrong saved value, see Reviewing Results and Event History.