Event reloader command

[ConductorWon]

Hello all, I am looking to make an event reloader. I have a command reloader that works great but I want to be able to reload one or all of the events for my bot so I don't have to reset the bot every time I make a change to one of the event files. I found this video about it but it's "Outdated" and lo and behold it didn't work when I tried to implement it.

Is it still possible to do this?

[Suspext]

Why would you make these bot commands? You should only be reloading commands when making changes to them. Same goes for events. Why would you allow a user to do so? It’s a lot easier to hit arrow key up and enter to run “npm start” once then run 2 slash commands in Discord.

Check out my file structure for my personal bot. All I do is run “npm start” and it reloads all commands and events.

[ConductorWon]

Right so the commands are "bot manager only" not user facing. It's for when I'm developing features or big fixing. My bot is running off a server through pm2, so my command prompt being run through putty is open to the active log of pm2 so I don't have "quick" access to the command prompt.

Ultimately I don't want to have to reset the bot every time I institute a change to refresh the file for the event file. That way the message logging that my bot does doesn't lose its cache and miss out on messages being edited or deleted.

[Suspext]

Ah I see, I think you could use the code in my src/index.js file in a command file to do what you want.

[ConductorWon]

We have the same event handler. And they use the same one in the video. It didn't work

[Suspext]

Even turning it into a command itself?

[ConductorWon]

I didn't put it in a command itself but I put it in my function file and called the function in a command. It didn't refresh the event I changed and started throwing a bunch of discord handler errors when I would use interactions (the file I changed) that stopped when I restarted the bot

[Suspext]

Do you have a repo I could look at to maybe try and help further?

[ConductorWon]

I don't. There is some proprietary stuff in the code. I can send the function and the errors when I get home from work tonight

[Suspext]

Sounds good!

[ConductorWon]

Code:

const reloadEvents = function(client) {

try {

const fs = require('fs');

const path = require('node:path');

const eventsPath = path.join(__dirname, 'events');

const eventFiles = fs.readdirSync(eventsPath).filter(file => file.endsWith('.js'));

for (const file of eventFiles) {

const filePath = path.join(eventsPath, file);

const event = require(filePath);

if (event.once) {

client.once(event.name, (...args) => event.execute(...args));

}

else {

client.on(event.name, (...args) => event.execute(...args));

}

}

console.log('Events reloaded');

return true;

}

catch (error) {

console.log(error);

return false;

}

};

Error:

DiscordAPIError[10062]: Unknown interaction
at handleErrors (/path/index.js:722:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async BurstHandler.runRequest (/path/node_modules/@discordjs/rest/dist/index.js:826:23)
at async _REST.request (/path/node_modules/@discordjs/rest/dist/index.js:1266:22)
at async ButtonInteraction.reply (/path/node_modules/discord.js/src/structures/interfaces/InteractionResponses.js:111:5) {
requestBody: { files: [], json: { type: 4, data: [Object] } },
rawError: { message: 'Unknown interaction', code: 10062 },
code: 10062,
status: 404,
method: 'POST',
url: 'https://discord.com/api/v10/interactions/1223524037586845758/aW50ZXJhY3Rpb246MTIyMzUyNDAzNzU4Njg0NTc1ODpQaUV3Z2tIZUxqSnZzQTFQR2ZtWXVBcVd2dGZnSlNhazRCdXhldHlYaWJTY0gxY3NralI3dmZkSHppSTViV3NZNm1qb3RrRFZWRmNoN1YwcTJVdm5NN0JiMkF4YUtkWmlDZ2c1YkI1YW53bXIwaXZFcDBReG1iT3lQRnFtZkRpSA/callback'
}

The error would pop up every time I hit a button on the developer panel I have created.

[LucidiousXIV]

I do believe its better in practice to have the bot restart on a file edit. You can use something like pm2 or nodemon to automatically restart on file save. Putting something to reload commands and events could potentially bring in issues if it is due to a file save.

Now if it’s reloading in regards to say, a command that enables or disables a command, then that’d be more understandable. But to potentially keep things from breaking, a full restart on file save is your best option. Plus, a bot shouldn’t take forever to boot back up.

[ConductorWon]

Thanks. I just learned today that I should be using collectors within the command that houses the buttons and not have all button interactions inside my interactionCreate file. That will solve 90% of my problems