Insufficient error message for `member.displayHexColor` when GUILDS intent is missing

[MaksiRose]

Which package is this bug report for?

discord.js

Issue description

1. Create a bot without GUILDS intent.
2. Get a guild member
3. call member.displayHexColor
4. Get an error

The problem here is not inherently with getting an error, but rather with the fact that the error is hard to understand for someone who has no idea that they are missing the GUILDS intent. They might try to console log, but will only get this error again, not undefined or anything. I fully believe this is very confusing and there should be a check for the guilds intent (or if the roles cache is empty) that throws with the message that the GUILDS intent is missing.

Code sample

const client = new Client({
  intents: [],
})

client.on('interactionCreate, async (interaction) => {
  if (!interaction.member || interaction.member === undefined) { return; }
  console.log(interaction?.member?.displayHexColor) // This will error
})

Package version

13.8.1

Node.js version

17.5.0

Operating system

Linux Manjaro

Priority this issue should have

Low (slightly annoying)

Which partials do you have configured?

Not applicable (subpackage bug)

Which gateway intents are you subscribing to?

No Intents

I have tested this issue on a development release

No response

[iCrawl]

I don't want to say this is "working as intended", but this is working as intended.
v13 and v14 and potentially v15 simply do not work without setting a certain amount of intents.

This will most likely be resolved in the typescript rewrite, but not before.

[MaksiRose]

I don't want to say this is "working as intended", but this is working as intended.

v13 and v14 and potentially v15 simply do not work without setting a certain amount of intents.

This will most likely be resolved in the typescript rewrite, but not before.

I am not saying that it should work without the intent. I am saying that it should display a clearer error message. I feel like there is no reason to not include an error that is clearer, really. Is there?

[iCrawl]

No, we definitely should document it better, thats true.

[MaksiRose]

No, we definitely should document it better, thats true.

Ok yeah, that was my entire point :) I don't mind the needed intent, I just think the error message is unclear and should give clear instructions towards a missing Intent 😁

[notarib-catcher]

No, we definitely should document it better, thats true.

Ok yeah, that was my entire point :) I don't mind the needed intent, I just think the error message is unclear and should give clear instructions towards a missing Intent 😁

Just taking opinions... Would an 'unable to resolve role' message or similar be enough of a clue as to the source of this error? I think that sort of error message would be sufficient information for someone to eventually diagnose this issue.

[MaksiRose]

@ribcatcher I do think that would have helped me at least, I would have asked myself why it can't resolve a role, probably tested some other role-related things, and then noticed that most of the guild things are not working and went to the intents.

[ZarakiKanzaki]

Hi! I have a question related to this issue. It seems that the previous PR was rejected as said in the comment because it would be a bad implementation. So, what I would love to know: the plan is to implement a correct documentation or creare some sort of warning for the clientGuildId?
thanks in advance