Interaction has already been acknowledged

[bold arch]

We would need more than that code to figure this out

[tranquil marten]

sure, 1 sec

[bold arch]

Are you sure you are not using the follow up async twice

[tranquil marten]

Dont think i do

oh

is it the last part where the issue is right now?

[bold arch]

I see the problem

Are you trying to update the follow up you just send or the previous one that triggered this reaction? Here
IComponentInteraction interaction = (IComponentInteraction)Context.Interaction;
await interaction.UpdateAsync(msg =>
{
msg.Embed = embed;
});

[tranquil marten]

that edits the embed to show who the ticket assignee is

[bold arch]

You would have to use something else for that 2s

[tranquil marten]

maybe it would be better to just leave the claim confirmation entirely out of the code lmao

[bold arch]

Context.Interaction.GetOriginalResponseAsync()

[tranquil marten]

you'll see anyways

[bold arch]

Then you modify what you get returned

[tranquil marten]

oh okay i see, thank you for your quick reply, i will see what i can do! have a nice day

[cunning summit]

uhm

ModifyOriginalResponseAsync

[bold arch]

            RestInteractionMessage restInteractionMessage = await Context.Interaction.GetOriginalResponseAsync();
            await restInteractionMessage.ModifyAsync(m => m.Embed = embed);

[cunning summit]

[bold arch]

Or that

[tranquil marten]

[tranquil marten]

i stole this emoji from u yesterday

[bold arch]

I tend to go the long way

XD

[tranquil marten]

mine now

[cunning summit]

which is bad in this case

¯_(ツ)_/¯

2 requests vs 1

[bold arch]

How

Ohhhh

Thought it was doing the same in the background

[cunning summit]

[cunning summit]

nope
those methods just call the api

[tranquil marten]

omg there's more

u win

[cunning summit]

[tranquil marten]

💀

[bold arch]

@tranquil marten

ModifyOriginalResponseAsync(m => m.Embed = embed);

[cunning summit]

also if you just do ModifyOriginalResponseAsync in a interaction module class it will do... a getoriginal response + modify

cuz someone thought that made sense

[tranquil marten]

oh cool and then i can just do respondasync for the ticket claim confirmation msg?

[cunning summit]

(it does not)

so do Context.Interaction.ModifyOriginalResponseAsync instead
this one actually makes only one request and can actually update ephemeral messages

[tranquil marten]

[bold arch]

Yeah you do not need the line above it

[tranquil marten]

cool

removed it

[bold arch]

Goody

[cunning summit]

https://docs.discordnet.dev/faq/int_framework/respondings-schemes.html

[tranquil marten]

i already had that open but i honestly didnt feel like reading all that 💀

will do next time

maybe

but it works now, thanks guys!

[cunning summit]

i mean
the point of that is so u dont need to read much

[tranquil marten]

oh it makes sense

i thought it was something difficult to understand but it's really just connecting dots

got it

thanks!

https://tenor.com/view/spongebob-spongebob-meme-death-dies-noo-gif-15662544042879608963

[bold arch]

You learn something everyday did not know the deferloading was a thing

[cunning summit]

it wasnt at some point iirc

[bold arch]

Been out of the game for a fair bit

[cunning summit]

component/modal specific impls were (and still are) quite fucky in dnet