Events & Rewards Guide
Everything you need to know about how reward events work in the Resonance Discord bot — from the 3 default events to creating custom ones.
How Events Work
An event defines a rewardable action in your Discord server. Each event has:
- Event ID — Unique identifier (e.g.,
daily_checkin) - Reward amount — RSNC tokens awarded per trigger
- Detection method — How the bot recognizes the action
- Cooldown — Minimum time between claims per user
- Max claims — Maximum triggers per cooldown period
Events are stored as monitoring_rules in your server configuration and sync between the Discord bot and the Partner Portal.
The 3 Default Events
When you run /setup connect, three events are automatically created:
1. Daily Check-in (daily_checkin)
| Setting | Value |
|---|---|
| Reward | 2 RSNC |
| Cooldown | 24 hours |
| Max claims | 1 per cooldown |
| Detection | Gateway pattern — regex matching GM/GN messages |
Triggers when a member sends a message matching the GM/GN pattern (case-insensitive): "gm", "good morning", "gn", "good night", and variations.
2. News Tracker (news_tracker)
| Setting | Value |
|---|---|
| Reward | 5 RSNC |
| Max claims | 1 per user per message |
| Detection | Channel watch — emoji reaction drops |
This is a template event for the /watch command. When you run /watch start channel:#announcements, the bot auto-creates a reaction drop on every new message in that channel using this event's settings.
To activate: /watch start channel:#announcements
3. Regular Engagement (regular_engagement)
| Setting | Value |
|---|---|
| Reward | 10 RSNC |
| Cooldown | 1 hour |
| Max claims | 5 per day |
| Detection | Gateway analysis — quality message detection |
Triggers when a member sends a quality message: 100+ characters, 20+ words, not a command, not spam.
Creating Custom Events
Via Discord Commands
/config events
This opens an interactive menu to create, edit, or delete events.
Via Partner Portal
- Go to partners.rsnc.network
- Navigate to Discord → Events
- Click "Create Event"
- Configure settings and save
Changes sync automatically between Discord and the Portal.
Quick Reward Adjustment
To quickly change a reward amount without opening the full editor:
/config reward daily_checkin 5
Detection Methods
The bot uses different methods to detect rewardable actions:
Gateway Pattern (Regex)
Matches messages against a regex pattern. Used by the default daily_checkin event.
How it works: The bot's natural participation gateway processes every message and checks it against configured patterns.
Best for: GM/GN detection, keyword-based rewards, specific phrases.
Gateway Analysis (Quality Detection)
Analyzes message quality based on length, word count, and content type. Used by regular_engagement.
How it works: Messages are scored on character count (100+ chars), word count (20+ words), and content quality (not commands, not spam, not links-only).
Best for: Rewarding thoughtful contributions and quality discussions.
Channel Watch (Auto-Drops)
Creates automatic reaction drops on every new message in a watched channel. Used by news_tracker.
How it works: When you run /watch start channel:#announcements, the bot monitors that channel. Every new message gets a reaction drop with the event's emoji. Members click to claim.
Best for: Announcement engagement, news channels, important updates.
Manual Drops
Admin-triggered button or reaction drops. Created with /drop.
How it works: Admins create drops that appear as clickable buttons or emoji reactions. Members interact to claim.
Best for: AMA rewards, event participation, special occasions.
Cooldowns & Max Claims
Cooldown
The minimum time between claims per user per event. After claiming, the user must wait for the cooldown before claiming again.
| Cooldown | Typical Use |
|---|---|
| 1 hour | Engagement events, quality messages |
| 24 hours | Daily check-ins |
| None (0) | One-time events, drops |
Max Claims
The maximum number of times a user can trigger an event within the cooldown period.
| Max Claims | Behavior |
|---|---|
| 1 | One claim per cooldown (standard) |
| 5 | Up to 5 claims per cooldown (e.g., 5 quality messages per day) |
| Unlimited | No cap (use with caution) |
How They Work Together
Example: regular_engagement has a 1-hour cooldown and 5 max claims per day.
- User posts a quality message → earns 10 RSNC
- Same user posts another quality message 30 minutes later → rejected (1-hour cooldown)
- Same user posts quality message 1 hour later → earns 10 RSNC (2nd claim)
- After 5 claims in one day → no more claims until next day
Event Configuration Options
| Field | Description | Example |
|---|---|---|
event_id | Unique identifier | weekly_challenge |
reward_amount | RSNC per trigger | 10 |
cooldown_seconds | Cooldown in seconds | 3600 (1 hour) |
max_claims | Max claims per cooldown | 5 |
detection_method | How to detect | gateway_pattern, gateway_analysis, channel_watch |
pattern | Regex (for gateway_pattern) | ^(gm|good morning) |
enabled | Active or not | true |
channels | Restrict to channels | ["#general", "#chat"] |
Syncing Between Discord & Partner Portal
Events configured via Discord commands are automatically synced to the Partner Portal, and vice versa. This means:
- Create an event in Discord → it appears in the Portal immediately
- Edit an event in the Portal → the Discord bot picks up changes on next interaction
- Delete an event in either place → it's removed from both
If you edit the same event in both places simultaneously, the most recent change wins. For complex configurations, use either the Portal or Discord commands — not both at the same time.
Event Examples by Community Type
Gaming Community
| Event | Reward | Trigger |
|---|---|---|
daily_checkin | 5 RSNC | GM/GN messages |
screenshot_share | 10 RSNC | Quality posts in #screenshots |
Creator Community
| Event | Reward | Trigger |
|---|---|---|
daily_checkin | 2 RSNC | GM/GN messages |
content_share | 15 RSNC | Quality posts in #showcase |
feedback_given | 10 RSNC | Quality messages in #feedback |
announcement_engage | 5 RSNC | Watching #announcements |
Web3 / Crypto Community
| Event | Reward | Trigger |
|---|---|---|
daily_checkin | 3 RSNC | GM/GN messages |
quality_discussion | 10 RSNC | Quality messages |
alpha_share | 20 RSNC | Quality posts in #alpha |
event_attendance | 15 RSNC | AMA/Twitter Space drops |
Related Guides
- Commands Reference — All
/configcommands - Configuration Guide — Detailed configuration options
- Drops & Events — Creating and managing drops
- Sample Programs — Complete pre-built templates