Theme
KvK 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 information.
Check whether resource proof is required
The application states whether Resource Proof is optional or required. If proof is disabled for the cycle, the upload section is not part of that application.
When required, upload at least one valid resource screenshot before submitting. The proof control accepts PNG images and allows up to five screenshots. Wait for the preview and Resource proof provided confirmation; choosing a file without a successful upload is not enough.
Crop out private chat, payment information, and unrelated account details before uploading. Resource screenshots are private review evidence, not public schedule illustrations.
Evidence has a limited lifetime
Resource proof expires according to the cycle's 14-day retention window, measured from creation of the Castle instance, not as a fresh 14 days for each later upload. An expired item shows that its screenshot has been removed. Keep your own appropriate records if you need them beyond that window, and ask the organizer how to proceed if required proof has expired.
Neither a screenshot nor its removal changes the amount of resources in your game. Proof helps a human reviewer assess a declaration; it does not automatically certify ownership or appoint the applicant.
Read the scoring reference by day
The Built-in KvK scoring registry presents Days 1 to 5 separately. Choose the relevant day, search for a resource, then open Why this formula? to read the source and verification context.
The reference is read-only. A resource can count on one day and not another, and a points rate may apply per item, per minute, per troop, or per progression score increase. Always read the unit alongside the rate.
Governor Gear and Charm progression are not simply a fixed number of points per material owned. Their supported scoring depends on the progression increase. A stockpile can therefore be useful without translating directly into a reliable point total.
Use estimates to discuss a plan
Example: An applicant declares general speedups and resource screenshots. The reviewer checks the appropriate preparation day and supported conversion, then compares availability and the requested time. The estimate informs review; it does not override a scheduling conflict or guarantee the final event score.
The Points view uses the selected kingdom context. Castle administration remembers a valid kingdom choice so returning to the planner should not require the same selection again. Still verify the displayed kingdom before making changes, especially after switching accounts or access.
For a private what-if budget with custom rates, use the local resource calculator. Its numbers do not update an application or the built-in scoring reference.