Move config screen event registration to an event

[Technici4n]

So that we can deprecate the FML extension point system for removal.

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: 81b94a655b77ea274a7131a3ec12ebd5e053d518.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged:neoforge:20.4.126-beta-pr-560-config-screen-event

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 #560' // https://github.com/neoforged/NeoForge/pull/560
        url 'https://prmaven.neoforged.net/NeoForge/pr560'
        content {
            includeModule('net.neoforged', 'neoforge')
        }
    }
}

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-pr560.
On Powershell you will need to remove the -L flag from the curl invocation.

mkdir NeoForge-pr560
cd NeoForge-pr560
curl -L https://prmaven.neoforged.net/NeoForge/pr560/net/neoforged/neoforge/20.4.126-beta-pr-560-config-screen-event/mdk-pr560.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.

[dima-dencep]

I think it's better to register and load configs immediately when they are created or when something tries to get some value

[Technici4n]

Alternative: simplify extension point API: neoforged/FancyModLoader#80.