EclipseUI
If you have ever opened a mod's configuration screen and winced at a wall of unstyled buttons, you already understand why EclipseUI exists. EclipseUI is a lightweight, themeable config screen library built for Minecraft mods, and it gives developers a clean, modern way to present settings without reinventing the wheel. Whether you are a player curious about the library behind your favorite mods or a developer looking to ship a polished interface, EclipseUI is worth a closer look.
What Is EclipseUI?
EclipseUI is a configuration screen library rather than a gameplay mod. It does not add blocks, mobs, or mechanics. Instead, it provides the building blocks that mod authors use to create attractive, functional config menus. The library ships with two distinct themes: Faithful, which mirrors the classic vanilla look, and Modern, a flat design aesthetic that feels right at home in contemporary modpacks.
The widget set is genuinely rich. Developers can drop in toggles, sliders, dropdowns, color pickers, and text fields without writing custom rendering code from scratch. Every widget is designed to feel consistent, so a settings screen built with EclipseUI looks intentional rather than cobbled together.
Supported Versions and Loaders
EclipseUI supports both Fabric and NeoForge, which covers the two dominant modding platforms in the modern Minecraft ecosystem. This dual-loader approach means a single library can serve a huge portion of the community, and developers do not need to maintain separate UI codebases for each loader. If you are running a recent version of Minecraft with either loader installed, EclipseUI is built to fit into your setup.
Why Players and Developers Care
For players, the benefit is subtle but real. Mods that use EclipseUI tend to have config screens that are easier to navigate, with clear labels and controls that behave the way you expect. For developers, the appeal is more direct: less time fighting with layout code and more time building the features that make a mod worth downloading.
- Two ready-made themes: Faithful and Modern
- Toggles, sliders, dropdowns, color pickers, and text fields out of the box
- ModMenu integration that works without extra configuration
- Fabric and NeoForge support from a single library
- MIT licensed, so it is friendly to almost any project
ModMenu Integration Out of the Box
One detail that stands out is ModMenu integration. ModMenu is the standard way players access mod settings in Fabric environments, and EclipseUI hooks into it without requiring developers to write glue code. That means the moment a mod adopts EclipseUI, its config screen becomes reachable through the familiar ModMenu button. It is a small convenience that makes a noticeable difference in daily play.
How to Install EclipseUI
Installation depends on who you are. If you are a player, you generally do not install EclipseUI directly. Instead, it arrives bundled with whatever mod depends on it. When you download a mod that lists EclipseUI as a dependency, the library comes along for the ride, and you simply drop everything into your mods folder as usual.
If you are a mod developer, the process is a bit more involved but still straightforward. You add EclipseUI as a dependency in your build configuration, pointing to the appropriate Fabric or NeoForge artifact. From there, you follow the usage guide to wire up your config screen. A typical setup defines a title, a parent screen, a theme, and then nests categories containing widgets like toggles and sliders. The API is chainable, so a full config screen can be described in a single readable block of code.
Quick Dependency Setup
Developers add the JitPack repository and then declare either the Fabric or NeoForge implementation, depending on their target platform. Once that is in place, calling the config screen builder gives you a working menu with minimal effort. For those who prefer a guided path, the foxygame.net launcher streamlines this whole process by offering a curated add-on catalog where EclipseUI can be added with a single click, complete with automatic version matching and updates.
Building Your First Config Screen
The quick start flow is intentionally simple. You begin by calling the config screen method, set a title and parent, choose a theme, and then define categories. Inside each category, you attach widgets. A toggle binds to a boolean value, a slider binds to an integer range, and so on. Default values are declared inline, which keeps your configuration logic close to the UI that controls it.
Because the API is fluent, the resulting code reads almost like a description of the screen itself. That readability matters when a mod grows and its settings multiply. Instead of hunting through scattered event handlers, you can see the entire structure in one place.
Final Thoughts
EclipseUI fills a gap that many mods quietly suffer from: inconsistent, unattractive configuration screens. By offering two polished themes, a broad widget set, and support for both Fabric and NeoForge, it gives developers a fast route to interfaces that feel professional. For players, it means the settings menus in their modded worlds become cleaner and easier to use. If you are building a mod and want your config screen to look like it belongs in a modern modpack, EclipseUI is a smart place to start.