TweenkySuwaru
TweenkySuwaru
SIASapphire - Imagine a framework
Created by TweenkySuwaru on 10/15/2024 in #sapphire-support
Subcommand in Direct Messages even with guildIds option
Will stick to that solution for now 👍 But it feels like that an very bad solution...
54 replies
SIASapphire - Imagine a framework
Created by TweenkySuwaru on 10/15/2024 in #sapphire-support
Subcommand in Direct Messages even with guildIds option
I even tried to delete this commands using d.js and info from that doc about commands being stored and not removed after created. Anyway same result, they registreting to global list. I will try to reinstall node_modules, maybe that an issue with cache or something else at the deeper lvl... And if that will not solve the issue - i have 0 ideas why this could happening
54 replies
SIASapphire - Imagine a framework
Created by TweenkySuwaru on 10/15/2024 in #sapphire-support
Subcommand in Direct Messages even with guildIds option
I found out that commands have .setContexts() method. It worked! Commands are no longer visible in dms if I set it to Guild. But anyway, sapphire still register them as global commands, very weird why it's registering globally at all with provided guildIds
54 replies
SIASapphire - Imagine a framework
Created by TweenkySuwaru on 10/15/2024 in #sapphire-support
Subcommand in Direct Messages even with guildIds option
Like why ApplicationCommandRegistries.setDefaultGuildIds worked, but
public override registerApplicationCommands(registry: Command.Registry) {
registry.registerChatInputCommand((builder) =>
builder.setName(this.name).setDescription(this.description)
),
{
guildIds: [this.container.config.guildId],
}
}
public override registerApplicationCommands(registry: Command.Registry) {
registry.registerChatInputCommand((builder) =>
builder.setName(this.name).setDescription(this.description)
),
{
guildIds: [this.container.config.guildId],
}
}
this code dont
54 replies
SIASapphire - Imagine a framework
Created by TweenkySuwaru on 10/15/2024 in #sapphire-support
Subcommand in Direct Messages even with guildIds option
using ApplicationCommandRegistries.setDefaultGuildIds and RegisterBehavior.BulkOverwrite worked fine. Global commands were removed, and old commands that don't even exist too. But I have command for example /ticket that should be available globaly. I wonder why sapphire registers some commands to global list even with provided guildIds property on them
54 replies
SIASapphire - Imagine a framework
Created by TweenkySuwaru on 10/15/2024 in #sapphire-support
Subcommand in Direct Messages even with guildIds option
Okay so... I have like 5 bots, and some of them has some commands that registered globally. Tried to remove all applicationCommands for one of them just to see if it will solve the issue. But no, when I restarted bot command still was registering to global list even with specified guildId. I looked up at setup file that I call for registering plugins and found that: ApplicationCommandRegistries.setDefaultBehaviorWhenNotIdentical(RegisterBehavior.Overwrite). Changed to just Overwrite, but still commans remain in global list and even some old commands that no longer included in bot (they was literally deleted from files) are here, wtf :/
54 replies
SIASapphire - Imagine a framework
Created by TweenkySuwaru on 9/11/2024 in #sapphire-support
sapphire problem with types
That helped, thanks 👍
5 replies