As for server-info/server-status :
The main difference is the authorization ;
info has more details than status, but status can be called by any user on the guild. User doesn't need to have the miscord-user role.
It's also designed to be more readable and accessible.
However, since you got a working player list now, we could re-integrate it under info.
Also, if possible, idea would be to consider info as a main "hub" for commands : give clickable options, either in the embed directly, or reactions, to trigger other commands (chat bubble icon > server-message / computer icon > server-restart / etc etc).
-- edit add : maybe if we can create other lightened version of commands, to be accessible by any users, it would be wise to separate them from server-* group, to have a group on their own, like a "Public" group or something. Ideally, letting the admin choose individually which commands to allow/disallow for that public group would be purrfect.
As for server-info/server-status : The main difference is the authorization ; info has more details than status, but status can be called by any user on the guild. User doesn't need to have the miscord-user role. It's also designed to be more readable and accessible. However, since you got a working player list now, we could re-integrate it under info.
Also, if possible, idea would be to consider info as a main "hub" for commands : give clickable options, either in the embed directly, or reactions, to trigger other commands (chat bubble icon > server-message / computer icon > server-restart / etc etc).
-- edit add : maybe if we can create other lightened version of commands, to be accessible by any users, it would be wise to separate them from server-* group, to have a group on their own, like a "Public" group or something. Ideally, letting the admin choose individually which commands to allow/disallow for that public group would be purrfect.