Parrots on shoulder cause crashing
I saw that the issue was posted on the github as an issue, but I also want it to be known here. I have attached the crash report. I can provide a full list of mods and libraries as well if needed.
Version: 1.21.1
Neoforge version: 21.1.206
Iris: 1.8.12+mc1.21.1
Sodium: 0.6.13+mc1.21.1
23 Replies
crash-2025-08-31_14.53.50-client.txt uploaded to mclo.gsUploaded by dragonfire0612
That's a lot of mods in your crash log. Have you at least confirmed it happening with only Sodium and Iris?
Also, it seems like the crash is caused by Entity Texture Features.
Yeah, it only happens with Sodium and Iris turned on.
Entity Texture Features doesn't cause the crash on it's own
:thonkwithshades:
Can you test with only Sodium and Iris enabled then? Remove or put all those other mods away and retest.
Currently recovering my Windows install, so I can't test it on my side yet.
Yeah, I can do that tomorrow. If that's ok
All good.
Well, I got someone on my server to test. It does appear to be something conflicting between Fresh Animations, Sodium, and Iris.
crash-2025-08-31_20.49.26-client.txt uploaded to mclo.gsUploaded by dragonfire0612
Alright, this should be workable. Pinging @IMS to see if he can do anything about this.
I do not see how this could be Iris
But I guess I can try tomorrow
Reminder completed.
Reminder set!
I will remind you at <t:1756744050:F> (<t:1756744050:R>)
Custom Message
do that
Use
/reminder remove to cancel this reminder@IMS
Reminder
do that
Set time
<t:1756700850:F>
hhh
you were right
storing here
cc @Traben, not quite sure what's going on here but the code seems suspicious
trying to look at it more
you wouldn't have seen it there
these were typed incorrectly in the source at some point when i changed the mixin due to some forge limitation
was
Consumer<T> rather than the correct Consumer<EntityType<?>>
would affect all < 1.21.2had to make this jank modify arg wrapper because forge refuses to let me target the lambda at head and tail
will be fixed shortly, gonna look at other bugs first
You all are awesome for looking into this. I've seen plenty of devs in the past not even bother to respond to reports like this. But, I've also seen a handful of devs, like you guys, react in a positive way and sincerely look into the issue.
Keep up the good work :)