[Feature Request] Channel ID for notifications on config file
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 2.8k
- PR merge metrics
- No merged PRs in 30d
Description
### Is your feature request related to a problem? Please describe.
Hi, I saw on the example configuration file:
// By default, the bot will DM the owner if the bot is running and a new version of the bot
// becomes available. Set this to false to disable this feature.
updatealerts=true
so like the command "help" the bot send a private message (PM) to the user, but many users has set a different privacy for PM so the bot can't communicate to the command issuer.
### What is your ideal solution to the problem?
I was thinking about adding a channel ID variable that can be set on config file to send bot notifications like updates on a chosen channel of the server
### How would this feature be used?
Set the discord channel ID for bot notifications on config file
### Additional Info
_No response_
### Checklist
- [X] I have checked [the documentation](https://jmusicbot.com/) to make sure this feature doesn't already exist
- [X] I have searched for [similar feature requests](https://github.com/jagrosh/MusicBot/labels/enhancement)
- [X] I have confirmed that my requests is **not** on the [list of things that will not be added](https://jmusicbot.com/things-that-wont-be-added)
- [X] I am running the latest version of the bot: 
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the example configuration entry for updatealerts and the code that sends version-update notifications. Trace how configuration values reach notification handling; done means a configured Discord channel ID routes bot notifications there while preserving the existing behavior when it is unset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100