Commit 4c970f6b16c93cf0ac2d2d58e32ac1336a9fda2a broke custom bot prefixes because it just does a literal match of the config string in prefixes instead of the old behaviour introduced in 2b44d0af29588456f3c74d2571b0850d0760abce where bots can have a list of possible custom prefixes because some people like one over the other. So instead of a config prefix string of "!." allowing users to choose !command or .command, it forces users to use !.command instead.
Commit 4c970f6b16c93cf0ac2d2d58e32ac1336a9fda2a broke custom bot prefixes because it just does a literal match of the config string in prefixes instead of the old behaviour introduced in 2b44d0af29588456f3c74d2571b0850d0760abce where bots can have a list of possible custom prefixes because some people like one over the other. So instead of a config prefix string of "!." allowing users to choose !command or .command, it forces users to use !.command instead.
Am I the only one who thinks this is an issue?