Modder Name Lib

**Modder Name Lib** is my personal library of code shared between all *Season 2* projects. Code that benefits from only *one* copy of it existing, rather than one copy per-mod; and code that I'm tired of cut-and-pasting between mods. **You probably do not need to install Modder Name Lib separately.** Modder Name Lib is included in all mods that use it using the "jar-in-jar" systems in (https://wiki.fabricmc.net/documentation:fabric_loader#nested_jars) and (https://docs.neoforged.net/neogradle/docs/dependencies/jarinjar/). If you choose to manually install it, the version you select will (probably) be used instead of the bundled versions. At the moment, it contains: * basic mod scaffolding, * a custom system for registering content and datagenning stuff at the same time, * abstractions over the differences between modloaders, * an error-reporting system, * a configuration library, usable through both fabric and neoforge. As *Season 2* expands in scope, it will grow to contain anything else I need. ## what is *"Season 2"* This is part of the *quat's mods "Season 2"* project. All *Season 2* mods are developed and tested together, in (https://github.com/quat1024/mods), compiled from the same codebase. > During *Season 1* (2018-2025), I developed all my mods separately. This made it difficult to start new projects, annoying to port projects between Minecraft versions, error-prone to maintain code shared between multiple projects, and switching between projects sometimes required long waiting periods as the development tooling got its act together. These factors combined caused me to burn out of Minecraft modding. > > During *Season 2* (2025-?), I aim to address these problems with (https://notes.highlysuspect.agency/project-sanity.html). ## what's in a name? A *moddernamelib* is a derisive term for "library mods only intended to be used by one modder." I have become the thing I sought to destroy.