Skip to content

main source set always displays as NeoForge with ModDevGradle #2586

@Swedz

Description

@Swedz

Minecraft Development for IntelliJ plugin version

2025.3-1.8.11

IntelliJ version

2025.3.2

Operating System

Pop! OS 24.04

Target platform

NeoForge

Description of the bug

Using ModDevGradle, I have NeoForge configured so that only the neoforge source set has access to the NeoForge and Minecraft sources. main does not have this access. Below is a minimal example of what I am using:

neoForge {
	enable {
		version = neoforge_version
		enabledSourceSets = [sourceSets.neoforge]
	}

	mods {
		"${mod_id}" {
			sourceSet sourceSets.neoforge
		}
	}
	
	runs {
		configureEach {
			sourceSet = project.sourceSets.neoforge
		}
	}
}

However, the Minecraft Development plugin still displays the main source set as a NeoForge source set. This persists after restarting IntelliJ as well as invalidating caches. As far as I am aware this does not cause any tangible problems, it is only a visual bug. See below:

Image

NeoForge 21.11.38-beta
ModDevGradle 2.0.140

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions