Skip to content
SwisserAI LogoSwisserAI
Discord Bot Generator HelpSwisserAI HelpOpen app

Build

Changing your bot

A finished bot is not the end. Ask for a change, paste an error, or ask how to set something up, all in the box under the log.

Asking for a change

Under the build log of every Discord Bot Generator bot sits the change box: Ask for a change, or paste an error you are stuck on. Type what should be different and press the send button or Ctrl+Enter(Cmd+Enter on a Mac). Plain Enter starts a new line.

  1. 1. Ask for a change, or paste an error you are stuck on.: Ctrl+Enter sends
  2. 2. Send

A change runs like a build: the log shows the files it reads and edits, the checks run again, and the result is saved. The file tree marks what changed with new, mod or del. Download again to get the new version.

  1. 1. What you got: what this change did
  2. 2. Built and verified
  3. 3. MOD: files this change edited
Time-lapse of one change to the finished bot. The request appears at the top of the log, the bot reads and edits two files, the checks run again and the run ends with the cost in the header.

This change took 53 seconds and cost 77 credits.

  • One change per message works best. "Add /status" and "fix the log channel" are two messages.
  • Say what should happen, not only what is wrong: "Decline should also post the reason in the log channel."
  • The box is disabled while a run is going; one run per bot at a time.

Pasting an error

When the bot fails on your PC or server, copy the error from the terminal or server console. Paste it into the change box with one line on what you did, for example:

I ran npm start and got this:
Error: Missing required environment variable: GUILD_ID

The builder reads the files and fixes the cause, or explains the setting you missed. Paste the whole error block, not only the last line: the file and line numbers matter.

Asking a setup question

Not every problem is in the code. Ask "Where do I put the token?" or "Why do my commands not show?" and the round ends with an Answer in the log instead of a change. The status line then says Answered, and no file is touched.

  1. 1. Answer: the reply, no file changed
  2. 2. Answered

This answer took 14 seconds and cost 31 credits. A question costs less than a change. The same answers are in Running your bot and Troubleshooting for free.

Earlier runs

Each build, change and question is a run. The label above the log, such as run 4 of 4, opens the list of all runs with what you asked, the credits it cost and when it ran. Pick one to replay its log.

  1. 1. run 4 of 4: opens the list
  2. 2. Runs: first build and changes, with credits

The files always show the newest version. There is no button to go back to an earlier one; to undo a change, ask for it: "Undo the last change to the log channel."

What a change costs

Changes and questions cost credits by the work they take. On paid runs so far, a change cost about 50-150 credits and a question about 30. The header shows the cost of the run you are looking at, and the run list shows every run's cost.

To start a change, 800 credits must be available. They are held while the run works; the unused part returns at once. With less, the page says Not enough credits. This needs 800.