Giveaways
Create free giveaways and review their recorded results.
Before you start
Dashboard changes are currently restricted to the configured Yume owner. Sign in with Discord and choose Yume. Public documentation is available to everyone.
Vault needs access to the giveaway channel and permission to post and update the announcement.
Set it up
- Check feature availability: Open General settings → Feature availability. Enable this module, save, then use Apply feature availability to update the running bot.
- Prepare a giveaway: Open Create a free giveaway. Choose a channel, prize, duration, winner count and optional message requirement.
- Review before posting: Check the visual preview and exact confirmation. Confirming creates a real Discord post; use Giveaway history to inspect its result.
Check it works
Check the post and its receipt. Winners are selected when the giveaway ends. An uncertain announcement needs inspection rather than another submission.
How it works
Duration is from 1 minute to 30 days. Choose 1 to 10 winners and 0 to 1,000 qualifying messages after posting. Discord also accepts durations such as 30m, 2h or 1d.
A giveaway can have a message requirement counted after it starts. Explain any requirement clearly in the announcement.
Scheduling and drawing are handled by the implemented giveaway system. The website does not invent live entry totals or winners.
Create, inspect and reroll
Entry is free. Preview the prize, channel, duration and requirements before confirming the post. Review recorded entries, selected winners and delivery outcomes. Winners are saved before announcement; an uncertain announcement never automatically selects or announces again. The workspace shows the latest 100 entrants and 50 replacement selections. Selection checks current server membership and excludes bots and previous winners.
Staff actions, privacy and refresh
Staff actions require Discord sign-in and current authorized server access. Recovery sign-in supports settings only. Review the exact confirmation before submitting; changes and partial deliveries have a request receipt.
An uncertain outcome is not a confirmed failure. Check the receipt, record and Discord before acknowledging it. Acknowledgment does not retry an effect or remove the server’s duplicate-action protection. Safe notes and other records remain usable; unresolved effects require owner investigation.
Active workspace pages refresh every 30 seconds and Overview every minute while visible. Refresh pauses for drafts or focused controls. Manual refresh preserves edits; a changed staff record requires explicit review before keeping its draft. Private drafts remain in this tab and are not saved in browser storage.
Use Save after editing. If a change is marked as requiring a restart, it is stored but will only apply when Vault next starts. Refresh after the restart to check the pending indicator.
If something is not working
Check that the feature is enabled, that the selected channel or role still exists, and that Vault has the required Discord permissions. A higher role cannot be assigned or moderated by a bot below it.
If the dashboard cannot load or save, keep your edits on the page, check Status, then try again. An expired session requires signing in again. Do not repeatedly submit an action whose result is uncertain.