> For the complete documentation index, see [llms.txt](https://itemsadder.devs.beer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://itemsadder.devs.beer/japanese/faq/broken-emote-textures.md). # Broken emote textures ## Shader Mod issues Mods that allow the usage of custom shaders will break emotes due to them overriding/replacing the vanilla Shader which ItemsAdder uses for the Emotes feature. The only way to *"fix"* this is by disabling the shaders themself or removing the shader mod in question. {% tabs %} {% tab title="With Shaders on (Bug)" %} ![shader bug](/files/7JxjAaNz7mUQWkFj8pZX) {% endtab %} {% tab title="With Shaders off (No Bug)" %} ![no shader bug](/files/g2c7uH9jiFLkNuvPMjPn) {% endtab %} {% endtabs %} Known shader mods that cause issues: ### Optifine Related issue: ### IrisShaders Related issue: ## Mods that change the player skins A mod may change the default player model/skin and can therefore be affected by ItemsAdder's shader manipulations, or vice-versa. Known Mods that cause issues: ### 3DSkinLayers The mod alters the outer skin layer to make them appear in 3D, which alters the player model itself. A possible fix is to disable `3D Skulls` and `3D Skull Items` in the mod's settings.\ There is currently no workaround for using 3D layers in Emote animations. Additional information can be found in the related issue: ### Customizable Player Models This mod allows the complete customization of the player model including replacing parts of it or the model as a whole.\ Due to this will Emotes not display properly in ItemsAdder and there is currently no fix available outside of not using the mod or not using the Emote animations. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://itemsadder.devs.beer/japanese/faq/broken-emote-textures.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.