A giveaway picker generator for organisers: Woobox's picker and two Discord bots
A giveaway picker generator such as Woobox's social winner picker needs a sign-in, a connected social platform and a chosen post. The organiser then chooses comments, likes or both, sets eligibility filters and clicks Pick a winner, and the free plan covers the whole sequence without a credit card. DiscordCraft's tutorial for GiveawayBot starts on Discord with a permission check instead: Manage Server or Administrator.
Prepared by ContestsOnline editorial desk — Revised
Who can host a giveaway through a bot: Manage Server or Administrator
Hosting a giveaway through a Discord bot is gated by a permission before it is gated by a command. DiscordCraft's tutorial for GiveawayBot places the check ahead of setup: the organiser confirms Manage Server or Administrator permissions first, and the bot comes second.
MSK Scripts applies the same kind of gate at another point. Its getting-started page says the server choice lists only servers where the manager holds Manage Server and the bot is present, so a server the bot has not joined never appears, and neither does one where the permission is missing.
Hosting has a second meaning here. MSK Scripts says its official public instance of the Giveaway bot needs no hosting, no database and no setup, which leaves the software side with the provider. What the organiser hosts is the giveaway itself: the channel, the conditions and the rules it runs under.
Woobox's picker: three choices before one click
Woobox's winner picker page describes the social picker as a short sequence. The organiser signs in to Woobox, connects the social platform the giveaway was posted on (Woobox names Facebook, Instagram and YouTube), and picks the post. The same page puts the social winner picker on the free plan, with no credit card, so the account needed is an ordinary sign-in.
Three choices shape the result. The post fixes where the entries live. The pool is comments, likes or both, and it has to match the entry method the rules announce, so a rule that asks for comments is paired with a comments pool. The eligibility filters then narrow the pool to the entries the rules accept.
Each exclusion the rules announce needs a filter that applies it, and the organiser confirms in the picker that such a filter exists before promising the exclusion to entrants. An exclusion the rules state but no filter applies has to be checked by hand. A filter that removes entries the rules never mention invites a dispute.
Only then does the organiser click Pick a winner. That click is the whole draw as Woobox's page describes it, which is why the settings before it decide the result.
A fair draw: equal chances unless the rules say otherwise
Fairness in a draw is a property of the pool. The button only reads it. When every eligible entry holds one chance the draw is equal; when some entries hold more, the draw is weighted, and the published rules have to say for whom and by what rule.
MSK Scripts builds weighting into the tool: its entry conditions include blocked roles, required roles and bonus entries per role. A blocked role keeps its members out of the draw, a required role limits the draw to its members, and a role with bonus entries gives its members extra chances. All three change the pool before anyone draws, so all three belong in the published rules as well as in the bot's settings.
A setup page shows how to arrange a draw. A promise that the draw is random or verifiable needs the tool's own words behind it, so an organiser who wants to make that promise quotes the tool's page exactly and otherwise limits the promise to what the rules fix: who is eligible, what counts as an entry, and which roles carry more.
An auditable draw: the inputs written down before the click
A draw from a giveaway picker generator is auditable when someone who was not there can rebuild the pool from what the organiser published. That takes the inputs on record before the click, because a setting described after the result says nothing about the draw that produced it.
And the record is the organiser's to keep: the published rules, plus a dated copy of each setting as it stood at the click.
- Source: the Woobox post and its platform, or the Discord server and the channel where the command was run.
- Pool: comments, likes or both on Woobox; members who joined by the button on MSK Scripts' bot.
- Conditions: Woobox's eligibility filters, or MSK Scripts' blocked roles, required roles and bonus entries per role.
- Operator: the account that ran the pick or the command, holding Manage Server or Administrator on Discord.
- Timing: the moment of the click or the command, written in the rules' own time zone.
Platform rules and disqualification: conditions exclude before the draw
Disqualification happens at two points: a condition excludes an entry before the draw, or the organiser's rules drop a winner after it. Woobox's eligibility filters and MSK Scripts' blocked and required roles belong to the first point, and the second belongs to the rules.
Limits also come from outside the tools. Discord controls which members hold Manage Server or Administrator, which is why that permission comes first, and each social network sets its own terms for promotions on its posts. The organiser reads those terms on the network itself, because a picker that reads a post does not change the network's terms for running one.
Whether the organiser disqualifies a winner who fails a condition, and whether a new draw follows from the same pool, is for the rules to state before entries open. A rule added after the result reads as a change of terms.
A required role checks the role, so the organiser checks the account
On MSK Scripts' bot, a required role proves that the member holds the role and nothing more. Whether the account behind it is genuine stays a question for the organiser, who checks the winner against the rules before announcing.
Woobox's eligibility filters work the same way: a filter checks the condition it names. Nothing in a giveaway picker generator's click or in a bot's slash command vouches for the result by itself, so the organiser's own check of the winner settles whether the entry stands.
| Tool | Needed before it runs | What the organiser sets |
|---|---|---|
| Woobox social picker | Sign-in, a connected social platform and one chosen post; the free plan, no credit card | Comments, likes or both; eligibility filters; then Pick a winner |
| GiveawayBot (DiscordCraft) | Manage Server or Administrator permissions; Add to Discord, select the server, authorize permissions | The /gstart command, run in the channel where giveaways are announced |
| MSK Scripts Giveaway bot | Manage Server held by the manager and the bot present; the public instance needs no hosting, database or setup | The /gcreate command; blocked and required roles; bonus entries per role; one-click joining |
Procedure
-
Confirm Manage Server or Administrator first
DiscordCraft's tutorial for GiveawayBot makes this the first item, ahead of setup. A server manager on MSK Scripts' bot needs the same standing, because its server choice lists only servers where Manage Server is held and the bot is present.
-
Invite the bot to the server
For GiveawayBot, DiscordCraft's tutorial has the organiser click Add to Discord on the bot's site, select the server and authorize permissions. MSK Scripts' getting-started page points to its official public instance of the Giveaway bot, which needs no hosting, no database and no setup.
-
Open the giveaway with the bot's command
GiveawayBot's command, per DiscordCraft, is /gstart, run in any channel where giveaways should be announced. On MSK Scripts' Giveaway bot a server manager runs /gcreate to open a giveaway. The channel and the command are the public side of the giveaway, so the published rules name them.
-
Set the entry conditions
MSK Scripts' getting-started page has the organiser set blocked roles, required roles and bonus entries per role at this point. Each one changes who is in the draw or how many entries a member holds, so each needs a matching line in the rules before entries open.
-
Let members join by button
Members join an MSK Scripts giveaway with a single button click. The roles set in the previous step decide who can use that button to enter.
-
Publish the conditions before entries open
The permission, the command, the channel and the roles are fixed before the first entry arrives, and the published rules name each one. A condition added later changes the pool that members already joined.
Readers ask
How to use giveaway bot on Discord?
Using GiveawayBot, per DiscordCraft's tutorial, starts with Manage Server or Administrator permissions and ends with /gstart in the channel where giveaways are announced. Between the two, the organiser clicks Add to Discord on the bot's site, selects the server and authorizes permissions. MSK Scripts' Giveaway bot opens a giveaway with /gcreate instead.
How to host a giveaway on Discord with giveaway bot?
A server manager hosts the giveaway by running the bot's command: /gcreate on MSK Scripts' Giveaway bot, /gstart on GiveawayBot. The organiser's part is the channel, the conditions and the published rules, since MSK Scripts' public instance runs without hosting on the organiser's side.
Does the Discord giveaway bot from MSK Scripts need hosting or a database?
No. MSK Scripts' getting-started page describes its official public instance of the Giveaway bot as needing no hosting, no database and no setup. What the organiser still needs is the Manage Server permission and the bot present on the server.
How do members join an MSK Scripts giveaway?
Members join with a single button click, according to MSK Scripts' getting-started page. The entry conditions the manager set, blocked roles and required roles, decide who can use that button to enter.
What disqualifies an entry in a bot or picker giveaway?
A condition the organiser set disqualifies an entry: a blocked role, or a required role the member lacks, on MSK Scripts' bot, or an eligibility filter on Woobox's picker. Dropping a winner after the draw rests on the organiser's published rules and the platform's terms, not on the tool.
What makes a draw from a giveaway picker generator look fake?
A draw looks fake when its pool and conditions cannot be checked: a post or channel never named, filters or roles the rules never mentioned, or settings changed after entries opened. The published rules and a dated copy of each setting make a draw checkable; the click or the command alone does not.
Notes and sources
- Woobox. woobox.com/pickawinner.
- Woobox. woobox.com/pickawinner.
- discordcraft.com. discordcraft.com/blog/discord-giveaway-bot-tutorial-host-and-automate-giveaways.
- discordcraft.com. discordcraft.com/blog/discord-giveaway-bot-tutorial-host-and-automate-giveaways.
- docu.msk-scripts.de. docu.msk-scripts.de/discord/discord_giveaway/getting-started/.
Nothing on this page is legal advice: whether a giveaway is lawful where it runs and where entrants live is a question for a lawyer or attorney. A picker or a bot cannot make a draw lawful, cannot certify how a winner was selected, and does not override Discord's or a social network's own terms. The organiser's published rules, not the tool, decide who is eligible and what follows when a winner fails a condition.
Woobox's user terms require entrants to agree to the organiser's official rules, so any limit on bought or incentivised votes depends on the particular contest. Walmart's Associate Talent Search rules prohibit paying for votes and let Walmart void fraudulent votes or disqualify the entrant. The platform's terms and the organiser's rules are two documents, and a disqualification is decided under the second.
Woobox lists three warning signs of bought votes: many votes from one IP address, votes from people in different countries and regular voting intervals. Award Force says its platform detects and blocks automated or scripted voting and rate-limits rapid voting. Ordinary participation is uneven in time and independent in origin, so it shows none of those patterns; this describes how checks read a count and is not a method for passing one.
In the United States, the FTC says a sweepstakes cannot require a purchase to enter, and California says a sweepstakes must offer a way to enter without cost. Those rules concern sweepstakes entry, not votes: whether a contest allows paid votes is written in its own rules, and ViralSweep even lets organisers configure Pay to Vote. Contests whose rules bar outside votes are refused, and so are political ballots.
Once voting closes, a refund applies where votes ordered for a contest never appear in the count the contest itself displays. ViralSweep says its protections may silently flag and block a vote, and Woobox says votes from IP addresses it has flagged as fraudulent do not count even when the voter appears to have succeeded, so the displayed count is the test. An organiser's ruling or a disqualification is never refunded, and neither is an account ban such as the permanent one Gleam says a breach of its terms may bring.