ETF Backwards-Compatibility Toggles for OptiFine Behaviour

guide

Entity Texture Features includes a set of options that exist purely to match how OptiFine handles random textures, and these toggles live in the mod's settings screen. The settings screen opens from the Settings button, whose position is controlled by the Settings button location option in the resource pack menu; hovering over any button shows a tooltip explaining it. The compatibility options are grouped under a description stating that they exist for backwards compatibility with OptiFine, that some of them limit certain features because OptiFine does, and that some enable odd behaviours because OptiFine does.

Rule number gaps

OptiFine caps the numbering used in random `.properties` files: when rules are read in sequence, the numbers cannot jump by more than nine. The Limit rule number gaps toggle makes ETF enforce that same cap. Turn it on if you want `.properties` files written for OptiFine to behave identically here.

Random suffix skipping

When a pack uses numbered random suffix variants instead of a `.properties` file, OptiFine permits those numbers to skip values. Skipping is considered bad practice since the numbers should run in sequence, but the Allow random suffix number skipping toggle lets ETF skip numbers the same way OptiFine does. Enable it to load packs that rely on that behaviour.

Base texture overrides

The Prevent base texture overrides toggle stops ETF from loading overrides for the base texture when one is present in the optifine/etf directories. As an example, a chicken texture placed there would no longer act as an override for the vanilla texture. Having this on matches default OptiFine behaviour.

Broken texture paths

Vanilla refuses texture paths containing any character outside `a-z0-9/._-`. The Allow broken texture paths toggle overrides that restriction, so textures using spaces or capital letters can load. It is disabled by default, since these naming problems are better fixed by the resource pack creator. When ETF meets such a path while the option is off, it reports that the texture will be ignored unless you enable the option, then shows the vanilla error message. When the option is on and such a resource loads, ETF warns that the file name should be corrected.

A few nearby options also exist for matching or working around OptiFine-format packs:

Allow restricting unknown texture properties sets whether spawn condition restrictions are permitted for properties added by ETF, EMF, or other mods.
Always check for '_e' emissive makes the mod look for the `_e` suffix even when a resource pack has configured a different emissive suffix.
Disable using default directory turns off the vanilla directory for random textures and enforces use of the optifine and etf folders, which helps with mods whose entity textures are named like `mob2.png`.
Allow warden glowing textures for full model extends a warden's glowing textures, which vanilla renders on only one body part, across the whole model.
Automatic animation compat stops ETF from touching any texture that currently has an animation, but only when the MoreMcmeta mod is present; it may introduce z-fighting depending on your shader.
Automatic PBR compat stops ETF from touching textures that have PBR textures alongside them when shader mods are present, and may likewise introduce z-fighting.
Emissive armor & trims can be switched off if ETF's armor code conflicts with modded armor, until that code is reimplemented.

Operating the toggles

Every one of these options is a simple on/off switch inside the ETF config screen. Click the Settings button in the resource pack menu to reach them, hover a control to read its tooltip, and click to flip its state. Because the options change how textures are loaded, expect to reload resources after adjusting them.