Commands don't need any prefix

[pajlada]

Currently, you can add a command that does not start with a prefix (e.g. / or ! or ^ etc). The command works perfectly fine (assuming you type it as the first word).
Proposed solution: I feel like this is prone to errors, so I'd like to remove this without a replacement.
Considerations: If a user has /foo and foo added as commands, we'd only consider the first of those commands. If a user has bar as a command, we would treat the command as /bar

[Nerixyz]

Proposed solution: I feel like this is prone to errors, so I'd like to remove this without a replacement.

I use . as my prefix for commands. I'd expect others to have prefixes like ! or $. There's nothing in Chatterino that says "commands must start with /".

[pajlada]

I use . as my prefix for commands. I'd expect others to have prefixes like ! or $. There's nothing in Chatterino that says "commands must start with /".

What about "a command has to start with a non a-zA-Z0-9 character, where we default to / if no such prefix exists?"

[Mm2PL]

I do agree that it should be solved this way rather than enforcing a strict / prefix. I'll bikeshed a little and say that: I don't think the expectation of usage of ascii latin letters only for command names is good. I think we should check the characters' unicode category for being a letter or number instead.

[Nerixyz]

What about "a command has to start with a non a-zA-Z0-9 character, where we default to / if no such prefix exists?"

That would sound reasonable. Though, do we need to make this restriction at all? I imagine we check if the string starts with the command and then run the command on that. A warning like "this will run every time your message starts with {command}, are you sure?" when entering such a command would be better than silently assuming they meant to use / as their prefix.