#YesOrNine - Replied and such
1 messages · Page 1 of 1 (latest)
async execute(int, client) {
await int.deferReply();
return int.editReply({ embeds: [ListEmbed] }).catch(() => { });
}
ok, and what runs that execute?
try {
return command.execute(int, client);
} catch (error) {
console.error(error);
return outputErr(int, 404);
}
``` interactionCreate event
And the code before that code, doesn't include int.deferReply()
its not looping, id receive an error for only replying too
nope would also throw an error when only replying
Where does ListEmbed come from btw?
its defined somewhere in between but doesnt matter here
DiscordAPIError: Unknown interaction
at RequestHandler.execute (/root/kaede/node_modules/discord.js/src/rest/RequestHandler.js:350:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async RequestHandler.push (/root/kaede/node_modules/discord.js/src/rest/RequestHandler.js:51:14)
at async CommandInteraction.deferReply (/root/kaede/node_modules/discord.js/src/structures/interfaces/InteractionResponses.js:57:5)
at async Object.execute (/root/kaede/src/bot/commands/list.js:8:3) {
method: 'post',
path: '/interactions/960896475603288064/aW50ZXJhY3Rpb246OTYwODk2NDc1NjAzMjg4MDY0Om5hWk5BRFFMVkdGRlNCT3NXQU41WVluU1JVUXIxeUY3UFlhbDRYdE81c1JiRU5SWEhSbGxwQklMdGVrTGtJengyV282d21GMmNVanFsSGZhcXdONW8xaGd2WGtyN2RJaXZ3eUdkNzVIWTdQMVlJbEtnbjdSS3B6VjRvbHBzdW1H/callback',
code: 10062,
httpStatus: 404,
requestData: { json: { type: 5, data: { flags: undefined } }, files: [] }
}
Let's check the timing.
Can you stick console.log('Start', new Date().toISOString()) after the interactionCreate function starts
and console.log('Defer', new Date().toISOString()) before the deferReply
u relize u can just do console.time() and console.timeEnd() after deferReply ...
I'm a fan of the basic at times.
you guys are just gonna come up with the same answer or a wrong answer
that is basic
The super basic.
use followUp instead
that is super basic
followUp does the same thing
won't change anything.
From what I see so far, they have the same code I do.
They do deferReply and then editReply so I fail to see the issue so far.
stop... jessus
There's a possibility that you're running 2 instances at one time
told u, u can't see if an instance is being ran twice.
its not, believe me
Alright. We should end it here.
You are either replying twice, or taking too long. Final answer
neither is it though
well u said it's not running after 3s, so that's the only explanation for it
or u are using another interaction response inside ur interaction create
@rocky sluice & @simple mirage
I made a thread to keep it out of #djs-help-v14
Would you kindly go away if you're going to say the same things over and over.
It is MY CHOICE to help them here.
on the same interaction
to get the same answer or the wrong answer but ok
actually what is the err?
unknown interaction
stack trace is above
Your nickname is hard to ping - Rule 7️⃣
I bet there's another instance
Try any other commands and you should face the same issue
do you know what running two instances means? no offence
Humm, good point, YesOrNine can you try a different command?
i do but express would trough an error if it tries to run twice on the same port
so how do you receive your interaction
i said this at the beginning, it doesnt work for other commands either but i dont think (reason above) that its running twice
@obtuse wigeon
I assume you have it running on a host, and on your local machine (for developing)?
what is express thing, are you using express?
nope only the host
yes
to get interaction callbacks?
no
ok, can you add a console.log when your interactionCreate callback starts, so we can be 100% that it doesn't log twice.
Or if you have no access to logs, add a message to a internal channel, I assume you have a dev server
putting a log doesn't tell u that they have 2 instances, since that other instance cud probly be done after a second which isn't fast enuf to cause that issue
Your input is not desired, keep it up I'll ask them to just go to DMs.
then do so, if u dont want other opinions... On someone issue.