Me
What is the difference between Recurring events, one-time events and ongoing events. create a comparison table
Enki
# Comparison of Event Types
Based on the documentation, here's a comprehensive comparison of the three event types:
| **Aspect** | **One-Time Events** | **Recurring Events** | **Onboarding Events** |
|---|---|---|---|
| **Definition** | Single-instance events configured to happen at a specific time, date, and duration | Events that automatically repeat over a specified time frame without manual reconfiguration | Events triggered at the right moment for each player based on eligibility criteria (e.g., reaching a specific level) |
| **Frequency** | Occurs only once | Repeats automatically based on configured schedule | Triggered once per player when they become eligible |
| **Use Cases** | Limited, predetermined in-game activities | Events spanning multiple days or occurring periodically | Guaranteeing complete player experience at the right moment for each player |
| **Configuration** | Set a specific date and time for a single occurrence | Define recurrence pattern (cooldown-based or weekly-based) with optional occurrence limits | Set eligibility conditions and trigger events automatically when conditions are met |
| **Recurrence Pattern** | N/A | **Cooldown-based:** Specific cooldown period between occurrences (e.g., every 2 days)<br><br>**Weekly-based:** Specific days of the week (e.g., every Monday and Thursday) | N/A |
| **Timing Flexibility** | Fixed to a predetermined schedule | Fixed schedule that may not align with player eligibility | Aligned with player's individual progression and eligibility |
| **When It Runs** | At the configured date/time regardless of player status | On the configured schedule regardless of when players become eligible | When the player reaches the specified eligibility condition |
| **Key Advantage** | Simple, straightforward execution for special events | Automation without repeated manual setup | Ensures no player misses the event due to timing misalignment with eligibility |
| **Example Scenario** | Holiday event running December 25-27 | Weekly racing competition every Monday and Thursday, repeating for 8 weeks | Level 10 milestone event that triggers when a player reaches level 10 |
| **Player Assignment** | Players assigned during preload stay in event until next preload | Players assigned during preload stay in event until next preload | Players assigned when they meet eligibility criteria |
## Key Distinctions
**Recurring vs. One-Time:**
- One-time events are ideal for unique, single-occasion activities, while recurring events automate repetition without requiring manual reconfiguration each cycle.
**Recurring vs. Onboarding:**
- Recurring events follow a fixed schedule that may not align with individual player progression. Onboarding events solve this by triggering when players become eligible, ensuring they don't miss the event due to timing misalignment.
**Real-World Example:**
If a recurring event spans only 2 days and a player reaches level 10 during a cooldown period, they would miss the entire event with a recurring event configuration. An onboarding event would trigger the moment they reach level 10, guaranteeing they experience it.