latitude-ui-and-hud-lifecycle

Manage Latitude mod UI screen lifecycle and HUD overlay rendering rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unintended UI behaviors in the Latitude mod, ensuring screens and HUDs appear only when and where they should, improving user experience and preventing visual clutter.

Core Features & Use Cases

  • Prevent Auto-Opening Screens: Stops configuration or worldgen screens from appearing unexpectedly after joining a world.
  • Enforce World Creation Flows: Restricts worldgen-related screens to the world creation process only.
  • Manage HUD Rendering: Ensures HUD overlays do not obstruct other GUI elements like inventories.
  • Debug Gating: Provides controlled access for developer-only auto-opening features.

Quick Start

Ensure that no Latitude configuration screens automatically open when a player joins a world.

Frequently Asked Questions about latitude-ui-and-hud-lifecycle

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

FAQPage Schema
How do I stop Minecraft mod config screens from automatically opening when joining a world?

To stop Minecraft mod config screens from automatically opening, enforce UI lifecycle rules that prevent configuration or worldgen screens from appearing unexpectedly after a player joins a world.

How does HUD rendering lifecycle management work for Minecraft mods?

HUD rendering lifecycle management works by codifying overlay display logic to prevent conflicts, ensuring HUD overlays do not obstruct other GUI elements like inventories during gameplay.

How to restrict worldgen screens to only appear during world creation in Minecraft?

To restrict worldgen screens to the world creation process, enforce UI lifecycle gates that confine world creation specific screens to that flow and block their appearance elsewhere.

Can I keep developer debug screen auto-opening features without affecting normal players?

Yes, you can maintain developer debug access by applying debug gating, which provides controlled auto-opening screen features exclusively for developers while restricting them for normal users.

Why does my Minecraft mod HUD overlay conflict with inventory GUI elements?

Your HUD overlay conflicts with inventory GUI elements because the rendering lifecycle lacks codified display logic, causing unmanaged overlays to obstruct other active GUI elements.

Does Latitude UI lifecycle management prevent all automatic screen openings?

No, Latitude UI lifecycle management prevents unintended automatic screen openings in-world but still allows controlled developer debug access through specific gating rules.