Choose a resource
Open Insights → Clan → Resources. Choose a category, then a resource. The choices wrap to fit narrow screens. Officers, administrators and leaders can read this area when Clan Capital collection is enabled. Forest Essence appears after it has been observed; earlier seasonal history remains available.
Silver, Lumber, Iron, Stone and Food show member contributions and activity for the selected period. Clan speedups show durations. Scientific tractates, Boards, Steel and Cement retain individual activity. A resource with no retained activity shows an empty state.
Dragon Coins have a lifetime personal ledger and balances. Administrators and leaders can correct a payout's source or add an audited adjustment with a player, amount and explanation. Adjustments affect coin balances; they are excluded from contribution requirements.
Search and move through tables
Search report players filters the contributions and activity in the selected range. Search ledger players filters only the lifetime Dragon Coin ledger. Clear the search field and choose Search to show all players again. Each table has its own previous/next controls and result count. Changing one table's page does not change the others. The selected filters and pages are retained in the page address.
During a refresh, previous results remain visible with an updating message. Editing is temporarily unavailable until the new results arrive. A failed refresh shows an error; retry the search or refresh before editing. Quantities use your selected language's number separators, including negative and very large values. Enter whole numbers without separators in amount fields.
Use the Dragon Coin ledger
The lifetime ledger shows retained supported changes and player balances. Clan-wide total owed stays the total for the whole clan even when the table is filtered. A historical player remains available when they have never registered, changed identity, or left the clan.
To correct a payout, choose Edit source on its row. Search and select the historical player inside the editor, or choose Recorded player to use the original record, or Clan for a clan payout. Choose Save, or Cancel to leave it unchanged. Source lookup searches player choices; it does not filter the ledger or hide the payout being edited.
For a separate balance adjustment, expand Manual adjustment, choose a player, enter the amount, select Add or Deduct, and give a clear note. Choose Save adjustment. Check any error before retrying; your entered values remain available. Officers can read these records but cannot edit them.
Start fragment accounting
Torch of Olympus fragments and Chronoglyph fragments belong to the clan. Open each fragment tab, enter Current stock and choose Start accounting now. Administrators and leaders can start accounting once per fragment, including with zero stock. Runekist saves the amount, author and start time. Repeated submissions preserve that original record.
Enter the stock at the start time. Events in that same timestamp second or earlier are already included. Later event rewards increase stock; distributions to players decrease it. Delayed imports use the event's original time. No older history is required to start.
The stock stays independent of the selected period, recipient search and page. Recipients in this range shows who received how many fragments; activity lists their original times. Older retained entries remain visible and are marked as before accounting started. Event rewards belong to the clan even when deposited through a leader. A leadership change does not reset stock.
Fragments have no personal balance, amount owed, payout-source selector or personal adjustment. Historical edits remain available as audit evidence but cannot change physical stock or the actual recipient. Unrecognized actions remain visible without changing stock. A negative stock is an inconsistency; collection gaps or unclassified activity after the start can make stock incomplete.
Correct an opening count
Stock not set means accounting has not begun for that fragment. A displayed zero is a real saved count. Torch of Olympus and Chronoglyph are set up independently.
If the initial number was mistaken, an administrator or leader can choose Correct opening stock, enter the corrected opening amount and a reason, review the current-stock preview, then choose Save correction. Incoming activity can change the preview. Cancel leaves the amount unchanged.
This corrects the original number; it does not start accounting again or record a fresh physical recount. The original start time, setup author and note stay the same, and all collected activity remains intact. For example, changing an opening from 100 to 120 changes a current stock of 85 to 105. Each effective correction records the old and new counts, author, date and reason in Correction history.
If another person has already corrected the amount, Runekist asks you to review the updated stock and save again deliberately. Repeating the same saved amount does not add another correction. A failed save leaves the opening and its audit history unchanged.
Choose a Hermes interval
Hermes shows summed loyalty contributions. It opens with the current period's exact bounds. Select a historical period to use its bounds, or enter local start and end times and choose Apply custom range. The displayed timezone is your browser's timezone. The start is included; the end is excluded.
A custom range can span several periods. Search, pagination and refresh preserve it. Reset to current period restores current-period bounds. These controls do not alter accounting periods or requirements.
Set resource requirements
In Scoring → Requirements, choose a resource metric, threshold and applicability scope. Silver, Lumber, Iron, Stone and Food support minimum sent. Dragon Coins support minimum sent, maximum taken and minimum net. Fragment limits track maximum received by the actual recipient. Old fragment minimum-sent and minimum-net requirements are retired for active and future periods; closed-period audit records are preserved. Forest Essence keeps its seasonal requirement.
Ordinary-resource penalties are opt-in, using the existing fine configuration. Fragment requirements do not create automatic fines.
Understand coverage
Reports sum deduplicated retained activity, so overlapping collections do not add the same event twice. They cannot prove that no activity occurred during a collection gap. Historical repair may update totals as recoverable rows are classified. Old speedup amounts without evidence of their units remain excluded rather than being guessed.