discord.js - Imagine an app•4w ago

Logs not working

I am still kind of new to coding so please do not judge on that fact, but I've tried multiple things (events & audit logs) and only a few of my logs work (member joins and message edits).

logs.js

10 Replies

d.js toolkit•4w ago

- What's your exact discord.js npm list discord.js and node node -v version? - Not a discord.js issue? Check out #other-js-ts. - Consider reading #how-to-get-help to improve your question! - Explain what exactly your issue is. - Post the full error stack trace, not just the top part! - Show your code! - Issue solved? Press the button!

d.js docs•4w ago

To share long code snippets, use a service like gist, sourcebin, pastebin, or similar instead of posting them as large code blocks or files.

Samtino•4w ago

Also make sure to answer the questions above @Sincerely, alxx ᴬᴳ

Sincerely, alxx ᴬᴳOP•4w ago

sigh They were answered but okay

Sincerely, alxx ᴬᴳOP•4w ago

https://pastebin.com/LD3jTfS8

Pastebin

Code - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

Sincerely, alxx ᴬᴳOP•4w ago

- v14.18.0 & v20.18.0 - It's a discord.js issue - Read - My issue is only some of my logs work, so I am confused on what I am doing wrong. The logs that mainly work are member joins and message edits. I have tried events & audit logs, which are not working still. - It just does not log certain itmes. - Code: https://pastebin.com/LD3jTfS8 - No it's not solved

Pastebin

Code - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

Samtino•4w ago

Well first thing, you have 29 different client.on() events in in this file, and 18 of those are for Events.GuildAuditLogEntryCreate It is recommended that you only have 1 of each event. You should refactor this with a single Events.GuildAuditLogEntryCreate and then identify which type it is and format it. This is also a 700 line file with a lot going on and almost no console.log's, so I would recommend going 1 by 1 to see which one's in particular aren't working. Which one in particular are you having issues with? (also note, that audit logs aren't always real time, they can sometimes take a couple seconds to create after the event triggering them happens to be made)

Sincerely, alxx ᴬᴳOP•4w ago

I'll put that into my code! Thank you for the suggestion!!

Samtino•4w ago

For example, to debug your MessageDelete event, you should change the return to have a console.log saying you returned early and another one at the end saying it completed. And purely for debugging, you can also split any if-or's into seprate if checks so you can see which one are or aren't triggering. So you could do something like this

client.on(Events.MessageDelete, async (message) => {
      // if (!message.guild || message.author.bot || IGNORED_CHANNELS.includes(message.channel.id)) return;
      if (!message.guild) {
        console.log("[MessageDelete] No guild");
        return;
      }

      if (message.author.bot) {
        console.log("[MessageDelete] Author is a bot");
        return;
      }

      if (IGNORED_CHANNELS.includes(message.channel.id)) {
        console.log("[MessageDelete] Ignored channel");
        return;
      }

      let description = `**Author:** <@${message.author.id}>\n**Channel:** <#${message.channel.id}>\n`;
      if (message.content) {
        description += `**Message:**\n${message.content}`;
      } else {
        description += "**Message:** [No Content]";
      }

      if (message.attachments.size > 0) {
        description += `\n**Attachment:** [Link](${
          message.attachments.first().url
        })`;
      }

      await logEvent(
        message.guild,
        "MESSAGE DELETED",
        description,
        message.author
      )
        .then(() => {
          console.log("[MessageDelete] Log sent");
        })
        .catch((e) => console.error("[MessageDelete] Error sending log", e));
    });

client.on(Events.MessageDelete, async (message) => {
      // if (!message.guild || message.author.bot || IGNORED_CHANNELS.includes(message.channel.id)) return;
      if (!message.guild) {
        console.log("[MessageDelete] No guild");
        return;
      }

      if (message.author.bot) {
        console.log("[MessageDelete] Author is a bot");
        return;
      }

      if (IGNORED_CHANNELS.includes(message.channel.id)) {
        console.log("[MessageDelete] Ignored channel");
        return;
      }

      let description = `**Author:** <@${message.author.id}>\n**Channel:** <#${message.channel.id}>\n`;
      if (message.content) {
        description += `**Message:**\n${message.content}`;
      } else {
        description += "**Message:** [No Content]";
      }

      if (message.attachments.size > 0) {
        description += `\n**Attachment:** [Link](${
          message.attachments.first().url
        })`;
      }

      await logEvent(
        message.guild,
        "MESSAGE DELETED",
        description,
        message.author
      )
        .then(() => {
          console.log("[MessageDelete] Log sent");
        })
        .catch((e) => console.error("[MessageDelete] Error sending log", e));
    });

What intents does your client have? And what permissions does it have in the server you are testing in? For testing, it can be easiest to just give your bot Administrator permissions (but this isn't recommended for production use, as giving a bot administrator permissions is a security risk, as if your token was ever to be compromised, your application would have unrestricted access to perform any action in your server)

Gaming

Programming

Logs not working

Did you find this page helpful?