Theme
Player or Alliance Member
Confirm your profile and scope; use personal analytics, events, rewards, applications, Knowledge Hub, and available Lab tools. Ask an alliance manager when a shared record needs correction.
Recommended sequence
- Sign in when the workflow requires it and confirm profile information.
- Select the correct kingdom or alliance scope.
- Open the page named in the current navigation.
- Review inputs and status before saving, submitting, accepting, or publishing.
- Verify the result in the destination view.
When to ask for help
Contact the community manager responsible for the current scope when information is missing or an action is unavailable. Contact platform support only after checking the account, scope, role assignment, feature availability, and visible error.
Related guides
Practical depth
Your recurring path
Keep the account linked, select the current community, enter results inside the active window, review personal history, follow Castle application statuses, and treat Lab outputs as planning assumptions rather than live records.
Your account may be linked to a player while an event result, reward decision, or Castle application remains managed by someone else. You can inspect the visible source and state, but do not create a second player or submission to hide a correction problem.
Worked example and limits
Starting situation: Your personal Analytics omits yesterday's event. Confirm the linked external player ID, active alliance, event and date filters, then open the visible event history. If no accepted result exists, ask the alliance result manager to inspect the source batch. If a result exists but remains outside your chosen boundary, change the filter. The output should be either a visible contributing row or a precise source correction request. Player access cannot override locks, edit another manager's batch, or guarantee premium features. Include the player, event, date, scope, and visible status when asking for help, never credentials.