New Health Analyzer UI

[Aeshus]

About the PR

This PR focuses on redesigning the Health Analyzer’s user interface.

Additionally, it also introduces new information:

• Picture / Entity Sprite
• Status
• Species

It also resolves a bug that caused the Health Analyzer to resize itself every time it was redrawn.

As requested, the UI will also grow up until a point (525 pixels) so that if there is a reasonable amount of damage types, a doctor won't be required to scroll. If it's unreasonable, it will continue to be scroll-able.

Why / Balance

This update aims to make the Health Analyzer more user-friendly for doctors by providing information that could already be manually collected, but in a more accessible manner. Instead of needing to look at the person closely to identify their species or needing a medical hud.

The current UI of the Health Analyzer lacks visual appeal, with basically no margins and an overall cluttered appearance. Thus, this PR improves visual distinction between different sections.

• The entity sprite allows doctors to easily recall who they scanned by simply viewing their icon.

• Species information is important because it influences the type of medicine that can be administered (e.g., copper for certain species).

• The status section is added to make it easier for medical interns to quickly identify the condition of a patient or those who forgot to grab a medical hud.

Future enhancements could involve integrating the Alerts system (e.g., notifications for Bleeding, Low Oxygen, etc.) into the Health Analyzer, which would allow doctors to diagnose issues more efficiently via the icons. This would also complement the reintroduction of conditions like malnutrition and help in recognizing eye-related issues.

Technical details

The entity sprite feature was adapted from the Character screen.

Species information is derived from the HumanoidAppearance. Anything else (e.g. Pun-Pun, Borgs, Mice) will be labeled as "Non-Humanoid."

Status is determined by reading the MobState and converting the byte result into a localized string. I couldn’t find a more succinct method that provides the same outcome.

Media

Old

New

Requirements

• I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
• I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

No changes to any public interfaces were made. Only changes made were interior to the Health Analyzer .xaml and .xaml.cs files.

Changelog

🆑

• add: The Health Analyzer now displays the patient's picture, species, and current status.

[lzk228]

sometime it feels shitty to scroll to see all the damage, maybe you can somehow put all the available damage on one non-scrollable ui?

[Aeshus]

I'm unsure on what you mean by that.

Do you mean the window itself should resize so scrolling isn't needed?

[lzk228]

yes, this one also would be great

[Veritable-Calamity]

In-regards to a non-scrolling UI:
Consider having the damage types listed in a table of sorts with two columns, that way the UI doesn't become super long when multiple damage categories are present.

For example:

Brute	Burn
Blunt ###.#	Heat: ###.#
Piercing ###.#

[Aeshus]

In-regards to a non-scrolling UI: Consider having the damage types listed in a table of sorts with two columns, that way the UI doesn't become super long when multiple damage categories are present.

For example:
Brute Burn
Blunt ###.# Heat: ###.#
Piercing ###.#

I was also thinking at one point of having an element similar to the gas analyzer where it showed the composition of the damage types. This would only really be useful for the bigger categories, but could make it easy to recognize quickly "Oh, this guy is like 90% airloss"

[Veritable-Calamity]

I was also thinking ... of having an element similar to the gas analyzer where it showed the composition of the damage types.

Maybe have a percentage of how much damage each category makes up in the header for the damage category. So it'd be:

Brute: ###.# (90%) | Burn: ###.# (10%)
or something.

[Aeshus]

yes, this one also would be great

This seems to work, though I'll need to keep scrolling for exceptionally long ones.

Image