Skip to content

Ship

Files and download

The file panel shows every file of the bot. Download packs all of them into one zip, named after the bot.

The file panel

The right half of a Discord Bot Generator bot is the file panel: the tree under Files with the number of files, and an editor that shows the file you click. Folders open and close with a click.

  1. 1. Files: every file of the project
  2. 2. Download: the same zip as in the checks panel
  • Read-only. The files are what a checked build produced. To change one, ask in the change box, so the checks run again.
  • Change marks. After a change, new, mod and del show which files that run touched.
  • Compiled files are hidden. The dist folder of a FiveM resource is in the download but not in the tree. That is why the tree can count 15 files while the bot card says 25.

On a phone the log and the files do not fit side by side. Two tabs, Build log and Files, switch between them.

  1. 1. Build log / Files: switch between the two panes

Downloading the zip

Download saves the whole project as one zip named after the bot, for example status-whitelist-bot.zip. There are two buttons with the same result: one in the checks panel when the checks pass, one above the editor.

  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

Downloading is free and can be repeated. After a change, download again: the zip always holds the newest version. The files sit at the top of the zip, without a folder around them, so unzip into a folder you created.

What is in the zip

The zip of the FiveM bot in this guide holds 25 files:

fxmanifest.lua
package.json
README.md
tsconfig.json
src/server.ts
src/config.ts
src/globals.d.ts
src/commands/apply.ts
src/commands/players.ts
src/events/client-ready.ts
src/events/interaction-create.ts
src/events/player-connecting.ts
src/lib/application.ts
src/lib/command.ts
src/lib/load-commands.ts
dist/...   (the same files compiled to .js)
  • .env.example

    Standalone:Yes: copy it to .env and fill it in
    FiveM resource:No: settings go into server.cfg
  • .gitignore

    Standalone:Yes, keeps .env out of Git
    FiveM resource:No
  • fxmanifest.lua

    Standalone:No
    FiveM resource:Yes
  • dist/

    Standalone:No: npm run build creates it
    FiveM resource:Yes, ready to run
  • node_modules/

    Standalone:No: npm install creates it
    FiveM resource:No: the yarn resource installs it

Read README.md first. It is written for this bot: the permissions it needs, whether it needs privileged intents, the exact setting names and the start command.

  1. 1. server.cfg lines: the settings this bot reads