Quick answer: WizeBot's command list and syntax change over time, so use the live command list in WizeBot's official documentation rather than copying an old “100+ commands” article. Start with a few information commands, set permissions and cooldowns, then add polls, giveaways, counters, or integrations only when the channel needs them.

This guide was substantially rewritten in July 2026 from WizeBot's current documentation. It intentionally does not reproduce a giant static command dump that becomes stale.

Find the current WizeBot command list

Open WizeBot's official documentation and choose List of commands. The same documentation covers text tags, multi-text responses, aliases, permissions, protection rules, polls, predictions, giveaways, song requests, virtual currency, screen overlays, integrations, and scripted commands.

Check whether the command is global, custom, restricted, disabled, or tied to an optional module before using it in chat.

Set up WizeBot carefully

  1. Visit the official WizeBot site and authorize the correct Twitch channel.
  2. Read the requested Twitch permissions.
  3. Give the authentic WizeBot account only the moderator access required by enabled features.
  4. Disable modules and global commands you will not use.
  5. Create a small set of custom commands.
  6. Test as owner, moderator, subscriber, and normal viewer where permissions differ.

Never share a Twitch password, stream key, OAuth token, webhook secret, or browser cookie in a command response or support conversation.

Useful starter commands to create

The exact creation syntax and tags must come from the current WizeBot interface, but these response patterns are broadly useful:

Rules

!rules — Be respectful, no spoilers or self-promotion, and follow moderator requests. Full rules: https://example.com/rules

Schedule

!schedule — Live Tuesday and Thursday at 19:00 UTC. Updates: https://example.com/schedule

Social or community link

!discord — Join the community: https://example.com/discord

Game settings

!settings — Current game settings and gear: https://example.com/setup

Use a direct, maintained destination. Do not place affiliate claims, shortened mystery links, or expired sponsor messages in unattended commands.

Permissions and cooldowns

  • Everyone: harmless information such as schedule or rules.
  • Subscribers/regulars: engagement commands that could become noisy.
  • Moderators: counters, polls, giveaways, or operational responses.
  • Owner: sensitive configuration and account-level actions.

Start informational commands around a 20–30 second cooldown and increase it if chat becomes repetitive. A bot response should not bury human conversation.

Text tags and dynamic responses

WizeBot uses tags to insert dynamic values into messages. Its documentation includes general text tags, multi-text management, aliases, authorization through URLs, and JavaScript scripted commands.

Dynamic commands have more failure modes than static ones. Confirm:

  • the tag still exists and has the expected format;
  • user-provided text is handled safely;
  • an external URL is HTTPS and controlled by a trusted party;
  • timeouts and empty responses fail cleanly;
  • private data is never returned to public chat.

Polls, predictions, giveaways, and virtual currency

WizeBot documents modules for polls, predictions, draws, automatic giveaways, betting, shops, and virtual currency. Enable them only with clear rules.

For a real prize, publish eligibility, geography, age, start and end times, selection method, sponsor details, and other legally required terms. A bot choosing a random chatter is not a complete giveaway policy.

Song requests and media

A working song-request command does not grant music rights. The broadcaster remains responsible for what appears in the live stream, VOD, and clips. Restrict requests, moderate the queue, and use content you are licensed to broadcast.

Protection settings

WizeBot's current documentation includes permit systems and user restrictions. Coordinate these with Twitch AutoMod and channel verification settings:

  • block recurring spam without blocking ordinary language;
  • whitelist only trusted domains;
  • exempt moderators carefully;
  • write a clear response explaining what the chatter must change;
  • review false positives after real streams.

Troubleshooting WizeBot commands

  • No response: confirm the bot joined, the command/module is enabled, and cooldown expired.
  • Permission denied: inspect the command's user restriction and the caller's Twitch role.
  • Wrong text: review tag syntax, aliases, multi-text options, and cached values.
  • Link missing: Twitch AutoMod or bot protection may be filtering the URL.
  • Duplicate response: another bot may own the same command.
  • Integration fails: reconnect only through the official authorization flow and remove stale access.

Frequently asked questions

Where is the full WizeBot command list?

Use the “List of commands” section in WizeBot's official documentation. A copied third-party list may contain removed or renamed commands.

Can moderators create WizeBot commands?

WizeBot documents command creation from chat and permission controls. Enable that access only for trusted moderators and verify the current syntax in the official guide.

Can WizeBot use custom scripts?

The documentation includes JavaScript scripted commands and APIs. Scripted commands should validate input, protect secrets, restrict network destinations, and fail safely.

Should I enable every command?

No. A smaller command set is easier to remember, secure, and maintain. Add a command when viewers repeatedly need the response or moderators need the action.