Modder Name Lib is my personal library of code shared between all Season 2 projects.
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 Fabric and NeoForge. 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 and abstractions over the differences between modloaders,
- a custom system for registering content and datagenning stuff at the same time,
- an error-reporting system,
- a configuration library, usable through both fabric and neoforge, with a custom config format on Fabric
And it will grow to contain anything else I need.
what is "Season 2"
All Season 2 mods are developed and tested together, in the same Git repo, 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. This factors combined caused me to burn out of Minecraft modding.
During Season 2 (2025-?), I aim to address these problems with new development tooling.
One such tool is this library, which holds all the duplicated code and helps me hit the ground running when I choose to port to a new version of Minecraft.
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.
All Versions
+ Add Version| Name | Game version | Platforms | Published | Downloads | Actions |
|---|---|---|---|---|---|
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 2mo ago | 1 | ||||
| 3mo ago | 1 | ||||
| 3mo ago | 1 | ||||
| 3mo ago | 1 | ||||
| 3mo ago | 1 | ||||
| 3mo ago | 1 | ||||
| 3mo ago | 1 | ||||
| 3mo ago | 1 | ||||
| 3mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| 10mo ago | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 | ||||
| last yr. | 1 |
- (Fabric) Tone down the amount of config-file-related log spam at startup.
- Now supports 26.1.2.
- (Fabric) Tone down the amount of config-file-related log spam at startup.
- Now supports 26.1.2.
- (Fabric) Tone down the amount of config-file-related log spam at startup.
- Now supports 26.1.2.
- (Fabric) Tone down the amount of config-file-related log spam at startup.
- Now supports 26.1.2.
- (Fabric) Tone down the amount of config-file-related log spam at startup.
- Now supports 26.1.2.
- (Fabric) Tone down the amount of config-file-related log spam at startup.
- Now supports 26.1.2.
- (Fabric) Tone down the amount of config-file-related log spam at startup.
- Now supports 26.1.2.
- (Fabric) Tone down the amount of config-file-related log spam at startup.
- Now supports 26.1.2.
I rewrote the ENTIRE build system; all of my mods are now built with a new build pipeline that's faster and clearer than before. Kinda proud of it but I also want to push out a build to make extra sure nothing has broken in the meantime.
- Compile with new tooling.
- Push down blockentity renderer utils (preparation for 26.1; it finally stopped being crossroadable)
- (All Forge and Neoforge versions) Cut down on startup logspam.
I rewrote the ENTIRE build system; all of my mods are now built with a new build pipeline that's faster and clearer than before. Kinda proud of it but I also want to push out a build to make extra sure nothing has broken in the meantime.
- Compile with new tooling.
- Push down blockentity renderer utils (preparation for 26.1; it finally stopped being crossroadable)
- (All Forge and Neoforge versions) Cut down on startup logspam.
I rewrote the ENTIRE build system; all of my mods are now built with a new build pipeline that's faster and clearer than before. Kinda proud of it but I also want to push out a build to make extra sure nothing has broken in the meantime.
- Compile with new tooling.
- Push down blockentity renderer utils (preparation for 26.1; it finally stopped being crossroadable)
- (All Forge and Neoforge versions) Cut down on startup logspam.
I rewrote the ENTIRE build system; all of my mods are now built with a new build pipeline that's faster and clearer than before. Kinda proud of it but I also want to push out a build to make extra sure nothing has broken in the meantime.
- Compile with new tooling.
- Push down blockentity renderer utils (preparation for 26.1; it finally stopped being crossroadable)
- (All Forge and Neoforge versions) Cut down on startup logspam.
I rewrote the ENTIRE build system; all of my mods are now built with a new build pipeline that's faster and clearer than before. Kinda proud of it but I also want to push out a build to make extra sure nothing has broken in the meantime.
- Compile with new tooling.
- Push down blockentity renderer utils (preparation for 26.1; it finally stopped being crossroadable)
- (All Forge and Neoforge versions) Cut down on startup logspam.
I rewrote the ENTIRE build system; all of my mods are now built with a new build pipeline that's faster and clearer than before. Kinda proud of it but I also want to push out a build to make extra sure nothing has broken in the meantime.
- Compile with new tooling.
- Push down blockentity renderer utils (preparation for 26.1; it finally stopped being crossroadable)
- (All Forge and Neoforge versions) Cut down on startup logspam.
No changes; just uploading because a version of ModderNameLib with this version exists in Packages 1.21.1, which *did* get a release today, and I want you to be able to find it standalone if you need it. (The woes of date-based versioning.)
No changes; just uploading because a version of ModderNameLib with this version exists in Packages 1.21.1, which *did* get a release today, and I want you to be able to find it standalone if you need it. (The woes of date-based versioning.)
- Drop 1.21.5 support.
- Always datagen to version-specific folders by default.
- Drop 1.21.5 support.
- Always datagen to version-specific folders by default.
- Drop 1.21.5 support.
- Always datagen to version-specific folders by default.
- Drop 1.21.5 support.
- Always datagen to version-specific folders by default.
- Drop 1.21.5 support.
- Always datagen to version-specific folders by default.
- Drop 1.21.5 support.
- Always datagen to version-specific folders by default.
- Update tooling.
- New version of Loom means Fabric mods no longer ship with a separate refmap file. This is a big change, so please report mixin apply failures.
- Now supports 1.21.11.
- Remove usages of
RenderTypeto account for changes in 1.21.11. - (1.21.1 Neoforge, 1.21.5 Neoforge) Correct a cut-paste typo in an error message.
- Large refactor of the datagen/registry system.
- Add a DyeColor and color-handling utility.
- (1.20.1) Add a BlockColor/ItemColor utility.
- (1.21.5) Fix client utilities.
- Update tooling.
- New version of Loom means Fabric mods no longer ship with a separate refmap file. This is a big change, so please report mixin apply failures.
- Now supports 1.21.11.
- Remove usages of
RenderTypeto account for changes in 1.21.11. - (1.21.1 Neoforge, 1.21.5 Neoforge) Correct a cut-paste typo in an error message.
- Large refactor of the datagen/registry system.
- Add a DyeColor and color-handling utility.
- (1.20.1) Add a BlockColor/ItemColor utility.
- (1.21.5) Fix client utilities.
- Update tooling.
- New version of Loom means Fabric mods no longer ship with a separate refmap file. This is a big change, so please report mixin apply failures.
- Now supports 1.21.11.
- Remove usages of
RenderTypeto account for changes in 1.21.11. - (1.21.1 Neoforge, 1.21.5 Neoforge) Correct a cut-paste typo in an error message.
- Large refactor of the datagen/registry system.
- Add a DyeColor and color-handling utility.
- (1.20.1) Add a BlockColor/ItemColor utility.
- (1.21.5) Fix client utilities.
- Update tooling.
- New version of Loom means Fabric mods no longer ship with a separate refmap file. This is a big change, so please report mixin apply failures.
- Now supports 1.21.11.
- Remove usages of
RenderTypeto account for changes in 1.21.11. - (1.21.1 Neoforge, 1.21.5 Neoforge) Correct a cut-paste typo in an error message.
- Large refactor of the datagen/registry system.
- Add a DyeColor and color-handling utility.
- (1.20.1) Add a BlockColor/ItemColor utility.
- (1.21.5) Fix client utilities.
- Update tooling.
- New version of Loom means Fabric mods no longer ship with a separate refmap file. This is a big change, so please report mixin apply failures.
- Now supports 1.21.11.
- Remove usages of
RenderTypeto account for changes in 1.21.11. - (1.21.1 Neoforge, 1.21.5 Neoforge) Correct a cut-paste typo in an error message.
- Large refactor of the datagen/registry system.
- Add a DyeColor and color-handling utility.
- (1.20.1) Add a BlockColor/ItemColor utility.
- (1.21.5) Fix client utilities.
- Update tooling.
- New version of Loom means Fabric mods no longer ship with a separate refmap file. This is a big change, so please report mixin apply failures.
- Now supports 1.21.11.
- Remove usages of
RenderTypeto account for changes in 1.21.11. - (1.21.1 Neoforge, 1.21.5 Neoforge) Correct a cut-paste typo in an error message.
- Large refactor of the datagen/registry system.
- Add a DyeColor and color-handling utility.
- (1.20.1) Add a BlockColor/ItemColor utility.
- (1.21.5) Fix client utilities.
- Update tooling.
- New version of Loom means Fabric mods no longer ship with a separate refmap file. This is a big change, so please report mixin apply failures.
- Now supports 1.21.11.
- Remove usages of
RenderTypeto account for changes in 1.21.11. - (1.21.1 Neoforge, 1.21.5 Neoforge) Correct a cut-paste typo in an error message.
- Large refactor of the datagen/registry system.
- Add a DyeColor and color-handling utility.
- (1.20.1) Add a BlockColor/ItemColor utility.
- (1.21.5) Fix client utilities.
- Update tooling.
- New version of Loom means Fabric mods no longer ship with a separate refmap file. This is a big change, so please report mixin apply failures.
- Now supports 1.21.11.
- Remove usages of
RenderTypeto account for changes in 1.21.11. - (1.21.1 Neoforge, 1.21.5 Neoforge) Correct a cut-paste typo in an error message.
- Large refactor of the datagen/registry system.
- Add a DyeColor and color-handling utility.
- (1.20.1) Add a BlockColor/ItemColor utility.
- (1.21.5) Fix client utilities.