Giveaways
Create scheduled button-entry giveaways and select winners automatically.
How it works
The giveaway manager publishes an entry message, accepts button entries, closes at the scheduled time, and selects the configured number of winners.
Before you start
- Choose a channel where Airwavy can view, send, embed, and read message history.
- Decide the prize, duration, and number of winners before publishing.
Configure it
- Open Giveaways in the dashboard and start a new giveaway.
- Enter the prize, destination channel, end time, and winner count.
- Review the values carefully, publish, and confirm the entry button works.
Entry and scheduling
- Giveaways can run for one minute through 30 days and select from one through 50 winners.
- A member's entry is recorded once, and the button confirmation is private to that member.
- Premium giveaways can start after a scheduled delay, require a role, and use a custom presentation.
- Airwavy checks current server membership and any required role again when selecting winners.
Bonus entries and rerolls
- Premium can configure up to ten bonus roles, each worth one through 50 additional entries.
- Weighted winner selection does not select the same member twice in one draw.
- A reroll prefers eligible members who were not already selected while retaining the prior result for staff context.
- If nobody is currently eligible, Airwavy preserves the previous outcome instead of inventing a winner.
Expected result
- Members can enter through the giveaway message button.
- At the scheduled end, entries close and winners are selected automatically.
Common errors
The giveaway does not close on time
Check the dashboard's recorded end time and the public status page. Do not delete the original giveaway message while it is active.
Saved changes do not take effect
Reload the feature page and confirm the saved values. Then verify that the selected Discord channel or role still exists and that Airwavy can access it.
Discord reports missing permissions
Check the permission on both the server role and the target channel. Channel overwrites and role hierarchy can deny an action even when the server-level permission is present.