fuzzball icon indicating copy to clipboard operation
fuzzball copied to clipboard

Idea: categorize messages (including in-server) with prefix coding

Open wyld-sw opened this issue 1 year ago • 3 comments

Some MUCKs use muf words and mpi macros to visually separate messages to help identify success, failure, or unknown. I've seen this called "stoplights" as they're usually accompanied by a red/yellow/green color.

This seems to be used well on HLM, and having it built-in for server messages might be good too, in addition to the following MUF primitives and MPI functions:

  • PREFIX_GOOD or {prefixgood:} could change a string "Your command was successful" into something like "<*> Your command was successful.", with a system-defined prefix that may include color codes.
  • PREFIX_WARN or {prefixwarn:} could change a string "Please review the above messages." into something like "<?> Please review the above messages.", with a system-defined prefix that may include color codes.
  • PREFIX_BAD or {prefixbad:} could change a string "Permission denied." something like "<!> Permission denied.", with a system-defined prefix that may include color codes.

Sysparms that could work with this include:

  • enable_message_categories. if no, none of these new words or macros [or server functionality] change the message.
  • message_category_good_prefix. Prepended to the message if the "good" category is used. Can include color codes.
  • message_category_bad_prefix. Prepended to the message if the "bad" category is used. Can include color codes.
  • message_category_warn_prefix. Prepended to the message if the "warn" category is used. Can include color codes.

If color codes are accepted, we would need to add a reset code in case the prefix doesn't include it.

(names of sysparms, primitives, and functions not set in stone, of course!)

Thoughts?

wyld-sw avatar May 06 '23 22:05 wyld-sw