Skip to main content

Server Boost Events

Configure custom rewards for Discord Nitro boosters.

Available Boost Event Types

Event TypeDescriptionWhen It Triggers
server_boostDefault boost eventEvery time someone boosts (fallback)
first_boostFirst-time boost rewardUser's first time boosting
tier_1_boostTier 1 boost rewardWhen server reaches Tier 1 (2 boosts)
tier_2_boostTier 2 boost rewardWhen server reaches Tier 2 (7 boosts)
tier_3_boostTier 3 boost rewardWhen server reaches Tier 3 (14 boosts)
boost_tier_upgradeTier upgrade rewardWhen server tier increases

Event Priority Order

The bot checks boost events in this order:

  1. Tier-specific (tier_1_boost, tier_2_boost, tier_3_boost)
  2. First boost (first_boost)
  3. Tier upgrade (boost_tier_upgrade)
  4. Generic (server_boost) - fallback

Creating Boost Events

Via Discord Commands

Create first boost event:

/config events action:create name:first_boost reward:1000 cooldown:0 max-claims:1

Create tier-specific events:

/config events action:create name:tier_2_boost reward:500 cooldown:0
/config events action:create name:tier_3_boost reward:1000 cooldown:0

Edit existing boost event:

/config events action:edit name:first_boost reward:1500
/config events action:edit name:server_boost reward:600

Toggle events:

/config events action:toggle name:first_boost enabled:true
/config events action:toggle name:server_boost enabled:false

Via Partner Portal

  1. Go to EventsCreate Event
  2. Set Event Type to first_boost, tier_2_boost, etc.
  3. Configure reward, max claims, cooldown
  4. Enable the event

Configuration Examples

First Boost + Standard Boost

Reward first-time boosters generously, then standard rewards:

First boost:

  • Event: first_boost
  • Reward: 1,000 LTZ
  • Max Claims: 1
  • Cooldown: 0

Subsequent boosts:

  • Event: server_boost
  • Reward: 500 LTZ
  • Max Claims: Unlimited
  • Cooldown: 0 (or 30 days)

Result:

  • First boost: User gets 1,000 LTZ
  • Later boosts: User gets 500 LTZ

Tier-Scaled Rewards

Scale rewards based on server tier:

EventReward
tier_1_boost200 LTZ
tier_2_boost500 LTZ
tier_3_boost1,000 LTZ

Result:

  • Tier 1 servers: Boosters get 200 LTZ
  • Tier 2 servers: Boosters get 500 LTZ
  • Tier 3 servers: Boosters get 1,000 LTZ

First Boost Detection

The bot automatically tracks whether a user has boosted before:

  • First boost: Triggers first_boost event (if configured)
  • Subsequent boosts: Triggers server_boost or tier-specific events

First boost status is permanently stored, so first_boost only fires once per user, even across server restarts.


Tier Upgrade Events

When the server tier increases (Tier 1→2 or 2→3), the boost_tier_upgrade event triggers:

  • Detected via Discord's guild events
  • Includes new tier level in event data
  • Useful for rewarding users when server hits milestones

Role Bonuses for Boosters

Combine boost events with role bonuses:

/config role-bonus role:@Server Booster multiplier:2.0 flat-bonus:10

Boosters get:

  • Boost reward (from boost event)
  • 2x multiplier on ALL rewards
  • +10 LTZ on every claim

Best Practices

Encourage First Boosts

  • Set first_boost higher than server_boost
  • Promote the first-boost bonus in your server

Reward Loyalty

  • Track boost duration
  • Consider monthly boost rewards

Combine with Role Rewards

  • Server Booster role bonuses stack with boost events
  • Create a compelling "booster package"

Communicate Clearly

  • Announce boost rewards in your server
  • Thank boosters publicly

Troubleshooting

"Boost not detected"

  1. Check event is enabled:

    /config events
  2. Verify event type is correct:

    • Must be server_boost, first_boost, or tier-specific
  3. Check bot permissions:

    • Bot needs to see boost events in the server

"First boost fired multiple times"

This shouldn't happen - first boost status is permanent. If it does:

  1. Check the event's max-claims is set to 1
  2. Contact support if issue persists

"Tier event not firing"

  1. Verify server is actually at that tier
  2. Check the tier-specific event is enabled
  3. Ensure priority order is correct (tier events take precedence)