Add Vanilla runs in NeoForge development environment and give each run its own folder

[Technici4n]

Adds client, data and server runs for Vanilla. (In the base subproject). This is mostly useful when porting, to step through Vanilla with a debugger even though NeoForge doesn't compile yet.

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: 8bc5b4c3c363220eb50280e296ea151bb037f50b.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged:neoforge:21.3.42-beta-pr-1697-base-runs
• 📦 net.neoforged:testframework:21.3.42-beta-pr-1697-base-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 #1697' // https://github.com/neoforged/NeoForge/pull/1697
        url 'https://prmaven.neoforged.net/NeoForge/pr1697'
        content {
            includeModule('net.neoforged', 'neoforge')
            includeModule('net.neoforged', 'testframework')
        }
    }
}

MDK installation

In order to setup a MDK using the latest PR version, run the following commands in a terminal.
The script works on both *nix and Windows as long as you have the JDK bin folder on the path.
The script will clone the MDK in a folder named NeoForge-pr1697.
On Powershell you will need to remove the -L flag from the curl invocation.

mkdir NeoForge-pr1697
cd NeoForge-pr1697
curl -L https://prmaven.neoforged.net/NeoForge/pr1697/net/neoforged/neoforge/21.3.42-beta-pr-1697-base-runs/mdk-pr1697.zip -o mdk.zip
jar xf mdk.zip
rm mdk.zip || del mdk.zip

To test a production environment, you can download the installer from here.

[neoforged-releases]

🚀 This PR has been released as NeoForge version 21.3.39-beta.