Skip to content

feat: NeoForge artifact#24

Open
obus-globus wants to merge 2 commits into
CCBlueX:26.1from
obus-globus:neoforge-26.1
Open

feat: NeoForge artifact#24
obus-globus wants to merge 2 commits into
CCBlueX:26.1from
obus-globus:neoforge-26.1

Conversation

@obus-globus

@obus-globus obus-globus commented Jun 10, 2026

Copy link
Copy Markdown

Adds a neoforge/ module that builds and publishes net.ccbluex:mcef-neoforge from the same sources as the Fabric artifact (same code, same java-cef sources, same resources; the only new class is an empty @Mod("mcef") entry point). Companion change for the LiquidBounce NeoForge port (CCBlueX/LiquidBounce#8480), which nests this artifact the way its Fabric jar nests mcef.

The Fabric build and artifact are untouched, and the existing workflows pick the module up as-is: ./gradlew build/publish match the module's tasks, and CI already runs on JDK 25, which NeoForge 26.1 requires (the Fabric artifact stays on Java 21). In case NeoForge lags behind after a Minecraft update, the module disables its own tasks with a warning while the NeoForge version does not match minecraft_version: Fabric is the more important target, and its build and push-triggered snapshot publishing are never blocked by NeoForge.

Tested: artifact class listing is identical to the Fabric artifact plus the entry class; consumed by the LiquidBounce NeoForge dev client (browser boots, JCEF renders); both workflows ran locally with act (build green, publish reaches the upload).

Builds mcef-neoforge from the same sources via ModDevGradle. Publish
with: ./gradlew :neoforge:publishToMavenLocal -Pmod_version=<version>
Disable the module's tasks while the NeoForge version does not match
the Minecraft version: NeoForge releases lag new Minecraft versions,
and a failing neoforge build would otherwise block the push-triggered
publishing workflow. Pin the bytecode target to Java 25 (required by
NeoForge 26.1; the Fabric artifact stays on 21), declare the version
ranges as processResources inputs, and limit the NeoForged repository
to its own groups.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant