sp614x / optifine

1.8k stars 418 forks source link

Ender Dragon Random Entity Skins #3750

Open SkaliberWasTaken opened 4 years ago

SkaliberWasTaken commented 4 years ago

Renaming the ender dragon doesn't change it's skin

ghost commented 4 years ago

More details please...? Like from the template?

SkaliberWasTaken commented 4 years ago

When using name detection with random entity skins, the dragon does not change its skin. My assumption is that this was simply never implemented because you can't apply name tags to the dragon in vanilla Minecraft. However, datapacks are becoming increasingly common, and we can now assign a custom name to any mob (including the dragon) therefore I am asking that this inconsistency be accounted for (: It's not exactly a bug report, it's just the game lacking a feature that was previously not possible, but now is!

sp614x commented 4 years ago

Which OptiFine version?

anjoismysign commented 4 years ago

1.15

ofseaandstars commented 4 years ago

I can confirm this is still occurring on 1.16.2 (with latest Optifine build). Works fine with another mob (pig).

Waywardson22 commented 3 years ago

Bump for 1.16.3. Issue is still there

ofseaandstars commented 3 years ago

I can also confirm this is the case. Using MC 1.16.3 and Optifine 1.16.3_HD_U_G5 and I cannot get the Ender Dragon to load a custom skin. Working fine for Pigs/Spiders/Wolves etc.

File structure is assets/minecraft/optifine/random/entity/enderdragon/dragon.properties Texture is called dragon2.png and the properties has:

skins.2=2
name.2=Prismatic Dragon
SirLeezus commented 3 years ago

Having the same issue on 1.16.5 right now, did anyone solve this yet? All other mobs work fine.

Rixic commented 3 years ago

https://github.com/sp614x/optifine/issues/5067

I should note that this is also true for custom parts you add to the enderdragon, if you try change the skin of a custom part baesd on the name it just doesn't do anything

Ancientkingg commented 2 years ago

I can confirm this is still the case for 1.17.1

CadenKoehl commented 2 years ago

I can also confirm that this is the case for 1.18.1