A giveaway can introduce new members to a community, reward regulars, or bring attention to an event. But the prize alone does not make a giveaway successful. Members also need clear rules, a simple way to enter, and confidence that winners are selected fairly.

Strom manages that full lifecycle: creation, eligibility, entry, announcements, winner selection, direct messages, and rerolls. Staff can configure giveaways from the dashboard, while members can participate from Discord.

What a well-run giveaway needs

Before creating anything, answer five questions:

What is the prize?
Who is eligible?
When does entry close?
How many winners will be selected?
How will the result be announced and fulfilled?

Ambiguity causes most giveaway disputes. Put important conditions in the description instead of adding them after entries have started.

Create a giveaway in Strom

The Strom dashboard lets you set an internal title, announcement channel, start behavior, end date, entry slots, winner count, description, and the Discord embed members will see.

You can also create immediately with:

/giveaway create <title> <channel> <duration> [winners] [slots] [description]

Command-created giveaways start immediately. Duration must be between 2 minutes and 24 weeks. A slot value of 0 means entry is unlimited; otherwise, the giveaway closes to new participants when all slots are filled.

The server's plan controls how many giveaways can be scheduled or running at once.

Choose eligibility rules that match the goal

Strom can restrict entry with:

required roles
excluded roles
a minimum Discord account age
a minimum time in the server
an option that prevents a member from joining multiple active giveaways

These controls serve different purposes. A member-only giveaway may require a verified role. A loyalty reward may require longer server membership. An account-age minimum can make quick giveaway abuse harder.

Avoid adding restrictions just because they are available. Every rule reduces the eligible audience and should support a clear reason.

Make entry easy to understand

Members can join from giveaway controls in Discord or use /giveaway join <identifier>. They can withdraw with /giveaway leave <identifier>, inspect an event with /giveaway status <identifier>, and browse active or inactive events with /giveaway list.

The list view is interactive, so members can discover giveaways and join or leave without searching through old announcements.

Use one recognizable announcement channel for most giveaways. If events are spread across many channels, a list becomes even more important.

Understand the giveaway lifecycle

Strom tracks distinct giveaway states, including scheduled, pending, active, paused, ended, and cancelled. That makes it possible for staff to prepare an event, pause it when necessary, and review completed giveaways without treating every record as live.

When an active giveaway reaches its end, Strom selects unique winners from valid entries. Members who have been blacklisted or are no longer in the server are excluded from the draw. Strom updates the original announcement, posts the completion result, and attempts to direct-message each winner.

A blocked direct message does not erase the public result, so staff can still contact a winner through the server.

End, decide, and reroll responsibly

Some giveaways need to end early. The host or server owner can use /giveaway decide <identifier> to select winners immediately and publish the result.

If an ended giveaway needs a replacement winner, a member with Manage Server can use /giveaway reroll <identifier>. Rerolls should have a documented reason, such as a winner being ineligible under the original rules or failing to claim the prize within the stated period.

Do not silently reroll because a preferred participant did not win. Trust is more valuable than a short-term spike in entries.

Customize the announcement without hiding the rules

Strom supports custom giveaway content and embeds with giveaway-specific replacement variables. Use the visual design to make the prize and deadline easy to scan, but keep the rules readable.

A strong announcement usually includes:

the exact prize
closing date and time, including timezone
number of winners
eligibility requirements
how to enter
claim deadline
any geographic or platform restrictions
who members should contact with questions

Do not rely only on an image for critical details. Text is easier to search, translate, and review later.

Key giveaway commands

Command	Purpose
`/giveaway list <active\|inactive>`	Browse giveaways and use interactive entry controls
`/giveaway create ...`	Create and immediately start a giveaway
`/giveaway join <identifier>`	Enter an eligible giveaway
`/giveaway leave <identifier>`	Withdraw an entry
`/giveaway status <identifier>`	Check giveaway details and status
`/giveaway decide <identifier>`	End early and draw winners as the host or owner
`/giveaway reroll <identifier>`	Draw again after a giveaway has ended

The same workflows are available through Strom's prefix-command support where enabled.

Protect fairness and reduce abuse

Publish all eligibility rules before opening entries.
Use role or membership-age requirements only when relevant.
Set an account-age minimum for higher-risk public giveaways.
Avoid changing the winner count after members have entered.
State how long winners have to claim a prize.
Record why any reroll happened.
Never ask winners for passwords, recovery codes, or payment to receive a prize.

If a prize has monetary value, also check the laws, platform rules, age requirements, and tax obligations that apply to the organizer and participants. Strom manages the Discord workflow; it does not replace those responsibilities.

Common giveaway problems

A member cannot join

Check whether the giveaway is active, has open slots, and allows the member under its role, account-age, membership-age, blacklist, and multiple-participation settings.

The giveaway cannot be created

Verify the duration and required fields, then check whether the server has reached its plan's concurrent giveaway limit.

A winner did not receive a direct message

The member may block server direct messages or Strom. Use the public result to contact them and follow the claim process stated in the original rules.

A live giveaway cannot be deleted

End or cancel the live event through its available controls first. Strom protects active giveaway records from being casually removed mid-event.

Use prizes to strengthen the community

The best giveaway is connected to the server's purpose. Reward tournament participation in a gaming server, celebrate a creator milestone, or give active contributors early access to an event. Clear rules and reliable automation make the prize feel like part of the community—not a temporary shortcut to inflated member numbers.