Styz Bot Builder Setup Guide

The Styz Bot Builder lets you create, host, and manage your own custom Discord bots without writing code. Bots are built from flows: a visual chain of nodes that defines what happens when a user runs a slash command.

What is the Styz Bot Builder?

The Builder is a separate product from the main Styz Bot. It is available at builder.styz.cloud. You create a bot application on the Discord Developer Portal, enter its token into the Builder, and the Builder hosts it for you.

Each bot gets its own set of slash commands. Commands are built with the flow editor: a drag-and-drop canvas where you connect a trigger node to action, logic, advanced, and game nodes. When a user runs the command, the bot follows the flow from start to finish.

The Builder is ideal for server owners who want a custom-branded bot or advanced commands that the main Styz Bot does not provide.

Plans and limits

Premium is required for the Builder itself. The Free plan lets you test the core nodes. To publish a bot with game commands, AI, HTTP, economy, or more than five flows, upgrade to Starter or Pro.

Creating your first bot

1. Go to builder.styz.cloud and log in with Discord.
2. Open the Discord Developer Portal and create a New Application at discord.com/developers/applications.
3. Navigate to Bot in the left menu, then click Add Bot. Under Privileged Gateway Intents, enable Server Members Intent and Message Content Intent if you plan to use prefix commands, conditions, or moderation.
4. Copy the bot token and save it privately. Do not share it. If it leaks, reset it immediately in the Developer Portal.
5. In the Builder, click New bot, paste the token, and enter the Application ID from the General Information page.
6. Add an avatar and a short description, then save.
7. Use the OAuth2 URL Generator in the Developer Portal to create an invite link with bot and applications.commands scopes. Add the bot to your test server.

Dashboard overview

The Builder dashboard has three tabs per bot:

• Flows: create, search, sort, and edit your slash commands.
• Settings: change the bot token, prefix, status, activity, and public visibility.
• Analytics: view total uses, command counts, uptime, and recent errors.

Building a flow

A flow is a command. It starts with a Trigger node that defines the slash command name, then runs through connected nodes.

• Trigger node: the trigger name becomes the slash command. Only lowercase letters, numbers, underscores, and hyphens are allowed. Set the description, cooldown, allowed role IDs, and allowed channel IDs. Blank role or channel fields mean everyone or any channel.
• Canvas: click a step in the left sidebar to add it to the canvas. Drag nodes to position them. Click a node's output dot and then another node's input dot to connect them. You can zoom, pan, auto-arrange, and fit the view.
• Step inspector: when a node is selected, the right panel shows its configuration. Each step has its own fields. Some steps, like Condition and Random Branch, have two output wires: then and else.

Step categories

Variables

Many text fields support variables. The bot replaces these with live values when the command runs.

For moderation steps you can also use {userId} in the target user ID field to target the command runner.

Game server commands (FiveM, Roblox, Rust)

Premium. Send commands from Discord to your game server. The Builder POSTs a JSON payload to the endpoint you provide.

• Endpoint URL: the HTTPS address of your game server's command API.
• Auth token: a secret token your API validates in the Authorization header.
• Command: the command name your API expects, such as kick.
• Arguments: the rest of the command, with variables allowed. Example: {userId} rule breaking.

Your game server must expose an HTTP endpoint that accepts POST requests, validates the token, and runs the requested command on the server.

Saving, syncing, and testing

1. Click Save changes or Create flow in the right panel. The flow is validated on the server before it is stored.
2. Go to the bot's Settings tab and click Sync commands. This registers the slash commands with Discord. It may take up to one hour for global commands to appear, or instantly for guild commands.
3. In your test server, type / and look for the command name.
4. Run the command and watch the output. Check the analytics tab for errors or confirm the action worked.

Permissions and security

• Keep your bot token private. Anyone with the token can control your bot.
• Do not store tokens in public repositories or deploy archives. Use environment variables if you self-host the backend.
• The Builder stores tokens encrypted in the database.
• Your bot needs appropriate Discord permissions in the server for the actions you use: Manage Roles, Manage Channels, Ban Members, Kick Members, Manage Messages, Connect, Speak, etc.
• Move the bot's top role above any roles it should manage.
• Disable unused gateway intents to reduce attack surface.

Troubleshooting

• Commands not appearing: click Sync commands and wait a few minutes. Re-invite the bot with applications.commands scope if the issue persists.
• Bot says it is not running: check the status on the dashboard. If it shows Error, re-enter the token or contact support.
• Flow does nothing: make sure nodes are connected from the trigger and at least one step is wired to the trigger's output dot.
• Step fails silently: the bot skips failed steps. Check the step config and the bot's permissions.
• Premium step error: upgrade the Builder plan to use that node type.
• Typing deletes the node or paste does not work: this was a keyboard shortcut bug that has been fixed. Refresh the page if you still see it.