-
Notifications
You must be signed in to change notification settings - Fork 28
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
Status CH by choosing a GuildID & Channel ID #10
Comments
Hello, @x-Ghosts! Can you please send me your
Obviously the message didn't generate/send and it can't get the ID from it, because it doesn't exist. If it still doesn't work, try to give the bot administrator permission to just try it again. |
Hello @PetyXbron , The Bot has actually all the permissions needed, acting as an Admin, + bots applications.commands feature on. Moreover, it's full access on the channel to read & send the messages, to manage the channel too. Here is the File : I shared it via Mediafire, the link is below : https://www.mediafire.com/file/6nxd5bd0h7c16k6/config.js/file PS: I am aware of the IP chosen, I am testing my server for some few coding purposes. |
Hello, Any news about the issue, or, an issue from my side ? I hope I've done things as they should be done via the guide. |
Hello, I am a bit busy this week. I will try to check out all issues of this project this weekend. And I have in my plan to make some bug-fixing release/update with some new functions. I will let you know in a couple of days. |
@x-Ghosts can you please invite me to your Discord server to inspect it more closely? I couldn't find any mistake in your config. |
Hello !
I've tried to follow the Guide about an Auto-Message refreshing for the server status.
Well, at the Terminal, right before the Bot finishes booting up, I get this : (Resulting the failure of its bootup)
I hope I did not do any mistake regarding adding only The GuildID & Channel ID where it supposed at the end to show, after every interval timer the status of the server without typing the Status command.
The text was updated successfully, but these errors were encountered: