Q: difference between Discord.SlashCommandBuilder and the Discord.Interactions.Builders same name

[mwpowellhtx]

There is Discord.SlashCommandBuilder and there is Discord.Interactions.Builders.SlashCommandBuilder, is there a difference, has one superseded the other? Would someone mind advising please? Thank you... Best...

[mwpowellhtx]

Going to guess based on a surface level smoke test, Discord.Interactions.Builders is probably superfluous and unnecessary or at least at this level, or that is more geared towards quote unquote modularization which, my packaging somewhat does today, could perhaps be more self contained in separate modules, but we'll cross that complexity bridge if necessary.

// Asking for `ModuleBuilder` and `ExecutionCallback` for starters...
Discord.Interactions.Builders.SlashCommandBuilder x = new();

Versus:

// Which simply "is" zero parameters, TL;DR did not configure anything "yet"... just getting a flavor of the surface requirements.
Discord.SlashCommandBuilder y = new();
// Which is good if we have for instance, SocketGuild source.
source.CreateApplicationCommandAsync(y.Build());

[Misha-133]

Discord.Interactions.Builders are meant to be used with the InteractionService from the Discord.Interactions package. For general use you should only utilize builders from the Discord namespace

[mwpowellhtx]

I guess that's my question, I kind of figured there's probably a sync of some sort, but overall the question is more along the lines of "so what" or what's the big idea or why does someone want to use the interaction service. I'm not clear on that part. Otherwise, I'd just use the base feature, I suppose.

[Misha-133]

why does someone want to use the interaction service

Because it's abstracts a lot of the boilerplate leading to better DX. (you can read the docs here).
tl;dr is that you can define commands as their own methods, use the modules structure and handle components (and modals) in a similar manner. Or, well, just any kind of discord interactions.
While leaving all the command "routing", custom id matching, DI up to the existing backend.
So instead of doing new SlashCommandBuilder().WithX().WithY()... and then "manually" handling the InteractionCreated event you can simply do

[SlashCommand("name", "Cool description")]
public async Task CoolCommandAsync(int parameter)
{
    await RespondAsync("Hello there!");
}

(it's not as simple as you still need to setup some things for it to work properly, but after going over the initial setup it provides some great DX. You can also reference the sample I made)

[mwpowellhtx]

Yep I did pick up on the attribution approaches... Something I might chew on does it make sense to do so, at least in my case. I've got things fairly well dissected at the moment, to where it is not difficult to follow the fluent approach, either. But good to know either way. Cheers, thanks! 🍻