feat: Additional Features - #1345
Conversation
Co-authored-by: MrMythicalYT <91077061+MrMythicalYT@users.noreply.github.com>
|
I think this is a really good section to have, however the require method doesn't work in ESM. Although we still use CJS I know there's been talk of moving to ESM or at least including snippets for that. Might be worth including a warning that this won't work in ESM, or try out a module like https://www.npmjs.com/package/hot-esm (untested) and add a separate ESM subsection |
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
|
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: Jiralite <33201955+Jiralite@users.noreply.github.com>
Co-authored-by: Jiralite <33201955+Jiralite@users.noreply.github.com>
Co-authored-by: Jiralite <33201955+Jiralite@users.noreply.github.com>
Co-authored-by: Jaworek <jaworekwiadomosci@gmail.com>
Co-authored-by: Jaworek <jaworekwiadomosci@gmail.com>
Co-authored-by: Jaworek <jaworekwiadomosci@gmail.com>
Co-authored-by: Jaworek <jaworekwiadomosci@gmail.com>
Co-authored-by: Jaworek <jaworekwiadomosci@gmail.com>
Co-authored-by: Jaworek <jaworekwiadomosci@gmail.com>
|
|
||
| Spam is something you generally want to avoid–especially if one of your commands requires calls to other APIs or takes a bit of time to build/send. Cooldowns are also a very common feature bot developers want to integrate into their projects, so let's get started on that! | ||
|
|
||
| This section assumes you followed the [Command Handling](/guide/creating-your-bot/command-handling.md) part. |
There was a problem hiding this comment.
might be good to use the standard TIP for previous sections here
| }); | ||
| ``` | ||
|
|
||
| ## Command categories |
There was a problem hiding this comment.
Should this be integrated with subcommands so that categories are commands and their files are subcommands and make this actually useful
|
Also maybe the other pages could've been introduced in different prs this feels like a bit of a mess |
Co-authored-by: Jaworek <jaworekwiadomosci@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
Co-authored-by: megatank58 <tanumegatank@gmail.com>
| async execute(interaction) { | ||
| // interaction.user is the object representing the User who ran the command | ||
| // interaction.member is the GuildMember object, which represents the user in the specific guild | ||
| await interaction.reply(`This command was run by ${interaction.user.username}, who joined on ${interaction.member.joinedAt}.`); |
There was a problem hiding this comment.
for every file maybe better use unix timestamps
- it looks cool
- date after converting to string looks like
Mon Feb 20 2023 15:38:11 GMT+0100 (Central European Standard Time)
There was a problem hiding this comment.
yeah but it's just an example
they're free to change the code however they want
There was a problem hiding this comment.
yeah its just a suggestion
There was a problem hiding this comment.
Another alternative could be using timestamp markdown.
Please describe the changes this PR makes and why it should be merged:
Closes #1342 (normally).
I've copy pasted this from the old v12 guide and tried to adapt it for interactions.