Skip to content
SwisserAI LogoSwisserAI
Discord Bot Generator HelpSwisserAI HelpOpen app

Build

The build and the checks

A build runs on our side in five phases. You can watch every file being written, or close the tab and come back later.

The five phases

A Discord Bot Generator build moves through five phases, shown as a rail under the bot name. A check mark means done, the spinning one is running now.

  1. 1. Status line: what it does right now, files, lookups, time
  2. 2. Planning, Writing, Checking, Fixing, Packaging
  1. 1. Built and verified: the status line
  2. 2. Fixing ×1: one fixing round ran
The same rail after the build: all five phases done, Fixing ran once.

  • Planning

    What happens:It works out the files and looks up the discord.js API it needs.
    Status line says:Working out what to build

  • Writing

    What happens:It writes each file of the project.
    Status line says:Writing the project

  • Checking

    What happens:The four checks run on the whole project.
    Status line says:Compiling and checking

  • Fixing

    What happens:It fixes what the checks found, up to three rounds. Skipped when nothing is wrong.
    Status line says:Fixing what the checks found

  • Packaging

    What happens:It saves the files and, for FiveM, the compiled output.
    Status line says:Finishing up

A first build usually takes two to three minutes, a change about one. Right of the status line, three counters show the files written, the documentation lookups and the time since the build started.

Time-lapse of the first two minutes of a real build of a FiveM status and whitelist bot. The phase rail moves from Planning to Writing, the log lists each lookup and file, and all 15 source files appear in the file panel. The checks that follow are shown in the screenshots.

Reading the build log

The Build log on the left tells the story of the run from top to bottom:

  • You asked: your request, at the top.
  • Steps such as Looked up, Wrote, Read and Changed, each with the file or topic.
  • Dividers for the checks, for example Checking compile, scan, boot, and Round 1 all errors cleared.
  • What you got: a short summary of the finished bot, when the build writes one.

The file panel on the right follows along: each new file appears in the tree and opens in the editor while the build runs. Scroll up in the log to read; a button brings you back to the newest step.

The four checks

After writing, the build checks the whole project. Each check has its own group in the checks panel:

  • Compiler

    Panel text:tsc --strict against discord.js 14.27.0
    What it catches:Type errors, wrong imports, calls that do not exist.

  • Deprecated API

    Panel text:v13 names and superseded v14 calls
    What it catches:Code copied from old tutorials that no longer works.

  • Project rules

    Panel text:runtime constraints a compiler cannot see
    What it catches:For FiveM: the Node version line, CommonJS, no top-level await.

  • Startup

    Panel text:the bot actually started, gateway stubbed
    What it catches:Crashes on start, missing files, broken config loading.
  1. 1. Everything checks out: all four checks passed
  2. 2. Download: the project as a zip
  3. 3. How to get it running: the setup guide

The Startup check starts the bot with placeholder settings and a stand-in for Discord. It proves the bot boots. It cannot prove that a command does what you meant in your server, so try the commands once the bot is online.

When a check finds something

When the checks find errors, the panel header reads Problems found with the count, grouped by check, each with the file and line. The build then fixes them on its own: the rail shows Fixing with a counter such as ×1, and the panel shows which finding it is working on.

Up to three rounds run. Our showcase bot needed one: 4 errors after writing, 0 after round 1. A round that makes things worse is undone. The log marks each step with a divider:

  1. 1. Checking: compile, scan, boot
  2. 2. Round 1: all errors cleared by the fixing round
  3. 3. Reached max tool iterations: the build used all its writing steps

When a fixing round is undone, a note says so:

Repair round 1 introduced more problems than it solved (3 before, 4 after), so it was rolled back.

If problems are left after the last round, the build still delivers the files and the status reads Built, with problems the checks could not fix. See The build ended with problems.

Leaving and stopping

Builds run on our side. You can close the tab, switch pages or open the bot on another device. The browser tab title shows Done or Failed when it ends. When you come back, the log replays in full.

Stop in the header ends a running build. You are only charged for what already ran, and the files written so far are kept, but they were not checked. The log then says:

Stopped early. The 18 files written so far were kept, but they were never compiled or checked.

How a build can end

  • Built and verified

    All four checks passed. Download it.

  • Built, with problems the checks could not fix

    The files are there, but some check still fails. Ask for a fix before you use it.

  • Answered

    A follow-up question got an answer; no file changed.

  • Stopped

    You pressed Stop. Files so far are kept, unchecked.

  • The build failed

    Something went wrong on our side. The error shows under the log. Rare: 2 of 166 first builds so far.

A yellow note in the log such as Reached max tool iterations (15). Returning current workspace state. means the build used all of its writing steps. What it wrote was still checked; if a feature from your request is missing, ask for it as a change.