25 replies

Issue with application commands after logging in after client#destroy()

If I login after doing client.destroy(), the bot logs in fine, but the application commands aren't registered again. Am I doing something wrong?

Some example code:

client = new SapphireClient({
  intents: Constants.INTENTS,
  partials: Constants.PARTIALS,
  presence: Constants.PRESENCE,
});
ApplicationCommandRegistries.setDefaultBehaviorWhenNotIdentical(
  RegisterBehavior.Overwrite,
);

await client.login(process.env.TOKEN);
await client.destroy();

client = new SapphireClient({
  intents: Constants.INTENTS,
  partials: Constants.PARTIALS,
  presence: Constants.PRESENCE,
});
await client.login(process.env.TOKEN);

client = new SapphireClient({
  intents: Constants.INTENTS,
  partials: Constants.PARTIALS,
  presence: Constants.PRESENCE,
});
ApplicationCommandRegistries.setDefaultBehaviorWhenNotIdentical(
  RegisterBehavior.Overwrite,
);

await client.login(process.env.TOKEN);
await client.destroy();

client = new SapphireClient({
  intents: Constants.INTENTS,
  partials: Constants.PARTIALS,
  presence: Constants.PRESENCE,
});
await client.login(process.env.TOKEN);

The first login I get (I am logging

Bot has connected

Bot has connected

on the ready event):

ApplicationCommandRegistries: Initializing...
Bot has connected.
ApplicationCommandRegistries: Took 6ms to initialize.

ApplicationCommandRegistries: Initializing...
Bot has connected.
ApplicationCommandRegistries: Took 6ms to initialize.

But on the second login I only get:

Bot has connected.

Bot has connected.

So it seems like ApplicationCommandRegistries isn't being initialised again. Should I be recreating the SapphireClient, or is there another way I should be doing this? Thanks!

Issue with application commands after logging in after client#destroy()

If I login after doing client.destroy(), the bot logs in fine, but the application commands aren't registered again. Am I doing something wrong?

Some example code:

client = new SapphireClient({
  intents: Constants.INTENTS,
  partials: Constants.PARTIALS,
  presence: Constants.PRESENCE,
});
ApplicationCommandRegistries.setDefaultBehaviorWhenNotIdentical(
  RegisterBehavior.Overwrite,
);

await client.login(process.env.TOKEN);
await client.destroy();

client = new SapphireClient({
  intents: Constants.INTENTS,
  partials: Constants.PARTIALS,
  presence: Constants.PRESENCE,
});
await client.login(process.env.TOKEN);

client = new SapphireClient({
  intents: Constants.INTENTS,
  partials: Constants.PARTIALS,
  presence: Constants.PRESENCE,
});
ApplicationCommandRegistries.setDefaultBehaviorWhenNotIdentical(
  RegisterBehavior.Overwrite,
);

await client.login(process.env.TOKEN);
await client.destroy();

client = new SapphireClient({
  intents: Constants.INTENTS,
  partials: Constants.PARTIALS,
  presence: Constants.PRESENCE,
});
await client.login(process.env.TOKEN);

The first login I get (I am logging

Bot has connected

Bot has connected

on the ready event):

ApplicationCommandRegistries: Initializing...
Bot has connected.
ApplicationCommandRegistries: Took 6ms to initialize.

ApplicationCommandRegistries: Initializing...
Bot has connected.
ApplicationCommandRegistries: Took 6ms to initialize.

But on the second login I only get:

Bot has connected.

Bot has connected.

So it seems like ApplicationCommandRegistries isn't being initialised again. Should I be recreating the SapphireClient, or is there another way I should be doing this? Thanks!

Issue with application commands after logging in after client#destroy()

Issue with application commands after logging in after client#destroy()

Continue the conversation

Sapphire - Imagine a Framework

Continue the conversation

Sapphire - Imagine a Framework

Similar Threads