Skip to content

FAQ & Troubleshooting

The plugin won’t start / database errors

Section titled “The plugin won’t start / database errors”

dLottery requires MySQL or MariaDB — there’s no flat-file mode. Check database.yml has correct credentials and enabled: true, and that the database server is reachable. The schema is created automatically on a successful connection. See database.yml.

You need Vault and an economy plugin (EssentialsX, CMI, …). Without an economy provider, purchases can’t be charged.

That’s the default cap. Grant a VIP tier permission (dlottery.tickets.iron/gold/diamond/emerald) for a higher cap, or raise the numbers under maxTickets in settings.yml.

Either no tickets were sold, or fewer than minPlayers unique players joined — in which case everyone is refunded. Lower minPlayers if your server is small. See How a Round Works.

A player won while offline — did they lose the prize?

Section titled “A player won while offline — did they lose the prize?”

No. Offline winners get a pending payout and are paid automatically on their next login. See Winning & Payouts.

I changed the ticket price but the current round still uses the old one

Section titled “I changed the ticket price but the current round still uses the old one”

Settings apply to the next round. End the current one with /lottery shuffle or /lottery reset to apply changes immediately. See Reloading.

By weighted random selection — your odds equal your share of all tickets. Buying more tickets improves your chance but never guarantees a win.

Can I run one lottery across several servers?

Section titled “Can I run one lottery across several servers?”

Point them at the same database. Just make sure only one server runs the draw timer to avoid double draws. See database.yml.

/lottery shuffle draws now; /lottery reset cancels and refunds everyone. Both need op. See Admin Controls.