User Apps' behavior with guild oriented contexts and integration types

[Vioshim]

I've been experimenting with user apps lately and realized some unexpected behavior or at least from my team's perspective when it comes to the behavior from the types. And I was wondering if this proposal can be applied in order to give some consistency or flexibility in the design of user apps.

GUILD_INSTALL is present	GUILD is present	Current behavior	Expected Behavior
False	False	Not in servers	Not in servers
False	True	In servers	In Mutual Servers
True	False	Not in servers	Not in Mutual Servers
True	True	In servers	In servers

[yonilerner]

Can you elaborate here on what these things mean? For example in the second row, what does "in servers" and "in mutual servers" actually mean?

Also what does "GUILD is present" mean? Is that referring to the interaction having a guild property (meaning it was run in a guild)? Does that mean the interaction's context is GUILD? Either way, it just means the interaction was executed in a guild

[Vioshim]

In the moment that we are registering app commands, we are meant to specify the scope in which they work.

These two are the integration_types and contexts

For this reason, GUILD_INSTALL refers to the integration type and GUILD refers to the context

The inconsistency I notice is, that despite I'm specifying that a command can't be installed in guilds, it does show anyways if the GUILD context is provided. Similarly if I specify that the command can be installed but yet no guild context, it simply doesn't show in servers. Meaning that the context is the only one that does anything in these conditions.

For that reason, I think it'd make sense that if we specify no guild install yet specify guild context, it'd mean that it will only work in servers that have the bot installed. Installable Guild being rather if it works in any server, and context being rather a filter.

Saying it for the use case of having commands that only work if the bot is in that server, or commands that work in DMs and servers that have the bot (hence mutual) but not in servers that don't have the bot. (to prevent flooding etc)

[yonilerner]

The two fields are working exactly as intended. If you want a command to work only if the bot is in the server, or with the bot's DM, then you specify integration_types=[GUILD_INSTALL].

There is no way to specify that you want a command to work in DMs between users specifically when they share a guild with the app installed, because that is simply not how user installed commands work

[Vioshim]

that makes sense, right, I suppose it'd probably be best for such use case to just keep it open and use the interaction's authorization info to tell and rather solve it in the code, thanks for the answer