-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added unverified bots default intent. #500
Conversation
Does unverified bots have message content intent enabled by default? 🤔 |
no, this only applies to unverified bots added before the change not new ones created today the message content is still a privileged intent and should not be made default by dpp |
Any unverified bot that is below 100 server should have no problems using message intents tho, right? |
yes but it is still a privileged intent and you still have to go into developer page and turn it on... we would be introducing issues later when the bot grows and they then require approval to use the intent... |
It is called |
still shouldn't be defaulted imho, it becomes something else later and people will get used to having it enabled |
hmm this actually looks different to what I saw before.... I'll merge it later |
Agreed with this statement here. |
It's really unnecessary and in-fact over-thought imo. |
It's not replacing the |
I'm aware it's not replacing that, but I still feel the same. Rest is up to @braindigitalis. |
I agree tbh. If people need the message content intent, they should just pass that besides the default intents. It also makes it not really easier to use |
We already have a |
I would suggest |
That is literally just as verbose as |
Idk just feels like having aliases is fine
Seems fine to me, we'll let brain decide |
Maybe |
Same as
i_default_intents
but also hasi_message_content
intent.