[Feature Request] Config Setting/Command to shuffle all songs in queue, regardless of requester
- 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.
N/A
### What is your ideal solution to the problem?
A config option seems like the most optimal way to implement this feature, however a separate command would also be acceptable.
### How would this feature be used?
1. (If adding the config setting) Set setting to true
2. Run command
3. The bot shuffles all requested songs in the queue, regardless of requester
### Additional Info
This music bot is very attractive to my small server of friends, but a lack of this feature is an absolute deal breaker. Having this feature would make us switch immediately. Also, this may be considered a clone of [Issue #1025](https://github.com/jagrosh/MusicBot/issues/1025), however due to its age and status as "Open," I have right to believe it was overlooked and believe it should be brought up again.
### 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
Research direction
The issue names no files, tests, or entry points. Start by locating the existing queue command and configuration handling, then determine where requester-specific ordering is applied. Done means a setting or command shuffles all songs currently in the queue regardless of requester, with coverage for the resulting order.
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