Admin guide

Last updated: 28 September 2026

Everything you need to set RecheBot up on your server and run CS2 skin giveaways: from inviting the bot to delivering the prize and handling your community's privacy requests.

Command names are in Spanish. If your Discord is set to English you may see translated names instead, for example /config ver appears as /config view. In the tables, admin means anyone with Discord's "Manage Server" permission or the configured admin role, and mod means any admin or anyone with the configured mod role. Discord hides staff commands from members without the default permission; you can change this in Server Settings, Integrations, RecheBot.

Add the bot

Use the official invite link: add RecheBot to Discord. Discord will ask you to pick a server and confirm these permissions:

PermissionWhat it is used for
Manage RolesCreating the /setup roles and assigning the Winner, Member and "Under review" roles and the roles in role panels.
Manage ChannelsCreating the /setup categories and channels with their permissions.
View Channels, Send Messages, Read Message HistoryPosting giveaways, announcements and notices, and updating the giveaway message when it closes.
Embed LinksShowing giveaways and notices as rich messages with a link to their transparency page.
Attach FilesSending files, such as the data export from /privacidad ver.
Manage MessagesDeleting messages with dangerous links if you turn on the anti-scam guard.
Mention @everyone, @here and All RolesPinging the staff role, for example on middleman requests.
  • The bot does not ask for "Timeout Members". You only need it if you set the anti-scam guard to the timeout action; without it the guard deletes the message but does not time the user out.
  • RecheBot's role must sit above the roles it assigns. If it does not, move it in Server Settings, Roles.

By adding RecheBot you accept the Terms of Service and, on behalf of the server, the Data Processing Agreement. From then on your server is the data controller for your community's data and RecheBot acts as processor.

First setup

Server template

Run /setup preview first: it shows what would be created without changing anything. Then /setup aplicar creates:

  • Roles: Admin, Mod, Winner 🏆, Member and Unverified.
  • Channels: INFO (rules, announcements, giveaways), COMMUNITY (general, clips, memes), CS2 (trade talk, find a team and two voice channels) and STAFF (staff and bot logs, visible to staff only).
  • A rules panel with a verify button that grants the Member role.
  • The bot's channel and role configuration, ready to use.

It checks that the bot has the permissions it needs before starting. It is safe to run again: it reuses what already exists instead of duplicating it. If you already have your own rules channel, /panel-verificacion canal rol-miembro posts just the panel with the verify button.

Role and channel names are created in the server's language, so they may differ from the ones listed here.

Settings

CommandWhoWhat it does
/config verAdminShows language, channels, roles and the link to your server's public giveaways page.
/config canalAdminAssigns a channel to a function: welcome, announcements, giveaways, logs, rules or levels.
/config rolAdminAssigns a role to a function: admin, mod, winner or member.
/config idiomaAdminLanguage (Spanish or English) of public messages: giveaways, announcements and notices.

The server language only affects what everyone sees. Private command replies follow the language each person uses in Discord.

Your server's public giveaways page is https://rechebot.rechedev.cloud/sorteos?guild=<server id>. /config ver gives you the exact link to share.

Before a giveaway

You are the organizer of the giveaway; RecheBot is the tool. Before opening one:

  • Publish your rules in the server, for example in the rules channel. There is a giveaway rules template ready to adapt.
  • Make the age requirements clear: entrants must be 14 or older and winners 18 or older to receive the prize. You check this before delivering it.
  • Have the prize in your Steam inventory. You deliver it by hand with a trade offer. RecheBot never holds or sends skins.
  • Any taxes on the prize are the organizer's responsibility. The rules template has an indicative tax section.

Run a giveaway

Create it

/sorteo crear posts the giveaway with an "Enter" button. Options:

OptionWhat it does
premioRequired. Prize: the skin name, for example "AK-47 | Redline FT".
duracionRequired. Duration, for example 30m, 12h, 2d or 1d12h, up to 365 days.
ganadoresNumber of winners, 1 to 20. Default 1.
canalChannel to post in. Default: the configured giveaways channel.
imagenURL of an image of the skin.
valorEstimated value in euros.
rol-requeridoOnly members with this role can enter.
dias-minimosMinimum days in the server to enter.
cuenta-steamRequires Steam verification and allows one entry per Steam account. See Steam verification.
antiguedad-steam-minimaMinimum age of the Steam account, in days.

If an option is not available at that moment, the bot tells you and does not create the giveaway. Requirements are checked on entry and again at close.

Each person enters once. There are no coins, extra tickets or paid entries, and you cannot require any purchase to enter.

Manage it

