Lottery: Jackpot Draw Setup and Ticket Management

Run an automated hourly lottery with a growing jackpot pool, configurable ticket limits, server-wide countdown announcements, and Discord webhook alerts.

The LiricCasino lottery runs on a fully automated timer — no staff intervention required. Players buy numbered tickets for a flat price, a portion of every sale feeds the jackpot pool, and the server draws a winning number on a configurable interval. If nobody holds the winning number, the jackpot rolls over and keeps growing until someone wins. When there are multiple winners, they split the jackpot equally.

How the Jackpot Works

Every ticket purchase contributes 50 % of the ticket price directly to the jackpot pool (configurable via jackpot-contribution in config.yml). The pool starts at a minimum floor of $50,000 and accumulates across draws until a winner is found. After a win, the jackpot resets to the configured floor value.

The jackpot and all active tickets are persisted to lottery.yml in the plugin data folder. The jackpot survives server restarts.

Draw Cycle

1. Countdown begins

   When the plugin starts (or after each completed draw), a 60-minute countdown begins automatically. The interval is configurable via draw-interval-minutes in config.yml.

2. Server-wide announcements

   The server broadcasts countdown messages to all online players at these intervals before the draw:

   Time Remaining	Announcement
   1 hour	Early warning
   30 minutes	Reminder
   10 minutes	Urgency alert
   1 minute	Final call
   30 seconds	Imminent
   10 seconds	Countdown

3. Winning number drawn

   At zero, the server picks a random number between 1 and 1,000 (configurable via number-range). Every ticket held by any player has exactly one number assigned at purchase.

4. Winners determined

   All tickets whose number matches the draw win. If multiple players hold winning tickets, the jackpot is split equally among them.

5. Discord webhook fires

   When there is at least one winner, a Discord webhook notification is sent automatically with the winner name(s) and prize amount.

6. Reset and repeat

   All tickets are cleared, the jackpot resets to the floor value if it was claimed, and a new 60-minute countdown starts immediately.

Buying Tickets

Run /lottery (alias: /loteria) to open the ticket purchase GUI. Select how many tickets you want — up to your remaining daily limit. Each ticket costs $5,000 by default and is assigned a unique random number at the moment of purchase. You can hold a maximum of 5 tickets per draw period.

Buying multiple tickets increases your coverage of the 1–1,000 number range. With 5 tickets you cover 0.5 % of all possible numbers.

Ticket numbers are randomly assigned and cannot be chosen. There is no guarantee two tickets will have different numbers, though collisions are statistically unlikely with a 1,000-number range.

Daily Use Limits

Default Players

Up to 5 tickets per day.

VIP Players

Up to 10 tickets per day (casinoliric.uses.vip permission).

Admins with casinoliric.uses.admin have unlimited daily ticket purchases. Limits are set under lottery.uses in config.yml.

Commands

Player Commands

Command	Description
/lottery	Opens the lottery ticket purchase GUI
/loteria	Alias for /lottery

Admin Commands

Command	Description
/lottery forcestart	Immediately triggers the draw, bypassing the countdown
/lottery give <player> [amount]	Gives the specified player free lottery tickets without charging them

Configuration Reference

Lottery settings

lottery:
  active: true
  ticket-price: 5000.0
  max-tickets-per-player: 5
  draw-interval-minutes: 60
  number-range: 1000
  jackpot-start: 50000.0
  jackpot-contribution: 0.5   # 50 % of each ticket price

lottery:
  uses:
    default:
      max-uses-per-day: 5
    ranks:
      vip:
        permission: "casinoliric.uses.vip"
        max-uses-per-day: 10
      admin:
        permission: "casinoliric.uses.admin"
        max-uses-per-day: -1  # unlimited

Using /lottery forcestart clears all current tickets and resets the jackpot after paying out. Use it carefully in production — it cannot be undone.