A fair, visible appointment cycle

Coordinate eligibility, applications, review, scheduling, publication, and later changes without losing the status of each applicant.

castle positions

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

9 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 guideIntermediateCastle Candidate Ranking and Schedule SuggestionsCastle Candidate Ranking and Schedule Suggestions The planner separates eligibility , ranking , and placement . A high score never makes an ineligible application eligible. An unresolved player cannot be placed. Suggestions never publish thMatched in: IntroductionCastle PositionsKings and Ministers of JusticeAlgorithm and decision logicAdvancedCastle Positions OverviewCoordinate eligibility, applications, review, scheduling, publication, and later changes without losing the status of each applicant. Castle Positions Overview Castle Positions coordinates player applications and a kingdom schedule. PlayersMatched in: IntroductionCastle PositionsPlayers and kingdom managersTask guideIntermediateCastle Position Applicant GuideCastle Position Applicant Guide Open the public Castle Positions link for the intended kingdom and application cycle. The form is available without a platform account and can be switched among the supported languages from the application paMatched in: IntroductionCastle PositionsPlayersTask guideIntermediateCastle Position Review WorkflowCastle Position Review Workflow Review turns submitted applications into a reliable candidate pool. Acceptance makes a player eligible for scheduling. It does not assign or publish a Castle Position.Matched in: IntroductionCastle PositionsKings, kingdom managers, and Ministers of JusticeTask guideIntermediatePlanning, Scheduling, and PublishingPlanning, Scheduling, and Publishing The scheduling workspace turns reviewed candidates into a dated Castle Position schedule. Select the correct kingdom, application cycle, and stage before moving anyone.Matched in: IntroductionCastle PositionsAuthorized kingdom managersTask guideIntermediateCastle Position Statuses, Changes, and NotificationsCastle Position Statuses, Changes, and Notifications Castle Positions has separate application and schedule states. Accepted describes an application; scheduled describes a placement; published describes the schedule version participants caMatched in: IntroductionCastle PositionsApplicants and managersTask guideIntermediate

Castle Positions Overview

Castle Positions coordinates player applications and a kingdom schedule. Players submit identity, stage availability, time choices, resources, and configured answers. Authorized kingdom managers review candidates, build a draft schedule, and publish the result participants can rely on.

Accessible summary: Applications move through review and draft planning; only publication creates the participant schedule and later change notices.

An accepted application is not a guaranteed assignment. A requested time is not confirmed until the published schedule contains the player. Suggestions do not appoint players automatically.

Start by perspective

• Players: apply and update an application.
• Kings, kingdom managers, and Ministers of Justice: review candidates, then plan and publish.
• Everyone: understand statuses and changes.

Core hierarchy

One kingdom instance contains stages. A stage represents a dated scheduling segment and contains supported castle positions and time slots. Applications record a player's choices for those stages. The planner places a candidate into one compatible slot and position, subject to the current stage configuration, conflicts, and locks.

Castle Positions lifecycle landmarks

The public application and manager planner show different parts of the same kingdom instance.

• Application-period state, kingdom identity, stage cards, availability and requested time.
• Candidate review pools with player identity, resources, preferences, conflicts, and review status.
• Planner stage selector, position columns, time rows, player cards, suggestions, and locks.
• Draft save, publish state, participant schedule, and changed-assignment notices.

Castle Positions is separate from event score tracking and KvK Prep. It may use player records and kingdom context, but publishing a schedule does not create an event result.

How the mechanisms relate

Application configuration establishes the active kingdom cycle, stages, positions, time slots, questions, and permitted resource choices. A player submits one application with identity, preferred time, availability, relevant resources, position choices, and required answers. An unlinked or uncertain identity can move the application to Needs Review; it must not be silently attached to a similar nickname.

Review separates eligibility from scheduling preference. An eligible candidate can still have no compatible time, lose a conflict, encounter a full row, or remain standby. The planner combines open grid capacity, compatible candidates, resource relevance, locks, current placements, and public-safe suggestion order. A manager decides whether to accept a suggestion or place manually. Whole-draft validation precedes publication.

Important states and common mistakes

Applications can be draft, submitted, needs review, eligible, rejected, scheduled, standby, or otherwise closed by the cycle. Schedules remain draft until publish validation succeeds. A published version is participant-facing and identifiable; a later change creates a controlled new version and notices rather than silently editing history.

Common mistakes are treating submission as appointment, changing an applicant's declared time to fill a row, assuming an unlinked name is the intended player, unlocking a deliberate placement before generating suggestions, or reading an old notice instead of the latest published version. Recover in the owning application or draft, not by creating a second cycle.

Worked example

Starting situation: Ana applies for a position, is eligible, and prefers the final time slot. That row is already full and all other times are incompatible. Rules: Eligibility does not override capacity or declared time compatibility. Branch: Ana remains standby. Output: The planner shows the gap between eligibility and placement; the published schedule does not include her. Next action: If a compatible place opens, a manager starts a controlled change, rechecks locks and conflicts, validates the draft, and publishes the next version.

Recommended reading order

Read Applicant Guide, Resources and Eligibility, Review Workflow, Candidate Ranking and Suggestions, Planning and Publishing, then Statuses and Changes. Use Castle Position Problems for recovery.

The system cannot see offline agreements, unsubmitted availability, or missing resource information. Human review remains responsible for exceptional context and fair communication.

New ways to prepare a schedule

• Local Castle Planner for Guests: fixed half-hour slots and a five-day resource scratchpad, without registration or shared records.
• Temporary Participants and Reviewed Players: include someone for one managed schedule, or approve a genuine roster identity.
• KvK Resources, Proof, and Points: understand supporting screenshots, retention, and day-specific estimates.

Choose the local helper for small tasks. For full assignments, applications, and history, register and work in the managed kingdom schedule with the appropriate access.