Get All Status

[bauepete]

Story

As a player or virologist I want to get the current status of all players in order to see their progress.

Example

Player @jfuerlinger is on level M.

+serta-status

Expected response

• The color bar on the left side indicates the level color
• The message of the day is dependent on the level and chosen randomly if more than one message is available
• The immunisation level is taken from an satellite training system (e.g., SoloLearn) and transformed into the Serta immunisation scale
• The thumbnail shows the first letter of the game level and is red (if the user is infected), green (if the user's immune level allows a health check), and yellow otherwise
• If the player suffers from an infection the footer shows the following message: "INFECTION ALERT!! You currently suffer from an infection and this will last another 2 hours, 20 minutes and 10 seconds.

Remark

• Calls of +serta-status @<some name> and `+serta-status @ @ are handled by issue Get Player Status #4

DoD

• The list of status messages shall be sorted from the highest to the lowest game levels in descending order. Within a game level the immune level shall be the second sort order (again descending)
• The color bar reflects the level of the player
• The avatar is shown correctly
• The message of the day is chosen randomly from the list of level specific messages
• The thumbnail has the correct level abbreviation (S, A, M, C, F, P)
• The Level field shows the correct game level
• The immunisation level is taken from SoloLearn where the the points of SoloLearn are subtracted by a correction (see MISSING) and multiplied by 0.1
• The Infection Alert is shown correctly.
• If the infection has passed the immune level has to be reduced by some amount (concrete amount to be taken from the config)

[jfuerlinger]

@bauepete would you be so kind to provide me some funny messages for the different levels:

e.g. "M" => Hospitals line up to get your help!

It would be great to have more than one message per level.

[bauepete]

Yes this is an issue with low priority (see issue #12). I will add them as we go. Did not have the creativity last night …