Introduction

GooberLib was initially made and designed out of pure frustration. Today, the main focus is to be easy to use, yet remain powerful for both users and developers. As an added bonus, it looks really good. GooberLib tries to remain vanilla-like while stretching Minecraft's rendering capabilities to their limits.

Why GooberLib?

No libraries will be named and no fingers will be pointed, because it's no single library's fault, but instead the entire modding ecosystem's. GooberLib is built on ideas and concepts from the longest-standing config libraries, but tries to innovate in both user friendliness and developer freedom.

//TODO: big rant on why everyone else sucks

The Basics

GooberLib provides the basic set of options such as primitives, Strings and lists. GooberLib uses a more novel approach to expressing configurations, using a mix of both builders and special config classes (think MaLiLib). However, builders do not mean that you need to write an ungodly amount of code for a simple config, as GooberLib offers solutions for that.

The Non-Basics

Child Options

Like the average config library, configs are organized into categories and sections (or groups). GooberLib goes a step further with child options, letting you have options that are grouped together or depend on each other, which is visibly indicated.

Our mascot, Kenny, in the background.

Custom Widget Providers

While other libraries' may force you to use a single widget to edit a value of a certain type, GooberLib provides a way to pick which ones you want to use. There is a large amount of widgets that are included, and utilities to help with rendering your own.