Skip to content
SwisserAI LogoSwisserAI
Discord Bot Generator HelpSwisserAI HelpOpen app

Build

Describing your bot

The new bot page asks one real question, where the bot runs, and then for a name and a description. The description decides almost everything.

Where it runs

The new bot page of the Discord Bot Generator starts with Where will it run?. The answer is not cosmetic: a FiveM resource is written for the Node runtime inside your FiveM server, a standalone bot for ordinary Node.

  1. 1. Standalone: a Node bot you host anywhere
  2. 2. FiveM resource: runs inside your FiveM server

The target is fixed for the project. To get the same bot for the other target, start a new bot and paste the same request. The differences are on Standalone or FiveM resource.

The name

The Name labels the project card and becomes the name of the zip, for example status-whitelist-bot.zip. Short names in lowercase with hyphens work best, because a FiveM resource folder is usually named the same.

It is not the name members see in Discord. That name comes from the application you create in the Discord Developer Portal, see Create the application.

Writing a good request

What should it do? needs at least 10 characters and takes up to 8,000. Write it the way you would explain the bot to a person. The page itself asks for three things: commands, who may use them, and what happens when they do.

  • Each command and its options

    /apply opens a form with in-game name, age and why they want to join

  • Who may use it

    Only the Staff role may use /kick and /ban

  • What happens, step by step

    Approve gives the whitelist role and sends a direct message

  • Where things go

    Answers go to a staff channel; every action is logged to a log channel

  • What must be configurable

    Put all role and channel ids in the config

  • Timing and limits

    Update the channel name every 60 seconds

This is the request behind the bot in this guide, written in plain sentences:

  1. 1. Name: the project and the zip get this name
  2. 2. What should it do?: commands, who may use them, what happens

Several small wishes beat one vague one

"Make it advanced" or "the best bot ever" gives the builder nothing to act on. Name the features. If a request grows long, build the core first and add the rest as changes.

You can write the request in another language. Say which language the bot itself should use for its messages in Discord, so nobody has to guess.

Starting from a template

Under the box, Or start from one of these and change it: offers six starting points for the chosen target. A click puts the full request into the box, where you can edit it before you build.

  1. 1. Live player count: a click fills the text box
  2. 2. A whole server management system: the large example

  • Moderation with a log

    Live player count

  • Support tickets

    Whitelist

  • Welcome and roles

    Run the server from Discord

  • Applications with a review queue

    Tickets and ban appeals

  • Reminders and scheduled posts

    Department applications

  • A whole community bot

    A whole server management system

The last template of each list combines the others into one project. Change the details to your server before you build: role names, channel names, how often things update.

What it will not build well

  • Music bots. Streaming from video sites breaks their terms, and the largest music bots were shut down over it.
  • Bots that need a paid outside service, such as an AI chat bot. The bot can call any web API, but you bring the key and the account.
  • Spam, raid or wipe bots. Mass messages, mass pings and deleting channels in bulk break Discord's rules and get the bot and its owner banned.

Bots that already exist for free everywhere, like leveling, are possible, but a ready-made bot may serve you better. The generator shines where a bot has to fit your own server, roles and data.