Maybe make it toggleable, but I think it should be enabled by default.

Caching the last known version and using said cached version when no network is present would be a "good enough" solution.

Not all mod names are valid for Maven publishing, but all mod IDs are. For instance "World Host" is invalid (because it has a space), while "world-host" is valid. Additionally, I prefer my JARs to use the mod ID rather than the mod name.

Idk what you exactly want

As Weave mod loader is growing slowly bigger and bigger it would be natural for dgt to support it

pack200 not here 😭😭😭😭😭
this fix black magic

loom {
    forge {
        pack200Provider.set(dev.architectury.pack200.java.Pack200Adapter())
    }
}

monke strong together

Self explanatory

The output of the sourcesJar task is used. However, this output is renamed to be -dev by Loom, and remapSources is set up to output to the original location.

Post-compilation, while using a .jar file compiled with this Gradle toolkit, issues arise with IChatComponent. Minecraft's chat GUI does not render.

Currently if you have a resource with preprocessing, it will try to expand the properties in the file before running preprocessor, causing the build to fail because property expansion doesn't like the dollar signs.

$java_version yields JAVA_16 on 1.18+ because Java 16 code is compatible with Java 17, as can be seen here: