Getting original userID of slash command via Button Interaction

[viscid sundial]

Hey, so I'm using a button Handler. But everyone can interact with the button. How do I restrict the button to be usable by the user who ran the slash command from which the button originated? (I use the interactionCreate event to reply to the buttons, so I can only get the buttonInteraction). I don't wanna use db

[ashen kelp]

you will have to associate the original author with the button, somehow
if you are just looking for confirm buttons, i'd probably recommend using a component collector in the scope you have "original author" available and supplying it as a filter condition.

if this is happening in another scope, you still need to somehow know who triggered the original response, either via in-memory map or by having the user id in the custom id and parsing it from there

[echo phoenix]

You can always use ephemeral responses so only the user can see it

or another option is what Souji stated

You could cache the response with something like userID: messageID

Basically associating the button to specifically that user via that message itself and then if someone clicks that button, you can check if that user is associated with that button

and if not, handle it with what you prefer

[viscid sundial]

I was looking for a solution for non-ephemeral responses

[viscid sundial]

how do I cache the response?

[echo phoenix]

by cache I mean like

store it in memory

You can have a collection

and add it to them

and them remove it after x minutes etc

[viscid sundial]

but doesn't collection clear on restart?

[viscid sundial]

I'm not sure how to store in memory..

[echo phoenix]

yes it does

then you need a db to store it

[muted pagoda]

@viscid sundial maybe you could just input the userid in the customid? That's how I handle things like that sometimes

[viscid sundial]

I really wish I could use that, but since I use a button handler, I'll have to handle the buttons like

module.exports = {
  customId: 'the-custom-id',
  run: async (client, interaction) => {
  ...
}}

[muted pagoda]

How about a special character, like a hyphen in your customid, which seperates the name, and the I'd?

[viscid sundial]

I mean yea, but how would I access interaction when it's defined after customId

[muted pagoda]

That's easy to figure out, give it a few minutes of thought

If i tell you, would be spoonfeed of sorts

[viscid sundial]

I didn't figure it.. I tried this didn't work

[muted pagoda]

What do you mean by "i tried this", @viscid sundial

[viscid sundial]

nvm, I got it. Just had to change my command handler a bit

[echo phoenix]

@viscid sundial Why not just use a file storing db

If you need to store these buttons for really long times then maybe not the best call but

you can always use a JSON file storing method for it if you want

[violet pumice]

u want to get user which invoked interaction with button?

so <buttonInteraction>.message.interaction.user.id

[viscid sundial]

ah, finally. Thank you

[muted pagoda]

That's a property? Damn, thank you so much

[violet pumice]

yeah