[Feature Request] Improve shuffle UX
- 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.**
More often than not, I see users shuffling their songs and calling the queue command repeatedly until the next several songs in the queue contain what they want to be played. IMO, this is not very user or chat friendly.
**Describe the solution you'd like**
Allow an argument to be passed to shuffle, say `shuffle queue`, that combines shuffle and queue (limited to only the user's songs).
**Describe the basic flow/steps of using this feature**
1. User calls `shuffle queue`.
2. Bot displays queue filtered to only the user's songs.
3. Bot reacts with 🔀 and the existing queue emojis.
4. Reacting with shuffle does what the current shuffle command does and edits the message in place.
5. When the user is satisfied, they can react with the stop emoji or let it timeout.
**Additional context**
Could be related to #194.
**Have you confirmed that this idea is not already described here?**
Yes
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the existing `shuffle` and `queue` commands and review the related discussion in #194. Verify how queue display filtering, reactions, message editing, stopping, and timeout currently work. Done means `shuffle queue` shows only the user's songs and supports the specified shuffle, queue, stop, and timeout flow.
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