I think the TEXT COLOR of the different messages that are displayed in the "Logs" section of the TUI could be improved.
The majority of the messages appear in "RED" color and I feel this makes it difficult to differentiate between what are less critical and more critical Status messages.
FEATURE REQUEST
Please go through all the different status messages and categorise them into the following 3 "color" buckets:
A) GREEN COLOR [Error Codes: 1001-10xx]
These are for non-critical errors. The Epic server is still performing perfectly and the status messages are more "informative" in nature.
E.g. "Yay! You won a block" or "...job_id XX - Submitted too late."
B) ORANGE COLOR [Error Codes: 2001-20xx]
These are for semi-critical errors, where the Epic server is operating, but may need some attention.
E.g. BanReason issues
C) RED COLOR [Error Codes: 3001-30xx]
These messages are show-stopper errors that inform the administrator that the server is malfunctioning and not processing blocks or not able to mine blocks etc.
E.g. "Error building new block: Can't connect to wallet listener."
I am happy for the developers to use there own discretion as to the categorisation of the different status messages into the different "color" buckets as they would know (better than I) what are non-critical vs semi-critical vs show-stopper errors are in the scheme of things.
ERROR CODE NUMBERS
After each bucket is a Code range. I feel each Error should be assigned a unique Code that corresponds to the level of the error. This way when an Admin sees an Error Code and may want to do a little more research on the error, they can Google the Error Code and they can some across a GitHub page with all the Error Codes and more detailed descriptions and remedies.
This should help reduce the number of Support Tickets on error codes.
I think the TEXT COLOR of the different messages that are displayed in the "Logs" section of the TUI could be improved.
The majority of the messages appear in "RED" color and I feel this makes it difficult to differentiate between what are less critical and more critical Status messages.
FEATURE REQUEST
Please go through all the different status messages and categorise them into the following 3 "color" buckets:
A) GREEN COLOR [Error Codes: 1001-10xx] These are for non-critical errors. The Epic server is still performing perfectly and the status messages are more "informative" in nature.
E.g. "Yay! You won a block" or "...job_id XX - Submitted too late."
B) ORANGE COLOR [Error Codes: 2001-20xx] These are for semi-critical errors, where the Epic server is operating, but may need some attention.
E.g. BanReason issues
C) RED COLOR [Error Codes: 3001-30xx] These messages are show-stopper errors that inform the administrator that the server is malfunctioning and not processing blocks or not able to mine blocks etc.
E.g. "Error building new block: Can't connect to wallet listener."
I am happy for the developers to use there own discretion as to the categorisation of the different status messages into the different "color" buckets as they would know (better than I) what are non-critical vs semi-critical vs show-stopper errors are in the scheme of things.
ERROR CODE NUMBERS
After each bucket is a Code range. I feel each Error should be assigned a unique Code that corresponds to the level of the error. This way when an Admin sees an Error Code and may want to do a little more research on the error, they can Google the Error Code and they can some across a GitHub page with all the Error Codes and more detailed descriptions and remedies.
This should help reduce the number of Support Tickets on error codes.