[Feature] NeoForge Support

[Neoteric-Dev]

Pre-Request Checklist

• I have checked that I am on the latest version of Terra.
• I have searched github for similar features requests, including closed
  ones, and found none.
• I believe this is within the scope of Terra.
• This feature request is for all of Terra, and isn't something that
  should be implemented by a pack or addon.

Feature Description

Add support for newer NeoForge versions (1.21+)

What Problem Does This Solve?

Forge support of Terra has not been updated in 2 years

A Solution You'd Like

NeoForge versions for 1.21+ available on Modrinth

Alternative Solutions

1. Continue developing in Fabric and reject this request
2. Pregen entire world in Fabric and export world file to NeoForge save
3. Accept monetary contribution to incentivize this development

Additional Context

Please ;)

[solonovamax]

honestly I'm not opposed to dropping forge support and entirely migrating to neo instead

@duplexsystem you were the one who wrote the forge platform originally, and I'm assuming you're primarily maintaining it, what are your thoughts on this?

[ArgentVASIMR]

@solonovamax Neoforge user here, I would also really appreciate seeing Terra on Neoforge, as all of my other mods are on that platform. Given it has a Forge version and primarily focuses on terrain generation without new blocks or mobs, it probably isn't too difficult to port?

[McHearty]

We have done some testing of Terra via Sinytra Connector on NeoForge 1.21.1. While the environment is largely functional in single-player, multiplayer is currently non-viable due to a consistent, fatal java.util.NoSuchElementException during the finish_configuration network packet phase.

The stack trace points directly to RegistryDataLoader.redirect$bop000$terra$grabManager. This suggests that the Connector’s registry shim is unable to provide the expected manager to Terra's mixins during the finalization of a remote handshake.

We should note that the repository’s architecture is currently unclear to track regarding branching and tags; it is difficult to determine if there is any active movement toward a native platform implementation. Given that a native port is the only long-term solution to these protocol-level translation failures, have there been any internal decisions or priority shifts regarding a native 1.21.1 NeoForge implementation?