latitude-rendering-compat-rules

Enforces Latitude mod rendering compatibility rules for Sodium and Iris shaders.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/joolbits/latitude --skill latitude-rendering-compat-rules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: latitude-rendering-compat-rules
Source: https://github.com/joolbits/latitude/tree/main/.windsurf/skills/latitude-rendering-compat-rules
Command: npx skills add https://github.com/joolbits/latitude --skill latitude-rendering-compat-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses rendering regressions that occur when mods designed for the vanilla Minecraft renderer are used with shader packs like Sodium and Iris, ensuring visual consistency across different rendering pipelines.

Core Features & Use Cases

  • Shader Compatibility: Enforces rules to prevent rendering issues with Sodium and Iris.
  • Modern Rendering Practices: Mandates the use of VertexConsumer and approved RenderLayers, forbidding direct GL state manipulation.
  • Use Case: When developing new visual elements for Latitude, such as storm walls or fog overlays, this Skill's rules ensure they appear correctly whether shaders are enabled or not.

Quick Start

Apply the rendering compatibility rules to the storm wall rendering code.

Frequently Asked Questions about latitude-rendering-compat-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why do my Minecraft rendering elements break with Sodium and Iris shaders?▼

Rendering elements break with shaders due to direct GL state manipulation and outdated vertex emission patterns. Enforcing modern VertexConsumer usage and approved RenderLayers ensures seamless integration and visual consistency across different rendering pipelines.

How do I ensure custom Minecraft mod rendering is compatible with shaders?▼

To ensure shader compatibility, mandate modern vertex emission patterns and use approved RenderLayers while forbidding direct GL state calls. This approach guarantees visual stability across vanilla and shader pipelines like Sodium and Iris.

What are rendering compatibility rules for Minecraft shader pipelines?▼

Rendering compatibility rules require using VertexConsumer for vertex emission and approved RenderLayers for rendering. They forbid direct GL state manipulation to maintain stability and satisfy shader-safe debugging constraints in hot render paths.

Does my mod need modern vertex emission patterns to work with Iris shaders?▼

Yes, mods need modern vertex emission patterns using VertexConsumer to work with Iris shaders. Direct GL state calls are forbidden because they cause rendering regressions and visual inconsistency across different rendering pipelines.

What is the best way to render fog overlays without breaking Sodium compatibility?▼

The best way to render fog overlays without breaking Sodium compatibility is to apply rendering compatibility rules that mandate approved RenderLayers and VertexConsumer usage, preventing direct GL state manipulation in hot render paths.

When should I not use direct GL state calls in Minecraft mod rendering?▼

You should not use direct GL state calls when developing visual elements for shader compatibility. Forbidding direct GL state manipulation and using VertexConsumer ensures rendering stability across Sodium and Iris shader pipelines.