CommandWhoWhat it does
/sorteo listaModLists active giveaways with their ID.
/sorteo terminarModCloses an active giveaway now and picks winners.
/sorteo cancelarModCancels an active giveaway without picking a winner.
/sorteo rerollAdminPicks a new winner for an ended giveaway. It asks for a reason, which is posted in the logs channel. By default it replaces the most recent undelivered winner; use usuario to choose who. Up to 10 per giveaway. The replaced winner stays visible on the public page, marked as replaced.
/sorteo entregadoAdminMarks the prize as delivered and announces it in the giveaway channel.
/sorteo ganadoresAdminPrivately shows the giveaway winners, their Trade URL and whether the prize has been delivered.

In every command you can pick the giveaway from a list or type its ID, which is shown on the giveaway message.

How the winner is picked

When the giveaway is created, RecheBot generates a secret seed and publishes its SHA-256 hash. At close it reveals the seed and picks the winners from it and from the entries that still meet the requirements. Nobody, neither you nor RecheBot, can change the outcome without it showing. Anyone can check it on the giveaway page; the giveaway documentation explains how.

Deliver the prize

  1. The winner gets a direct message asking for their Steam Trade URL (they can also save it beforehand with /trade-url). If you configured a winner role, they get it.
  2. The logs channel shows a "manual delivery pending" notice and another one when the winner saves their Trade URL. If their direct messages are closed, the notice says so: ask them to use /trade-url.
  3. You check the winner is 18 or older and send the skin with a Steam trade offer.
  4. You run /sorteo entregado. Winners who have not given their Trade URL yet stay pending.

If the winner does not reply within the period in your rules or does not meet the requirements, use /sorteo reroll with the reason.

Steam verification

CommandWhoWhat it does
/steam vincularEveryoneSends a single-use link, valid for 10 minutes, to sign in on the official Steam website and prove the account is theirs.
/steam verEveryoneShows whether an account is verified or only derived from its Trade URL.
/trade-urlEveryoneSaves the Trade URL to receive prizes.

A Trade URL does not prove that the Steam account belongs to whoever shares it. That is why cuenta-steam requires verification through Steam sign-in and also rejects a second entry with the same verified Steam account. So several Discord accounts from the same person with a single Steam account count as one entry.

It does not guarantee that each person has only one Discord or Steam account. Combine it with antiguedad-steam-minima or dias-minimos to make things harder for new accounts.

Community tools

Moderation

CommandWhoWhat it does
/antiscam configAdminTurns the anti-scam guard on or off and chooses what it does: log (notice only), delete (deletes the message) or timeout (deletes and times the user out for the minutes you set). Off by default.
/antiscam dominiosAdminAdds, removes or lists blocked domains in your server.
/antiscam testAdminTests the detector on a text without deleting anything.
/scammer flagModPuts a member under review, with evidence or a reason.
/scammer unflagModRemoves the review and the role.
/scammer listaModLists members under review.

The guard also warns staff when someone joins or changes their name to imitate a staff member. Its notices go to the logs channel.

Putting someone under review gives them the public, neutral "⚠️ Under review" role ("⚠️ En revisión" on Spanish servers). The reason is visible to staff only, in the logs channel, and the flag belongs to your server only: it is never shared with other servers. As data controller you are responsible for how it is used: flag only with evidence, write the minimum reason needed and remove the flag when it is no longer justified.

Community

CommandWhoWhat it does
/vouchEveryoneLeaves a vouch with a visible comment after a trade. One per person being vouched for, and the giver must have been in the server for at least 7 days.
/perfilEveryoneProfile with level, reputation and trader status. If the account is under review, it says so in neutral terms.
/mmEveryoneOpens a thread with the other member and pings staff to act as middleman for a trade.
/nivelEveryoneLevel and XP, earned by chatting.
/leaderboardEveryoneServer activity leaderboard.
/trade-urlEveryoneSaves the Steam Trade URL to receive prizes.
/anuncio programarAdminSchedules an announcement for later, in the channel you choose. Also lista and cancelar.
/roles-panel crearAdminPosts a panel with buttons so each member can add or remove up to 5 roles.

Your privacy duties

As controller of your community's data:

  • Inform your members: publish your rules and link the Privacy Policy.
  • Self-service: any member can use /privacidad ver to view and download their data, and /privacidad borrar to delete it across all servers. In giveaways that have already closed, their entry is kept but their ID is shown as [eliminado] (deleted), so they remain verifiable.
  • Requests sent to you: point people to /privacidad first. Whatever it does not cover, such as correcting a vouch or removing a review flag, your staff handles. You have one month to reply. If you need help, write to rechedev@hotmail.com.
  • Review flags: /privacidad borrar does not remove a review flag. If someone disputes it, review it and, if appropriate, use /scammer unflag.
  • Free text: do not write sensitive data in reasons, comments or announcements.
  • If you remove the bot: your server's data is deleted 30 days after you kick it. If you add it back before then, you get your configuration back.

The details are in the Data Processing Agreement.

Support

Support is by email only: rechedev@hotmail.com. Include your server ID and, if it is about a giveaway, its ID.