Sapphire - Imagine a Framework•10mo ago•

23 replies

Command not Registering

So my command isint registering, here is the code

import { Command } from '@sapphire/framework';

export class KycCommand extends Command {
  public constructor(context: Command.LoaderContext, options: Command.Options) {
    super(context, {
      ...options,
      enabled: true,
      name: 'kyc',
      description: 'Do Know-your-customer verification.',
    });
  }

  public override registerApplicationCommands(registry: Command.Registry) {
    registry.registerChatInputCommand((builder) =>
      builder //
        .setName(this.name)
        .setDescription(this.description)
        .addUserOption((option) =>
          option //
            .setName('ign')
            .setDescription('Your Minecraft IGN')
            .setRequired(true)
        )
    );
  }

  public override async chatInputRun(interaction: Command.ChatInputCommandInteraction) {
    const mcIGN = interaction.options.getString('ign', true);

    return await interaction.reply({
      content: `MC Ign is: ${mcIGN}`,
    });
  }
}

import { Command } from '@sapphire/framework';

export class KycCommand extends Command {
  public constructor(context: Command.LoaderContext, options: Command.Options) {
    super(context, {
      ...options,
      enabled: true,
      name: 'kyc',
      description: 'Do Know-your-customer verification.',
    });
  }

  public override registerApplicationCommands(registry: Command.Registry) {
    registry.registerChatInputCommand((builder) =>
      builder //
        .setName(this.name)
        .setDescription(this.description)
        .addUserOption((option) =>
          option //
            .setName('ign')
            .setDescription('Your Minecraft IGN')
            .setRequired(true)
        )
    );
  }

  public override async chatInputRun(interaction: Command.ChatInputCommandInteraction) {
    const mcIGN = interaction.options.getString('ign', true);

    return await interaction.reply({
      content: `MC Ign is: ${mcIGN}`,
    });
  }
}

as a sanity check, I copied the ping example from the docs and it worked

Solution

TL;DR: Do not use
ts-node
ts-node
, use
tsc-watch
tsc-watch
instead.

We very strongly discourage using

ts-node

ts-node

because it was never meant to be used for bots.

ts-node

ts-node

is designed for

REPL

REPL

purposes. That's short for

Read Eval Print Loop

Read Eval Print Loop

.
Which means to read some code, dump it in an

eval()

eval()

statement, print the result, and loop.

A discord bot is not that.

A Discord bot sets up a permanent web socket connection to the Discord server and connects to the rest gateway.
There is read yes, but no eval, no print, and no loop.

So what should you use instead?

The most ideal way is to just use the

watch

watch

flag of

tsc

tsc

(

tsc --watch

tsc --watch

) and run

node dist/index.js

node dist/index.js

to run your bot, then cancel that process and restart it when you have changes that require restarting.
You would open 2 terminal tabs, 1 in which you run

tsc --watch

tsc --watch

and another in which you run the bot.
This is, in particular, the most ideal way, because Discord has a limit to the amount of times you can log in with your bot, or register commands, per day.
Constantly logging in over and over again due to an auto-restarting process will get you close to that limit very quickly and once you exceed it, your development will be halted entirely for the current day.

However, this can be quite tedious so a great package to use instead is

tsc-watch

tsc-watch

Jump to solution

S-IaF

Sapphire - Imagine a Framework•10mo ago•

23 replies

tortenwashere

Command not Registering

So my command isint registering, here is the code

import { Command } from '@sapphire/framework';

export class KycCommand extends Command {
  public constructor(context: Command.LoaderContext, options: Command.Options) {
    super(context, {
      ...options,
      enabled: true,
      name: 'kyc',
      description: 'Do Know-your-customer verification.',
    });
  }

  public override registerApplicationCommands(registry: Command.Registry) {
    registry.registerChatInputCommand((builder) =>
      builder //
        .setName(this.name)
        .setDescription(this.description)
        .addUserOption((option) =>
          option //
            .setName('ign')
            .setDescription('Your Minecraft IGN')
            .setRequired(true)
        )
    );
  }

  public override async chatInputRun(interaction: Command.ChatInputCommandInteraction) {
    const mcIGN = interaction.options.getString('ign', true);

    return await interaction.reply({
      content: `MC Ign is: ${mcIGN}`,
    });
  }
}

import { Command } from '@sapphire/framework';

export class KycCommand extends Command {
  public constructor(context: Command.LoaderContext, options: Command.Options) {
    super(context, {
      ...options,
      enabled: true,
      name: 'kyc',
      description: 'Do Know-your-customer verification.',
    });
  }

  public override registerApplicationCommands(registry: Command.Registry) {
    registry.registerChatInputCommand((builder) =>
      builder //
        .setName(this.name)
        .setDescription(this.description)
        .addUserOption((option) =>
          option //
            .setName('ign')
            .setDescription('Your Minecraft IGN')
            .setRequired(true)
        )
    );
  }

  public override async chatInputRun(interaction: Command.ChatInputCommandInteraction) {
    const mcIGN = interaction.options.getString('ign', true);

    return await interaction.reply({
      content: `MC Ign is: ${mcIGN}`,
    });
  }
}

as a sanity check, I copied the ping example from the docs and it worked

Solution

TL;DR: Do not use
ts-node
ts-node
, use
tsc-watch
tsc-watch
instead.

We very strongly discourage using

ts-node

ts-node

because it was never meant to be used for bots.

ts-node

ts-node

is designed for

REPL

REPL

purposes. That's short for

Read Eval Print Loop

Read Eval Print Loop

.
Which means to read some code, dump it in an

eval()

eval()

watch

watch

flag of

tsc

tsc

(

tsc --watch

tsc --watch

) and run

node dist/index.js

node dist/index.js

to run your bot, then cancel that process and restart it when you have changes that require restarting.
You would open 2 terminal tabs, 1 in which you run

tsc --watch

tsc --watch

tsc-watch

tsc-watch

Jump to solution

Command not Registering

Command not Registering

Similar Threads

Similar Threads

Similar Threads