MEMBER TRANSPARENCY โ€ข PRIVACY-FIRST CLARITY

Help members understand their inactivity status

Give members instant clarity on their private inactivity score, contextual Why? explanations directly on notices, and a dedicated comment thread to talk with staff.

Private Score Check (/my_score)
Contextual Why? Explainer Buttons
Dedicated Discussion Threads
No Message Content Reading
Command Reference

Member status previews

Private My Score
CLNRCLNRโœ“ APP22:16

๐Ÿ“Š Status and Activity of bivvo

Here is an overview of your personal activity status.

๐Ÿ•ต๏ธ Last Activity

Last activity: 08.10.2026 (0 days ago)
Joined date: 28.10.2023

๐Ÿ”ฅ Activity Streak

Current Activity Streak: 226 day(s). Your streak increases for every consecutive day you are active. Your personal record is 226 day(s)!

๐ŸŒŸ Activity Reward Roles

Earn special roles by keeping a daily activity streak. Higher streaks unlock higher roles:

  • @Pioneer - min streak 7
  • @Vanguard โ˜† - min streak 14
  • @Breacher โ˜†โ˜† - min streak 21
  • @Guerrilla โ˜… - min streak 28
  • @Pathfinder โ˜…โ˜… - min streak 40

๐Ÿ˜ด Inactivity Score

Your current score is 0.00. The score, also known as decay score, increases with inactivity and is reduced by activity to keep the server active.

Score Explanation

Last decay evaluation or tracking refresh: Thursday, 8. October 2026 at 21:57.
Next expected decay check for this member: Friday, 9. October 2026 at 21:57.

๐Ÿ—“๏ธ Last 14 Days

๐ŸŸข๐ŸŸข๐ŸŸข๐ŸŸข๐ŸŸข๐ŸŸข๐ŸŸข
๐ŸŸข๐ŸŸข๐ŸŸข๐ŸŸข๐ŸŸข๐ŸŸข๐ŸŸข
Active on 14 of the last 14 tracked days.
๐ŸŸข active day  โšช quiet or graced day

โš ๏ธ Thresholds

Your inactivity score has thresholds that trigger certain actions:
  • At 14, you will be assigned the inactive role.
  • At 21, you become eligible for manual staff review.

๐Ÿ’ก Tip: Stay Active!

To reset your inactivity score to 0, simply send a message, react to a message, or join a voice chat!

Privacy note

This score is based only on activity signals from this server. CLNR does not read or store message content.

Quiet appreciation

Want to recognize someone who helped the community? Use /thanks to send a private note.

๐Ÿ“‹ Inactivity Score History

Score 0.00 at 08.10.2026
Score 0.00 at 07.10.2026
Score 0.00 at 06.10.2026
Score 0.00 at 05.10.2026
Score 0.00 at 04.10.2026

Help more members understand their activity

This score view explains activity without reading messages. A vote helps more communities discover CLNR.

๐Ÿ”’ CLNR ethics statement: Ethics #15 - When I warn, review, or remove members, I should do it with context, clear thresholds, and the option for staff oversight.
Why? explanation: page 1 of 6
CLNRCLNRโœ“ APP22:20

Why You Received This Notification

โฐ Warning Triggered: CLNR sent this inactivity warning because your decay score reached the server's warning threshold.
๐Ÿ—“๏ธ Activity Window: CLNR reviews roughly the last 21 days of activity data (decay interval: 1 day(s)).

Page 1/6

๐Ÿ”’ CLNR ethics statement: Ethics #05 - I use no ads, trackers, or pixels, and I work without sensitive privileged intents.

Example scores, dates, roles, and thresholds, not live data or defaults. The Why? preview shows its first page.

Self-Service Clarity

Reading a Lower-Is-Better Inactivity Score

Members can check their status privately at any time with /my_score without disturbing the server or alerting others.

01

Lower Decay Score Means Less Inactivity

In CLNR, a score of 0.00 means no current inactivity score. Scores rise during configured inactivity periods and decrease or reset with eligible server activity, subject to server settings, grace, and amnesty. Learn more about score math in our Discord Decay Score deep dive.

02

14-Day Activity Calendar

The personal score response includes a 14-day calendar: green indicates an active day; white indicates a quiet or graced day. Missing activity information is not proof that a member was inactive.

03

Streak & Known Activity

Shows the member's activity streak and known activity. Streak intervals and eligible activity sources follow the server's configuration, without reading message content.

Fairness & Context

Unknown vs Observed Activity & Grace Context

Personal status gives context for observed activity, missing activity information, exemptions, and any active decay grace or amnesty window.

โ“

Unknown Activity Labels

When last activity is unknown or not recorded, status labels the missing information. The calendar is not a transcript of activity in unobserved channels.

โณ

Active Grace & Amnesty Timing

