promotional bannermobile promotional banner

Lazy Utilities [Deprecated]

My little Toolbox for my mods

File Details

lazy_utilities-3.3+1.21.1-NeoForge.jar

  • R
  • Mar 12, 2026
  • 866.21 KB
  • 1.9K
  • 1.21.1
  • NeoForge

File Name

lazy_utilities-3.3+1.21.1-NeoForge.jar

Supported Versions

  • 1.21.1

Curse Maven Snippet

NeoForge

implementation "curse.maven:lazy-utilities-1196825:7748496"
Curse Maven does not yet support mods that have disabled 3rd party sharing

Learn more about Curse Maven

Additions

A new module, "LZM: Runner," has been added. Its function is to allow me to access dependent .jar files (mods) during an early stage of execution.

LZM: Runner – Dependency Package System

A new dependency loading system has been introduced. This system allows LZM: Runner to automatically read structured JSON (or any other file really) “packages” provided by other mods that declare a dependency on it.

In practice, this means that dependent mods can now include additional content such as compatibility modules, passive abilities, skill books, innate abilities, or other data-driven features through JSON files packaged directly inside their .jar.

 

How it works

The dependency system is intentionally simple:

  1. Your mod must declare a dependency on lzm_runner in its META-INF mod descriptor.

  2. During startup, LZM: Runner scans the loaded mod list and identifies all mods that depend on it.

  3. If a dependent mod contains a folder following this structure:

/lzm_runner/<your_mod_id>/

the system will automatically detect and read the files inside that directory.

Once detected, the files inside this folder become accessible to LZM: Runner during initialization and can be processed as data-driven extensions.

 

Minimal requirements

For a packaged archive to be recognized as a mod and scanned by the system, it must contain a valid META-INF descriptor including at least:

modLoader="lowcodefml"

This ensures that the .jar or .zip archive is treated as a valid mod by the loader.