You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please check if a similar issue has already been reported.
I checked this type of issue has never been reported.
Please check you're using proper versions.
I checked all of them in the right version.
Please check if this issue's from out of our area
I understood the problem.
The name of the mod
No response
After all of these, please check if you're just pressing the ok buttons to skip this process.
I read the checklist and I promise I'll provide all the information that is needed to fix the issue
Minecraft Version
1.20.1
The Issue
I was doing some tests with datapacks with differents model and armature, but i noticed theres a texture bug that happens to entities that use the "epicfight:custom" render when using shaders
in the first image you can see the patched entity without shaders, in the second image i was using complementary and in the third image i was using bliss
Steps to Reproduce
patch an entity using the "epicfight:custom" render type
use some shaders
The text was updated successfully, but these errors were encountered:
Please check if a similar issue has already been reported.
Please check you're using proper versions.
Please check if this issue's from out of our area
The name of the mod
No response
After all of these, please check if you're just pressing the ok buttons to skip this process.
Minecraft Version
1.20.1
The Issue
I was doing some tests with datapacks with differents model and armature, but i noticed theres a texture bug that happens to entities that use the "epicfight:custom" render when using shaders
in the first image you can see the patched entity without shaders, in the second image i was using complementary and in the third image i was using bliss
Steps to Reproduce
patch an entity using the "epicfight:custom" render type
use some shaders
The text was updated successfully, but these errors were encountered: