Castle 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 page.

Submit a new application

1. Confirm the kingdom and alliance. If your alliance is not listed, use the visible unlisted-alliance option and enter the requested label.
2. Identify the governor. A signed-in linked player may be suggested, while a guest provides the required public identity details.
3. Enter the requested resources and custom answers. True Gold is entered and displayed as an item count, while configured speedup resources can use effective days.
4. Upload resource proof when the cycle marks it required. Wait for the upload to finish.
5. For every stage, choose Not available, Any available time, or a specific UTC time.
6. Review identity, resources, proof, answers, and every stage choice.
7. Submit once and keep the confirmation details.

The form shows step errors after you attempt to continue. It does not leave the time step until every stage has a valid choice.

An occupied time is not automatically available. Where the cycle permits it, choose the request action and add a useful note for the reviewer. The request remains provisional until leadership resolves it.

Keep the guest secret access code

A guest submission can return a Guest Secret Access Code. Copy and store it privately. The browser also remembers the code for convenience, but browser storage is not a reliable backup.

The code reopens that exact application from the public Castle page. Treat it like a secret link: anyone with it may be able to view or edit the associated application while changes are allowed.

An ordinary new-application link does not silently open a remembered application. Enter the code or use the exact edit link when you intend to return to an existing record.

Edit one application or create another

Use Edit application from the confirmation or return with the exact application link or guest code. An edit updates that application; it does not create a duplicate.

When the cycle permits multiple applications, Create another application starts from step one with a clean identity and form. It deliberately ignores the previous draft and guest key so the earlier application is not overwritten.

Do not use create-another mode merely to correct a time or resource amount. Edit the intended application instead. If the system detects a duplicate, the review team decides whether to use the latest submission or keep the existing one.

Repeated clicks while a submission is already in progress are suppressed. Wait for the result before trying again.

Understand status and leadership changes

• Submitted or Updated: received and ready for review;
• Needs review, Under review, or Standby: identity, eligibility, or another detail needs attention;
• Accepted: eligible for scheduling, but not guaranteed a slot;
• Rejected: not included unless leadership reopens and reviews it again.

Leadership can correct an application record after checking the source evidence. The applicant status view identifies an adjusted record, shows the note and changed fields, and preserves the original submission for comparison.

Requested times are not appointments. A slot becomes authoritative only when it appears in the published schedule.

Proof and privacy

Proof screenshots have limited retention and are not public schedule images. Upload only the requested evidence. Do not include passwords, unrelated conversations, or unnecessary personal information.

See KvK Resources, Proof, and Points for proof rules, Statuses and Changes for application and publication states, and Local Castle Planner for a browser-only personal schedule.