Describe the bug
In the latest versions of Optifine, a base model for variations is only required if you don't have a .properties file. So it either need to have a base model or a .properties file to make variations work. In EMF, with the "Require base model - compatibility" option turned on (default settings), variations will only work if you have both, a base model and a .properties file. With the "Require base model - compatibility" option turned off, the base model is not mandatory, but the combination of base_model + variation2 + variation3 still won't work, unlike in Optifine.
To summarize:
In Optifine:
model2 + model3 + model.properties will work
base_model + model2 + model3 will work (a random model with equal chances is chosen, similar to how Random Entities work)
model2 + model3 won't work
base_model + model2 + model3 + model.properties will obviously work
In EMF (with "Require base model" enabled):
base_model + model2 + model3 + model.properties will only work
In EMF (with "Require base model" disabled):
model2 + model3 + model.properties will work
base_model + model2 + model3 won't work
base_model + model2 + model3 + model.properties will work
Describe the bug
In the latest versions of Optifine, a base model for variations is only required if you don't have a .properties file. So it either need to have a base model or a .properties file to make variations work. In EMF, with the "Require base model - compatibility" option turned on (default settings), variations will only work if you have both, a base model and a .properties file. With the "Require base model - compatibility" option turned off, the base model is not mandatory, but the combination of base_model + variation2 + variation3 still won't work, unlike in Optifine.
To summarize:
In Optifine:
In EMF (with "Require base model" enabled):
In EMF (with "Require base model" disabled):
List and link to broken resourcepacks resources_end_test.zip
Expected behavior and Screenshots Optifine: EMF:
Versions: