Information

Minecraft version: 1.21.4
Modloader: Fabric

Mod name: GUI Followers

Feature description

Hi! Can we add compatibility for Wolf Armor? I don't know if there's also a bug, but it seems to retain old information of wolves in specific server worlds, despite either being full health, but regardless! Can there also be Icons similar to Xaero's Map mod icons to identify which wolf is which? In the case of collecting all the wolf variants in a journey, it's difficult to tell who is hurt or who isn't hurt as there is no distinguishing features between the wolves on said trip other than their fur type or collar, I believe it'd be amazing to try to have an identifier of sorts to show collar, whether they have wolf armor or not, dyed wolf armor even something to help separate them if possible! And % of the Wolf armor and how much it needs to be healed, maybe even a clearer indicator that it badly needs to be repaired or it will break, something to try to show urgency? I've lost too many wolves not realizing their armor's been broken despite leaving them be for a minute in a trial chamber, only to realize they've lost the armor and died suddenly.
Still, I hope you can consider it!
Best regards, love your mod!

Hey!

I appreciate the suggestion! While I'd love to add all features submitted on the issue-tracker, I've got to prioritize working on them due to having limited time. In order to see which features users would like to see most, I've created https://serilum.com/mods/requests, which shows a table with all feature request submitted.

I'm aware that this is not the reaction you were looking for, but the reality is that I can't keep up with the demand. I try to do as much as I can.

Users are able to upvote requests by reacting to the first issue comment on this GitHub page with one of the 👍 😀 🎉 ❤️ 🚀 👀 emoji's. The request with the most unique reactions, will be shown at the top. You can of course add the reactions yourself too, but don't have to :). The author of the feature is already counted as +1.

I won't only focus on popular features in the upcoming years, but it does help with prioritizing. I'll probably work on a combination of popular and interesting/needed/fun submissions.

I'll close this issue with "not planned" as a way to separate an open feature request from an actual completed issue. This does not actually mean it's not planned! Incompatibilities and bug reports will still remain open.

When the feature is implemented, I'll again post a comment and close it as "completed".

Thank you for taking the time to submit the suggestion! ❤️