When decay grace or seasonal amnesty is active, status views explain its timing and when score growth resumes. Receiving a notice or check-in does not itself grant a new grace period.

โญ

Explicit Exemption Context

Members with exempt roles receive explicit exemption context instead of a misleading streak calendar. Kick exemptions and broader exempt-role settings remain separate controls.

How Context Reduces Member Friction

Self-Service

Unclear bot actions cause member anxiety and flood staff with tickets. By publishing clear rules and personal score cards, members understand exactly how to maintain their status.

Without clear explanations

Members may struggle to understand which inactivity rule applies.

With CLNR Transparency

Members check status anytime, see the rule trigger on notices, and ask staff directly in threads.

Pair transparency with Community Check-ins or DM-Only Inactivity Notices to keep communication calm and predictable.
Context at the Point of Notice

Contextual Why? Explanation Buttons

Supported CLNR warning, inactive-role, recovery, reward, and review announcements can include a contextual Why? button when enabled.

๐Ÿ’ก

Rule-Based Instant Explanations

Pressing Why? opens a private explanation of the relevant notice using the server's configured rules. Available details depend on the announcement type.

๐Ÿ”’

Privacy & Ethics Explanation

Why? explanations include privacy and ethics context. They use configured rules and relevant activity metadata without revealing message content or creating a behavioral transcript.

โš™๏ธ

On by Default & Configurable

Why? buttons are enabled by default across all notices. Admins can toggle them on new posts using /toggle why_buttons.

Need guidance on setting up fair server policies? Explore the Inactivity Policy Template and Explain Inactivity Rules guides.
Public Discussion & Support

Dedicated Comment Threads & Retention

Public warning announcements can include a Comment button that automatically creates a dedicated Discord discussion thread attached to the post.

  • โ€ข Dedicated Space for Questions: Gives members a clear place to ask staff about their warning or request extended leave without cluttering main text channels.
  • โ€ข Configurable Retention (30-Day Default): Notification threads carry an explicit notice about scheduled closure or deletion. Retention defaults to 30 days and is configurable.
  • โ€ข No Permanent Storage Promises: Threads are auto-cleaned based on server retention settings. CLNR does not claim permanent archival of support discussions.
  • โ€ข Toggle Control: Notification threads are on by default and can be hidden on new posts using /toggle notification_threads.

Comment Thread Lifecycle

Automatic Cleanup
1. Thread Created On Warning Post

Member clicks ๐Ÿ’ฌ Comment on public notice card. Discord thread opens automatically.

2. Staff Dialogue Contextual Discussion

Member and moderators discuss inactivity, vacation context, or check-in options directly.

3. Scheduled Retention Purge Configurable (30 Days)

Threads carry a notice about scheduled closure/deletion. Cleanup follows the configured retention and requires CLNR's thread permissions.

Combine comment threads with Auto-Kick Guardrails or Staff Removal Approval when reviewing the server's moderation workflow.
Admin Controls & Rules

Configuration Controls & Rule Boundaries

Understand the clear boundary between explaining a notice and modifying server rules.

Explaining vs Altering Scores

Strict Function Separation

It is important to distinguish explaining an existing notice from changing a member's score or granting an exemption:

  • โ€ข Why? Buttons are Strictly Informational: Pressing Why? explains the server's configured rules. It never alters a member's score, resets grace timing, or applies exempt roles.
  • โ€ข Admin Overview with /user_score: Admins use /user_score to inspect another member's score, streak, calendar, and exemption status during support reviews.
  • โ€ข Separate Exemption Rules: Exemptions and role grants are managed separately through server role configuration and exempt settings.

Defaults and future notices

Why? buttons and notification comment threads are on by default. Admin controls affect new posts; these descriptions are not a saved-settings preview.

Thread retention defaults to 30 days and is configurable. Threads explain their scheduled closure/deletion; do not rely on permanent storage of a support discussion.

Slash Commands & Controls

Command Reference Center

Click any command chip below to copy it directly to your clipboard for Discord.

All Members

Private Personal Inactivity Score

Displays your private inactivity score, activity streak, exempt status, observed activity type, 14-day calendar, and score explanation. Lower Decay Score means less inactivity.

Admin Only

Member Inactivity Context for Staff

Allows admins to inspect a member's decay and activity score and history, with relevant activity, grace, amnesty, and exemption context.

Admin Only

Toggle Contextual Why? Buttons

Toggles whether contextual Why? explanation buttons are attached to newly posted server notices and warning announcements. On by default.

Admin Only

Toggle Notification Discussion Threads

Toggles whether public warning announcements open a dedicated comment thread for member questions. On by default with scheduled 30-day retention.

โ„น๏ธ Note: Why? and Comment are buttons on Discord notice cards, not slash subcommands.

Bring complete clarity to your community inactivity policy.

Help members check their status, understand notices, and ask staff about their inactivity rules.

Command copied to clipboard!