Veil Lib Mod FAQ

Veil Lib is a library mod that other mods depend on—it doesn't add content on its own. You need to install mods that use Veil Lib to see its features in action, such as mods that add custom shaders or animated entities.

Several mods depend on Veil Lib for their rendering systems, but the best way to find them is to check the mod's CurseForge or Modrinth page for a list of dependents. New mods are added regularly as developers adopt the library.

No configuration is required for basic use—Veil Lib works automatically as a dependency. Mods built on top of it may have their own config files for enabling or disabling specific visual features.

Veil Lib's post-processing pipeline and shader injection system are designed to work alongside resource packs, though heavily modified shader packs may conflict with injected changes. Test your combination to ensure compatibility.

Veil Lib provides the Necromancer system and bone-animation tools, but vanilla mobs still use their default animation system. Only mods that specifically rebuild their entity models using Veil Lib's bone system will have bone-based animations.

Veil Lib itself has minimal overhead as a library, but the visual features it enables—custom shaders, post-processing, and bone animations—depend on how intensively dependent mods use them. Performance impact scales with the number and complexity of active effects.

Veil Lib is compatible with most optimization mods, but incompatibilities can occur with mods that heavily modify the rendering pipeline. Check the mod's issue tracker or community forums if you experience crashes or visual glitches.

Veil Lib's color management system is designed for applying consistent visual themes across custom elements and effects, allowing mods to manage colors programmatically rather than hardcoding them. This makes it easier for resource packs to override visual styling.

Yes—Veil Lib supports all standard OpenGL shader types and provides a JSON-driven framebuffer system for custom graphic passes. You'll need to write shader code and configure it through JSON, which requires some graphics programming knowledge.

Check that your JSON framebuffer configuration is correct, that texture bindings match your shader uniforms, and that the post-processing pipeline is enabled in the dependent mod's settings. Enable debug logging to identify shader compilation errors.