WildBeast is a wheels-attached Discord bot - meaning the heavy lifting is already done for you, making WildBeast easy to modify and extend to perfectly fit your use case.

This documentation focusses on self-hosting and extending WildBeast. If you don't feel like hosting your own instance, we host a publicly available version of WildBeast known as WildBot which you can invite to your own server.

Getting Started

Ready to get your hands dirty? Pick one of these guides to get started with WildBeast.

Fundamentals: Dive a little deeper

Looking to write your own commands, or other custom features? Look below for our advanced guides.

Need to run WildBeast 24/7? Get a cheap VPS. We recommend any of the below.

Hetzner

Cheap Finland and Germany-based VPSes.

The gold standard. Locations available worldwide.

Incredibly cheap but powerful VPSes, owned by online.net, based in France and The Netherlands.

A hosting solution made by Discord bot developers, aimed at a lower price range, starting from $2.49.

Cheap VPSes, used by many people. France and Canadian locations available.

US-based VPS provider, locations available worldwide.

US-based VPS provider, locations available worldwide.

Options are the primary way to take user input for slash commands, they're type-checked on Discord's side, so type safety is guaranteed!

In practise

Basic setup

A job either extends the Job class, or the ScheduledJob class, a scheduled job will run on a set time schedule and a normal job runs when called

Jobs are indexed and required based on their name either in context of the client, or in context of the cluster, a cluster job is called only once and a client job is called for each client that the cluster holds.

Cluster jobs should be named job-name.cluster.ts Client jobs should be named job-name.client.ts

In practise

Scheduled jobs work like this:

While regular jobs work like this:

Subcommands are a great way to nest seperate commands under one base command, each subcommand is their own seperate command and can be called as such.

In practise

1. Navigate to your (you might need to login for this)

2. Click "New Application" on the top right of the page

3. Think of a name for your bot, and click "Create"

Buttons are a simple way to create follow ups after a slash command has finished.

In practise

import { Interaction } from 'detritus-client'
import { ComponentContext, Components, Embed } from 'detritus-client/lib/utils'
import fetch from 'node-fetch'

import { BaseSlashCommand } from '../base'

export default class RandomCatCommand extends BaseSlashCommand {
  name = 'cat'
  description = 'Sends a random cat image'

  async run (context: Interaction.InteractionContext | ComponentContext): Promise<void> {
    const components = new Components({
      timeout: 5 * (60 * 1000),
      onTimeout: async () => await context.editOrRespond({ components: [] })
    })
    components.addButton({
      emoji: '🔃',
      run: async (componentContext: ComponentContext) => {
        await this.run(componentContext)
      }
    })
    const { fact } = await (await fetch('https://catfact.ninja/fact')).json()
    const embed = new Embed()
      .setDescription(fact)
      .setImage(`https://cataas.com/cat?${context.interaction.id}`) // cache busting
      .setFooter('Powered by cataas.com')
    await context.editOrRespond({
      embed,
      components
    })
  }
}

Making a new service

Start creating a new service:

Copy and paste the following example:

Controlling the service

Starting

Stopping

Start on boot

To undo:

Restarting

1. Once you have created a bot account, navigate to the OAuth2 page of your application

2. Scroll down to the OAuth2 URL Generator and check the "applications.commands" and "bot" scopes

3. Copy the link it generates and open it in a new tab, choosing what server you want to add it to, and hit "Authorize"

There are 3 types of commands, slash commands and 2 types of context menu commands. Documentation for each type is provided below.

The basics

We need a few prerequisites:

• A computer running any

  • You need sudo or doas privileges, or access to the root account

  • If you want to run WildBeast 24/7, you should get a

Installation

Installing Node.js

1. Run the following code in your terminal:

   (Not a fan of curl <url> | bash -? You can do this too.)

2. Install Node.js with the following command:

Installing Postgres

Postgres is available to install by default on Ubuntu, just run the following code in your terminal:

We need to do some extra steps to prepare Postgres for use:

1. Create a new user for WildBeast to use:

   The new user does not need to be a superuser, and can be called whatever you want.

2. Finally, create a new database:

   (We used wildbeast here as the database user, change it if you used something else in the previous step)

Setting up

Getting the code

Clone the code and install the required modules:

Setting the options

Open the example configuration file in nano and enter your details:

When you're done, save the file as .env

Starting the database

Before we can start, we need to initialize the database. Run the following code:

Testing it out!

Now for the fun part, testing to see if it worked!

Start WildBeast for the first time with the following command:

You should see something similar to the following if everything went well

19:11:41 [info] Gateway: Client ready

19:11:41 [info] Gateway - shard 0: Gateway ready

Test if your bot works by running the /ping command

Next steps

Creating commands

A finished command looks like this:

There are a few things to note with regard to how commands are constructed:

• All commands are new classes that extend a base class, in this example the command is a plain slash command.

• The resulting command is exported as the default export.

• The constructor with a super call is used to set properties of the class instead of directly assigning them, this avoids incompatibilities with Detritus.

In practice

When restarting WildBeast, your newly created command will automatically be registered as a global command, and will be available within a few hours.

Rather want a guild-based command instead of a global one? Add guild IDs to the constructor of your command:

What's next?

There are more things you can do with commands, like adding options, creating subcommands, and adding buttons and select menus.

There are 2 types of context menu actions, depending on what the end user is opening the context menu on.

import { Interaction } from 'detritus-client'
import { MessageFlags } from 'detritus-client/lib/constants'

import { BaseContextMenuUserCommand, ContextMenuUserArgs } from '../../base'

export default class InformationCommand extends BaseContextMenuUserCommand

import { Interaction } from 'detritus-client'
import { MessageFlags } from 'detritus-client/lib/constants'

import { BaseContextMenuMessageCommand, ContextMenuMessageArgs } from '../../base'

export default class InformationCommand extends BaseContextMenuMessageCommand {
  name = 'Message ID'

  async run (context: Interaction.InteractionContext, args: ContextMenuMessageArgs): Promise<void> {
    await context.editOrRespond({
      embed: {
        description: `Message ID: ${args.message.id}`
      },
      flags: MessageFlags.EPHEMERAL
    })
  }
}