Description
One of the mod's users reported to me that custom elytra (by renaming) don't work with the resource pack of his server. I checked it, compared to Optifine, this feature really does not work as expected.

Used resource pack
Example Pack.zip

Technical Info

• Minecraft: 1.18.2
• CIT Resewn: latest from Modrinth (1.0.1)
• Fabric Loader: 0.13.3
• Fabric API: 0.50.0
• Windows 10

Additional
Also tested with CITResewn 1.0.2 SNAPSHOT, but the result was the same.

If removing them still doesn't fix the issue I'll need logs.

latest.log
I'm sorry, I completely forgot about it...

If this really only happens with MinecraftCapes installed, I can't help you here.

I cannot(and will not) add explicit support for closed-source mods.

Every single one of the elytra texture cits have a stray elytra in their 2nd line. (bee.properties, niki.properties & yoohoo.properties)

Not sure why optifine's properties wouldn't ignore that but with the nature of my .properties interpreter I won't let it through in CIT Resewn.

If removing them still doesn't fix the issue I'll need logs.

removing them still doesn't fix the issue

This really worked in a clean install (only CIT Resewn and LazyDFU), but when I checked in the main installation with the rest of the mods, the result returned to the start point.

It looks like this is an incompatibility with the MinecraftCapes mod or with the cape as such. In that case, CITResewn 1.0.2 SNAPSHOT didn't fix the problem described in #121.