Texture MetaData not parsing Optifine options properly

[Boy0000]

It is a mod only thing but it causes issues so some "UnknownMetadata" class or something would suffice

[azapg]

Just to try to reproduce, how are you using .mcmeta there? I thought Optifine used .properties files

[yusshu]

Since we have Sodium classes now, we could add Optifine too, feel free to open a PR if this is still a priority!

Also I have thought about UnknownMetadata class which would make sense, but since the information is unknown, it would be a pretty weird api, maybe something like

interface UnknownMetadataPart extends MetadataPart {
    String name();

    // json-serialized content
    @ApiStatus.Internal
    String content();
}

which is a bit inconsistent since the core api is "format-agnostic"

[FixedDev]

Since we have Sodium classes now, we could add Optifine too, feel free to open a PR if this is still a priority!

Also I have thought about UnknownMetadata class which would make sense, but since the information is unknown, it would be a pretty weird api, maybe something like

interface UnknownMetadataPart extends MetadataPart {
String name();

// json-serialized content
@ApiStatus.Internal
String content();

}
which is a bit inconsistent since the core api is "format-agnostic"

Maybe something like a Map<String, Object> would be good enough?