MCM-427[1.8] Previously Horse variants were hard-coded. Now they aren't, causing issues for older Horse behaviour files
Partner Rank:
3
Partner Team Reporting:
Polymaps
Verification builds and Platforms:
ver. 1.8.11.0 build 1294025
Summary:
Pre-1.8, Horses did not have a behaviour to determine their variant or markings. 1.8 has added "minecraft:variant" and "minecraft:mark_variant" (awesome), but it has caused an issue with horse behaviours which were made before 1.8. If a behaviour file does not use the variant component, all horses which spawn will be the same variant.
Impact:
Many pieces of content use horse variants as a way to have random models. For example, in Block & Seek, horse variants are used for the different "props". The horse will randomly spawn in as a Skull, Cake, Brewing Stand, Chest, Flower Pot or Cobweb model. Since 1.8, these horses only ever spawn in as Skull models. This negatively affects our map because it limits how the map was supposed to be played and players aren't getting the intended experience.
Repro Steps:
- Download Block & Seek from the Store
- Create a new world, ensuring Cheats Enabled is ON
- Summon horses in the lobby with /summon horse
- (Ignore the fact that they are instantly killed, but their model is still visible during the death animation)
Observed Results:
Horses always spawn in as the Skull model.
Expected Results:
Horses should spawn as random variants for older maps which do not specify "minecraft:variant" components to ensure backwards compatibility.
Screenshots/Videos attached: Yes/No
Yes, screenshots of the props spawning in 1.8 and spawning in 1.7 (ignore the fact that the horses are dying, that's part of the map) Notice how 1.8 only spawns Skull models, while 1.7 spawns different models.
Regression Builds:
Horse variants work normally in 1.7
Notes:
If it's not possible to have some sort of backwards compatibility check for the horses, then a notice to all creators that we need to update content which relies on horse variants would be appreciated!
