Skip to content

Initial NeoForge port#321

Open
Influenze0 wants to merge 3 commits into
MCRcortex:devfrom
Influenze0:mc/neoforge-1.21.x
Open

Initial NeoForge port#321
Influenze0 wants to merge 3 commits into
MCRcortex:devfrom
Influenze0:mc/neoforge-1.21.x

Conversation

@Influenze0
Copy link
Copy Markdown

No description provided.

@KarmaMarazu
Copy link
Copy Markdown
Collaborator

please stop spamming with new pull requests

@theoparis
Copy link
Copy Markdown

theoparis commented Dec 10, 2025

I don't see how this is spam - I'd like to see a neoforge port as well. However I do think this would have to be placed in a separate fork since this PR has so many changes that would break the fabric version.

@Skillnoob
Copy link
Copy Markdown

@theoparis they opened and closed multiple pull requests before this one.

@lgbtaye777
Copy link
Copy Markdown

Tested on MC 1.21.1 / NeoForge 21.1.219 / Sodium 0.6.0+mc1.21.1, GPU RTX 4070.

The mod is discovered and initialized correctly (no crash, backend active), but:

  • No NeoForge config spec is registered (no ModConfig / no file created in .minecraft/config after multiple launches)
  • No config screen factory is registered (Mod Menu shows no config)
  • No Sodium options page/tab is registered in the Video Settings UI (nothing appears in the Sodium sidebar)

I checked the NeoForge port code and could not find:

  • a call to ModLoadingContext.registerConfig(...)
  • a config screen factory / screen registration
  • any Sodium options page registration for Sodium 0.6.x

The port shows correct basic viability: when Sodium is replaced with Embeddium, the game fails early during mod loading with a clear dependency error (requires sodium >= 0.6.0), indicating that dependency/version checks are functioning as expected.

Is the lack of config/UI expected for this port at the moment, or is this part still pending?

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.

5 participants