Tutorial Slash Command

[thick venture]

https://discordjs.guide/creating-your-bot/slash-commands.html#before-you-continue

I got as far as the bit before it requests to create:

• commands/utility/user.js
• commands/utility/server.js

At this point it is supposed to respond with pong when I send ping. In in a text channel I think.
Can someone confirm this and help meunderstand why mine isn't working?

[gloomy shard]

• What's your exact discord.js npm list discord.js and node node -v version?
• Not a discord.js issue? Check out #1081585952654360687.
• 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!

[signal thunder]

1. Did you ever deploy your commands to discord (so they show up when you press / in your server)?
2. Do you have a client.on("interactionCreate") handler anywhere (either in an events/interactionCreate.js or index.js)?

Creating a command file is only part of the process. You have to keep going in the guide for "Command handling", "Registering slash commands", and "Event handling" before you can use the commands

[thick venture]

Ah, okay, so it's not meant to respond yet

[signal thunder]

No, it's not

If they don't appear like this, then Discord doesn't know your commands exist yet (which can be done in the "Registering slash commands" section)

[thick venture]

Where is the file you speak of in the folders:

https://github.com/discordjs/guide/tree/main/code-samples/creating-your-bot/slash-commands

It still doesn't work.

None of these guides make any damn sense

[signal thunder]

Deploys commands to Discord: Guide and Github
Handles slash command interactions: Guide and Github

[thick venture]

It's so depressing and uninspiring

[prisma pewter]

you haven’t really said what is so confusing about our guide

[thick venture]

I wanted to build a bot. Nothing makes sense. Nothing runs.

[prisma pewter]

if you can show your code so we can see what we’re working with, it would really be helpful to further assist you

[thick venture]

The samecode as you have on the github

[prisma pewter]

i want to see what you have.

[thick venture]

and then at some points it just jumps you just expand the code and nothinbgn makes sense

[prisma pewter]

please stop saying “nothing makes sense”. it doesn’t help anyone if you’re not explaining what’s so confusing

[signal thunder]

show your index.js to start with

thats the core of your entire code

[forest night]

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

[prisma pewter]

if you could explain what you’re confused about, maybe we could help elaborate on that

if you’ve never made a discord bot before, i would hope you have prior knowledge of javascript since that is expected before using discord.js

[thick venture]

There's no point. It's too late. Wasted hours on different versions that just don't work. This project is depressing

[prisma pewter]

we can’t help if you have that type of mentality

we’re trying to help you figure it out, but you don’t seem to want to understand it

it’s ultimately your choice

[signal thunder]

You can also just sleep on it and ask again tomorrow. Getting frustrated with code not working can sometimes just need a "fresh pair of eyes" and just try again later to figure out

[thick venture]

It's quite simple really. Just attempt to complete the discord.js guide. None of it works.

Good Night

[prisma pewter]

it’s not simple. if you read the guide slowly and carefully, it works fine

you haven’t said what’s confusing

so how can anyone help

it’s a waste of my time

saying “nothing works” just tells us that you haven’t looked fully and don’t want to put in the effort into trying and isn’t fair to us because we’re trying to help you

[signal thunder]

the guide definitely works. thats how i learned how to use the library. but if you put code into a file OTHER than your index.js, then you need to do something in index.js to load that file. your code only does what you tell it to. it doesn't magically know that commands/utility/ping.js is a command file unless you tell it somewhere to load it as a command file, etc..etc..etc

"none of it works" is user error, not an error of the guide

[prisma pewter]

every couple of months we always get complaints of how our guide doesn’t meet their standards of what they want, but we can only do so much since this is all up to the user for what they want to do in their project.

frankly isn’t fair, but can’t do anything about it so

ultimately up to the user for how much they want to pay attention to. we can only help so much

[signal thunder]

I'm sorry. The DJS guide is one of the best made guides for an npm package I've ever seen (maybe other than a frontend framework like Auth.js competes)