Fix global formatting for command responses

[almanacks-zz]

Everything is gray. Some things are red`.

Everything should follow proper SERVER, INFO and STAFF formats.

[falceso]

I marked the /event command as INFO as it seems fit, but it's also a staff only command so yeah...

Anyways this is a side-issue. I've reviewed Command_permban & Command_unpermban and was wondering if it was purposely coded to display only to the staff member who did it. Now sending to all online staff.

Also are kick/ban messages included under INFO?

Finally, is the message always going to be grey(&7) or can we change it out as suited.

Remaining:

• PlayerListener - Mixed, mostly STAFF
• Staff & Architect Command
• Unpermban & PermBan - STAFF ONLY?
• Event Mode? (Awaiting Reply)

[ncurran02]

@falceso the permban messages were intentional.

[falceso]

To my knowledge, command outputs are now up to format.

For future reference:
STAFF: &8<-> &4&lSTAFF
INFO: &8<-> &3&lINFO
SERVER: &8<-> &9&lSERVER

This issue is now safe to close.

[falceso]

New Question: We should probably have more output into Console. I suspect a quick change of the NUtil.globalMessage would do, haven't tested it yet.

[ajaxvp]

I'm starting to replace old ways of getting messages out with NUtil.globalMessage() instead.

Also, we should be replacing ChatColor with NUtil.colorize() instead, to follow code format.

[falceso]

Yeah, good idea. Going to attach the output to console on the globalMessage system.

[almanacks-zz]

Remaining messages:

• Blocked commands
• User doesn't have permissions to use a command
• /rank
• /staff info
• /mode
• Exiting staff mode