![[ETF] Entity Texture Features - [Fabric & Forge]](https://media.forgecdn.net/avatars/thumbnails/983/279/256/256/638491557830728907.png)
[Suggestion] Variable textures based on entity health
EnderBC opened this issue · 7 comments
I'm the creator of the pack Torturable Healthbars, that uses a function that only optifine has right now, which is the ability to change the texture of a specific mob based on its health.
I've noticed that many people have also asked me if ETF compatibility is possible, and I use it too, and I would really like it if it could be done, obviously if it can be done and if you would like to add it.
Thanks if you would like to add this feature, otherwise thanks anyway for taking your time to read
If the pack is needed, here's the link https://modrinth.com/resourcepack/torturable-healthbars , that has all the information needed and all the pictures of the mobs
thats already in etf
the pack should work if it uses optifine random texture properties
does it not work?
I tried and it doesn't seem to work, at least for me, unless it has been added in an update this week. It does use random texture properties
This is a simple ETF fix, Fabric Skyboxes Interop had the same issue. Optifine supports properties with range matches -, but it's not mentioned anywhere in the documentation. It seems that the dev of Torturable Healthbars has only included this format of range matching, where as it seems ETF only supports - ranges at the moment.
Oh wow thanks a lot it works now!
This is a simple ETF fix, Fabric Skyboxes Interop had the same issue. Optifine supports properties with range matches <max>-<min>, but it's not mentioned anywhere in the documentation. It seems that the dev of Torturable Healthbars has only included this format of range matching, where as it seems ETF only supports <min>-<max> ranges at the moment.
Also some testing may be needed, as swapping the numbers directly seems to behave weirdly in the case where health is between a range, for example if an entity has a health between 9 and 10, then it will not match either the 5-9 range or the 10-12 range, however this might be correct in Optifine and just be because I'm swapping the numbers, or it could be an oversite by the dev.