fabric-loader VS Gradle

Btw what you could've done to find a Fabric Loader version by date is just scroll the GitHub releases. I imagine you would've had the date of when you created the pack from the dates of the mod files.

I'm not too familiar with the fabric system and I was hoping someone could help me with modifying the fabric loader, mod loading in specific. I am trying to let the loader get mods from multiple directories, rather than just the /mods directory. I have modified and built a jar from this link https://github.com/FabricMC/fabric-loader

Go look at the GitHub if you want

Request for this feature was rejected by Fabric team in 2020. (https://github.com/FabricMC/fabric-loader/issues/181)

I wrote a bug report, and at the end included my lengthy solution to the problem. https://github.com/FabricMC/fabric-loader/issues/647

How about a git commit? https://github.com/FabricMC/fabric-loader/commit/7f8086f2bfe8e8f75c9a319ccd7f2be40be1265e

FabricLoader.getAllMods().

Since Fabric Loader 0.11.0, added with this commit: https://github.com/FabricMC/fabric-loader/commit/5cd3b1b1bd3f12525bc5245a6edaeb657c146ebe

A ("shared") build service is kind of like a singleton, in that when you register one in any project, it's available in all projects as a single instance. (This unfortunately turns out not to be true, in some cases, when using composite builds, but can be worked around.) An actual singleton (global static instance) doesn't work at all, for the record—try it if you want to lose some sanity. Anyway, use a build service whenever you need global mutable state in your build.

When using build tools like Maven or Gradle, you can configure environment variables in the build scripts or configuration files.

For large projects, purpose-made build tools such as Gradle and Maven are preferred for managing the directory structure since they introduce additional semantics for managing test code and other programming languages (among lots of other things). Most IDEs can integrate with these build tools easily. If you're just starting out though, I wouldn't worry too much about these, you can visit them later.

Project Build and Management: Apache Maven 3 (3.9.5), Gradle 8 (8.3)

No wonder this had been raised previously, https://github.com/gradle/gradle/issues/15383

Ktor, a powerful web framework built with Kotlin, offers a lightweight and flexible solution for building web applications. In this article, we will guide you through the process of creating a Ktor project manually using Gradle and SDKMAN!. By following the steps below, you'll have a basic Ktor project up and running in no time.

The details regarding the code compiling would vary from one project to another. For that project, it seems that it uses Gradle (a helper tool) for compiling. Check Gradle's documentation for more information.

At the moment, Java 20 is the latest version, but Java 17 is the latest LTS release. It's usually best to use an LTS release, because the latest releases won't be widely supported. And that's true of Gradle too. You're using Gradle 8.0, but not even the latest version of Gradle (8.2) fully supports Java 20. You'll have to wait for Gradle 8.3 to use Java 20.