What fines can record
When enabled, Runekist can support missed-requirement assessments, assignments from journal events, manual fines, payments, forgiveness, silver, chest points, specific chest types or chest groups, and ranking deductions.
Choose the chest target carefully
A chest fine targets either one chest type or one non-empty chest group. Type and group debts are separate: record payments or forgiveness against the same target used by the fine. Progress for a type counts that chest type. Progress for a group counts accepted chests from the types currently in that group, so changing group membership changes which future progress counts.
During an open period, qualifying chests are allocated to typed fines before they score on the leaderboard. Type-specific fines are handled before group fines, and a group uses the highest-point qualifying chest types first. A chest can satisfy only one fine. Chests beyond the amount owed still score normally, and chest-point debt is applied only after typed-chest allocations. The Fines view shows the original obligation, the amount submitted to it in the period, and the amount remaining.
Open-period allocations are projections and can change when collector data, identity matching, point rules, forgiveness, or the active stat version changes. After the period closes, Runekist records the final allocation as an automatic append-only payment. Later corrections add a matching payment or reversal rather than rewriting ledger history.
Review journal-event amounts
Optional chest-point, silver, and chest-count fields can be left blank when the intended amount is zero. Required scores, breakpoints, and warning thresholds still need valid values.
On the override step, mark a player Not fineable when the reviewed row should create no debt. Runekist keeps that decision and all final amounts at zero if you move back from confirmation. The immutable assignment item remains in the audit history, but no fine ledger entry is created for that player.
Members see only their permitted account information. Officers can inspect intended oversight views. Authorised leaders and superiors receive configuration and action controls.
Keep the history understandable
Fine accounts are append-oriented. Correct a mistake with the supported compensating action instead of silently rewriting history. When applying a fine from a journal event, inspect the complete source rows and preview before confirming.
Configure fine rules through Scoring → Configure scoring. Review resulting accounts under Scoring → Fines.