What Runekist does
Runekist turns collected Total Battle reward chests, gifts, and clan operational records into a shared clan operating record.
Depending on your clan’s setup, Runekist can help you:
- follow period standings and personal progress;
- apply point and requirement rules consistently;
- identify members below requirements;
- review reward chest types, activity, Ancient Summons, and clan resources;
- resolve player-name and identity mismatches;
- manage Rules, announcements, calendars, Polls, and Questionnaires;
- assess and track fines;
- export records and receive alerts;
- ask the Runekist Assistant questions about clan data.
What you see depends on your role, enabled features, the data Runekist has observed, and the period you selected.
Choose the correct clan and period first
A Runekist account may belong to more than one clan. Before reviewing or changing anything:
- Confirm the clan name at the top of the dashboard.
- Use the clan switcher if necessary.
- Check the selected period.
- Read the collection-freshness message.
Most reports are period-specific. Looking at the wrong period is the most common reason a valid record appears to be missing.
The browser displays dates and times in a suitable local form where supported. Exports and integrations use explicit timestamps so their time basis remains clear.
Roles and permissions
Clan leader
The clan leader owns the Runekist clan. The leader has the broadest set of actions, including leadership transfer and leader-specific billing decisions. A clan has one active leader.
Superior
A superior can manage most clan configuration, scoring, members, collaboration features, and operational corrections. Leadership transfer and leader-specific billing decisions remain available only to the clan leader.
Officer
An officer can review leadership-facing reports intended for clan oversight but does not receive general write access. A missing edit, delete, payment, or configuration button may therefore be correct even when the officer can read the page.
Member
A member can review personal and permitted clan information, participate in Polls and Questionnaires, use personal tools such as Shield of Peace, and manage personal notification choices.
Runekist always checks permissions on the server. A visible link is not the only protection, and hiding a link does not grant or remove permission. Read Understand clans, roles, and periods for more detail.
Leader and superior quick start
Use this order when setting up a clan or taking over day-to-day operation.
- Open Leadership → Collection and review the collection configuration. A clan leader must complete the connected Total Battle account actions.
- Open Scoring → Configure scoring and add only the scores and requirements your clan uses.
- Open Leadership → People to invite, approve, and organise members.
- Open Leadership → Data quality and resolve names Runekist could not match safely.
- Open Clan to publish Rules, announcements, events, Polls, and Questionnaires.
- Enable useful alerts and calendar integrations.
- Review the first complete period in Overview, Scoring, and Insights.
The Leader or superior quick start turns this sequence into a focused checklist with links to each task.
Officer quick start
- Confirm the clan and period.
- Use Overview to check freshness and operational warnings.
- Use Scoring → Leaderboard for standings.
- Use Scoring → Member performance and Requirements & chests for member-level review.
- Use Insights for reward chest, Ancient, Guardsmen, and clan-wide analysis.
- Use Clan to read Rules, announcements, events, Polls, and Questionnaires.
- Report configuration or data-quality issues to a leader or superior when the corresponding write control is not available.
See the Officer quick start for a shorter working route through these areas.
Member quick start
- Confirm the correct clan.
- Open Overview to see the current period and your headline status.
- Open Scoring to review your rank, points, reward chests, requirements, and visible fines.
- Open Clan to read announcements and Rules.
- Open Clan → Calendar to record your Shield of Peace expiry and see clan events.
- Participate in open Polls and Questionnaires.
- Enable alerts that are useful to you.
The Member quick start keeps these first steps together.
Understanding the dashboard
The period selector
A period is the reporting window used for standings and most requirements. Changing the selected period changes the report context; it does not edit underlying source data.
Past periods are useful for comparing development, checking a completed requirement cycle, reviewing an Ancient or Guardsmen observation, and understanding when a score or fine was applied.
Reading collection freshness
The freshness area tells you how recently Runekist received or processed relevant data. Check it before treating a report as final.
Old or incomplete data can mean collection is paused, credentials or 2FA failed, a collector is still running, the clan lacks usable credits for another run, imported rows are being aggregated, the selected period has no rows, or a specialist source has not been read recently.
Calculating or updating statistics
Runekist can rebuild period aggregates after scoring, requirement, mapping, or source changes. Old active statistics remain visible where supported while a replacement is prepared. Avoid repeatedly editing the same rule just because recalculation is not instantaneous.
Conditional sections
A section may be absent because your role cannot access it, the clan has not enabled it, the feature is disabled globally, required data has not been observed, the selected period has no relevant records, or setup is incomplete.
For example, Forest Essence appears only after the relevant data has been observed. Fines and the Assistant appear only when their features are available.
Overview
Overview answers: What is happening now, and does anything need attention?
Depending on your role, it may show active members, contributors, reward chest and point totals, inactive members, people below requirements, your own result, collection freshness, collector health, credits, review-queue counts, period progress, and recent activity.
Use Overview for a quick health check. Follow its attention links into the specialist area:
| Signal | Open | | --- | --- | | Collection is paused or unhealthy | Leadership → Collection | | Credits are low or exhausted | Leadership → Billing & rewards | | Review queue is not empty | Leadership → Data quality | | Members are below requirements | Scoring → Requirements & chests | | Totals look wrong | Check the period and freshness, then Scoring and Data quality | | An announcement or event needs action | Clan | | Statistics are calculating | Let recalculation complete, then refresh |
Scoring
Scoring answers: How is the clan performing, and are members meeting the agreed expectations?
Leaderboard
The leaderboard is the main period ranking. It can show total points, reward chest count, raw points, fine-adjusted ranking points, debt paid through point deductions, remaining point debt, and your own result.
A high reward chest count and a high point score are not necessarily the same. Point rules determine how much each scored reward chest or group contributes. See Read the leaderboard.
Member performance
Use Scoring → Member performance when the leaderboard is not enough. Review member name, registration, role, requirement status, period totals, last activity, and top source. This is a contribution report, not the place to change a person’s role or remove them; those actions belong under Leadership → People.
Requirements and reward chests
Use Requirements & chests to understand why someone is meeting or missing an expectation. It can show each threshold, the current value, met status, reward chest-type counts and points, rank, and supported resource values. Select the correct period before drawing a conclusion.
A requirement can use more than total points. It may be based on a reward chest count, group, resource, or another supported measure.
Fines
Fines are optional. When enabled, Runekist can support missed-requirement assessments, assignments from journal events, manual fines, payments, forgiveness, silver or chest-point ledgers, and ranking deductions.
Fine history is audit-oriented. Corrections normally use compensating entries rather than silently rewriting the past. Members see only their permitted view; officers receive their intended review view; authorised leaders and superiors receive write controls.
Configure scoring
Authorised leaders and superiors use Configure scoring to manage scores, requirements, groups, catalog choices, and fine rules.
Clan → Rules is the human-readable, versioned document. Scoring → Configure scoring tells Runekist how to calculate. A clan can explain policy in Rules and implement its measurable part in scoring setup. Read Rules vs scoring setup.
Good scoring practice is simple: measure only what matters, name requirements clearly, use groups for related reward chests, review a completed period after changes, explain important changes to members, and let recalculation finish before changing the same rule again.
Insights
Insights answers: What can we learn from the collected records beyond the main standings?
Chest analysis
Chest analysis shows which reward chest types are common, who collected a selected type or group, how periods compare, and how many matching chests each member collected. Where available, select periods, search types and groups, view a chart, rank members, and export CSV or XLSX.
Ancients
Ancient reports come from completed captures explicitly uploaded through the Runekist Ancient Summons Collector. Reports can include summons, fights, contribution changes, Ancient health, first-hit or threshold analysis, and the cohort implied by the configured interpretation.
Use the dedicated Ancient Collector guide for installation, monitoring, upload, and repair. For report reading, see Use Ancient Summons reports.
Guardsmen tiers
Guardsmen-tier insight is based on tiers observed from Ancient Personal rewards. It is not a manually maintained profile field for every member. A person may be absent because they were not observed in the chosen Ancient event or period.
Insights → Clan
Open Insights → Clan for roster changes, journal events, Dragon Coins, and Forest Essence. The section is organised around what the data describes, not the collector source that supplied it.
Check the data-freshness or read-status message before treating a balance or roster event as current. Clan Capital read describes how this data was obtained; it is not the navigation name.
Roster changes
Roster changes show members detected as joined or observed as having left. This differs from Member performance, which is about contribution during a period.
Journal events
Journal events are imported operational records. Depending on the event and permission, you can open detail, export source rows, or create one controlled fine assignment. They are an audit trail, not a substitute for Clan → Calendar.
Dragon Coins
The Dragon Coin ledger records supported changes and balances. A source player can remain in history without a current Runekist membership. Authorised manual adjustments should carry a clear reason so the ledger remains understandable.
Forest Essence
Forest Essence appears after Runekist observes relevant data. If it is absent, confirm collection is enabled, check freshness, confirm the game source has produced Forest Essence data, and verify the selected period.
Clan
Clan answers: What has the clan published, planned, or asked members to do?
Announcements
Announcements may be imported from supported journal data or authored in Runekist. Depending on role and configuration, you can search, open a stable link, expand content, create an announcement, translate it, and manage notification preferences. A new translation may use configured clan credits; a cached translation can be reused.
Rules
Clan → Rules contains the clan’s versioned Markdown document. Authorised leaders and superiors can edit, preview, publish, review history, control visibility, and enable translations. Members see the permitted current version.
Use headings and short sections. When Runekist must evaluate a measurable value, put it in scoring setup as well as explaining it in Rules.
Clan → Calendar
The Calendar under Clan contains personal Shield of Peace information and clan-authored events. It differs from the public Total Battle calendar, which contains the fixed game schedule.
Shield of Peace
Record remaining days and hours plus an optional reminder lead time. Runekist calculates the expiry. Replacing the value updates your record; removing it deletes the current personal entry. Leaders do not use this page to inspect every member’s private shield entry.
Clan events
Members see events allowed for their role. An event can include a category or custom title, start and end, notes, minimum role, private-feed inclusion, reminders, and active or cancelled state.
Authorised leaders and superiors can create and manage events. Verify the saved event in the member-facing list.
Polls
Polls can be draft, open, closed, or archived. Options can be times of day, yes/no answers, or custom choices. A poll can allow one or several selections, control when results become visible, set a deadline, and optionally let members change their membership-associated votes. Authorised leadership can export results to CSV with voter membership information. A poll with votes cannot be deleted; close or archive it instead. Voting permission and result visibility are checked separately.
Questionnaires
Questionnaires collect structured member progress. They can support self-responses, captain responses for configured participants, values and notes, progress summaries, active and archived states, and spreadsheet exports. Archiving keeps historical responses.
Assistant
The Runekist Assistant answers bounded questions about the current clan’s reporting data. It is read-only: it cannot change rows, scoring, requirements, members, billing, collection, fines, Polls, or announcements.
Make a question self-contained. Include the period, member or group, measure, and desired result shape. For example:
- “Show the ten members with the most points this period.”
- “Which members are below the weekly points requirement?”
- “How many Clan reward chests did Alex collect last period?”
- “Compare Dragon Coins for Maria and Stefan in the current period.”
The Assistant may return an ambiguity, unsupported question, missing-data, allowance, credit, or rate-limit message rather than guessing. See Ask effective questions.
Leadership
Leadership is for operating the Runekist clan, not routine member browsing.
People
Use Member management to search active or former memberships, review usernames, change permitted roles, remove a member where allowed, and understand registration state. Invitations bring people in with an allowed role. Approvals accept or reject pending requests.
Leadership transfer is a dedicated, audited, leader-only flow. It can affect future automatic billing for the outgoing leader, so both people should read the confirmation and understand their payment or top-up responsibilities.
Data quality
The review queue contains collected data Runekist could not resolve safely, such as an unknown player or reward chest identity. Do not guess merely to empty the queue. Name corrections keep stable aliases when collector or OCR names differ from the intended identity.
Check spelling, punctuation, renamed players, reused names, Seasonal Kingdom account differences, and accidental mappings before saving a correction. A mapping change can trigger recalculation.
Collection
Clan leaders and superiors can review collection and configure the setup controls available to their role, including Clan Capital read settings. Replacing collector credentials, refreshing the linked-account list, pausing collection, and resuming collection are clan-leader-only actions.
Runekist schedules normal collection automatically. A clan leader can request a pause when the game account must be used manually, but must wait until Runekist explicitly reports that the account is ready. A pause request is not yet a confirmed stop, and final captured rows may continue importing afterwards. Resume only after the manual work is complete. Never paste passwords, 2FA secrets, API tokens, calendar tokens, or push keys into support messages.
Access and sharing
Export API tokens are sensitive bearer credentials. A raw token may be shown only once; Runekist stores a hash. Use one token per integration, revoke anything exposed, and never include a token in a screenshot or public repository.
Public sharing can include a clan URL, Rules, or leaderboard surface. Confirm exactly what is exposed before distributing a link.
Discord and Telegram use an identity link between the platform account and a Runekist user plus a space mapping between the chat location and a clan. Chat roles do not replace Runekist membership.
Billing and rewards
This area can include subscription status, invoices, the payment portal, credits, top-ups, member contributions, and rewards. Collection credits belong to the clan, not to a transferable personal balance. Use the live billing page for current prices and allowances.
Settings
Settings contains clan-wide feature controls such as translation, Rules visibility, sharing, and member-contribution options. Leader-only controls should say so explicitly.
Tools outside the dashboard
Total Battle calendar
The public calendar displays the fixed Total Battle schedule. Main and Seasonal calendars are separate display modes, and neither is the clan-authored event list.
Eligible members may create a private subscription. Treat its token like a password: do not publish it, rotate it if exposed, and revoke it when no longer needed.
Stacking calculator
The stacking calculator is a public planning tool. Signed-in users may save private reusable layouts. A share snapshot is an immutable public result identified by an unguessable link.
Alerts and account
Push devices belong to the user account; notification preferences belong to a clan membership. One user can therefore choose different alerts for different clans.
Use Account for personal identity and security, language and theme, device subscriptions, notification testing, multi-clan context, and private saved tool layouts.
Common tasks
Find everyone below a requirement
- Confirm the period.
- Open Scoring → Member performance or Requirements & chests.
- Select the requirement and filter by missing status.
- Review each value and threshold.
- Check freshness before taking final action.
See Find members below requirements.
Investigate a score that looks wrong
Confirm the player and period, review Member performance, open Requirements & chests for the detailed breakdown, check whether fines affect ranked points, look for an unmatched or duplicate identity, and check whether statistics are recalculating. Change scoring only after collected rows and identity are confirmed.
Resolve an unknown player
Open Leadership → Data quality → Review queue, inspect the source context, search members and aliases, map only when certain, add a durable correction if needed, let recalculation complete, and recheck the affected period.
Change a requirement
Open Scoring → Configure scoring → Requirements, confirm the effective period, make the change, save, wait for recalculation, verify the member report, and update Rules or an announcement if members need to know.
Publish Rules or an announcement
For Rules, edit the Markdown, preview headings and links, publish a new version, check visibility and translation, and open the member-facing version. For an announcement, write a clear title and message, publish, then verify notification and translation behavior.
Create a clan event or update Shield of Peace
Use Clan → Calendar. Authorised event managers set the title, time, visibility, feed inclusion, and reminders, then verify the member view. Each member records their own Shield of Peace remaining time and optional reminder lead.
Review an Ancient upload
Confirm the extension is linked to the correct clan, the summon completed and was selected for upload, then open Insights → Ancients, choose the correct event window, and inspect the fight. Re-upload a corrected capture if the extension repaired it.
Apply a fine from a journal event
Confirm fines are enabled and you have permission. Open Insights → Clan → Journal events, inspect all source rows and the proposed configuration, preview the assignment, confirm only when correct, then review the resulting account under Scoring → Fines.
Export data
Exports live with the relevant feature rather than behind one universal button. Common exports include member performance, chest insights, journal events, point rules, Polls, Questionnaires, and API period or raw-row data. Every export repeats clan and role checks.
Troubleshooting
A feature or action is missing
Check the clan, membership, role, feature configuration, whether required data has been observed, the selected period, demo mode, and global availability. Officers may see a report without its edit control. Read A feature or action is missing.
Data is old or incomplete
Read the freshness message, check Leadership → Collection for a pause or credential failure, check credits, look for recalculation, confirm the period, and compare the latest source read. Do not change scoring to fix old collection data.
A member has no reward chests or appears twice
Check the period, freshness, exact game username, review queue, alternate identity, accepted versus unmatched rows, and whether the member actually contributed. Duplicate people usually indicate an alias or mapping problem; do not merge identities casually.
I can read the page but cannot change it
This is normal for an officer or member on a read-only surface. It can also happen in demo mode or after a membership change.
Notifications are not arriving
At the device level, confirm browser permission, service-worker subscription, device state, and a test push. At the membership level, confirm the clan, notification preference, active membership, event visibility, and suppression policy.
A calendar feed is not updating
Confirm the token is enabled, membership and clan eligibility remain active, the client uses the current token after rotation, caching is not hiding changes, and the event is included in iCal for your role.
The Assistant could not answer
Rewrite the question with an explicit period, exact member, one measure, and a bounded result. An unsupported mutation, ambiguity, unavailable dataset, allowance, credits, or rate limit can still produce a legitimate refusal.
An Ancient capture is missing
Check the linked clan, monitoring health, capture completion, upload selection, upload result, reset window, and whether a corrected upload replaced the existing fight.
Frequently asked questions
Can a leader manually create reward chest rows?
No. Collector rows are source records. Leaders configure interpretation, resolve identities, and manage rules; they do not invent collected reward chest rows.
Does changing a score rewrite everything immediately?
Runekist prepares a recomputed aggregate for the affected period. The interface may show calculating or updating while the replacement is built.
Why can a Dragon Coin record exist without a current membership?
Resource history belongs to the observed player record and remains auditable when someone never registered, changed identity, or left.
What is the difference between announcements and journal events?
Announcements are clan communication. Journal events are imported operational records that may support detail, export, or a controlled fine assignment.
What is the difference between Clan Calendar and the Total Battle calendar?
Clan → Calendar contains your clan’s events and personal Shield of Peace tools. The Total Battle calendar is the fixed public game schedule.
Can an officer change members or scoring?
Officers and superiors receive intended read access but not general administrative writes.
Can the Assistant change anything?
No. It is a read-only reporting assistant.
Should API or calendar tokens be sent to support?
No. Revoke or rotate an exposed token and never place reusable secrets in ordinary support messages.
Glossary
Accepted reward chest
A collected reward chest row that Runekist resolved and included in the active reporting interpretation.
Unmatched or unknown row
A collected row Runekist cannot safely assign to the intended player or reward chest identity.
Collection freshness
The age and state of the latest relevant collected and processed data.
Period
The reporting window used for standings and requirements.
Point rule and requirement
A point rule assigns points to a reward chest type or group. A requirement defines an expected threshold for a supported measure.
Chest group
A clan-defined group of reward chest types used for scoring, requirements, or analysis.
Scoring setup and Rules
Scoring setup configures calculations. Rules is the versioned human-readable Markdown document published by the clan.
Clan Capital read
A read of supported Clan Capital data used for resource balances, roster activity, and journal records.
Roster change and journal event
A roster change records a detected join or observed departure. A journal event is an imported operational record, distinct from a calendar event.
Dragon Coin ledger and Forest Essence
The ledger is an audit-oriented record of supported Dragon Coin changes. Forest Essence is shown after relevant Clan Capital data is observed.
Fine account
The append-oriented account that records penalties, payments, forgiveness, and remaining debt.
Shield of Peace reminders
A personal membership record of Shield of Peace expiry and an optional reminder.
Ancient report and Guardsmen tier
An Ancient report comes from a completed capture explicitly uploaded by an authorised extension user. A Guardsmen tier is observed from a supported Ancient Personal reward record.
Clan Calendar and Total Battle calendar
The Clan Calendar holds clan-authored events and personal Shield tools. The Total Battle calendar shows the public fixed game schedule.
Collection credits
Clan credits consumed by supported collection operations according to the current billing policy.
Navigation lookup
The guide uses the current grouped navigation:
| What you need | Where to find it | | --- | --- | | Standings | Scoring → Leaderboard | | Contribution detail | Scoring → Member performance | | Requirement and reward chest detail | Scoring → Requirements & chests | | Scoring configuration | Scoring → Configure scoring | | Chest analysis, Ancients, and Guardsmen | Insights | | Roster, journal, Dragon Coins, Forest Essence | Insights → Clan | | Rules, announcements, events, Polls, Questionnaires | Clan | | Member management and invitations | Leadership → People | | Unknown names and corrections | Leadership → Data quality | | Collector state | Leadership → Collection | | API, sharing, Discord, Telegram | Leadership → Access & sharing | | Credits, billing, and rewards | Leadership → Billing & rewards |