WibuGate Docs
From invite to first verified member in five commands — plus the concepts behind IDs, trust and every slash command in the bot.
Quick Start
Five steps and your gate is live. You need the Manage Server permission to add the bot.
- Invite WibuGate. Hit any Add to Discord button on this site and authorize the bot for your server.
- Pick a language. Run
/languageand choose from 21 bot languages. - Choose the audit channel. Run
/submission-channel— this is where submissions arrive for Approve/Reject. - Set the roles. Run
/verified-rolefor the role given on approval and/unverified-rolefor the role new joiners get. - Open the gate. Run
/send-buttonin a public channel to post the verification embed. Done — new members can now verify.
Optional next steps: restrict who can submit with /submitter-roles, require a screenshot with /verify-attachment, and format nicknames with /id-nickname.
WibuGate Guide
WibuGate turns joining your server into a checkpoint: submit → audit → approve → formatted nickname + ID + role. These are the four concepts everything is built on.
Submitter roles
Submitter roles decide who can open the verification form. Configure them with /submitter-roles — if none are set, everyone can submit. Use them to keep the gate closed to bots, alt accounts or members still in a holding role.
Trusted roles & users
Trusted roles and users are your gatekeepers: they can Approve or Reject submissions in the audit channel. Only the server owner can change them, with /trust-roles and /trust-users. The same trust powers the mod action and role action tool embeds.
Verified & unverified roles
New joiners receive the unverified role (/unverified-role) so you can lock channels behind it. On approval they receive the verified role (/verified-role). Pair these two with your channel permissions and the checkpoint enforces itself.
IDs
Every approval registers a unique numeric ID for that server, appended to the member's nickname. The SORT-BY mode decides how IDs are handed out:
- RANDOMIZE — an unpredictable overlap-free ID. Free
- ARRANGE — tidy sequential IDs, lowest free slot first. Premium
- ARRANGEFILL — sequential IDs that refill gaps left by departed members. Premium
- SUBMITTER CHOICE — the member submits the digit ID they already have in Wibuku, so it matches across both platforms. Premium
When a member leaves, is kicked or banned, their ID is cleaned up automatically. /flush-id-nickname resets the counter and freed IDs if you ever want a fresh start, and /checkid looks up a member's registered ID.
Basic Setup
The recommended order for a fresh server:
/language— pick the bot's language./submission-channel— pick the audit channel where staff review submissions./trust-roles+/trust-users— choose who can Approve/Reject (owner only)./verified-role+/unverified-role— wire up the role pair./submitter-roles(optional) and/verify-attachment(require an image)./id-nickname— choose the SORT-BY mode; add/before-nicknameand/after-nicknameon Premium./send-button— post the verification embed and open the gate.
Example
With this configuration:
/before-nickname→ 愛/after-nickname→ メMA1- ID symbol → #
When member Thommas is approved with ID 192025, WibuGate applies:
愛 Thommas #192025
Command List
Every slash command in WibuGate. Badges show who can use them; owner-only commands check the server owner.
Getting started 7 commands
/language
Choose bot language (21 languages)
Free
/send-button
Send the customizable verification embed with button
Free
/ping
Check if the bot is alive
Free
/premium
Show premium features & pricing button
Free
/credits
About the developer
Free
/support-us
Links & donation
Free
/about
About WibuGate
Free
Verification & IDs 13 commands
/before-nickname
Text placed before the nickname
Premium
/after-nickname
Text placed after the nickname
Premium
/id-nickname
ID suffix settings + SORT-BY: RANDOMIZE (free) / ARRANGE / ARRANGEFILL / SUBMITTER CHOICE
Free+
/flush-id-nickname
Reset the server's ID counter and freed IDs
Owner
/submission-channel
Choose the audit/submission channel
Free
/trust-roles
Roles allowed to Approve/Reject
Owner
/trust-users
Users allowed to Approve/Reject
Owner
/verified-role
Role given on approval
Free
/unverified-role
Role given to new joiners
Free
/submitter-roles
Roles allowed to open the verification form
Free
/verify-attachment
Require an image with each submission
Free
/action-rejected
Action after reject: Kick / Ban / Do Nothing
Free
/cooldown-submitter
Cooldown minutes between submissions
Free
Lookups & integration 2 commands
/checkid
Look up a member's registered ID
Free
/integration-wibuku
Sync a Wibuku clan page in real time, auto-kick gone IDs
Premium
Trust & data 1 command
/reset
Reset all server data
Owner
Mod action tools 4 commands
/send-button-modaction
Send the Kick/Ban tool embed
Trusted
/modaction-setting
Enable kick/ban, timer, timer & punishlog channels
Free
/modaction-checker-timer
Trusted roles/users who can lift a pending kick/ban
Free
/modaction-punishable
Roles that can be punished
Free
Role action tools 4 commands
/send-button-roleaction
Send the Assign/Remove role tool embed
Trusted
/roleaction-setting
Enable role tool + log channel
Free
/roleaction-trust
Trusted roles/users for the role tool
Free
/roleaction-assignable
Roles that can be assigned/removed by ID
Free
FAQ
What is WibuGate?
A Discord bot that works as a secure nickname & ID checkpoint: new members submit via a form, trusted staff approve, and the bot applies a formatted nickname with a unique ID and verified role.
How does the WibuGate system work?
Owner sends a verification button with /send-button, a member fills the built-in form, the submission lands in an audit channel, trusted roles/users Approve or Reject, and the bot handles nickname, roles and the ID database automatically.
Why am I getting an ID for entering a server?
IDs make member tracking overlap-free. SUBMITTER CHOICE suits Wibuku clans (it matches your Wibuku digit ID); RANDOMIZE / ARRANGE / ARRANGEFILL suit any community.
How do I reset my server's data?
Server owner runs /reset. Everything (settings, IDs) is wiped for that server only.
What are Visibility Modes?
Per-feature permission control: who can submit, who can approve/reject, who can use the mod action and role action tools — each is configured separately.