Currently some of the command names for custom commands seem to visually be uppercase and lowercase on char 1, we intended the first char to be uppercase just for visuals on the control panel etc.
This is due to a inconsistency between the chat command interactions of custom commands and the website control over custom commands.
But custom commands usage/running is not affected due to running of custom commands is case insensitive
Currently some of the command names for custom commands seem to visually be uppercase and lowercase on char 1, we intended the first char to be uppercase just for visuals on the control panel etc.
This is due to a inconsistency between the chat command interactions of custom commands and the website control over custom commands.
But custom commands usage/running is not affected due to running of custom commands is case insensitive