Add the ability to install and run a production client and server as well as moddev for testing FML.

[shartte]

This adds the ability to:

• Run :test:installNeoForgeServer to install a local copy of the NeoForge server into build/installs/server using the installers silent-install feature. This also produces several JVM argfiles that capture the required startup parameters to start it.
• Run :test:installNeoForgeClient to install a local copy of the NeoForge client into build/installs/client using the installers silent-install feature. This also produces several JVM argfiles that capture the required startup parameters to start it.
• Run :test:runProductionClient to start a NeoForge client from the local install using the current projects FML components.
• Run :test:runProductionServer to start a NeoForge server from the local install using the current projects FML components.
• Run :test:runClient to start a moddev client, using the local FML
• Run :test:runServer to start a moddev server, using the local FML

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: 53633e05ba7a958ce879ed5c46f2490cbd929d0d.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged.fancymodloader:junit-fml:4.0.29-pr-177-runs
• 📦 net.neoforged.fancymodloader:tests:4.0.29-pr-177-runs
• 📦 net.neoforged.fancymodloader:earlydisplay:4.0.29-pr-177-runs
• 📦 net.neoforged.fancymodloader:loader:4.0.29-pr-177-runs

Repository Declaration

In order to use the artifacts published by the PR, add the following repository to your buildscript:

repositories {
    maven {
        name 'Maven for PR #177' // https://github.com/neoforged/FancyModLoader/pull/177
        url 'https://prmaven.neoforged.net/FancyModLoader/pr177'
        content {
            includeModule('net.neoforged.fancymodloader', 'junit-fml')
            includeModule('net.neoforged.fancymodloader', 'tests')
            includeModule('net.neoforged.fancymodloader', 'earlydisplay')
            includeModule('net.neoforged.fancymodloader', 'loader')
        }
    }
}

[marchermans]

What is the usecase for this?

You can just includeBuild FML in NeoForge and you get the same result. Is this for production jars or what?

[covers1624]

I am not comfortable with FML having infrastructure to 'install' NeoForge, even for tests. What does this even help with? What is the expected use case of this?

[marchermans]

I can understand why this is needed.
But I don't think that using NFRT for just the asset download is a great idea.

I would really welcome it if we created an asset download library or something. I have been struggling with this in NG as well, and would welcome it for sure.

Alternatively I think that it should be build in into the installer if that is not wanted, potentially via installer utils.

Does that make sense?

[Matyrobbrt]

But I don't think that using NFRT for just the asset download is a great idea.

Why is that?

NFRT is the NeoForm Runtime, it's as close as you get to an asset downloading library.

[shartte]

But I don't think that using NFRT for just the asset download is a great idea.

NFRT is the asset download library :-P

It's far more involved than just downloading some files. It interacts with the launcher installation detection, which itself is needed to speed up generating the desired asset state without re-downloading them for every tool individually. I think as a tool that aims to produce usable assets (both jar and art) for development, NFRT is just the right place for it.

You can also just invoke NFRT from NG exclusively for asset downloads if you want to benefit from the launcher install detection and asset reuse.

Removed request for changes.

[neoforged-releases]

🚀 This PR has been released as FancyModLoader version 4.0.25.