Event Templates, Instances, and Results

Kingshot Events separates a reusable event definition from each dated occurrence.

• An event template defines the name, category, duration pattern, score-entry mode, stages, participation support, analytics visibility, and reward behavior.
• An event instance is one scheduled occurrence with its date or session window, current status, scope, and saved results.
• A result connects a player to that instance with participation, score, stage, position, or other supported values.

Editing a template can affect future entry and interpretation. Correcting an instance or result changes that occurrence. Always confirm which level you opened before saving.

Complete event journey

1. Choose an existing template or create an approved custom event.
2. Create or open the correct dated instance in the active kingdom or alliance.
3. Confirm whether entry is a single score, cumulative total, multi-stage score, participation-only, or another supported mode.
4. Enter results manually or upload a screenshot.
5. Review player matches, date, stage, participation, and score.
6. Save or accept the verified rows.
7. Open instance detail, records, or player history to review the result.
8. Use Analytics and reward eligibility after recalculation.
9. Correct the source result or reviewed import when a value is wrong.

Status and scope

Instances can move through scheduled or active use into completed, archived, or deleted states according to the controls available to the viewer. A session lock can prevent further edits while managers review or publish a stable result set. Locked or archived records should be treated as read-only unless an authorized workflow explicitly reopens them.

Alliance events affect the selected alliance. Kingdom events can span eligible alliances. A viewer's ability to see an instance does not imply permission to edit its template or results.

Event workflow landmarks

Start with the event card or instance list, then follow the dated record into results.

• Event template name, category, duration, score-entry mode, stage behavior, and analytics or reward settings.
• Instance date or session, active kingdom or alliance, and status or lock indicator.
• Manual entry and screenshot import actions with review feedback.
• Instance detail, saved results, record history, analytics, and correction actions.

Continue with Participation and Score Events, Manual Entry, and Review and History.

A clearer event workspace

Event lists, sessions, manual entry, result batches, and proposal screens have refreshed layouts, icons, status presentation, and responsive controls. The purpose is to make the next action and current event context easier to recognize on large and small screens.

The workflow boundaries are unchanged: selecting a card does not submit results, editing a draft does not publish a decision, and a notification does not approve a proposal. Confirm the event, date, selected community, and visible status before saving or reviewing work.