Duplicate texture-based CITs are ignored when non standard native models are supplied about citresewn HOT 11 CLOSED

Nono, nbt is working fine. I've tested it plenty, trust me.
I'm sorry but I can't help with what you've given me. Gonna need the logs and the resourcepack in question.

from citresewn.

Here's the pack. It works in the latest version with Optifine, but with CITR it does not seem to be reading the nbt properly

from citresewn.

Gonna need the logs, the pack works just fine for me with all of the stew types

from citresewn.

Hm... weird, I might have to update some stuff, gonna see if it works properly then. Also what do you mean by the logs

from citresewn.

I mean the game's logs. Make sure the pack is enabled and upload %appdata%/.minecraft/logs/latest.log

from citresewn.

Nevermind, I isolated the issue. It seems that, if you have a custom item model AND the CIT NBT data, the custom item model breaks everything. Here, I can quickly slap together a pack of what I mean

from citresewn.

I think the issue is a bit more specific than that. Item models and the nbt condition are completely separate and should not affect eachother at all.
CIT is supposed to work natively with models.

from citresewn.

Look, this is the pack. The only difference between this and what I sent you is I added the vanilla model for suspicious stew and a texture for it. When I added the item_particle parameter, everything stopped working and they use the withering suspicious stew texture. I mean they're called bugs for a reason, idk why that happens

from citresewn.

This'll be fixed in v0.8.0

from citresewn.

I know this is closed, but I found a workaround to the bug. As long as you specify a new texture for every single texture mentioned in the original model, it fixes the broken textures. Tedious, but possible

from citresewn.

Yeah, the fix I pushed in e27a529 just does that automatically(it generates a new file name internally so duplicates wont be overwritten)

from citresewn.