Troubleshooting

Start with what you see

A useful diagnosis names the symptom, identifies the current identity and scope, traces the owning source record, and chooses a recovery path that preserves history.

troubleshooting

Search tasks, concepts, states, and troubleshooting

I need to...

Search Kingshot Events documentation

Add or update a playerLink a game profileRecord event resultsImport a screenshotCorrect imported rowsReview analyticsConfigure reward rulesApply for a Castle PositionReview applicantsBuild and publish a scheduleRead a scoped articleCreate and publish an articleCreate a Reading Verification sessionUse a saved Lab profileOptimize Hero GearConfigure a Bear Trap rallyUnderstand premium accessRestore deleted information

Product areaAll product areasCastle PositionsSimulations and OptimizationsSubscriptions and UsageGetting StartedAccounts and AccessScopes and CommunitiesPlayersEvents and ResultsImports and Data EntryAnalytics and RewardsKnowledge HubTroubleshootingRole JourneysPlatform LifecyclesOverviewUpdatesRole or audienceAll rolesPlayer or memberAlliance leaderKingdom managerMinister of JusticeKnowledge author or reviewerReading-session managerContent typeAll content typesOverviewHow it worksTask guideAlgorithm and decision logicStatus referenceTroubleshootingRole journeyExperience levelAll levelsBeginnerIntermediateAdvanced

12 highest-relevance guides shown

Local Castle Planner for GuestsLocal Castle Planner for Guests The Local Castle Planner is a browser-only scratchpad for Guests and signed-in users. It is useful for a small personal schedule that does not need applications, account roles, or an official published versioMatched in: IntroductionCastle PositionsGuests and signed-in plannersTask guideIntermediateTemporary Participants and Reviewed PlayersTemporary Participants and Reviewed Players You do not need to build a complete roster before arranging every appointment. The managed Castle planner can include a temporary participant : a named person attached to this schedule, without crMatched in: IntroductionCastle PositionsCastle organizers and reviewersTask guideIntermediateKvK Resources, Proof, and PointsKvK Resources, Proof, and Points KvK appointment planning is easier when declared resources have context. Castle applications can collect resource amounts and supporting screenshots, while reviewers can inspect day-specific scoring informatMatched in: IntroductionCastle PositionsKvK applicants and Castle reviewersTask guideIntermediateAscension Path: Plan Your Next UpgradesAscension Path: Plan Your Next Upgrades Ascension Path compares Hero Gear, Governor Gear, and Charms in one progression workspace. It recommends an ordered path under the nine separate material balances in your selected account profile or tMatched in: IntroductionSimulations and OptimizationsPlayers planning account progressionAlgorithm and decision logicIntermediateImport Your Lab Build from ScreenshotsImport Your Lab Build from Screenshots Screenshot import can shorten the work of entering a build, but the review step is what makes it useful. The tool proposes recognized values; you decide which ones accurately describe your account. ThiMatched in: IntroductionSimulations and OptimizationsLab users entering or updating a buildAlgorithm and decision logicIntermediateFree and Premium Personal PlansFree and Premium Personal Plans Every registered account starts on Free . A personal paid plan, such as Premium , adds the benefits listed for that account. It is separate from a kingdom or alliance subscription.Matched in: IntroductionSubscriptions and UsageRegistered account holdersHow it worksIntermediateGetting StartedGetting Started Kingshot Events is scope-aware. A useful first session therefore confirms who you are, which game player record is linked to you, and which kingdom or alliance is active before opening data-entry or management tools.Matched in: IntroductionGetting StartedNew usersTask guideAdvancedAccounts and AccessAccounts and Access The platform does not decide access from a single role label. It combines account state, active scope, assignment or membership, stacked roles, feature availability, and any accepted subscription grant.Matched in: IntroductionAccounts and AccessAll signed-in usersHow it worksAdvancedScopes and CommunitiesScopes and Communities Scopes keep one kingdom or alliance from accidentally reading or changing another community's records. The active scope is a working context, not a new permission.Matched in: IntroductionScopes and CommunitiesMembers and community managersHow it worksAdvancedPlayersPlayers Player documentation separates the platform account, the alliance-local player record, and the linked game profile so that synchronization and lifecycle actions are predictable.Matched in: IntroductionPlayersPlayers and roster managersHow it worksAdvancedEvents and ResultsEvents and Results An event name describes a configured kind of activity. An event instance describes one occurrence in a scope. Results and record batches provide the player evidence attached to that occurrence.Matched in: IntroductionEvents and ResultsContributors and event reviewersHow it worksAdvancedImports and Data EntryImports and Data Entry Imports accelerate transcription, but extracted text is not authoritative. Event context, normalization, matching, duplicate checks, and review turn a file into eligible product records.Matched in: IntroductionImports and Data EntryContributors and import reviewersTask guideAdvanced

Safe diagnostic order

Troubleshooting decision path. Access checks precede data changes; correction occurs in the workflow that owns the information.

Accessible summary: Record the symptom, verify identity and scope, check access conditions, inspect source and state, then use a safe recovery or contact an authorized manager with evidence.

Find the symptom

What you see	What it usually means	Start here
A page or action is missing	Scope, assignment, feature availability, effective plan, or quota does not qualify	Access problems
Player missing, wrong name, or duplicate governor	Filter, alliance context, sync precedence, soft deletion, or ambiguous identity	Data and save problems
Same date, locked event, or result appears twice	Event-instance identity, duplicate result, batch overlap, or correction state	Event problems
Duplicate screenshot, unmatched name, or partial extraction	Reconciliation row requires review or the batch already exists	Import problems
Reward not eligible or Analytics is empty	Source record, eligibility, filters, date boundary, scope, or recalculation	Analytics sharing and troubleshooting
Castle standby, full row, or planner conflict	Candidate eligibility, time compatibility, lock, capacity, or draft state	Castle Position problems
Reading code fails or article is locked	Session applicability, assignment state, article access, or editorial state	Knowledge problems
Profile autosave is pending or optimizer result surprises you	Save state, profile switch, incomplete inputs, constraints, or model limits	Simulator problems
Grant quota or limited mode appears	Grant acceptance, allocation, effective plan, usage warning, or exhausted quota	Subscription troubleshooting

Worked example: Analytics is empty

Starting situation: An alliance leader opens Alliance Analytics and sees no rows after results were imported. Safe checks: She records the selected alliance, event, and date range; confirms the import rows were applied rather than merely accepted; opens event history; and checks that the results belong to the same alliance and boundary. Branch: The batch is still in reviewed state and was never applied. Recovery: She returns to the authorized import workflow, applies eligible rows, then reloads Analytics. Output: Totals appear after normal recalculation. Reason: Reviewed import proposals are not Analytics inputs until application creates the supported result records.

When to contact an authorized manager

Escalate when the recovery action requires a role you do not hold, a lock or immutable published state prevents the change, a restore request needs review, or the visible result remains inconsistent after the source and filters are verified. Include the page title, approximate time, active scope, event or record name, relevant date, visible status, exact error wording, safe screenshot with private information removed, expected outcome, and checks already performed. Never include passwords, security tokens, private endpoints, or internal recovery details.

Recovery principles

Correct a result in its event or record batch, a player in its profile and lifecycle, a schedule in its draft and publication workflow, an article through a new revision, and a Lab result by fixing the saved profile and rerunning. Avoid duplicate records as a workaround. Restore only through visible authorized recovery. Treat published revisions, closed sessions, locks, and applied batches according to their stated mutability rather than assuming every state can be edited in place.