[Question] In a multi-module project, how can I use classes from other modules in the startup module?

[lingting]

I tried to use it directly. The IDE did not report an error, but ClassNotFound was reported during runtime.

I tried to use additionalRuntimeClasspath, but the IDE reported an error Unresolved reference 'additionalRuntimeClasspath'. and could not compile

[lingting]

use additionalRuntimeClasspathConfiguration:
` runs {

    create("client") {
        client()
        systemProperty("neoforge.enabledGameTestNamespaces", modId)
        additionalRuntimeClasspathConfiguration.withDependencies {
            add(project.dependencies.project(":launch:launch-core"))
        }
    }

    create("server") {
        server()
        systemProperty("neoforge.enabledGameTestNamespaces", modId)
    }

    mods {
        create(modId) {
            sourceSet(sourceSets.main.get())
        }
    }


}`

[Technici4n]

It would be better to use your original snippet, it's just that additionalRuntimeClasspath is only accessible after the neoForge.version = ... call. If you were to move that call up the dependency configuration would be available in the dependencies block.

[lingting]

It would be better to use your original snippet, it's just that additionalRuntimeClasspath is only accessible after the neoForge.version = ... call. If you were to move that call up the dependency configuration would be available in the dependencies block.最好使用您的原始代码片段，只是 additionalRuntimeClasspath 只有在 neoForge.version = ... 调用后才能访问。如果您要向上移动该调用，则依赖项配置将在依赖项块中可用。

This is the configuration I'm using now, is there anything wrong with it?

val modId = project.properties["mod.id"] as String

plugins {
    alias(libs.plugins.neoforged.modedev)
}

dependencies {
    api(project(":launch:launch-core")) {
        exclude("org.slf4j")
    }
}

tasks.named { "classes" == it }.forEach {
    it.dependsOn("processAssets")
}

fun wrapperNeoForgeRuntime(configuration: Configuration) {
    val dependencies = listOf(
        project.dependencies.project(":launch:launch-core")
    )


    configuration.withDependencies {
        dependencies.forEach { add(it) }
    }
}

neoForge {
    version = project.properties["minecraft.neoforged.version"] as String

    parchment {
        mappingsVersion = project.properties["minecraft.mappings.version"] as String
        minecraftVersion = project.properties["minecraft.version"] as String
    }

    runs {

        create("client") {
            client()
            systemProperty("neoforge.enabledGameTestNamespaces", modId)
            wrapperNeoForgeRuntime(additionalRuntimeClasspathConfiguration)
        }

        create("server") {
            server()
            systemProperty("neoforge.enabledGameTestNamespaces", modId)
            wrapperNeoForgeRuntime(additionalRuntimeClasspathConfiguration)
        }

        mods {
            create(modId) {
                sourceSet(sourceSets.main.get())
            }
        }


    }

    ideSyncTask(tasks.named("processLaunchResources"))

}

[Technici4n]

Yes, withDependencies is generally not great, and iterating over all dependencies will potentially cause problems.

I would recommend sth like this:

val modId = project.properties["mod.id"] as String

plugins {
    alias(libs.plugins.neoforged.modedev)
}

neoForge {
    version = project.properties["minecraft.neoforged.version"] as String
}

dependencies {
    "additionalRuntimeClasspath"(api(project(":launch:launch-core")) {
        exclude("org.slf4j")
    })
}

tasks.named { "classes" == it }.forEach {
    it.dependsOn("processAssets")
}

neoForge {
    parchment {
        mappingsVersion = project.properties["minecraft.mappings.version"] as String
        minecraftVersion = project.properties["minecraft.version"] as String
    }

    runs {

        create("client") {
            client()
            systemProperty("neoforge.enabledGameTestNamespaces", modId)
        }

        create("server") {
            server()
            systemProperty("neoforge.enabledGameTestNamespaces", modId)
        }

        mods {
            create(modId) {
                sourceSet(sourceSets.main.get())
            }
        }


    }

    ideSyncTask(tasks.named("processLaunchResources"))

}

[lingting]

@Technici4n Thanks for your suggestion, I have modified my configuration

[MattSturgeon]

As additionalRuntimeClasspath is no longer created when the MC version is 1.21.9+ and dependency/extendsFrom have also been removed from neoForge.mods, how should we now configure multi-module project run configs?

If I'm interpreting docs correctly, it seems like I should use ModModel.sourceSet(). However, Gradle does not like cross-project sourceSet references (and they don't work at all when 'configure on demand' is enabled).

---

For example:

neoForge {
    mods.named("modid") {
        // With 'configure on demand' this throws, because the config project is not evaluated yet.
        // We should not be directly referencing other projects' source sets anyway...
        sourceSet(project(":config").sourceSets.main.get())
    }
}

dependencies {
    // In 1.21.9+ we cannot use `additionalRuntimeClasspath` anymore
    "additionalRuntimeClasspath"(api(bundle(project(":config"))!!)!!)
}

---

EDIT: I ended up working around the limitation by creating a source set to stage the dependencies.

In my case, internal dependencies are all added to a bundle configuration, so I used that:

neoForge {
    mods {
        register("modid") {
            sourceSet(sourceSets.main.get())

            // Mark internal dependencies as part of the mod, so their classes are loaded in dev runs.
            sourceSet(sourceSets.create("bundled") {
                output.dir(configurations.bundle)
            })
        }
    }
}