jagrosh / jagrosh/MusicBot

[Feature Request] Add Support For Multiple "AltPrefixes"

Open
#1,059 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
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.

I wanna have more than 3 prefixes for my server to use.

### What is your ideal solution to the problem?

make `altprefix` an array list

### How would this feature be used?

Maybe I have `!` and `music!`, but I _also_ wanna use a dot and a bracket instead of just an exclamation mark,
so I edit the config file, and put all the prefixes I'd like to use in a list of alternative prefixes.

### 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: ![Release](https://img.shields.io/github/release/jagrosh/MusicBot.svg)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the configuration handling for `altprefix` and the command-parsing entry point that currently limits prefixes. Trace how values from the config file are loaded and matched, then verify that multiple configured prefixes work for commands without breaking existing configurations.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.